Live data from Hacker News

How I decide between many programming languages

drewdevault.com

61–68 of 68 posts

Re: How I decide between many programming languages

#61
post #51

Earlier quoted context omitted.

>I'd have put PHP and C++ at the very top of the list, then reverse the whole list. I know what you probably meant, but if you put them at the very top of the list and then reverse it whole, they'll end up at the bottom again. Just saying.

No, that's exactly what I meant! I find PHP to be a bag of confused inconsistencies thrown together. While I have no disrespect to the people who put up with this on a daily basis, I'd never choose it for a new project. Similarly, C++ has never really appealed to me - its idea of OO seems misconceived, and it doesn't seem necessary - my current favourite for this niche is Nim

Thankfully, there's nothing mandatory about OO in C++. I mostly just use C++ as an incremental improvement over C - not "C with classes", but C with constexpr, a bit more type safety and a few other niceties. Nim is better in some ways, but often not really an option for me.

Re: How I decide between many programming languages

#62
post #56
post #40

Earlier quoted context omitted.

Maven is inherently bad too, though

In which way exactly? Having worked with many, many different package managers, I've come to appreciate Maven's way of doing things. Even though it has many drawbacks: - XML structure is verbose - Plugin architecture makes standard behaviour opaque - Default HTTP with no package signatures is recipe for security problems - "Stages" seem arbitrary and it's not always clear which stages are performed. - Community seems…

Well, I think you've covered the issues I was going to mention!

Re: How I decide between many programming languages

#65

Among the other criticisms, Ruby hasn't been hip for a while. Bootcamps started offering nodejs, meetups are more diverse, fewer conference topics on Ruby. One major local conference had such low attendence last year they were going to cancel it this year. It's a very low quality post.

I didn't mean this as a criticism of Ruby, either. I'm a Ruby/Rails dev and still enjoy the language, even if it feels like it's fallen out of favor

Re: How I decide between many programming languages

#66

> C++ > Pros: none > Cons: ill-defined, far too big, Object Oriented Programming, loads of baggage, ecosystem that buys into its crap, enjoyed by bad programmers. This is just rubbish. Fair chance the author wrote this with the help of C++ (your OS or browser maybe?). And I enjoy C++ and it's eco system as well, compared to other languages. So that makes me a bad programmer? I'm surprised people are taking this post…

Honestly most people I meet in real life (so not representing at all) who enjoyed C++ where technically skilled but had to fight with following problems:

- bad at keeping code simple

- to much focused on details instead of the broader picture

- bad as team leads due to missing some relevant management skills

- bad at producing solutions which where "just good enough" (instead of perfect)

Some of them where aware of their weakness and learned to improve on that areas, setting them on a path of becoming excellent software engineers.

Others where obvious about it or even in denial about it.

In a certain way they had been examples about how a person can be both a technical skilled programmer, as well as as bad programmer who on a subtile way accidentally makes it hard to produce a good end product in any reasonable amount of time.

Re: How I decide between many programming languages

#67
post #19

"C ... statically typed" C is just an assembler with macros, so I think this is a bold statement... "Haskell and every other functional-oriented programming language in its class, such as elixir, erlang, most lisps, even if they resent being lumped together" The set of problems I would try to solve in Haskell and the set of problems I would try to solve in Erlang are disjunct. And its not just about the language, it…

> C is just an assembler with macros

No. Can we put this dumb meme to rest? 1972 C was just an assembler with macros. 2019 C has been a major focus of highly complex compiler research and engineering for decades.

Sure, if you write broken code, C will happily access illegal memory if that's what the input program tells it to. But it will do so efficiently ;-)

Post reply on HN