3 ms·
I bet I could use it for an hour and come up with a long list of why I would hate that environment. But off the top of my head: Not all developers work on pro
by jjnoakes 10y ago
I bet I could use it for an hour and come up with a long list of why I would hate that environment.
But off the top of my head:
Not all developers work on projects which can be hosted by a third party company and require always-on super-stable internet access.
- tuxracer 10y agoWeb apps can work completely offline if the developer adds support https://codelabs.developers.google.com/codelabs/offline/ https://codelabs.developers.google.com/codelabs/offline/ Not sure why this misconception about web apps requiring "always-on super-stable internet access" persists when this technology has been available for quite some time (in the form of App Cache before Service Workers)
- stephenr 10y agoIt may be possible to host the ide component locally in the browser, but that doesn't give you the execution environment (ie you can't run a vagrant image or in the case of a server based ide, a container, in a browser)
- tuxracer 10y agoThere is a way to do this actually via https://copy.sh/v86/ https://copy.sh/v86/ Although this is straying from the main point. There are certainly things native apps can do that web apps cannot. But requiring "always-on super-stable internet access" is absolutely not required for web apps. This hasn't been true for at least 5 years now. It also seems to be the most often repeated (completely inaccurate) limitation about web apps. There are certainly limitations. Let's talk about the real limitations, not the mythical ones.