675 karma · joined May 2, 2017
Why does it require the most expensive model?
Well, it's exactly what many RISC-V folks are trying to do. There's news about a new high performance RISC-V core on the HN front page right now!
> but it feels like the architectural decisions we are "stuck with" today are inextricably intertwined with their contemporary market conditions and historical happenstance. It feels like all the experimental architectures that lost to x86/ARM (including Intel's own) were simply too much too soon,
I just want to note that ARM64 was a mostly clean break from prior versions of ARM. Basically a clean slate design started in the late 2000s. It's a modern design built with the same hindsight and approximate market conditions available to the designers of RISC-V.
? Like most distros that start you off but nothing but a minimal base, you can choose whether to install DBus or not. Almost everyone using Alpine as a daily driver on their PC probably has DBus installed and enabled.
One thing that surprised me is that KDE's software center gives package update notifications for Alpine packages OOTB, and the GUI Just Works(tm) for installing and upgrading.
> Seems like this stems from https://github.com/openssl/openssl/issues/16660 which contains the full backstory and some more information.
I wouldn't call that the "full backstory", since it is only about a single issue outlined in this proposal. Though she does explain that fact in that GitHub thread too, and also why they're looking into alternatives:
> Given that the OpenSSL 3 migration had an outcome where our contingency plan came into effect, I believe it to be the most prudent course of action to evaluate all possible options before committing to trying the OpenSSL 3 migration again, such an evaluation would be required by the TSC anyway.
> and instead the author chose to write on Twitter and in AlpineLinux GitLab about the frustrations.
Eh, I wouldn't read too much into short twitter vents. As for the Alpine Linux GitLab, well, she's the head of Alpine's security team and a member of the TSC, so coming up with proposals as for what should be investigated w.r.t. security critical packages is one of the things she's supposed to be doing.
Also, green tea is just fine at boiling, if it isn't of poor quality :)
The only cross platform alternative that actually works is OpenCL, but Blender is moving away from OpenCL, mostly because literally every GPU vendor is doing so as well.
More likely, they simply aren't noteworthy targets. If you rely on PGP to secure your emails, those emails will probably end up not actually secured, but you won't notice because your emails aren't valuable anyways and are probably secured by other stuff, like TLS, and Google's server security.
If this Steam Deck thing sells well, they'll probably make another one. If it sells poorly they'll probably keep the software updated and use put discounts on it to clear out stock.
If you need a big stack, you can just ask pthread to give you one.
Kernel overcommit has nothing to do with GNU, but default stack size has a lot to do with which libc you use. Musl has a different default than glibc. Overcommit is mentioned because it is the justification for glibc having a large stack size by default. Musl has defaults that make fewer assumptions about how the system is configured.