Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is back in the good old days when C++ didn't have all the crap, and everyone wanted to stay away from doing advanced stuff with STL and RTTI. Linus famously said that Linux is written in C if only to keep away the C++ developers.

Having said that, I used to write tutorials using the old ways as well: http://flipcode.com/archives/Theory_Practice-Issue_06_Event_...

Does anyone love the new C++, and if so, what are their experiences with being on teams that use the full range of functionality? Do you need a language lawyer?



I do enjoy programming in C++11 style. What I like the most is that once you understand the quirks, you would see a lot of opportunities to improve performance but only when necessary (Like using moving semantics if you have to pass a big object through several function calls)

Also STL has improved a lot and I am very happy that I don't need to include a huge dependency such as Boost or POCO just to have a hash table for instance.


This comment represents the my biggest frustration with current programming tools & practices. You shouldn't have to include any libraries. Ever! And you shouldn't have to rewrite some code that does something that's already available and well-written. That, and, if you want to include some functionality, there will be 13,000 versions of the same functionality for you to review before you decide which one to learn and commit to. (And it is easier to write it yourself sometimes.)

There's no reliable way for languages themselves to standardize and aggregate the work that others do. You just hope the language designers are willing to put up a new version, (and that it's a decent one) and they end up doing it ever-so-slowly because it's not automated in any way. Hand-pick and re-roll. There's no metric-based signaling or automated analysis or anything, it's just whatever your experts opine.


"You shouldn't have to include any libraries"

"you shouldn't have to rewrite some code that does something that's already available and well-written"

How are those not contradictions?


You tell the compiler what data type you're trying to use, and it finds a high-performance implementation for you over the internet.


That sounds incredibly safe.


Have you tried it? Or are you just imagining an extremely terrible implementation of the idea so you can write short quips about how bad it must be?


For basically every piece of software I work on this would have horrible security implications. Let me spell it out in black and white: every time someone does a deployment, by default it will download code from the internet and incorporate it into production code. All one would need do is subvert one external code provider and they'd have the ability to inject code into countless production systems at will. How much do you trust github or bitbucket? Would you give them the keys to your business, and your customer accounts?


Compile time never sounded so fun




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: