Spyke

Replies

Comment on

Man pages bad

Man pages are great to have, all documentation easily accessible, mostly complete and directly available in your terminal.

Compare this to the shitshow that is git --help in windows opening a stupid browser. Somebody should be defenestrated for that decission.

games

Comment on

Cyberpunk 2077 director thanks fans as the game hits a 95% positive review rating on Steam

I got this game finally last year, after waiting for the bugfixes, and have been playing since then. I've got over 170 hours now, did all the sidemissions and now finishing Phantom Liberty, and loved every minute of it. This was my first dive into the cyberpunk-genre and it is impressive, especially the dystopian future that also seeps through in modern times.

The way Cyberpunk 2077 tells its story and does world building is beautiful. The immense city with twirling roads, mountains of trash and dysfunctional society is really immersive. I understand that it is not possible to give every citizen a full back story with limited resources but the amount of detail and love that they were still able to put in is commendable. Even after all this time spent in the gameworld it still manages to surprise me with random encounters while exploring.

I'm glad I waited for the bugfixes and had only a few crashes and minor glitchy physics. I hope they learn that delivering a good product is more important then deadlines, since players like me will wait anyway.

Fun fact: in no other open-world-game I got run-over by cars as much as in this game. Hmm I wonder, maybe all cars evolved from Tesla's in this universe? (j/k)

Comment on

OOP is not that bad

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..

linux

Comment on

My week with Linux: I'm dumping Windows for Ubuntu to see how it goes

It is a nice look into the switch from a perspective of a windows user. But since he is experimenting there is a also a lot of bad choices or wrong information.

He gripes about things not going smoothly while replacing his whole desktop environment (when was the last time you replaced your explorer.exe?).

And clamping to old ways of doing things. Which is understandable but would go a lot better with a little bit of guidance. Why force Chrome while Firefox was probably pre-installed or Chromium also works. Using Filezilla while Dolphin can probably do it in an integrated way. Using Notepad++ while Kate probably covers most of his use-cases.

This doesn't invalidate his experiences but it does indicate a resistance to switch.

There is some valid criticisms as well though. The docking station that bugs out or KDE Connect that is confused. We can improve those things, but hardly force Logitech to bring their (horrible) software suite to Linux.

Maybe he should give it another few weeks to actually feel that while his old ways might not transfer over 1:1 the new ways give him a lot more power.