Free-market capitalist thing would be to do whatever the hell you want to make as much money as you can. That’s what you get when there is no regulations on the market to discourage bad behavior for competition, the consumer or environment.
“We also heard from attendees that the industry, which is perceived as struggling, would have difficulty selling games for $80 if GTA 6 came out at $70. We think it’s in Take-Two’s self-interest, as a publisher and partner to many developers, to raise the price point for the entire industry.”
That sounds a lot like an argument a cartel would make.
has around 69 different file-systems
VFS maintainers decided it’s time to lay out documentation with more clear-cut guidelines for getting new file-systems upstreamed.
Not really the same situation as that xkcd. They are not creating a new fs.
You can just use the filesystem and markdown files. That is a common way for applications to store note type data locally. This is what tools like Obsidian do and has the advantage of being easy to get the notes out if you want to use a different tool.
I have switched to using helix, so no matter which distro I am on I need to change it to be my default by setting the EDITOR env var.
Depends on which classification system you use. Botaically it is a fruit. But culinarily it is a vegetable.
Yeah… Ubuntu packages are never up to date on release date. They freeze them months before so they can iron out any bugs with the versions they picked. You don’t pick Ubuntu or any point release distro to get up to date packages.
If you can drop a .env file on a server. You can drop a well formed .ini file instead. I don’t see any reason to ever parse a env file as a ini file.
LSF is not a distro. It is a instruction manual and teaching aid. Don’t use it as a base for you main OS. And IMO Gentoo does not really teach you more then Arch does. It gives a bit of flexibility that not many care about (how things are compiled) at a very big cost (of having to compile everything yourself). I would not use either unless compiling things is your hobby.
Sure, try them in a VM if you really want to. But I would not really consider that moving on from your current distro nor do you really need to do that.
GTK does not mean libadwaita. That is a addition on top of GTK. Many of the GTK programs and environments don’t use libadwaita. It is mostly only the GNOME stuff that does.
From anyone that has the pkgstat package installed:
https://pkgstats.archlinux.de/fun/Desktop Environments/current
Debian has two main versions, stable - which is released every two years and supported for a long time. And unstable which is basically a rolling release and constantly changes adopting things to test them before the next stable release. There is also testing, but that is just to place thing in before promoting them to stable so has the same release cadence as stable.
Two years of fixed versions on a desktop is a very long time to be stuck on some packages - epically ones you use regularly. Most people want to use things that are newer then that, either new applications released or new features for apps they use in the past two years.
Ubuntu also has two release versions (that not really the right term though). They have a LTS version which is released every two years much like Debian is. But they also have a interim release that is released every 6 months. This gives users access to a lot newer versions of software and stuff that has been released more recently. Note that the LTS versions are just the same as the interim versions, its just that LTS versions are supported for a longer period of time, so you can use it for longer.
For the Ubuntu releases they basically take a snapshot of the Debian unstable version, and from that point on they maintain their own security patches for the versions they picked. They can share some of this work with Debians patches and backports, but since Debian stable and Ubuntu are based off different versions Ubuntu still needs to do a lot of work with figuring out which ones they need to apply to their stuff as well as ensuring things work on the versions they picked. Both distros do a lot of work in this regard and do work with each other where it makes sense.
Ubuntu also adds a few things on top of Debian. Some extra packages, does a few things that make the disto a bit more user friendly etc.
Any other distro that wants to base off one of these has to make the choice
For a lot of distro maintainers basing off Ubuntu gives them a newer set of packages to work with while doing a lot less work doing all that work themselves. Then they can focus on the value adds they want to add ontop of the distro rather then redoing the work Ubuntu already does or sticking with much older versions.
The value add work that needs to be done on either base I dont think is hugely different. You can take the core packages you want and change a few settings, or remake a few meta packages that you dont want from Ubuntu. This is really all stuff you will be doing which ever one you pick. It is a lot more work keeping up with security patching everything.
I am not sure that is fully true. Or at least not fully explained. The Steamdeck has a full KDE environment installed and it uses this when in desktop mode. But steam is not running in big picture mode in front of this.
KDE is not running at all when in the game mode of the Steamdeck. In that mode it uses a compositor written by valve called gamescope. Switching between these is effectively logging out and back in again to switch the compositor.
Also it now has a way to run the desktop as a nested session in game mode but that is winning kwin inside gamescope.
You cannot eliminate X11/wayland overhead. You need a display manager of some sort. I suspect most games/proton will require X11 or at least xwayland and a wayland compositor. You probably do want to use a window manager of some sort as well or you do lose out on a lot of controls like window placement and sizing. Some games might do weird things if they dont directly launch in full screen mode. And steam itself would probably want to be run in big picture mode to make it go full screen. If you want something designed for gaming then you might try gamescope which is what the steamdeck uses as its window manager in the game mode.
There are probably other areas with a higher impact that you can optimize more before really worrying about a lack of window manager though.
You are not considered to be working somewhere until you have signed a contract and after the start date on that contract. Accepting a offer is not signing a contract. You are not working at the new place yet. You have no obligations to do anything at that point. You just need to have stopped working at your current employment before your start date. You definitely do not need to quit before accepting the offer. No where I have worked requires that.
You are right. You cannot onboard a new job before you leave your old one. Accepting an offer is not part of the onboarding process though. It happens before.
After an interview process the company makes an offer. The candidate can then accept or reject it. But that is really all informal. You can then negotiate with them for an official start date and contract. You just need to ensure you can hand in your notice and work the rest of your notice period before the start date of your new contract.
I don’t know anyone that would hand in their notice before accepting the initial offer of a company. At least here in the UK.
Probably not the only thing they are used for considering it’s ties to the CIA
You assume they don’t already have a job and we’re just looking for other opportunities. Not everyone is unemployed before they apply for other jobs. If anything that is a good time to look as it gives you stronger position to negotiate from.
Yes it is a security issue. But almost everything is. You can make it secure enough with the right policies. However it overall increases the attack surface of your application and has a greater chance that you missed something or miss configured the policies. So many firebase apps have been hacked because of miss configured access to the database.
So it puts more work on you to get things right.
You shouldn’t need tooling to fix an issue. Better for a design that does not require extra tooling.