Chrome Is The New C Runtime
81–90 of 149 posts
Re: Chrome Is The New C Runtime
#82Earlier quoted context omitted.
XULRunner is a good option to build HTML or XUL based apps. We were looking for a great cross platform library for native (c++) apps. With support for OS specific features.
> We were looking for a great cross platform library for native (c++) apps. Isn't that what Qt is for, with the added bonus that it's what Qt is actually for and thus e.g. documented and supported?
If you want a fairly high level, cross platform C++ library, there is no reason NOT to use Qt.
Re: Chrome Is The New C Runtime
#83Earlier quoted context omitted.
> The C++ culture at Google is amazing Yet the C++ code powering downloads was pretty bad and poorly maintained, written, replaced with Go. http://talks.golang.org/2013/oscon-dl.slide#10 For sure there are great C++ programmers at Google, but across the company as a whole?
You're extrapolating the rewrite of a poorly maintained C++ server to mean something about the overall C++ quality at Google? I fully concur with haberman about the state of C++ at Google.
Re: Chrome Is The New C Runtime
#84Google sux, C++ sucks, Go sucks and you people suck.
Re: Chrome Is The New C Runtime
#85Earlier quoted context omitted.
Avoiding exceptions is a worst practice. The guide even admits they're only doing it because they're so far beyond a critical mass of exception-unsafe code that they've lost hope of solving the problem. If the profession ever wants to produce anything reliable in C++, one of the first things that needs to happen is to start treating all unsafe legacy code like toxic waste, marking it clearly, handling it carefully in…
> Avoiding exceptions is a worst practice You say this very matter-of-factly. Many (myself included) do not believe in exceptions, and in C++ where they are poorly implemented, think not using them is best practice. I would summarize, but this 10 year old article I've seen on HN a dozen times does a much better job than I: http://www.joelonsoftware.com/items/2003/10/13.html Error handling is essential, but exceptions…
http://nedbatchelder.com/text/exceptions-in-the-rainforest.h...
Re: Chrome Is The New C Runtime
#86Chrome is more like Java or .NET runtime than C runtime. You can build full blown apps as Chrome packaged apps. Google has not polished it very well. If done well, developers can use it to build apps that run on Windows/Mac/Linux without change.
Re: Chrome Is The New C Runtime
#87Earlier quoted context omitted.
I haven't worked with Chromium, but the main C++ code-base at Google is like this for the most part too (especially the core stuff). The C++ culture at Google is amazing, and proof that large-scale C++ can actually be really nice if you stay within best practices. It takes a lot of effort and experience from a lot of knowledgeable people to craft these practices, but thankfully Google publishes its C++ style guide (…
> The C++ culture at Google is amazing Yet the C++ code powering downloads was pretty bad and poorly maintained, written, replaced with Go. http://talks.golang.org/2013/oscon-dl.slide#10 For sure there are great C++ programmers at Google, but across the company as a whole?
Re: Chrome Is The New C Runtime
#88Earlier quoted context omitted.
> Avoiding exceptions is a worst practice You say this very matter-of-factly. Many (myself included) do not believe in exceptions, and in C++ where they are poorly implemented, think not using them is best practice. I would summarize, but this 10 year old article I've seen on HN a dozen times does a much better job than I: http://www.joelonsoftware.com/items/2003/10/13.html Error handling is essential, but exceptions…
I found this one compelling: http://nedbatchelder.com/text/exceptions-in-the-rainforest.h...
Also I don't personally agree with the idea that exceptions communicate errors better. In his examples, he's taking an error code and converting it to an exception. Obviously all the information needed about that error is conveyed by the code, otherwise this approach wouldn't work.
Wrangling of this information shouldn't be happening in the middle of application logic. The return code should be acknowledged by the recipient so the necessary cleanup can be performed, then it should be piped to a central class in charge of printing/logging errors. Sprinkling these error code conversions all over the place makes things messy and hard to maintain.
Re: Chrome Is The New C Runtime
#89This is interesting. Ideally, if the rendering and audio parts are of high performance enough, it could be used as platform abstraction for game development.
Have you seen the Epic Citadel demo? It's pretty amazing: http://www.unrealengine.com/html5/
Re: Chrome Is The New C Runtime
#90Earlier quoted context omitted.
Does it not freak you out that your laptop was created by a company that makes billions a year learning everything there is to know about you?
Yes, it absolutely does, and I am very much not happy about it. I am the most anti-Google person I know. Unfortunately, it is impossible to live in a world of ideals, and so, I must compromise from time to time. As I mentioned elsewhere, I have another machine with 100% free software that I use for PGP when I need to keep secrets.