3 ms·

Atom could have been Github his expansion. Its final monopoly settlement. A web based IDE so modernly written it would only work on Chromium nightly (for few m

Atom could have been Github his expansion. Its final monopoly settlement. A web based IDE so modernly written it would only work on Chromium nightly (for few months). A business model in which your IDE is in the cloud backed by Github. One private repository for free, public unlimited and after that maybe $0.99 per private repository/IDE-project or something. Synced all across the cloud, responsive, adaptive, buzzwords alike. You log in to atom.io and boom there is your IDE. Partner with Google for Chrome OS. But no, instead we get some poorly optimized, hacky IDE with half of a Sublime Text look-and-feel. In Javascript. On the desktop. This could have been it. They had all the ingredients. Too bad. Maybe in the future.

shadowmint 13y ago
nope. See, web ides have two fundamental fails that no one has figured out yet. 1) your browser context is not isolated; you have other tabs that kill performance, you have browsers you need to restart periodically (dns cache), or die because of dev javascripty things (eg webgl). Restarting your ide all day? yeah, no. 2) no access to local files without a stupid plugin. enough said. There are some not terrible run-your-own-local web ides, but how is that any better than a fat client? Its not a wasted chance; its that what you want currently cant exist in a form that isnt worse than the current solution.
- gbog 13y ago
  3) not using the terminal, which is the best way to have a shell nearby, and the shell with its extensible toolset is necessary for any serious coding task.