I don’t need research because I’ve been to Tokyo plenty of times and I saw in fact lots of trash in the ground.

And again you’re wrong, trash bins for recycling do exist in Europe because I use them all the time, and I also happen to have visited lots of European countries and I didn’t see that much more trash in the ground than Japan. It’s true for cigar butts (its mind boggling in the Mediterranean countries) , but not trash. You probably had one “bad” experience and are using that evidence anecdotally. You are comparing Japan, a country, to Europe, a continent, it’s not fair

And we all know Arch isn’t a distro right?

You are lying or not paying attention. Got to Tokyo and you’ll have plenty (as per Japanese standard) of trash in the streets specially near Shinjuku and Shibuya

And yes they mostly take their trash with them as there are no trash bins. But is it a smart design though?

Their whole aesthetics is super cringe

• You will spend your entire career chasing trends.

Depends on the language, that’s mostly a JavaScript/typescript issue.

• The market is volatile. People are constantly getting abruptly laid off. SD has never been very stable, so you should plan on getting a new job every few years.

Depends on the country, where I’m from there has been very few layoffs.

• Software companies are constantly looking for ways to make SD easier. As a result, your value will decrease over time, in preference for bootcampers and 2 year degree graduates.

Not sure what to say, I haven’t felt my value decrease. All I see are bubbles saying they will replace me… and then they burst.

Nobody listens to developers. Your manager’s beliefs about SD come entirely from consultants, magazines, and Elon Musk tweets.

Agree but that’s more of an engineering wide problem, specially when you get managers with very few engineering experience. Take the Apollo landings as an opposite example: great managers that were great engineers.

• Nobody cares about quality software. If you take the time to make your code efficient and lightweight, all your manager sees is you taking longer to make something than your peers. After all, we can just raise hardware requirements if the software is slow.

This is a bit too generic to argue against. You can get that in electrical engineering no? If you take more time designing that PCB because you want to better place the components to improve heat dissipation, will your manager care in the end?

I also never had an accident where I needed the seatbelt

I see your point, but in this case I feel OP was misinterpreting the situation

But that’s the thing where you are wrong. They clearly state they don’t want C developers to learn Rust. In the particular video posted he was saying “I want you to explain to me how this particular API works so that I can do it”

The concerns about who fixes what on a merge when the C code breaks Rust code are valid, but that’s easily fixed by gathering with the Rust developers, explaining the changes and letting them fix it.

Can you point out where I said that?

The issue is not agreeing, but behaving like an immature prick when arguing

Indeed :)

Isn’t Linux still Linux even though probably a lot of the original code is gone? Why would slowly rewriting it whole, or just parts, in Rust make it stop being Linux?

I agree with your views. But I have to give praise to Linus for bringing Rust into the kernel.

Yes I agree but the solution for a project so big and critical is not to fork. How do you maintain all of it while at the same time adding support to Rust?

The difference is that now you have a scope of where the memory unsafe code might be(unsafe keyword) and you look there instead of all the C code.

This is such a dumb take. For as much as I’d like to have a safer language in the kernel you need the current developers, the “big heads” at least because they have a lot of niche knowledge about their domains and how they implementation works (regardless of language) People shouldn’t take shit like this from the ext4 developer, but it doesn’t mean we should start vilifying all of them.

This guy’s concerns are real and valid but were expressed with the maturity of a lunatic child, but they are not all like this.

Better in what ways? Rust’s strong points are not to just make a program more stable, but more secure from a memory standpoint and I don’t think Linux keeps improving on that

I can’t understand Logseq, even though it seems appealing. I haven’t gone too deep yet but to me it feels weird that they say it’s simple and then their documentation is confusing and full of videos explaining how it works. That seems far from simple.

Well I have my Linux partition encrypted with a unique password. But I don’t dual boot anyway …

That’s not a nice thing to say. When you grow up perhaps we can continue this discussion