4 ms·

All of your points are completely valid today. I would come back in 5 years and see that probably all of those are achievable by the browser and Javascript. Eg

by marquis 13y ago

All of your points are completely valid today. I would come back in 5 years and see that probably all of those are achievable by the browser and Javascript. Eg: >1) Anything low level hardware (reading data via USB, or pushing data into HDMI, for instance) I would expect that a Nexus device can do Chromecast from browser screen, if not today then soon. >2) Interacting with ANY hardware that's not explicitly supported by Javascript. Try creating an HTML5/JS scanner app. You mean like, taking a photo and processing it? You can do that right now. >3) Writing super-fast CPU-specific code, think Assembly language. That's the reason there are no HTML5 apps of the Photoshop caliber Yet, agreed. But soon - only CPU is slowing it down, not the technology. >4) Disk access. Try creating a Javascript-based antivirus. Or an app that watches for changes in a certain directory. There won't be a filesystem as we know it. The 'cloud' and browser-accessible storage will be all we need. >5) Internal network access. Try writing a JS app interacting with your localhost or TCP/IP or UDP. Sockets, it's possible now.

ye 13y ago
> I would expect that a Nexus device can do Chromecast from browser screen, if not today then soon. No, that's not what I meant. Pushing any data into HDMI, controlled by the app, not the screencasting. > You mean like, taking a photo and processing it? You can do that right now. No, I mean connecting to a scanner, scanning a document. You can't do it now. And don't tell me taking a snapshot with a built-in camera is the same thing > There won't be a filesystem as we know it. The 'cloud' and browser-accessible storage will be all we need. Sorry, I wasn't aware you could predict the future, and I thought we were talking about now. > Sockets, it's possible now. No, your JS app can't access the internal network, unless you expose it to the internet with TCP/IP. Sockets only let you connect to public servers. And no UDP (at least not explicitly).
- marquis 13y ago
  >I thought we were talking about now. Ah well, I was talking about the future. You're correct about the above you mention, and regarding sockets I was of course referring to TCP/IP. I'm keeping an eye on the Jolla/ChromeOS/FireFox OS types, more than iOS as I think there will be significant changes to allow the above and more.

by marquis 13y ago

ye 13y ago

> I would expect that a Nexus device can do Chromecast from browser screen, if not today then soon. No, that's not what I meant. Pushing any data into HDMI, controlled by the app, not the screencasting. > You mean like, taking a photo and processing it? You can do that right now. No, I mean connecting to a scanner, scanning a document. You can't do it now. And don't tell me taking a snapshot with a built-in camera is the same thing > There won't be a filesystem as we know it. The 'cloud' and browser-accessible storage will be all we need. Sorry, I wasn't aware you could predict the future, and I thought we were talking about now. > Sockets, it's possible now. No, your JS app can't access the internal network, unless you expose it to the internet with TCP/IP. Sockets only let you connect to public servers. And no UDP (at least not explicitly).

marquis 13y ago
>I thought we were talking about now. Ah well, I was talking about the future. You're correct about the above you mention, and regarding sockets I was of course referring to TCP/IP. I'm keeping an eye on the Jolla/ChromeOS/FireFox OS types, more than iOS as I think there will be significant changes to allow the above and more.