Nice! And they will probably differentiate from the competition by allowing GPL applications and sideloading, and having a total control for your privacy and no tracking, right?

Right?

Meanwhile these CPUs are amazing on Linux

https://www.phoronix.com/review/amd-ryzen-9950x-9900x

https://www.phoronix.com/review/amd-zen5-avx-512-9950x

For some reason Windows scheduler is not as good as the one found in the Linux kernel with the zen5.

That thing which makes Meta and Apple so scared they do not release their new products in AI anymore in the EU to pressure us to loosen up the laws. That has already been costly to these companies.

That prevents Paypal from doing this change in the EU.

The law that has been awesome so far.

No, it means if you run Lemmy as a service and make modifications to it, you have to release your modifications back with the same license. Otherwise you couldn't use a browser that's not AGPL and read pages running on top of an AGPL server.

What AGPL is really good at is how nobody can take Lemmy, run a proprietary service and add incompatible features without giving them back to the community. So nobody can fork Lemmy, create a new VC-backed Reddit clone and start making incompatible changes to the source without the main project getting the source code.

Signal always responds to authorities when they ask for data, and they give them all they have: the day they registered, their phone number and the timestamp they last used the app.

Telegram has unencrypted channels of drug dealing, and what I heard is a lot of illegal porn too. The authorities want information on certain users there and Telegram doesn't comply. This is directly against the law Signal is not breaking, because they always send all the data they have to the law enforcement.

I just didn't watch this movie for years because I was thinking just like the reviewer here. This year I finally watched it and... it was ok. The biggest reason to see it was because I really like Joaquin Phoenix and I wanted to see the movie from which he won his Oscar.

There's a lot of things in his Joker performance worth a revisit: how he talks, and how he moves, is really unique and definitely worth the victory. I just wish he would've got his Oscar from The Master, which for me is a groundbreaking movie and has one of the best scenes of all time with Joaquin and Philip Seymour Hoffman in the jail cell.

But he got it from the Joker, and I'm glad he got the recognition.

It comes with the Office subscription. People who choose it are not the ones using it daily.

A great UI to stream your movie files from your TV. A bit like Plex, but open source.

For me the reason was that I wanted encryption, raid1 and compression with a mainlined filesystem to my workstation. Btrfs doesn't have encryption, so you need to do it with luks to an mdadm raid, and build btrfs on top of that. Luks on mdadm raid is known to be slow, and in general not a great idea.

ZFS has raid levels, encryption and compression, but doesn't have fsck. So you better have an UPS for your workstation for electric outages. If you do not unmount a ZFS volume cleanly, there's a risk of data loss. ZFS also has a weird license, so you will never get it with mainline Linux kernel. And if you install the module separately, you're not able to update to the latest kernel before ZFS supports it.

Bcachefs has all of this. And it's supposed to be faster than ZFS and btrfs. In a few years it can really be the golden Linux filesystem recommended for everybody. I sure hope Kent gets some more help and stops picking fights with Linus before that.

If it is a Samsung tv, they have been automatically connecting to any open wifi, maybe your neighbor has one. And there goes the data.

Avoid Samsung.

It's interesting to see how Cyberpunk 2077 is actually selling really well still. Looks like it worked out well for CDPR eventually.

Best of all you do not need to click the link, load the website, enable JavaScript because there is nothing without it and then tap the cookie banner away disabling all of the cookies first.

Me neither. But. I think the answer is much simpler here: Microsoft doesn't make their money with schedulers, but bundling that Office and tracking to everybody, and charging rent every month. They have way less people working on making the kernel as fast as possible, compared to Linux where:

• there are many companies running crazy workloads 24/7, and providing patches
• very talented individual hackers who have an open source kernel and can play around with things, getting that last oomph out from their system

This is why, for a pro user, Linux is an amazing platform.

The follow-up discussion was informative and the original commiter learned something. We all learned something when we read the discussion.

That's why you write your protocol as a sync library, then implement the async IO separately and mapping the data over the protocol modules.

Helix. A perfect programmer's editor you can use with almost no config.

I'm in Berlin and half of my neighbors have these 3m tall weed plants on their balconies. 3-4 usually, and nobody really cares. I wonder how the winter is going to be when everybody suddenly has half a kilo of weed...

Yeah, I'm also one of these people silently enjoying systemd and wayland. Every now and then there's fuzz on one of these. I shrug, and move on still enjoying both of them.

Yes. And I feel sad because I haven't been excited on any other OS for years after learning NixOS. I used to be excited about playing with things like FreeBSD, but now they all feel like something's missing...

Not for everybody, but as a software engineer nix/nixos is blessing.

So basically your typical network protocol is something that converts an async stream of bytes into things like Postgres Row objects. What you do then is you write a synchronous library that does the byte conversion, then you write an asynchronous library that talks with the database with async functions, but most of the business logic is sync for converting the data coming from the async pipe.

Now, this can also be done in a higher level application. You do a server that is by nature async in 2024. Write the server part in async, and implement a sync set of mapping functions which take a request coming in and returns a response. This can be sync. If you need a database, this sync set of functions maps a request to a database query, and your async code can then call the database with the query. Another set of sync functions maps the database result into http response. No need to color everything async.

The good part with this approach is that if you want to make a completely sync version of this library or application, you just rewrite the async IO parts and can reuse all the protocol business logic. And you can provide sync and async versions of your library too!