He's talking about using bits and pieces of Chromium's infrastructure in other programs, but didn't address open source licensing at all. I haven't looked at it myself, but according to Wikipedia, Chromium's source is licensed under: "BSD license, MIT License, LGPL, MS-PL and MPL/GPL/LGPL tri-licensed code, plus unlicensed files". This is all fine, but anyone using this code needs to make sure they understand what li…
I don't see how it would be different from using any other MIT-licensed code in your project. The Apache License doesn't seem any less restrictive than MIT at first glance? Edit: I assumed the entire codebase was multi-licensed, it looks like you're saying that different parts have different licenses, which does sound like a headache.
Chrome Is The New C Runtime
41–50 of 149 posts
Re: Chrome Is The New C Runtime
#42Re: Chrome Is The New C Runtime
#43Chromium, Gecko and Webkit codebases are huge, they are hard to compile. They are optimised for use in the browsers and nothing else. They are not universal runtimes yet! I like that idea but please don't make it sound like chromium runtime is ready for everybody to use for their projects.
Re: Chrome Is The New C Runtime
#44https://hg.mozilla.org/mozilla-central/file/tip/ipc/chromium
Re: Chrome Is The New C Runtime
#45Hi all, I'm the author of the post. Happy to answer detailed questions on using Chromium as a Dev platform. Any suggestions for a follow-up post?
So, you're not using any of the rendering parts?
Re: Chrome Is The New C Runtime
#46Earlier quoted context omitted.
> 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?
Qt is a higher-level application dev framework with UI support (like MFC but cross-platform). We were looking for lower-level constructs - especially in the networking and P2P areas.
(I haven't used Chromium libs and have no opinion about them)
Re: Chrome Is The New C Runtime
#47Earlier quoted context omitted.
> 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?
Qt is a higher-level application dev framework with UI support (like MFC but cross-platform). We were looking for lower-level constructs - especially in the networking and P2P areas.
Edit: in fact just to highlight how similar it is, the way that QtWebKit works is that it is built on top of these modules in a [hand wavy] similar way that blink is built on top of the chrome development platform (I have hacked on Qt, WebKit, and Chrome).
Re: Chrome Is The New C Runtime
#48Chromium, Gecko and Webkit codebases are huge, they are hard to compile. They are optimised for use in the browsers and nothing else. They are not universal runtimes yet! I like that idea but please don't make it sound like chromium runtime is ready for everybody to use for their projects.
I'm not sure what you mean by "optimized for use in browsers". I can't speak to the other 2, but Chromium is basically a vast collection of C++ cross-platform libraries that can be used in many applications.
Re: Chrome Is The New C Runtime
#49Earlier quoted context omitted.
Are you making bets on Dart or (P)NaCl staying with the platform in the long run?
We aren't relying on Dart. (P)Nacl is a very interesting option which I'm willing to bet will remain with the platform.
Re: Chrome Is The New C Runtime
#50Chromium is _huge_. If I just wanted to use the HTTP library (with tls and spdy) then how would I build just that, and cleanly integrate the build into my own project in a way that won't require constant revisiting every time I update my chromium sources?
You would only link with the net library (and its dependent libraries - like base and crypto)
Edit: to be clear after you get your app up and running with the current version how much time has to be spent on ongoing maintenance down the road?