I would probably see text quality issues on that setup. It depends on how far away the monitor is. PPI on phone screens tends to be much higher than PPI on laptops which tends to be higher than PPI on monitors, because each is typically used at a different distance.
If you're not using text around 9 pixels tall, as in the article, you're probably going to be okay. On a 27 inch screen at a typical office screen distance, I'd probably want 6k, but 4k is pretty good and 1080p is terrible.
In my experience, it seems to. My astigmatism (or other eye stuff) seems to move different colours different amounts, leading to wider RGB pixels and making things like Cleartype so much worse. So people were enjoying Cleartype and I was hating the obvious colour-changes and fringes that somehow they weren't seeing. I assume some people are lucky enough to have aberrations that actually make cleartype more pleasant.
It's not like the Cleartype tuner actually does what the pages claim - you can go through and use the magnifier to choose the grayscale-only outcomes and still see Windows doing RGB stripe cleartype throughout. People literally have to install third-party tools like MacType or GDI-PlusPlus to get solid font rendering. So blaming users for using it wrong (especially when they're not even on Windows) is odd.
Also, many people can see and are bothered by particular non-rectangular pixel layouts - it doesn't require doing odd things.
I had the same experience (Z Fold 4, screen protector at hinge broke at the five month mark - I replaced it with a third-party one to avoid a long repair period and another such breakage - the screen itself is now faulty at just beyond the two year mark).
If anyone were to buy a modern Samsung folding phone, I'd suggest you make sure you get the two-year coverage for the screen and assume it will break soon after that, so treat it like you're going to buy one every 2-3 years. But remember that warranty repairs sometimes involve sending the phone away for weeks, and Android's phone transfer story is still incomplete. That's merely my experience, of course.
The inhibition of movement via eddy currents works best while the needle is moving fast, so you can still end up with smaller oscillations for a while - the apparent jump-cut to a stationary needle could be hiding that.
It's far easier to just use a compass with a needle brake - manually dampen the oscillation using the brake (and let go to ensure you aren't holding an incorrect reading) and you get a reading quickly.
Would you mind checking again? I haven't found any new comments that note the spliced video and old ones I have replied to as well got removed.
If someone knows a way to unremove comments, this is the link to one:
https://www.youtube.com/watch?v=eiDhbZ8-BZI&lc=UgzCu8FPM4CtR...
The comments on this site (HN) may be what most people are talking about. Youtube comments are too easily censored, so they probably will never manage to stick around.
Your site still says "HOW TO ADD ALMOST EQUAL TO IN HTML? Use an HTML entity, a decimal code, or a hex code."
That is incorrect. As you say, you should just write the character in your HTML and ensure it's served with the correct encoding. If it's just for legacy cases, debugging or such, say so on the site.
Agreed. Updated the HTML section to recommend writing the literal character + UTF-8 by default. Numeric refs/entities are now explicitly framed as legacy / edge-case references.
A simpler way: You can avoid sampling neighbours by clamping the ray-march step so it never moves further than the current cell's boundary (plus a tiny epsilon). That way, you only cross into adjacent cells at the edge and avoid the 8 to maybe 26 extra SDF samples. (This only works if the geometry is entirely contained within each cell.)
> This sort of stuff is actually doable just with just video chat and OBS.
If what each person is hearing is 100-400ms delayed from what each person is producing, how can they possibly mutually react or even get their music in time? If B plays in time with what they hear from C, C hears what B did 200-800ms later - that's far too much and will sound terrible.
Jamming would seem to require incredibly low latency audio just for the rhythm to work between two performers.
I just showed you, with examples. Musicians reacts to musical structure, which can be very loose compared to what engineers think of latency. A 12-bar blues can give lots of free time to improvise without feedback.
Also, the stacked delay is part of their product. My solution just does it for free, but it's the same idea.
> garbage collection, I just link the Boehm GC. Not ideal, but good enough
It's worth noting that on 32-bit, the Boehm GC can have consistent issues [1] [2] [3] that make it worth avoiding for anything long-running. The Mono team implemented their own GC due to this. If a runtime is aiming to be useful on such systems, it may be worth implementing or using a less conservative GC.
If you're not using text around 9 pixels tall, as in the article, you're probably going to be okay. On a 27 inch screen at a typical office screen distance, I'd probably want 6k, but 4k is pretty good and 1080p is terrible.
reply