Public service announcement: Do not get married to your language, tools, or way of doing things. If there's an easier solution to something, try it before dismissing it. No language is perfect, and dumping everything on the responsibility of an API or framework can cause more headache then solve it.

Case in point: I love Java for backend programming, but node.js is a better solution to frontend programming then depending on JSP's and HTML within the same Java project. Less things go wrong and it's easier to debug issues.

There is no best programming language. Only best practices and using the right tool for the right job.

#exceptC++fuckthatlanguage

:^)

Here's an upvote, I choose to ignore that last partabout cpp

@myss Twas a joke. And C++ was my first language so I can take some potshots at it. :P

Crystal is perfect <3

mh I've become married to C so much that I even do string-heavy parsing shit in C with a truckload of raw pointer arithmetics where saner people would use Python (and have slow programs). Plus that I'm abusing GCC's preprocessor as static website generator just because it's easy for me.

@Fast-Nop That's the addicting thing about C and C++. You have access to the bare metal and you're always obsessing over how you can improve your algorithms.

Part of me misses it but part of me doesn't miss the bug fixing. :P

@starrynights89 the bug fixing goes away once you really start to think in assembly and use C as the portable macro assembler it is meant to be. That's why I don't have issues with raw pointer shit and the legendary segfaults.

@Fast-Nop That may explain a lot why I prefer static/dynamic typed languages like Python/Java/C#, I never much cared for working with assembly and I tried to make my C++ code closer to Java than to straight C/Assembly. I'm still glad my college made me learn bits of Assembly though because I wouldn't understand things like CPU run-times/cache and how important memory management is in programming.

I respect anybody who has the patience to work on that level. :)

@starrynights89 that's funny - I've never gotten around to C++ because everything of it feels like additional obfuscation to me and that I'm too fucking dumb to wrap my head around to get a clear idea of what assembly this shit is gonna spit out. Before I tackle a CPU, I read its fucking instruction set and cycle timing so that I know what's fine and what isn't, and my C code reflects that.

Many C++ programmers just don't care and go ahead trusting that things will work out; the rockstars of course do understand C++ down to assembly. Since I'm no rockstar, I either have to abandon full understanding or shun C++. Faced with that choice, I guess I'd even prefer selling my soul to the devil and go into management.

*Learning C++ stl*

It's good to know a language but it's better to know programming 😄
Try to learn the logic and paradigms underneath and no language is an obstacle.

@Fast-Nop Or just stick with C or Go. C++ will be around for specialized software and games (I used it for games programming until my interests changed) but I feel it's going to only be able to serve that niche. It's way too complex for any purpose beyond it's sheer speed.

I believe that C and Assembly will outlive C++, you always need software and firmware in that level.

@Synti True. Makes learning your 2nd and 3rd languages easier.

@starrynights89 even with speed, it's not gonna beat C. Yeah OK with stupid shit like qsort, but I wouldn't use that anyway when it impacts speed.

no language is perfect because nothing in this world is absolute. there exist, however, languages that are "perfect" in the sense of "best fulfilling their intended purpose and usage while containing the least amount of WTFs overall"

If I have to choose between an api which is not good for one's privacy but extremely easy to use and one which is fucking hard to use but is good for one's privacy, I'll go for the hard one.

Same with open vs closed source.