5 ms·
The best thing that has happened in the last years is not having to depend on C++ anymore Good changes, but too little, too late. Of course, we still depend o
by raverbashing 12y ago
The best thing that has happened in the last years is not having to depend on C++ anymore
Good changes, but too little, too late.
Of course, we still depend on it, but for an ever smaller set of use cases. Do what you have to do and "get out of there" as fast as you can to your favourite language.
- 4ad 12y agoAgreed. Many bad trends emerged in the industry in the last decade, but today I am happy I can afford not to write C++ anymore. And yes, I did say afford there.
- general_failure 12y agoExcellent wording. My employer cannot afford my team to write c++ either. It takes way too long to yeah each person the language features. C++ is awesome for seasoned developers but it tak s years to get there. Cannot wait for rust.
- progman 12y ago> Cannot wait for rust. Yes, Rust looks VERY promising.
- progman 12y agoThe examples remind me again why I turned away from C++ some years ago. In the first years of C++ it was real joy to write software in it but now the syntax seems to be much more useful for obfuscation rather than maintainability. Funny: When C++ began Ada 95 looked like a giant animal. Now Ada 2012 looks small and efficient in comparison although it is more powerful than Ada 95.
- pjmlp 12y agoUnfortunately Ada got relegated for niche areas where safety is of highest importance. System programming languages need OS vendors support to thrive.
- progman 12y agoAda is a general purpose programming language, including systems programming. http://www.ada2012.org http://www.ada2012.org Support is provided by AdaCore for instance: http://www.adacore.com http://www.adacore.com
- pjmlp 12y agoI do know a little bit about Ada, thanks. The point being systems programming languages die if not sponsored by the OS vendors, because they have to fight for mindshare among the so called business languages. In Ada's case, the high cost of development systems, rise of UNIX use in the enterprise, decline of Pascal based languages. All contributed to it being used in its field of origin (avionics) and systems where security and human life are of utmost importance. In Europe there was a rise of Ada projects due to lack of security in the usual C and C++, but these are always specialized projects, like train systems control and such. Not the typical Show HN applications. I would like to see Ada being more used in the industry, but sadly it won't happen.
- progman 12y ago> In Ada's case, the high cost of development systems Not necessarily. http://www.adacore.com/press/gnat-gpl-for-bare-board-arm/ http://www.adacore.com/press/gnat-gpl-for-bare-board-arm/ Look also for the book "Building Parallel, Embedded, and Real-Time Applications with Ada" by McCormick, Singhoff and Hugues. Some prominent embedded engineers wonder why Ada is not used much more: http://www.embedded.com/electronics-blogs/break-points/4008214/Why-aren-t-developers-interested-in-Ada- http://www.embedded.com/electronics-blogs/break-points/40082... > Rise of UNIX use in the enterprise Ada is available for Windows, Linux, OSX and ARM. GNAT/GCC is part of many Linux distros (usually Ada95). You can also download Ada2012 and Ada2014 compilers and tools from Adacore's website. > Decline of Pascal based languages. Ada looks a bit like Pascal but the language is far superior. In my opinion Ada's syntax makes software easier to maintain than C/Java like syntax. Even after years I have no problem to read into Ada code. C++ code can be difficult to read just after a short time. I think the real reason of Ada's decline is that it requires a lot of discipline of the developer. The same kind of discipline is required in Haskell. You cannot just sit down and code. You have to think a lot about your design before you hit the first key. Most developers don't like this, they want quick (and dirty) solutions, and they get it with C and C++.
- pjmlp 12y ago> Do what you have to do and "get out of there" as fast as you can to your favourite language. Which happens to be C++, until OS vendors support another one on their SDKs. So until Ada, Rust, D, Swift, .NET Native or something else get such a position, C++ it is.
- mwcampbell 12y agoFor what types of applications do you think it's actually important to use the native language of the OS? After all, non-native languages can have bindings for the OS APIs. In your opinion, what are the drawbacks of mostly avoiding C++ and using one's favorite language, as the GP said?
- pyrois 12y agoIf you're developing a fairly complex library for things such as image processing, machine learning, numerics, linear algebra, etc., then I think that C/C++ is the way to go. Most languages have some sort of FFI to interact with C, many are even designed explicitly to work with C (such as Cython). C++ is in a similar situation (though compiler support on esoteric processors such as DSPs is still not quite there yet), and it's fairly easy to get a C-compatible API. If you write your library in Perl, guess what, only people writing Perl will use it. If you write it in Java, well, maybe the Scala folk will wrap it up, or the Jython folk, but you won't get any people writing in Ruby to use it. If you write it in C++, you can provide efficient bindings to any of those languages. For an example, look at FFmpeg or ImageMagick. They are libraries that just _won't die_, no matter how hard people have tried. My god, ImageMagick was written in 1987, and it now has Haskell bindings[0]! The only way to get that sort of longevity (and old code is good code, after all [1]) is to write in language that will outlast the ups and downs of the language or framework du jour, and C and C++ have proven to have that staying power. Yeah, they're terrible; I hate them. But there is a reason to use them. [0] http://hackage.haskell.org/package/imagemagick http://hackage.haskell.org/package/imagemagick [1] http://www.joelonsoftware.com/articles/fog0000000069.html http://www.joelonsoftware.com/articles/fog0000000069.html
- pjmlp 12y ago- Not able to use the OS vendor tooling which only support the official languages - Another layer to debug (FFI) - Possible loss of performance when crossing the FFI barrier - Loss of productivity, because that cool API isn't available and so one has to write it - Writing drivers, daemons/services, OS plugins, ... One of the reasons I moved from Turbo Pascal to C++, when I started coding on Windows 3.0, was being fed up to write binding libraries by myself. Although I really enjoyed Turbo Pascal back then.
- Ragnarork 12y agoThis is still a matter of opinion. My favorite language is still C++. This is of course personal preference, but also mostly because I realized (and it seems to me that some people haven't, just go around and ask what is C/C++, and people will tell you it's one language...) that C++ is not just anymore "C with classes", and the fact there is C-ish, or even just bad C++ code out in the wild doesn't make the language bad in itself (it can still be less appropriate/completely irrelevant for some applications, which is fine).
- raverbashing 12y agoTrue, with STL and the recent changes the "C with classes" thing gets more distant. But sorry, I don't miss the includes, the huge class hierarchies, the template madness, etc C++ is good if you stick to a strict code standard and don't let people "go crazy" with it. But the thing is that good languages end up limiting the amount of "bad code" that naturally emerges. (Java does it through lack of flexibility and enforcement, I prefer the Python and Go way)