slver

81 ms·

811.
by slver 5y ago
"Note to the 1-bit people" is an odd redirect given Linus is known for his 1-bit opinions.
812.
by slver 5y ago
Rookie mistake. You gotta Math.random() that shit server-side.
813.
by slver 5y ago
The exposure/brightness control is not it either. When you tap on your screen, the camera focuses on the point you tapped. It also adjusts the exposure to the point you tapped. And right next to where you tapped, a simple slider with a
814.
by slver 5y ago
So you don’t just want Linux on the phone. You want basically the desktop Linux ecosystem on the phone. That’s a no go from the start. Even Apple didn’t do that when they made iOS. And the problem we solve with this is so you don’t have to
815.
by slver 5y ago
You've defined your market, it seems, as enthusiast developers who want Linux. But stock Android (without the Google services) is that already. It's FOSS, it uses the Linux kernel, and it comes with the infrastructure to run mobil
816.
by slver 5y ago
There is no three finger manual focus gesture on iPhone. Not sure where he got that from.
817.
by slver 5y ago
The Apple Camera app has no manual focus. It has autofocus, tap to focus and it has focus lock if you tap and hold. How come your “favorite example” isn’t even a real example...
818.
by slver 5y ago
Anyone at all, as long as there are millions of them and they want to actually buy those phones, not just rant about Android and Apple online.
819.
by slver 5y ago
Often it feels like "developer UI" is just "slap some buttons around and hook them to the handlers, call it a day". At least that's how Gimp feels to this day.
820.
by slver 5y ago
It's easy to make a light OS when no one uses it.
821.
by slver 5y ago
What consumer issue is solved here?
822.
by slver 5y ago
Shared libraries would be good if there were better semantics in how they're used. Saying "shared libraries bad" instead of working on fixing those semantics is unfortunate.
823.
by slver 5y ago
I feel like absurdist humor is not appreciated here. Shame :)
824.
by slver 5y ago
We're still people capable of speech and communication, if something is that urgent, we can communicate it to our peers. Changing code under their nose risks breaking bunch of projects. We can also fix this by rather communicating, rig
825.
by slver 5y ago
I'm sorry the conversation tone is changing, I didn't do this intentionally. But there are few things that logically don't connect for me here. Supporting FS using the macOS algorithm doesn't affect 1:1 rendering at all.
826.
by slver 5y ago
Semver was enough for me to resolve very simply a scenario above that was presented as some kind of unsurmountable nightmare. So I think Semver is just fine. It's an example of a simple, well designed abstraction. Having "more bit
827.
by slver 5y ago
> 2x scale displays certainly make East Asian text readable, but rendering 2x and downscaling to 1.5x will do a lot of damage to the legibility. It’s far from ideal. I'm typing this on a MacBook with scaled display and legibility is
828.
by slver 5y ago
Patching the code of 10 projects you don't maintain isn't an example of a "coordination system". It's an example of avoiding having one. In multithreading this would be basically mutable shared state with no coordin
829.
by slver 5y ago
Fractional scaling is mostly needed on High DPI displays. High DPI displays also happens to be the case where you don't need subpixel AA, nor you need native FS rendering. Even for East Asian languages. It's ironic, I think, you s
830.
by slver 5y ago
Is it too late to carve an exception for a site with basically no images, that loads bunch of frameworks?
831.
by slver 5y ago
Your monorepo scenario makes the following unlikely assumptions: 1. A critical security/performance fix has no other recourse than breaking the interface compatibility of a library. Far more common scenario is this can be fixed in the
832.
by slver 5y ago
First, they not only contributed upstream, upstream developers contributed to this patch. I.e. they got help outside GitHub to make this patch possible. Second, if they had decided to fork Git, then they'd have to maintain this fork fo
833.
by slver 5y ago
In theory this matters, because we could load the perfect image size for our element, if only HTML could. But in practice: 1. You wouldn't want to have thousands of slightly different size variations of the same image generated and cac
834.
by slver 5y ago
That sentence is phrased a bit odd, but if you're trying to say media size is even same order of magnitude as JS/CSS size in practice, then... no. Not even close.
835.
by slver 5y ago
You can make sure it's not abused at all if you sign the URL. In terms of performance it's a free feature because once the image is generated, you no longer have to check the signature (you only check it first time to generate).
836.
by slver 5y ago
We have repository systems built for centralized atomic updates, and giant monorepos, like SVN. Question is why are we trying to have Git do this, which was explicitly designed with the exact opposite goal? Is this an attempt to do SVN in G
837.
by slver 5y ago
I'm new to this terminology, but it looks a bit like lazily computing a data stream vs. eagerly computing it, doesn't it? Or am I wrong.
838.
by slver 5y ago
Well, it's nice to see they're rational, indeed.
839.
by slver 5y ago
It's in their mutual interest. Imagine what happens to GIThub if GIT goes out of fashion.
840.
by slver 5y ago
> I think it’s a fair philosophical choice. Fractional scaling is really hard. macOS doesn’t bother, choosing instead to render at an integer scale factor and downsample. Doing something similar on Linux would be hard, for mostly histori

More ›