> TODO: rewrite this entire service
remains.
1,727 karma · joined June 25, 2018
> TODO: rewrite this entire service
remains.
And in the many decades and OS rewrites since, they have long since corrected this mistake... right?
- Each monitor has own grid?
- The VD 'spans' the pair of monitors?
- VDs only on one monitor?
- The monitors form a fixed 'window' into the grid?
- Something else?
It's not unuseable, but it definitely feels like 'js hacking my scrolling' and not a native surface flinging around.
The experience is actually worse with smaller movements, i guess because my brain is more conscious when breaking the 'finger physically moving the text' illusion.
I don't mean to be dismissive - you're working on a really hard problem, and you're clearly approaching it with a mindset of perfection. I'm posting because I know you're probably able to solve this too :)
Edit: as a point of (unfair) comparison, the codemirror Huge File demo works fine: https://codemirror.net/examples/million/ It does suffer from the occasional partial paint when quickly coasting, but I'm not bothered by this at all, it's far less intrusive than dropping frames / stuttering / etc.
On mobile it kinda does. Scrolling diffs on mobile just kinda feels crap.
I have been spoiled by years of engineer hours spent getting scrolling to be 60- or even 120Hz smooth to match my finger, and diffs just.. isn't.
I know this is frustrating to hear, and that this is technically compounded by mobile probably having the lowest device performance to be playing with too, but.. There you go.
That's a very globally-conscious way to refer to the USA!
It runs off a 25cm square solar panel screwed to a wall that only receives direct illumination for 5 hours a day, and is not in any way optimised beyond 'that looks roughly like it's pointing at the sun'.
Works great!
Less pithy, i seem to recall many issue with programs that relied on suid and permission dropping, which would be the 'oldschool' way of firming up the above.
You're not wrong that complexity has been introduced, and I'm not a a fan of snap either, but ultimately sandboxes (esp backwards compatible ones that don't need source level modifications) are complex.
If you want simple and secure, you're probably looking at OpenBSD and pledge.
Vega/VGlite have amazing charting expressivity in their spec language, most other charting libs don't come close. It would be very cool to be able to take advantage of that.
As a Go dev, I'm looking at this article with great interest. I would very much like to apply this approach to Go as well, I think the author has got a very strong design there.
E.G. can you set one screen to 150% and one to 175%? (I think the answer to this is 'technically yes but then everything goes a bit blurry because they do it by rendering at 2x then downscaling')
Proper mixed dpi scaling means stuff will render pixel-perfectly instead of downscaling hacks.
This makes it very difficult for Wayland to evolve in a way that people want, as Gnome is the biggest player by user count.
Flatpak is installed by default and used by their app store, and Firefox is packaged as a deb so you can avoid the snap.
I consider it a deshittified Ubuntu.
How do the big Unicode OSS fonts like Noto, Deja Vu deal with this?
Even so, latency-in-zoom kind of becomes an attribute of the medium and you learn to adapt. How does it feel with the Vision Pro though? The article talks about a really convincing sense of being in the same place with someone - how does latency affect that? (And does it differ based on if you're all physically in Silicon Valley or not?)