NextCloud generally appears to use their own design system everywhere, Android apps are also not in Material or on iOS (iirc) in Cupertino. It makes for a subpar experience in general but is consistent.
NextCloud needs tuning (mostly of php-fpm and caching ) oob to be fast/usable in my experience. Just throwing resources at it won't make it faster as the defaults are generally quite conservative.
As a side note, it's PHP so your single core clocks will generally be more relevant for latency than multi-core performance, feeding many cores requires a lot of divisble work.
At least in germany it feels like you need a very dedicated and persistent person to make the case against a company/service (bonus points if they get media attention). Other countries are a bit better but it generally is not very consistent.
The enforcement for most small to mid-sized companies is often just not present and resources for relevant agencies are often only reluctantly allocated. Ime, in government institutions it is generally not very respected as it "impedes progress".
To be fair this likely should be handled by the interpreter/compiler for the compiled JS. V8 probably can merge this into one loop or another similar based on runtime types
You can iif you live in on of the supported cities that is not currently suspended. Waymo is a promising participant here, but it very much isn't at the "just be driven to work stage" for almost everyone.
>You can iif you live in on of the supported cities that is not currently suspended.
Yes. The claim was that “nobody” is doing this today when in fact tens / hundreds of thousands of people are doing this today. The tech is here, next is widespread adoption.
I'm sometimes amazed by project sizes, a 30k line codebase is small? I'm aware that the ceiling is high but 30k lines of code can encode so much information and behavioural nuance.
Maybe this is just my backend/network focus with Golang though. Scaling beyond 10-15k lines of code always was quite intimidating as it is usually where I lose the ability to just keep a model of the codebase fully in my head.
Many distros deal with the problem of learning about these issues the same time as the public. Some have fast track processes to ensure patches can get into their stable/rolling releases but it is still a lot of work (especially as kernel updates usually mean that automatic updates won't fully shipped you (without alsp automatically rebooting after an update)).
It already has official packaging for Tumbleweed, see https://github.com/mullvad/mullvadvpn-app/issues/2242 for the upstream issue. Leap can use the normal Linux application, you will just have to provide the dependencies yourself.
>The Mullvad VPN app is available in our repository for the following supported Linux distributions:
Ubuntu (24.04+)
Debian (12+)
Fedora (42+)
The only thing I see on the issue you linked is a way to jerry-rig the fedora package. When I tried that I kept getting untrusted key warnings. You can skip them of course, but it kind of undermines any type of trust here
It's a skill issue that they decide to not list open suse as a supported distro on their own help page ?
It's a skill issue that the thread has a bunch of different solutions and none of them are definitive and endorsed by the company I'm paying $5 a month too ?
reply