Ha sure, although since it is not well traveled there aren’t any Lemmy comments yet. But you’re very welcome to visit…

See: Gele Sneeuw

Nice, I did the same for my blog. Didn’t want to build a whole comment system when Lemmy fits the bill quite nicely :)

I do not agree. Very often, when using libraries for example, you need some extra custom handling on types and data. So the easy way is to inherit and extend to a custom type while keeping the original functionality intact. The alternative is to place the new functionality in some unrelated place or create non-obvious related methods somewhere else. Which makes everything unnecessary complex.

And I think the trait system (in Rust for example) creates so much duplicate or boilerplate code. And in Rust this is then solved by an even more complex macro system. But my Rust knowledge might just nog be mature enough, feel free to correct me if I’m wrong…

As a life-long developer in OOP languages (C++, Java, C#, among others) I still think OOP is quite good when used with discipline. And it pains me that there is so much misunderstood hate towards it nowdays.

Most often novice programmers try to abuse the inheritence for inpropper avoiding of duplicate code, and write themself into a horrible sphagetti of dependencies. So having a good base or design beforehand helps a lot. But building the code out of logical units with fenced responisbilities is in my opinion a good way to structure code.

Currently I’m doing a (hobby) project in Rust to get some feeling for it. And I have a hard time to wrap my mind around some design choices in the language that would have been very easily solved with a more OOP like structure. Without sacrificing the safety guarantees. But I think they’ve deliberatly avoided going in that direction. Ofcourse, my understanding of Rust is far from complete so it is probably that I missed some nuance… But still I wonder. It is a good learning experience though, a new way to look at things.

The article was not very readable on mobile for me but the examples seemed a bit contrived…

This is the best answer. I’ve been doing it for years at work. Dual-booting is just very inconvenient and WSL(2) is the worst of both worlds.

Install Linux on the machine and keep windows in a nice secure kvm-based cage where it can do less damage.

As others have said: it depends on your technical expertise… But a nice and cheap solution is hosting a static blog build with Jekyll on Gitlab pages.

Hey, careful now. German jokes are no laughing matter…

If you’re still interested it seems that they’ve uploaded the keynote, see link in my comment:
https://lemmy.deedium.nl/comment/115389

It seems they’ve uploaded the keynote, see:
Keynote: Linus Torvalds, Creator of Linux & Git, in Conversation with Dirk Hohndel

Don’t worry, also you will get a chance to learn… It’ll be fun!

Spaces are fine in filenames. Just always always always quote your paths and/or variables…

Sadly no, that one is three months old. Hopefully they’ll publish it on the Linux Foundation yt channel or something.

Great explanation, thank you for the well written post.