Chrome Is The New C Runtime • Hacker News Board

Re: Chrome Is The New C Runtime

#21

Post by sanjeevr » Fri, Jan 17, 2014, 11:14 PM UTC

snirp wrote: post #14

sanjeevr wrote: post #12

Hi 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?

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

#22

Post by dded » Fri, Jan 17, 2014, 11:15 PM UTC

steveklabnik wrote: post #4

I'm posting this from a Chromebook Pixel, which I use for all of my development. No crouton, just stock ChromeOS. This movement is really interesting to me. If I could clone myself, I'd be working on an exokernel in Rust that just exposes a V8 VM, and uses a DOM implementation as the native drawing interface. Processes == tabs... Of course, there's higher level work that needs to be done to expose more of the machine…

Have you any experience with VNC clients on ChromeOS? If so, what's the performance like?

I found the following, which mentions Chrome Web Browser, is that equivalent for the sake of applications? https://chrome.google.com/webstore/detail/vnc-viewer-for-goo...

Re: Chrome Is The New C Runtime

#23

Post by swah » Fri, Jan 17, 2014, 11:15 PM UTC

sanjeevr wrote: post #12

Hi 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

#24

Post by randallu » Fri, Jan 17, 2014, 11:15 PM UTC

Chromium 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?

Re: Chrome Is The New C Runtime

#25

Post by nilsbunger » Fri, Jan 17, 2014, 11:17 PM UTC

alexhutcheson wrote: post #20

Just a heads up, Web of Trust has this sited rated very poorly[1], ostensibly for spam. As a result, any users with the Web of Trust browser extension installed are shown a Big Scary Warning that they must click through before seeing the site's content. The warning is based on one review, and doesn't seem accurate in this case, so this might be something to try to get resolved. [1] https://www.mywot.com/en/scorecard/…

We asked them to review it a few days ago. It's from before we owned the domain. Thanks for the heads-up.

Re: Chrome Is The New C Runtime

#26

Post by [deleted] » Fri, Jan 17, 2014, 11:18 PM UTC

[deleted]

Re: Chrome Is The New C Runtime

#27

Post by mwfunk » Fri, Jan 17, 2014, 11:19 PM UTC

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 license(s) the code they are using is under and what the terms of those licenses are. Just because it's open source doesn't mean you can just do whatever you want with it; even less restrictive licenses like BSDL might have conditions like the advertising clause, and you should always be aware of any copyrights in the code and be sure to preserve them.

That said, I'm sure the Chromium source is a great resource- just a strange and important omission from the article.

I would also suggest that anyone looking for a platform-independent runtime check out APR (Apache Portable Runtime): http://apr.apache.org. It's lower-level than some of the Chromium libraries mentioned in the article (it would be equivalent to the "base libraries" block in the "Chrome Development Platform" figure), but sometimes that's all you need. Plus, it's already designed as a library for other applications to use, there's no need to repurpose anything like you might have to do with the Chromium sources.

Re: Chrome Is The New C Runtime

#28

Post by steveklabnik » Fri, Jan 17, 2014, 11:19 PM UTC

dded wrote: post #22

steveklabnik wrote: post #4

I'm posting this from a Chromebook Pixel, which I use for all of my development. No crouton, just stock ChromeOS. This movement is really interesting to me. If I could clone myself, I'd be working on an exokernel in Rust that just exposes a V8 VM, and uses a DOM implementation as the native drawing interface. Processes == tabs... Of course, there's higher level work that needs to be done to expose more of the machine…

Have you any experience with VNC clients on ChromeOS? If so, what's the performance like? I found the following, which mentions Chrome Web Browser, is that equivalent for the sake of applications? https://chrome.google.com/webstore/detail/vnc-viewer-for-goo...

I don't use VNC, so I can't give you any advice, sorry :/

Re: Chrome Is The New C Runtime

#29

Post by yeureka » Fri, Jan 17, 2014, 11:23 PM UTC

This is interesting. Ideally, if the rendering and audio parts are of high performance enough, it could be used as platform abstraction for game development.

Re: Chrome Is The New C Runtime

#30

Post by nonane » Fri, Jan 17, 2014, 11:24 PM UTC

zwieback wrote: post #18

sanjeevr wrote: post #12

Hi 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?

Simple sample app would be great for the next post.

I second this. Would love to see an actual app skeleton that links with Chromium's sources.