Huh, this seems like a cool optimization problem that I gotta dig in later.
As sweeping was mentioned, there's an argument to be made that we could/should optimize for:
- longest possible strides, you can pick up speed and minimize used time
- allowing overlapping strides on "intersections", as intersections have more traffic and thus should have more grime and wear.
- back-and-forth sweeping along a stride. Like with grass or mopping a floor, if there's any "evidence" left of the sweeping, it'll be more aesthetically more pleasing.
- finally minimizing extra turning, as turning is slow
If someone has any extra suggestions on what restrictions/optimization targets there should be and the rationale for that, I'd be more than happy to receive them!
After seeing a cool demo of using precomputed blue noise with thresholding to approximate transparency in shaders.
I'm quite interested about using the same technique for colour mixing.
Not sure if this is the same thing but I saw this one[0] a while back which has (spatiotemporal) blue noise applied to transparency, dithering, and various other shenanigans.
Do note that unfortunately any future devices by Sony are just phones by other manufacturers that are just Sony branded. Sony stopped their first party device manufacturing, so your mileage of the hardware might be wildly different in the future.
This is false, recently the details element has gotten support for grouping them: the [name] attribute.
This effectively enforces tab-like semantics where only one of the grouped details elements can be open at a time.
This is a quite recent addition and the modern web is evolving too fast so I wouldn't put it past myself for missing this :)
Yay for progress and for JavaScript free solutions!
No, it's still true. I'm aware of that hack, but unfortunately it doesn't solve the problems with pure HTML and CSS tabs.
Crucially, the `name` attribute does not semantically turn a group of <details> elements into a set of tabs. All it does is introduce the (visual) behavior where opening one <details> element closes the others.
right, i can solve this okay by rendering an image and then putting transparent text over it in order to preserve editability, but it's such a pain in the ass, and i know windows is capable of doing it because it does do it, i'm not looking for a solution, i want to understand a facet of windows font rendering
Not that I can answer for OP but as a personal anecdote; I've never been more productive than writing in Rust, it's a goddamn delight. Every codebase feels like it would've been my own and you can get to speed from 0 to 100 in no time.
Yeah, I’ve been working mainly in rust for the last few years. The compile time checks are so effective that run time bugs are rare. Like you can refactor half the codebase and not run the app for a week, and when you do it just works. I’ve never had that experience in other languages.
I don't understand this phrase. If I'm deciding whether to work for a company, I don't care about the ability to hold management decision-makers to account. I care only about the quality of the decisions. (I would rather an unaccountable decision maker that makes good decisions to an accountable decision maker that makes bad decisions.) Putting myself in the shoes of an owner of a company, I also have the same preference. The only person I can imagine actually preferring this rule is management themselves, as it means they can't be replaced by computers no matter how much worse they are at their jobs than a computer would be.
reply