Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Chrome Is The New C Runtime

uncloud (3503903) writes | about 7 months ago


uncloud (3503903) writes "Cross-platform app development is more important than ever. But what about when you need the features and performance of native code, across platforms? And you’re a startup with a small team and impossible deadlines?"
Link to Original Source

cancel ×

1 comment

Sorry! There are no comments related to the filter you selected.

web apps (1)

crutchy (1949900) | about 7 months ago | (#45994505)

TFA seems like a lame plug for another Silicon Valley startup company that I've neither heard of nor care about.

"Web apps are a good solution some of the time (except for that little detail called IE!)."

Developers should largely ignore browser-specific quirks and should focus development on purely standards-compliant code because the only way to coax users into using standards-compliant browsers is for much of the web that they browse to appear "broken" in any non-standards-compliant browser. Any aspect that doesn't appear broken in a non-standards-compliant browser doesn't need any attention from developers anyway because even if it looks a bit different between browsers, as long as the user is happy in their ignorance of the differences then there is no real problem.

As long as the organisation controlling the standards remains objective, standards should be the guiding force in web development. The W3C seems like a positive organisational structure to control standards, as long as it remains under international control. Possibly the biggest threat to the web is organisations like ICANN, which are under direct US government authority.

Web applications (or client-server applications generally) can solve many business problems that are currently addressed by either file-server or stand-alone compiled applications that aren't cross-platform. One simple example is Microsoft Access "applications".

Whilst there are no doubt performance gains from using native code, scripting languages can also take advantage of this ( After all, C code must still be "interpreted" before it can be compiled. The only difference is that compiled programs are executed directly. There is no reason why scripting engines like PHP can't operate in a similar fashion (recompiling only whenever there are changes to the code).

I definitely agree that "Chrome code has been battle-tested like almost nothing else" and that it is a useful baseline for any project that demands large scalability and high reliability and performance. I would only contest that if you're going to use Chromium as the baseline for your own app, why not just use Chromium as the interface to begin with (as in a web app)? At least then you don't have to concern yourself with integration issues and only have to debug your own code and not concerning yourself with possibly breaking perfectly good Chromium features. Also, web standards are fairly well-refined and it would seem like modifying the source of an existing standards-compliant browser would only be necessary if you wished to violate those standards. Performance is important, but spending money on high-performance server and network infrastructure would seem to be more cost-efficient than trying to maintaining high performance clients running custom browser software.

Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>