, the only reason it survived its early days is because it offerred an easy way for Java to access the DOM and Netscape couldn't be bothered to code that bridge again. During the first Browser Wars it got pulled from side
, while simultaneously getting no real respect from anyone. But it survived, and established a niche for itself.
A New Hope
The browser was becoming interesting again, and Firefox was giving Internet Explorer a run for its money. One thing lead to another
and the Browser Wars begun again, they had.
From that point on, the floodgates broke open. Speed rocketed sky high
Jeff Atwood, aptly and with tongue set firmly in cheek, put it thus:
Not. quite. yet.
Meanwhile in hardware-land
by 2020. Choose your grain of salt, but that's 6.5 devices per man woman and child on the planet. Even Paul Graham has hinted at the coming hardware renaissance
and sporting a fantastically healthy ecosystem
Let's build it!
Like Heroku, Resin.io believes pushing code should be as simple as 'git push resin master', but instead of targeting servers in amazon's data centres, Resin.io targets small devices that could be anywhere. It will help you during development on one device, and let you naturally transition to deploying to any number of devices when you're ready. Resin.io takes away DevOps considerations like VPNs, operating systems, cross-compilers, monitoring, network security, and so much more, leaving you to focus on things that bring value to your users: The application and the device.
If you feel what we feel, you can:
- Join the JS on Devices movement, hack on devices, organise your local community.
- Enter your email right below to get a Resin.io Beta invite when we're ready.
And of course, if you enjoyed this article, tell other hackers, follow us on Twitter
, or come find us on our community chat