Because the 2nd approach adds little value (latency isn't critical here) and feels unnecessary, you can safely bet on browsers.
Show this thread
Good take. Files/artifacts are in the cloud, and productive workflows increasingly require advanced cloud integration features. Long term, either you code in the browser, or you code in a local client that behaves for all intents and purposes like a browser.https://twitter.com/juli1pb/status/1423677047168065536 …
45% of respondents believe that the future of the coding environment is VS Code. I strongly believe the future is in the browser.
Your next IDE will be in the browser.
https://twitter.com/juli1pb/status/1422554206074925056 …
https://twitter.com/juli1pb/status/1422554206074925056 …
Show this thread
-
-
-
I've been browser-coding all pandemic. The only real downside is that a laptop screen is small, and Chrome removes extra screen space you could be using for your code. But that's more of a "coding on a laptop" issue.
Show this thread
End of conversation
New conversation -
-
-
I personally use Gitpod (
@gitpod ) which is essentially a VSCode in the browser -
New conversation -
-
-
@Suhail sounds like a task for@MightyApp!Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
For many text editors this is basically already true, given the success of node and electrum.
-
And with V8 there’s enormous potential for “the browser” to do essentially everything. Though lots of growing pains with actually setting up a workable development environment and maintaining personal configuration settings across instances.
End of conversation
New conversation -
-
-
This is essentially a take from the 1990s (for "in the cloud" read "on the server") except in the 1990s, many tech people didn't think there could be any clients at *all* except web browsers. It was unimaginative even back then. Long term, there'll be no such thing as a browser.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It‘s a fallacy that this means the browser will become the point of entry. It only seems plausible because the unmeasurable UX advantages of non-browser based software are hard to quantify. Superior workflows with standalone tools and remote integration won’t ever go away
-
If this was a the case, the Mac would never have been able to return in the 2000s. Computing environments are not simply commodity shells. For productive workflows, native integration matters. Ignoring that throws away significant value
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.