4 ms·
I’m confused by this comment. Why do they need to move to browser-based JS/TS? Their existing toolchain is all about doing everything in the IDE. (Remote dev e
by theptip 4y ago
I’m confused by this comment. Why do they need to move to browser-based JS/TS?
Their existing toolchain is all about doing everything in the IDE. (Remote dev envs, code review, all of it).
Am I missing something? I haven’t seen anything which suggests they are going down the path you refer to here. A local client they own is their differentiator over the browser, why would they abandon that?
- tomnipotent 4y ago> Am I missing something? Fleet (https://www.jetbrains.com/fleet/ https://www.jetbrains.com/fleet/). They're building a distributed IDE. A web-based UI would fit nicely into their new roadmap.
- theptip 4y agoI dunno, most of the stuff in Fleet looks to me like it benefits from being a native thin-client rather than a browser-based app (e.g. SSH to your remotes, run the language server locally, etc). I can see that a web-UI option could be built atop the "Space-hosted everything" architecture they are putting together, but I don't see any evidence that's actually what their core strategy is, as GP suggested. They spend a bunch of time discussing running things on "Your machine" too, which doesn't sound like a browser-first strategy. As I see it, their secret sauce is building client-side applications that are faster than other companies can build. I just don't see them giving up that performance edge to make a browser-based client their primary strategy.