Live data from Hacker News

Duetto: a C++ compiler for the Web going beyond Emscripten and Node.js

allievi.sssup.it

61–63 of 63 posts

Re: Duetto: a C++ compiler for the Web going beyond Emscripten and Node.js

#61
post #46

Earlier quoted context omitted.

Pray tell us, where does C++ need to be? All C++ programmers who I have talked to welcome most things in C++11. It simplifies their C++-code in many ways. As an example: specifying how to capture variables was something they were already dealing with when writing functors manually, now they have a shorthand syntax for it. As for the reason why non-C++ programmers don't like C++, perhaps you are in a better position t…

> Is there a book that teaches best practice C++11 without teaching any of the old cruft? http://www.stroustrup.com/4th.html

This might sound like an odd question, but what font are the code examples in?

I had an older version of the book that had all the code examples in a proportional italics font and it was some of the toughest reading I have done.

Re: Duetto: a C++ compiler for the Web going beyond Emscripten and Node.js

#62
post #46

Earlier quoted context omitted.

> Is there a book that teaches best practice C++11 without teaching any of the old cruft? http://www.stroustrup.com/4th.html

This might sound like an odd question, but what font are the code examples in? I had an older version of the book that had all the code examples in a proportional italics font and it was some of the toughest reading I have done.

The preview at http://www.amazon.com/The-Programming-Language-hardcover-Edi... shows a proportional dark blue font, with comments in italics, at least in the paperback edition (is color printing that cheap nowadays?)

The blue looks problematic on screen. I don't remember having problems with the font in the print edition.

Re: Duetto: a C++ compiler for the Web going beyond Emscripten and Node.js

#63

Earlier quoted context omitted.

"I bet with the currently developing standard (C++11, C++14) more people will start loving C++ again" I doubt it. C++11 takes C++ even further from where it needs to be. Every high-level feature is bogged down by low-level annoyances. Do you capture variables by value or by reference? Do you need a weak pointer to break this cycle, or can you use a weak pointer somewhere else (or maybe just not both with smart pointe…

Pray tell us, where does C++ need to be? All C++ programmers who I have talked to welcome most things in C++11. It simplifies their C++-code in many ways. As an example: specifying how to capture variables was something they were already dealing with when writing functors manually, now they have a shorthand syntax for it. As for the reason why non-C++ programmers don't like C++, perhaps you are in a better position t…

> As for the reason why non-C++ programmers don't like C++, perhaps you are in a better position to say.

As an ex-C++ programmer who did in fact do a large-scale web application deployment in C++ back in '99, and who used to do template meta-programming for fun:

It's too verbose.

C++11 does go some way to alleviate that, and might slow the number of people leaving C++, but it's unlikely to bring many people back, as the performance difference matters less and less, and the performance of language implementations for the languages people have jumped ship for (Ruby in my case) keeps getting better, narrowing the gap (and we already decided we could tolerate the much larger performance gaps of the past when we left in the first place).

Post reply on HN