Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

WWE 2K Gameplay Sliders | AI v AI V1 Presentation: Preference Match Options: Special: Normal Finisher: Slow #WWE2K26

13,230 Aufrufe • vor 5 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Well that was an adventure. Toad's fuzzy file search boosts first characters, smallest number of groups, and it highlights the best scoring match. So you can locate a file with the bare minimum of keypresses. It's an expensive algorithm as it scores every possible combination of the query characters. For any given path there could be many indices which match, and each of them is scored separately. Still, it was fast enough to search as you type for my largest repository. Alas, it was slow for very large repos. Like Microsoft's Typescript, which has more than 84,000 files. I figured I'd reach the limit of what I could do with Python. So my options were to use something like ripgrep or re-implement the fuzzy searching in a faster language. I didn't want to add the ripgrep dependency, so I built a Rust version (with the help of AI) which eventually yielded a ~14X speedup. Nice. Better. But it could still become painful to type under certain pathological conditions. An inefficient algorithm can always be slow if you add more items. So I scrapped the Rust solution and built an index in Python—so the fuzzy search could throw away most paths that wouldn't match or have low scores. And its faster than the Rust solution was. The only downside is that there is a little additional work upfront (done in the background). I think this will do for a while. Until I get an issue that it is slow with 10million files. Rust is still an option, as is doing the work in parallel. This will be in the next version of Toad. Here I am searching the Typescript repo... #Python

Will McGugan

12,261 Aufrufe • vor 6 Monaten

Friends, I’d like to seriously discuss a suggestion regarding the Galaxy camera. Please read this patiently. As we all know, HDR and the Scene Optimizer cannot be used in Pro mode. No matter how you adjust the parameters in Pro mode, photos taken under strong light conditions cannot activate HDR or the Scene Optimizer, which is a significant issue. So here is the solution we need: Samsung should add more manual customization options in the default Photo mode (where HDR and the Scene Optimizer are supported). Options such as saturation, contrast, sharpness, and HDR intensity should be available directly in the standard shooting interface. This would allow users to freely create their own shooting style and capture stunning photos without losing the benefits of HDR effects and AI-based optimizations. Currently, the industry leader in mobile photography—vivo—already does this. In vivo’s default Photo mode, users can adjust contrast, saturation, sharpness, and more. Many vivo users love this high level of customization because it lets them fine-tune the look of every shot according to their personal preference. Samsung, at the moment, cannot match this. In the default Photo mode, the only adjustable parameter is exposure, which is far too limited. Therefore, I strongly suggest that Samsung follow vivo’s approach and introduce more customizable options in the default Photo mode. Let’s take a look at how vivo implements this—please watch the video. If you want Samsung to add this feature too, please reply with: 1. Let’s make sure Samsung sees this demand and accelerates development of this feature.

Ice Universe

31,311 Aufrufe • vor 9 Monaten