I could look it up twenty times and I'll still need to look it up again some time later because I don't know what the fuck it means other than "this thing"
Anonymous B joined in and replied with this 2 years ago, 14 minutes later[^][v]#1,231,828
OOP is a paradigm for stupid people. If on the off chance it's actually useful for your particular problem, you'll probably already know that. Otherwise, don't waste your time. If it's being forced on you by the design of the language, then find a better language to write in.
Anonymous B replied with this 2 years ago, 7 hours later, 2 days after the original post[^][v]#1,232,151
@previous (C)
Quite literally one of the worst languages ever created. Created by a literal retard. But everyone uses it so now we are stuck with it and it's impossible to avoid.
It's no exaggeration to say books could be written to describe all of its flaws. It ought to be a case study in any comp sci curriculum, kind of like how business majors have case studies on major failures in the industry.
Anonymous B replied with this 2 years ago, 23 minutes later, 2 days after the original post[^][v]#1,232,160
@previous (C)
I like Rust, but haven't had a chance to use it in a few years. Last time I used it, I hated the library ecosystem though. Very unstable and things constantly broke or changed in the libraries. Plus, simple things pull in tons and tons of dependencies, which coupled with the exceptionally slow compile times, means I often had to resort to re-implementing basic stuff myself (like a random number generator out of all things). So even though I like the language, practically using it isn't as good as it should be and I don't have high hopes that this will improve in the future.
As for scripting, I use python because that's where all the libraries are and what all the code is written in these days (that I use at least). That's where all the stackoverflow answers are showing how to do X or Y in the most efficient way without needing to dive into tons of documentation. Without libraries, a scripting language is nothing. And nothing competes with python on that front, sadly.
My biggest issue with python, though, isn't the forced OOP, it's that everything is so lax that you can't know if there's a basic error (even a simple typo in a variable name) without running the code. This is a nightmare for larger code bases and it feels like once something semi-mission critical is working, I can barely touch it again. It feels like concrete that has dried, which is ironic because scripting languages are supposed to feel light and malleable. If I do make changes to a large codebase, I have to do tons and tons of testing that I don't need to do as much of with a normal compiled language. Maybe there are automated tools that help more with this that don't involve writing tons of extra test code. I don't know. I don't work it enough to have bothered to look into it. And I frankly think I shouldn't have to in any sane language.
What about you? What do you think? What do you use?
Anonymous C replied with this 2 years ago, 1 hour later, 2 days after the original post[^][v]#1,232,164
@previous (B)
Yeah that's true about Python, though if you're using a decent IDE (IMO PyCharm is absolute best) it'll highlight issues like that for you, and other editors that support plugins usually have one for pylint.
I mainly use Go. It's a pretty robust language and it 'fixes' a lot of the issues in C and other languages. It has its own quirks and shit but I like it. I'm forced to use it for work so it could be Stockholm syndrome.
Anonymous B replied with this 2 years ago, 1 hour later, 2 days after the original post[^][v]#1,232,180
@previous (C)
I've never used Go. How is the performance? Do you ever or often have to drop down into another language like C and call such functions from Go to get the performance you need?
That's a common thing I've had to do with python, which is kind of bitter sweet. On the one hand, it's annoying that I have to not so infrequently re-write code in C and call it from python, but on the other it's still much faster to develop and debug that way - "gluing" C functions together in python - than to write everything in C. I'd prefer to glue Rust functions together, but interfacing with python from C is already annoying enough imho, that I haven't yet felt the need to learn the current way to do it via Rust since I feel like it could change completely in a few years as the ecosystem settles (or doesn't).
spectacles joined in and replied with this 2 years ago, 1 day later, 3 days after the original post[^][v]#1,232,335
i use mainly chatGPT. yeah, it's true it can be a little temperamental at times, and sometimes i have to deal with figuring out where it introduces mistakes that i have a nightmare figuring out, like yeah, i guess
and
= aren't typos right, but as far as performance goes, hell, it could be harder i guess. i like it okay. coding, psh, am i right. oh, man.