21–30 of 68 posts
The list may be entertaining, but displays little in the way of objectivity. For instance, OOP is a major con of C++ (even though many people write C++ all day without any of it) but isn't even mentioned with regards to Java and C#? Really?
> OOP is a major con of C++ Not sure what exactly you mean by this, but many people use classes and objects all the time in C++, and see it as a pro rather than a con.
It seems Drew DeVault is highly opinionated and the opinions are more than 10 years old.
- Does it have a standard and a good track record for backwards compatibility?
- Is it memory safe? (Bound checking, no pointer arithmetic, etc.)
- Does the runtime have automatic memory management in the form of a tracing GC? How tweakable is it?
- Does it have kernel thread support?
- Does it have a centralized package repository?
- If typed, will the type system assist me in defining the business domain? Does it have type inference?
- If dynamic, will the development experience allow me to experiment, inspect and redefine stuff at runtime?
- Can I distribute my programs as a binary or dump everything onto an image?
- Can I go low level when it matters? How's the FFI experience and overhead?
- Does it run on the major operating systems?
Things I don't care about: Syntax, static vs dynamic typing / OOP vs FP religious wars, community size or "niceness", library count, logos, on-boarding experience aka the possibility of hiring cheap juniors.
Cute mascots are nice though. We need more of that.
It’s under the “I don’t like line”, but I came away from this feeling like I should look into Ruby.
Earlier quoted context omitted.
> OOP is a major con of C++ Not sure what exactly you mean by this, but many people use classes and objects all the time in C++, and see it as a pro rather than a con.
I was quoting the original article, not expressing an opinion on OOP.
Man, if one of Go's pros is "good package manager", I'd hate to see what terrible package managers he's experienced. Seems weird to call out Java package management as a con in comparison. I love Scala's type system, though, I suppose if I didn't have a very good CS degree I'd hate it. I think it strikes a good balance between powerful and usable.
Java doesn't come with a package manager out of the box so most projects seem to go with Maven. If you've tried to understand a project with multiple pom.xml's then for me putting it in the con is a good call.
> 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 serious.
The main platform language used by the target platform requested by the customer.
:
"every PHP programmer is bad at programming, the language is designed to accommodate them with convenient footguns (or faceguns) at every step, and the ecosystem is accordingly bad. No, PHP7 doesn’t fix this. Use a real programming language, jerk." This guy seems like a real open minded person who did his research and shared his opinion after making strong points. /s
yep, stopped reading after this. How can this be objective if you think that everyone is a "bad" programmer that uses this or that language, wtf. Pros for PHP could be, it's templating capabilities with HTML, easy to use DB interfaces and the entanglement with the web/HTML/web-server in general. Nowadays you don't really write these kinds of apps anymore where your backend returns whole HTML Pages but that doesn't me…
Of course, this comes at a price. But saying PHP has no pros is quite subjective