Antithetical

Took 'em long enough…

• https://www.nederlandwereldwijd.nl/reisadvies/verenigde-staten-van-amerika

Kind of ironic that the people joined facebook groups for that…

Add Microsoft to that first list. Many people are way too locked into their crappy software ecosystem.

I bit the bullet and bought the Jetbrains Ultimate bundle because I develop in lots of different languages. It includes WebStorm and it is a joy to use. It helps where necessary and doesn’t get in my way…

You could try the book… The movie is quite tame compared to the book though. It sketches a very detailed look into the time as well. Iirc there are about five pages in wich Bateman explains why he loves certain music albums. And of course his whole morning routine… I really liked it.

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…

On a city crossroad, with warning signs, lights, pylons and tape not to drive over it, was a car in the center. Sunken to its axels in freshly poured concrete. The idiot driver had just ignored everything and could now pay to have the concrete fixed.

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…