Earlier quoted context omitted.
Rust definitely is a good choice, if you can give up inheritance.
Wouldn’t classify Rust as OO though.
He said the opposite
C++: Is It Really a Cruel Joke? (2003)
61–70 of 155 posts
Re: C++: Is It Really a Cruel Joke? (2003)
#62Earlier quoted context omitted.
Anytime I see someone bashing Java/PHP/JavaScript on /r/programmerhumor (reddit) I challenge them to a coding contest. I use the language they just bashed, they use their ideal language. No takers yet. I think, more often than not, language choice is like golf club choice. Different pros have their preferences, but a pro can play a good game with any set of clubs. A novice will blame the clubs for a poor game.
And you can perform carpentry using a big rock instead of a hammer. That doesn't negate any downsides of choosing the rock.
I would say it's more like people are pooh-poohing certain brands of hammers as being inferior to TrendTech Hammers (R) which are "obviously" superior.
Re: C++: Is It Really a Cruel Joke? (2003)
#63I feel compelled to note that this page is from 2003-05-13, so I have no clue how much of its gripes are still valid in 'modern' C++ :)
I wonder how things have progressed from a security/stability standpoint - my OS definitely crashes a lot less, I'm guessing because there is less C in it now...
Which OS? Linux and Darwin are still entirely C in the kernel, I believe. Windows is C++.
Re: C++: Is It Really a Cruel Joke? (2003)
#64Earlier quoted context omitted.
If I had any real complaint about the execution of C++ it would probably just be the backwards compatibility with C. Don't get me wrong: I love C, and also I don't think it would've been possible for C++ to have gained so much relevance so fast had it not started as C with Classes. However, it does feel like a lot of kludges in C++ come from its legacy. Something that often confuses beginners is the sheer number of w…
If people wanted an object-orientated compiled language that didn't interlink with and offer a smooth transition from C, there were already alternatives (e.g. Modula).
The direction C++ went was pretty different from even what would've been considered 'object oriented' at the time. I'd say half of what made C++ special was how much stuff could happen purely at compile time.
Re: C++: Is It Really a Cruel Joke? (2003)
#65I know C++ isn't really dying off, but what is the best platform-agnostic compiled object-orientated language these days? I liked Borland Pascal, and I know Delphi is kind of ticking along, but I'd rather invest in a language that is growing. Swift looks nice but still seems too Apple focused. Don't want to start a war, just open to some tips on the ecosystem..
Native programmer for the last 16 years. D is the one I'm building with because it keeps the "everything is possible" ethos from C++ and has no big agenda.
Re: C++: Is It Really a Cruel Joke? (2003)
#66> There was this Oregon company - Mentor Graphics, I think they were called - really caught a cold trying to rewrite everything in C++ in about '90 or '91. I felt sorry for them really, but I thought people would learn from their mistakes. I've talked to some of the people at Mentor Graphics who were there during that period. The company basically went from #1 in the industry to #3 or so during the course of the C++…
> the hours were normal. What were 'normal' hours for a programmer in the 1990s? Did you guys work 9-5?
Isn't 9-5 still normal now?
Re: C++: Is It Really a Cruel Joke? (2003)
#67The only joke here is somehow this author thinks the success of your project is dependent on the language you pick
Funny how many people believe that language choice influences success. I guess they're all wrong? Sure, there are an uncountable number of other factors, but picking the wrong platform/language can be fatal.
I think it does and it doesn't. It really depends on what your end goal is. Writing a web application? Not sure it really matters much if you use Python/Django, Ruby/Rails, Java/Spring. Just use what you (or the developers) are most comfortable with. Trying to make a game engine for AAA games? Yeah your not going to get away with Ruby or Python.
Re: C++: Is It Really a Cruel Joke? (2003)
#68The only joke here is somehow this author thinks the success of your project is dependent on the language you pick
"Dependent" is a strong word, but tool/job fit is still important. I've personally never grown comfortable enough with C++ to get to a point where, were I to be the one calling the shots, it would ever be my first choice. But I also recognize that it's dominant in certain spaces for a reason. At the same time, I have a lot of sympathy for people who prefer C over C++. There's a lot of cognitive overhead involved in u…
> it's dominant in certain spaces for a reason.
That reason usually is: "no other compiler were available" or "no other choices at the times".
Re: C++: Is It Really a Cruel Joke? (2003)
#69Why do we as developers feel a need to constantly trash the things we don't like? If you don't like something, don't use it. Talk about the things you do like instead.
While I agree that it is good to not always dwell on the negative, there can be a lot of value in pointing out the deficiencies of programming languages.
Some folks will just use a language without thinking about its downsides. If you use language X for a long period of time, you can become blind to areas where it is wasting your time.
Again, I do agree that the tone could often be much more civil, but I would hate for experienced programmers to stop pointing out things that bother them about their programming languages. Much of the time it is not just about personal taste -- it is about real problems with the language that have a real cost.
Re: C++: Is It Really a Cruel Joke? (2003)
#70The only joke here is somehow this author thinks the success of your project is dependent on the language you pick
Funny how many people believe that language choice influences success. I guess they're all wrong? Sure, there are an uncountable number of other factors, but picking the wrong platform/language can be fatal.
Definitely pick the right tool for the right job.
Using C (maybe C++ ?) may be great for micro controllers, a BIOS, a stage 1 bloat loader, OS kernel and device drivers.
If you're writing application software, and probably even server software, you should be using something higher level and a bit more abstracted away from the hardware. Not necessarily by much. But definitely more than C / C++.