Licenses for sublime text 2 just said “and future updates”. I remember the “lifetime” thing being a selling point on producthunt. This was back in 2013 though, and the weird way the licensing change was handled made me switch to emacs.
Before sublime text 3 all updates were included in the single license, not just major revision updates. This was back in 2013.
Before the one license=one version switch in 2013 the license stated “and future updates” which they did, but they switched to needing to pay for new licenses for some reason. I remember that being the primary reason I switched to emacs.
After having been shafted by sublime text I will never believe anything called a “lifetime subscription” is such.
A “lifetime subscription” is just a “until we decide otherwise” subscription
The leadership response to this and the subsequent backlash is starting to remind me of the NixOS debacle from about a year ago.
That resulted in the project being split and like 30% of the community moving off and creating Lix.
I would be disappointed, but not surprised, if we see something similar in the Kernel sometime in the next year or two…
Man you better hope the kernel community gets its shit together then, cause Krummrich (the primary developer for nova and getting those changes upstreamed) is one of guys that got told their project was cancer by the “thin blue line” maintainer (Hellwig) from the article.
Nouveau is important because Nouveau is the default driver in Ubuntu, Fedora, OpenSUSE, Debian, and ever other distro.
Linux distributions can’t easily distribute the proprietary nvidia drivers or the slightly less proprietary nvidia-open drivers so they depend on nouveau as the default nvidia driver. When you install a distro it usually has to use the nouveau drivers before downloading the proprietary blobs from Nvidia.
Nouveau is the only reason anyone can use Linux on an Nvidia card long enough to install the other drivers.
It’s also actively maintained, receiving updates that get upstreamed almost daily.
I’m not sure what about those things says “defunct”.
And the rust developments in Asahi for the M1+ series of CPUs don’t just benefit Mac but all the ARM CPUs as well.
A few people from a downstream project like Asahi or an almost defunct driver like Nouveau
I’m not sure why you think Asahi is a minor player in the linux community when they’re responsible in the entirety for porting Linux to the Arm-based Mac M1+ series, or why you think Nouveau is defunct.
“the process works” Is I think how he phrased it. 🙄
I’m not surprised by this.
The general attitude around R4L is that it’s largely unneeded and for every 1 person actively working against the project, there are 10 saying either “waiting and seeing if it works is the right decision” or “if rust is so good they should prove it.”
So as a R4L developer you’re expected by the community to fight an uphill battle with basically no support on your side.
We will likely keep having developers on that project continue to burn out and leave until the entire thing collapses unless the decision is made ahead of time to cancel the project.
Every time I read any news about Rust for Linux I leave disappointed by the entire kernel community.
bc
It’s a simple command line calculator! I use it all the time.
I love locate! I have a cronjob that updates the db every night, then I can just find a file without having to think about where it is
Holy shit I was just talking about cp with progress today. Awesome
I run btrfs on every hard drive that my Linux boxes use and there’s the occasional hiccup but I’ve never run into anything “unrecoverable.”
I will say that compared to extfs, where the files will just eat shit if there’s a write corruption, because btrfs tries to baby the data I think there appear to be more “filesystem” issues.
Typically when there are “can’t mount” issues with btrfs it’s cause the write log got corrupted, and memory errors are usually the cause.
BTRFS needs a clean write log to guarantee the state of the blocks to put the filesystem overlay on top of, so if it’s corrupted btrfs usually chooses to not mount until you do some manual remediations.
If the data verification stuff seems more of a pain in the ass than it’s worth you can turn most of those features off with mount options.
I’ve had btrfs go into an error state because of a bad write before, but it was pretty easy to recover from
Yea a surprisingly small number of people don’t know a git remote can literally be any folder outside of your tree, over almost any kind of connection.
I thought about doing a forge but realized that if I was the only one working on this stuff then I could do the same thing by setting my remote to a folder on my NAS.
What do you mean by personal package manager?
What do people use for command line utilities? The selection on flatpak is a bit sparse
It was over eleven years ago at this point so my memory may be hazy on the details but I remember something happening in the major version change that pissed me off enough to switch off of it. 🤔