Those those who wonder how it can make it faster since it's using threads and Python has the GIL, numpy releases the gil while doing computation, so thread can actually use multiple cores if you speed most of your time in numpy world.
For this code we can also easily try the process executor instead of the thread executor - then we avoid the GIL. In this case, it has an approximate 10% performance penalty, probably since we have to serialize data back and forth, can't share memory.
If you use a data structure that supports the buffer protocol (such as a numpy array), you won't even pay a serialization cost.
Python has made a LOT of progress, concurrency wise. Between asyncio, process pools, threads releasing the GIL and shared memory, you can get much perfs with the stdlib alone.
Then of course you have Dask if you need more later.
Almost all devices containing a CPU run an OS. Can none of them, like IOT devices have service based accounts? This would make illegal almost all current consoles as well. I understand your ire at Microsoft but I don’t think massacring huge swathes of the current device ecosystem is proportionate or necessary.
> This would make illegal almost all current consoles as well.
Good! The inability to play a local game by putting in a disc and playing is enormously stupid, possibly even more than with a general purpose computer.
I'm pretty sure you can play games on consoles without creating an account on some service, at least in last gen consoles. Did that change with the current gen?
I'm not taking an absolutist stance on this, I think there's scope for regulation of how accounts can or cannot be used and privacy protection of user data. I just don't think eliminating online accounts is practical.
Just because it doesn't have an obvious minimal modern UI doesn't mean it doesn't do its job. Gotta read I guess .. but then again Nix also in general has a prerequisite of "calm down and read." But then again, so does Linux!
The only thing you need to do to be Nix-competent is not flip the table and blame the tool when you get an error you don't understand. (Same goes for Haskell.) That said, my years of industry experience has shown that that is a rare attribute - doubly so amongst those with experience and therefore egos.
People in this thread act like Nix users are out of touch. Maybe, but I'd rather be out of touch and learning than grumpy that I had to read.
> Make NixOS usable for non-technical users through a settings / package management GUI.
^ emphasis mine. What exactly does a non-techical user have to read to understand whatever's on the screenshot? Forget non-techincal, explain this to a technical person.
Apparently this has something to do with sound? Have you or any nix-person ever seen a sound configuration screen for non-technical users? I mean this one is by no means perfect, but do compare: https://www.techrepublic.com/a/hub/i/r/2016/10/05/a7dba7dd-3...
What? They're nothing alike. One has normal, logical options like selecting sound effects and output devices. The other has useless things like how much the media keys adjust the volume by and whether to entirely disable sound on the system, and is littered with technical jargon like 'undefined' and 'boolean'.
You don't select your output device with your configuration.nix. You use it to configure the underlying OS. So doing this stuff with a GUI? Unheard of in the mainstream. Unnecessary maybe too, but still. Not the same.
You can be "grumpy you had to read" or "grumpy about other being complaining they have to read". You chose that latter and I think it's a good choice :).
> I'm guessing that you actually need to know Nix to be able to use it, which kinda defeats the "usable for non-technical users" goal.
I don't think that's true. Excel is usable by non-technical users. Part of it is due to the GUI, part of it is due to the easy packaging. But you still need to know spreadsheets to use it. This project does the same for Nix.
Unfortunately Nix-Gui hasn't yet achieved it's tagline. Hopefully https://github.com/nix-gui/nix-gui/issues/77 letting users configure a predefined list of options relevant to completing a task will bring us closer to that goal.
The problem is, it's very old, and with Firefox, the good stuff comes with the last versions.
Especially, modern Firefox is wicked fast, while just a few versions before, it was less so. The difference is _staggering_.
I think there is a space for add ons to setup Firefox to be more privacy focused. It's easier to maintain than a fork: compiling on so many targets such a huge software is very hard.
On my phone, I have the newest version of Firefox Fennec and IceCatMobile (ancient and barely supported) - they both launch and function at, as far as I can see, exactly the same speed. Where is this speedup you mention actually found?
While I do use Firefox on mobile, I'm talking about the desktop version, like most people do.
The latest rendering improvements are showing great results, and hardware acceleration on Linux is now on part with Windows, so it's fantastic to use on a modern laptop.
Does Firefox do hardware acceleration for videos yet? It still does it in software by default on Linux as far as I know, unless this has changed recently?
This might worked on solo projects but if you’re working with people, I’d highly recommend enforcing type checking of some sort. People will ignore the IDE error messages.
Then they get caught in code review at least in any team I work.
No way I accept any unnecessary "disable lint" statement in a PR.
Also (of course, since it is default) the CI build system breaks if they commit and push without ignores, so no, trying to slide it past me doesn't work either.
It's not linting, it's typechecking which is slightly different. Linting won't catch type errors. All I'm recommending is to add a typecheck to the CI system so no one sneaks in a broken type (I couldn't recognize a broken type in a PR personally).
Typescript, esbuild and preact are hardly boring, since most JS dev don't even have tried it yet.
React is just starting to become "boring", and I mean that in the JS sense of the world. Because it's lifetime would be considered "modern" and any other language.