Well… Kingda Ka is said to have cost $25m. Using that as a ballpark figure.

I want wooden coasters, steel coasters, hyper coasters. Other attractions, too. Gotta buy the land, build the infrastructure around the park, employ lots of people, build hotels, gastronomy… a billion might not even be enough for everything.

Build my own theme park with all the roller coasters I want.

Yeah, which means you can’t just use any Linux you want… sounds almost like, I don’t know, a vendor lock-in.

just fine

Provided it’s an older one with an Intel CPU.

Macbook = Vendor Lock-In as Hardware.

The gravitational pull exerted on the baby caused by the midwife’s mass exceeds the gravitational pull of all planets combined by far.

I just can’t take people seriously who believe in bullshit like astronomy - so while this may be a fun project, sadly there are going to be people who honestly think this is a thing.

I just want shit to work. I want to use it as my daily driver so I can get work done, not waste time to get things working. I don’t want my installation to become obsolete. I want a nice desktop. I want a lot of nerdy console stuff, but good UI as well, so I can choose the best of both worlds for each use case, so I can work efficiently. I want to play the occasional game.

At the moment, EndeavourOS ticks all those boxes for me. I am aware other distros do as well, CachyOS looks nice. But I’m only gonna switch if it’s really worth the effort.

Not a cellphone in sight. Just capybaras living in the moment.

It definitely is, and yes, you’re right, I should open a bug report.

But then again, you could make the argument that a user-friendly OS shouldn’t require developer level expertise that’s necessary for opening bug reports in the first place. After all, bug reports require a certain quality level that’s not obvious to newbies (like how to reproduce et cetera).

For my fellow Germans (in case you don’t know the video yet).

(Explanation: It’s a German language clip taken from an obscure TV station, apparently about health tips for women or something like that. The moderator talks about how beneficial it is to your health to “put a cucumber in your juicer first thing in the morning”, which makes the female guest laugh uncontrollably because of the unintended innuendo.)

Unfortunately in Linux, UI tools often take away some of the transparency you get with the CLI tools they’re made for.

I’ve recently tried setting up a VPN connection to my workplace using the EndeavourOS configuration UI. It basically just said “can’t connect, haha, fuck you”, so I had to dig deeper. Finding out how to use the CLI commands necessary to identify and fix the problem took some time and effort, but in the end, I managed to set it up successfully (turned out most Windows admins still think l2tp is hot shit while the Linux world considers it obsolete).

In this case, UI wasn’t as user friendly as CLI, because it hid vital information that was necessary to solve the problem.

A better UI would probably have solved that problem quicker and easier. In an ideal world, you get intuitive GUI tools that cover all use cases and you still have the option to use the CLI if you want to dig deeper. So yeah, I agree with the point you’re making - Mint trying to be as user friendly as possible by offering accessible UI tools is a good thing and one of the reasons why Mint is so popular. (It’s also a reason why Windows sucks ass, because for most UI things the CLI equivalent is either non-existent or cryptic as hell…)

The point I’m making - GUI tools should always try and make using the CLI unnecessary. Taking away complexity without taking away functionality is the key, and as a consequence, those GUI tools will not be underappreciated for sure.

I know this seems unlikely and sounds outlandish, but I actually managed to jump to another employer in 2020 who wasn’t shitty and paid more. Don’t lose hope, everyone. They may be few and far between, but they exist.

Lemmy: We hate billionaires!

Me: Gabe Newell is a bill…

Lemmy: NOT THAT ONE.

Three dictators controlling about 11000 nuclear warheads.

Not a doomer, but that looks suspiciously like the Great Filter solution to the Fermi paradox.

Well, ideally you start new projects writing 100% Kotlin while only adding Kotlin code to older codebases you can’t get rid of. Personally, I don’t like mixing languages anyway and I would stay with Java in Java projects. One reason is the bloat argument you pointed out quite correctly.

True… but Kotlin makes Lombok quite unnecessary by having its concepts built in. It’s also worth to point out that null safety is opt-in in Java and opt-out in Kotlin.

Yes, there are things about Kotlin I don’t love either. But I still like how it was clearly developed having developer quality-of-life in mind.

Kotlin isn’t perfect and it gives the devs quite a lot of freedom. I would argue that if your Kotlin code is messy, that’s on you - but it will still be significantly less prone to failures like NPEs. Unless you opt out of null safety by using the dreaded ?-Operator.

NPEs are the reason why my team moved to Kotlin. Well, that and all the other myriad advantages Kotlin brings to the table.