There is the rule number one of the linux kernel: “We don’t break userspace.” Linux has refused fixes for buggy behavior in the past because of this rule. This would most certainly break userspace.
Also the alt text of the original image states this is fake.
I don’t like stacked windows.
Stuff that needs to run in the background moves to another desktop, like a console window logging output.
When layouting with ECAD I also like to have schematic and layout maximised. So wiki tickets and datasheets need to go somewhere.
It’s easier to handle with a tiling window manager. Sadly at work I’m stuck with windows.
No. The rate limit doesn’t work as they use huge IP Spaces to crawl. Each IP alone is not bad they just use several thousand of them.
Using the API would assume some basic changes. We don’t do that here. If they wanted that, they could run their own instance and would even get notified about changes. No crawling required at all.
Probably because the creator had a blog post that got shared around at a point in time where this exact problem was resonating with users.
It’s not always about being first but about marketing.
It also is an option to ensure everyone has the same dev environment.
There is another Frankfurt. It’s lies on the river Oder. The same word for other.
So there is Frankfurt Main and Frankfurt Other.
It’s possible to stream from jellyfin without an account. Jellyfin should not be connected to untrusted networks, like the internet. Several API just don’t check the key or don’t require one in the first place.
What should I call it, when there isn’t anything GNU installed? Uutils? Llvm?
Here is some more context. Are they biased? Probably in some shape or form.
I don’t think the aur can switch the delivered script whether you are piping it into sh or not.
Yes, writing safe code is a skill. But for most skills you need someone to teach you. My suggestion is, think about it differently:
The compiler isn’t training wheels, but rather a senior dev, that quickly looks over your shoulder and tells you, hey you might have missed something here. You can at any point tell them, trust me bro for this part. They need at some points a comment in the form of lifetime annotations. They are pretty good, but not perfect.
To pick up your example. They don’t tell you, you need a new wheel. They tell you, you’re bike has disc brakes, but your new wheel is missing the disk. When you later hit a wall, because you couldn’t break, you can check where you just said trust me.
The difference is, you put up a sign “here be dragons” with unsafe. Certain operations break the garanties of rust, like pointer operations and Cells. So now you need to write a wrapper which upholds checks that they are not violated. If it breaks, you just need to check your unsafe code, instead of everything. Now only one person needs to deal with unsafe for everyone in a team to benefit.
Memory safety isn’t a skill issue. There is a reason they happen in all big projects like android or chrome and only reduced when introducing safe languages.
I’d rather have a compiler that tells me why my code was refused than a compiler which prints 100 lines of templates. Or a compiler, which tells me a pointer/reference is null instead of a compiler that knows, but it’s UB-NDR so it isn’t snitching. If the compiler tells me, hey here you could have a race condition, it’s one less bug I have to find with a debugger. A compiler that complains about uninitiated variables, instead of a compiler that gives me potluck as content.
Some of these are bonkers. The argument not to fix them because of backwards compatibility is even wilder. Which normal client would need the ability to get data for any other account that it hasn’t the Auth token for.
There also IDEs that start instantly.
They don’t ship a whole browser though.
For a program at work the scripting language is Delphi and the Documentation is not available. If you want to know something call the support. CLI is not an option.
It’d be really useful to have a CI run, but that is never going to happen.
I don’t like the interface for setting up flows. Feels needlessly complicated.
The version with Linux, we call “GNU/Linux.” It is OK to call it “GNU” when you want to be really short, but it is better to call it “GNU/Linux” so as to give Torvalds some credit.
I suggest we call it Linux for short. Good thing you can use Linux without GNU.
With nix it’s easy to revert, if you keep your previous config. Version it with git and it’s really easy.
There is always the option of waydroid to get android apps running on Linux. It’s not a great solution, but a first stopgap measure to use services only available as apps.