Looks great, thanks for sharing

Random recommendation, but I recently stumbled upon https://monaspace.githubnext.com, and it seems like a pretty cool approach to the whole “monospace font for dev work”

Lol the out of memory error was a joke. A reference to that two people both trying to do the same thing will fill the heap since there’s unnecessary work.

I tried to make a code joke but it failed.

As far as what are they unwilling to release? Control. Ownership of any bit of the kernel they control

kernel maintainer Ted Ts’o, emphatically interjects: “Here’s the thing: you’re not going to force all of us to learn Rust.”

Lina tried to push small fixes that would make the C code “more robust and the lifetime requirements sensible,” but was blocked by the maintainer.

DeVault writes. “Every subsystem is a private fiefdom, subject to the whims of each one of Linux’s 1,700+ maintainers, almost all of whom have a dog in this race. It’s herding cats: introducing Rust effectively is one part coding work and ninety-nine parts political work – and it’s a lot of coding work.”

It’s a whole different ballgame. I’ve written a good amount of C and C++ in my day. I’ve been learning Rust for a year or so now. Switching between allocating your own memory and managing it, and the concept of “Ownership” https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html is just something many devs set in their ways aren’t willing to do.

I understand where they’re coming from, I’ve gone through massive refactors with new tech in my career. I think this approach needs to be more methodical and cautious than it is, but I don’t think they are correct in the end result. I think a memory-safe language is the way to go, and it needs to happen.

This to me is a classic software project with no manager and a bunch of devs arguing internally with no clear external goals. There needs to be definitive goals set over a timeline. If someone doesn’t agree after a consensus is reached they can leave the project. But as of now I think as others have said this is 80% infighting, 20% actual work that’s happening.

Ironically the majority of the rust memory management ruleset is called ownership, and they are unwilling to release any of it, and claiming all of it, so there’s an out of memory error.

But on the other hand you can’t expect some smaller and smaller subset of the population to primarily just learn C and meet the criteria of a kernel dev.

I absolutely agree with all your points, and most rust devs would agree, but the general idea is that over time that energy (which would have been spent tweaking malloc and such) should be spent on the rust compiler and memory management systems, which is already magic as someone who as written a lot of c, c++, and spent the better part of a year learning rust. (I’m no expert of course, but I have a pretty decent grasp on the low level memory management of both the Linux kernel and the rust compiler).

So that over time the effort that would be spent on memory management and kernel functionality can be properly divided. Rust not being efficient somewhere in catching memory faults or managing memory? Fix it. Someone writing unsafe rust code? Fix it.

I think at the end of the day everyone wants the same thing which is a memory safe kernel, and I think that rust Is being shoehorned into kernel projects too early in places where it shouldn’t be, but I also think there is unnatural resistance to it just because it’s different elsewhere to “how it’s always been done.”

micro has some improvements and default shortcuts that are much closer to common GUI text editors

https://micro-editor.github.io/

https://github.com/apple-oss-distributions/xnu

Though if we are using the brand UNIX, macos is one of the few UNIX brand products out there

https://www.opengroup.org/openbrand/register/

The BSD family has evolved, and while not having the Unix trademark, does have its roots in the same codebase

And if you don’t feel like using physical dice:

https://diceware.rempe.us/#eff

And if it was a kernel-level driver that failed, Linux machines would fail to boot too. The amount of people seeing this and saying “MS Bad,” (which is true, but has nothing to do with this) instead of “how does an 83 billion dollar IT security firm push an update this fucked” is hilarious

Not just scammy

Epik is an American domain registrar and web hostingcompany known for providing services to alt-tech websites that host far-right, neo-Nazi, and other extremist materials. It has been described as a “safehaven for the extreme right” because of its willingness to provide services to far-right websites that have been denied service by other Internet service providers.

https://en.wikipedia.org/wiki/Epik

I’m in no way surprised at what they did, and in fact only surprised that it wasn’t them that bought the expired domain, but instead was godaddy

Put on some socks, post in !unixsocks@lemmy.blahaj.zone, bam

Like Vegas? Sure. Open source stuff like kdenlive and shotcut exists. Davinci resolve is available for Linux for more professional stuff. Specifically Vegas? Probably only under a VM, and you’d likely get awful performance, so not worth it. If you’re a professional, Linux isn’t always an option, especially if you are in a software ecosystem that doesn’t work there

During my normal usage in Linux, which includes web browsing with Firefox, video playback with Haruna Media Player (with hwdec set to auto), writing in Obsidian, and lightweight coding in Visual Studio Code and Android Studio, the tablet lasts for 6 hours.

There’s no such thing as lightweight android studio lol. The battery would likely last much longer just playing a movie at low brightness, which is usually what hardware companies do to measure and advertise battery life.

It’s hilarious to me that I have to jump through so many hoops to get my old games working on windows when they run almost out of the box on Linux, but on the flip side with all the launchers and shit built into AAA games today it’s a hassle to get them set up on Linux. Like once I do get them set up they work great. But lutris, proton versions, winetricks, etc to get them working is an activity

And you’ll finally get your sound working on your new laptop after weeks of messing with pulse audio and realizing you just needed to install sof-firmware but didn’t scroll far enough in the wiki to see that, but now your pulse audio config is so messed up it’s just easier to reinstall Arch again

Source: my life