I always strongly disliked the OOP school of program design, even though I learned to parrot everything required by one's typical interview process.
Keeping data and functions together can be nice. In some rare cases inheritance is almost OK. But still don't understand how it all went nuts and they started writing, say, parsers in that style...
But it's always nice to hear that there are other people having similar opinions. Especially if it's people like Linus.
yeah but people hate writing Go. It’s like using the dullest possible knife. It doesn’t have objects, it doesn’t have generics (so you can’t really do Functional Programming) and it doesn’t really let you do C-style machine work either. Its basic assumption is that you’ll have an endless supply of human beings to
implement everything, because the computer isn’t going to let you abstract anything
> people hate writing Go
Bit of a blanket statement. I enjoy it much more than the little Node I investigated for work.
The lack of functional programming though, yeah. I feel like it might be due to GC optimisations as well, however. From what I understand, the reason the GC is so fast is because such a style of programming is heavily discouraged.
Re:I Don't Like Debuggers (2000)
by marcosdumay on Friday March 22, 2019 @05:13PM
(#19467031)
> I enjoy it much more than the little Node I investigated for work.
I'm another one that prefers putting a bullet on my foot than putting it on my head.
Somehow, the Go language is doing it, eschewing traditional OOP in favor of a get shit done fast and a little dirty approach. It's not even because of the charm of an individual either.
Then again, before Go there was JS as the big opponent to rigid OOP. I still don't understand why they felt like they had to add half-baked classes / OOP to it.