r1veRRR

ANY effective, long-term collective change REQUIRES that the large majority of people CHANGE THEIR CONSUMPTION HABBITS. While not great, the private plane stuff is exactly as pointless as the paper straws. Both are ways for everyone to point the finger at everyone else, and not have to change.

If the government implemented the "correct" laws tomorrow, but the populace doesn't want to change their habits, they will vote in people that give them back their old, bad things.

If a company implemented to "correct" processes, but the consumers don't want to pay the necessary price, they go bankrupt, and the company with the "incorrect, but cheap" processes wins.

ALL COLLECTIVE ACTION IS A COLLECTION OF INDIVIDUAL CHANGE. There is no alternative!

Writing a CHIP-8 Emulator was really fun. There's a lot of resources out there and it's really fun, small low level project you can "finish" in a week of casual coding. As someone who was mostly coding highlevel in my job, I really learned a lot.

The Prime Video example was more like moving from nano-service insanity to sanity. They basically split EVERY POSSIBLE STEP into separate lambdas. They switched to still using microservices, but they do all transcoding steps for a single video on the same microservice instance (aka sanity).

How's the filesystem performance? Whenever I've mounted something into a Docker Container, the performance has suffered. For example, things like NPM/MVN suddenly take way longer.

How do you manage JVM versions? We have many older projects that use 8, and some newer ones using 17, for example.

Kubernetes is so easy! Unless you're insane enough to have any state at all in your app. But who does that?

Nier Automata. I really hated the replaying it part. The combat gets incredibly boring after the first two playthroughs. I also found the supposedly "deep" story to be extremely lacking, very on the nose and, like way too much japanese entertainment, bipolar when it comes to emotions.

Ironically, I learned Rust first, and later looked at Go. I found a lot of the syntax needlessly "different". That being said, it's still a decent language. Point being, a lot of the weirdness subsides once you understand why it's there.

Personally, I don't actually care about the lifecycle and memory management stuff. What I like about Rust is:

• An enforced error type that is very convenient to use with the ? operator. No more err != nil spam, but same amount of safety
• ADTs with a host of wonderful features, like exhaustive match statements. Go enums are horrendously basic, let's be honest
• NO NIL!! Non existence is expressed with an Option type that, like the error type, comes with many conveniences
• Generics from the start, meaning you don't have older code that throws away type safety anywhere
• Traits/Interfaces can be implemented for foreign/external types and types can implement external interfaces (duh)
• Great tooling, good formatting tools, good LSP, that kind of stuff. Golang has that too

Why learn Rust? For the same reason everyone should learn different languages. To learn new concepts and see new perspectives on old problems. It'll make you a better developer even in your previous languages.

Compiler checked typing is strictly superior to dynamic typing. Any criticism of it is either ignorance, only applicable to older languages or a temporarily missing feature from the current languages.

Using dynamic languages is understandable for a lot of language "external" reasons, just that I really feel like there's no good argument for it.

For bigger projects, anything with MANDATORY types is a must for me. Optional, not compiler checked hinting doesn't cut it.

Not that i hate the language, but I do hate the tooling around it. I don't think I've ever had a pleasant experience with setting up a Python project. And all the data stuff is just wrappers for code in other languages, making the packaging story even uglier, even harder.

In my experience it HEAVILY depends on the language you're using. Nothing beats Intellij for Java or Kotlin, but Rust and Go feel at home in any editor.

I know that LSPs and DAPs somewhat take care of these, but the following are often easier in IDEs:

• Refactorings, including really smart language specific ones
• Support for fancy frameworks. For example, Intellij can analyse all annotations for Dependency Injection or Spring stuff, and will then tell you exactly how everything connects on a higher "framework" level. Arguably, this is a solution to a problem Enterprise Java created
• Debugging is easier
• In general, stuff works "well enough" out of the box. As a fan of Neovim, I've definitely been frustrated a lot the first time I had to set something up
• Fancy integrations, for example linking frontend code calling backend code directly, or an entire little Database Manager builtin, with magic SQL code completion

Yeah, well, that's just Python for you. List usages is now an LSP feature for most languages, so will work with "lesser" editors too.

All that being said, I use Intellij with Java daily, so I can see where you're coming from. But for example Rust or Go works wonderfully with Neovim (or VSCode).