Curious if anyone has gotten a remote extension (MS or otherwise) working on vscodium. I tried but could never get it working so I reluctantly switched to vscode proper.
Web IDE Beta
191–200 of 258 posts
Re: Web IDE Beta
#192Earlier quoted context omitted.
JetBrains' fundamental market position is that companies pay per seat for an it-just-works IDE. So if anything, IDE-in-browser, where code is executing on a hosted backend, is even more aligned with this. The real question is whether they can execute on this. Will they be able to replicate years of VS Code's work on providing UI extensibility without sacrificing performance, with a team that historically had been JVM…
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?
> Am I missing something?
Fleet (https://www.jetbrains.com/fleet/).
They're building a distributed IDE. A web-based UI would fit nicely into their new roadmap.
Re: Web IDE Beta
#193Earlier quoted context omitted.
I've seen Fleet in my JB Toolbox, but haven't touched it yet. But it is the obvious move. All the current JB IDEs are built upon the same basic IntelliJ platform, anyway. It's "only" a matter of restructuring all that to have only one IDE where you can opt-in to support specific languages and now you have something like VSCode.
You already have that with Idea, with a few exceptions (C/C++, and possibly C#). You can install the Python plugin & friends -> PyCharm You can install the Go plugin -> Goland Etc
This is only for most surface level features. The Idea PyCharm plugins lack scientific mode for example.
Re: Web IDE Beta
#194Earlier quoted context omitted.
JetBrains gives products in very niche areas. WebStorm for JS, PHPStorm for PHP, RubyMine for Ruby, and GoLand for GoLang. Visual Studio Code is used by people who like to many languages, but more specifically for someone who's job is to work with JavaScript then WebStorm is much better. JetBrains could very well combine all these IDEs into one, but then again think about the amount of space and data of this new IDE.
> Visual Studio Code is used by people who like to many languages I don't like these language. I'm forced to write them. I didn't ask for terraform, typescript, CSS, HTML, yaml, xml, JSON, and everything else. > for someone who's job is to work with JavaScript then WebStorm is much better It's never been my experience that a full IDE is better for dynamic interpreted languages. Maybe if you're used to that from writi…
Have you ever tried .NET?
Re: Web IDE Beta
#195Earlier quoted context omitted.
It's not. VSC is a packaged version of the open-source code with proprietary bits added. Integration with the plugin marketplace, telemetry, etc. VSCodium does not have that. In addition, a lot of the good language plugins are proprietary, like PyLance and the C# plugin.
> Integration with the plugin marketplace This is a big one. A lot of the value of VSCode comes from its plugins, and M$ doesn't allow VSCodium to access them.
Re: Web IDE Beta
#196Earlier quoted context omitted.
> If someone came out with a free, cross-platform, attractive text editor that was a native executable and got critical mass going with a plugin ecosystem, then VS Code would fall out of fashion within a year. Well yeah, there's the problem. This isn't an easy task, it has never been done before.
It's been done with Vim and Emacs, among others. Full desktop GUI versions, in addition to the original terminal-based form. It just hasn't been done RECENTLY... with an editor that is visually attractive, and uses modern keyboard conventions rather than arcane keystroke DSL's that are inaccessible for the masses. But that's just a matter of project philosophy, not technical limitations with what's doable.
This is definitely the first time I've ever seen the adjective 'attractive' applied to either vim or emacs.
Re: Web IDE Beta
#197Earlier quoted context omitted.
The way that VS Code is spreading, and the stranglehold Microsoft has on development and direction of the product, give me very strong IE4/5/6 vibes. I really hope some of the open source alternatives that aren't corporation-controlled gain traction over the next year.
> I really hope some of the open source alternatives that aren't corporation-controlled gain traction over the next year. Shout out to CodeLite. https://codelite.org/ https://en.wikipedia.org/wiki/CodeLite
I randomly typed in the word "lines" into a pacman search and discovered the existence of the lines IDE [0]. Never heard it mentioned anywhere before. I know nothing about it, I was just experimenting with pacman search out of boredom.
Re: Web IDE Beta
#198Earlier quoted context omitted.
Aside from the newly introduced Fleet the other commenter pointed out, Jetbrains' IDEA Ultimate can include all the functionality of all the individual niche products (via plugins), so you could just use a single Jetbrains IDE for most any language/flow you choose. I personally kind of like to keep them separate so I can keep different envs configured the way I most often use them, but you could just use the single I…
I thought it was weird when Jetbrains started to split up their product into language-specific products, but given how many people say they use WebStorm or an other niche product, and who say they use multiple, I can't blame Jetbrains - I think that in hindsight it was a great business move. An expensive "I can do everything" product has a higher barrier to entry than a specialized product. Personally I've been using…
> I thought it was weird when Jetbrains started to split up their product into language-specific products
They're for different audiences; the hurdle of trying to explain to a JS dev "yeah, I know when it starts up it asks for a Maven/Gradle/JVM, but just ignore that and open a directory after you install the following 8 plugins" is bad DX. As others have said, the standalone products are not feature parity with the IJ plugins. I have no idea why that is, or what incentives are driving that, but for the time being it is what it is
Re: Web IDE Beta
#199Earlier quoted context omitted.
Parents complaint is that paying lip service to FOSS is exactly the "extend" part of "Embrace, Extend, Extinguish". A mantra that was famously internally coined at Microsoft[0], and was found during anti-monopoly proceedings. As such they will always be looked at skeptically when adding proprietary things to open source things. [0]: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
This doesn't really match since the "Embrace" part is different. The classic formula was "embracing" an established standard, making proprietary extensions to that standard, then using the adoption of those proprietary extensions to extinguish the original standard's market share. In this case, Microsoft didn't embrace an existing code base or standard, they made one and open sourced it. What would the analagous "ext…
> What would the analagous "extinction" bere here?
Look at Android and how it is almost impossible to de-Google it for a live demonstration.
(I don't think there is a market for developer tools, though.)
Re: Web IDE Beta
#200Earlier quoted context omitted.
Parents complaint is that paying lip service to FOSS is exactly the "extend" part of "Embrace, Extend, Extinguish". A mantra that was famously internally coined at Microsoft[0], and was found during anti-monopoly proceedings. As such they will always be looked at skeptically when adding proprietary things to open source things. [0]: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
This doesn't really match since the "Embrace" part is different. The classic formula was "embracing" an established standard, making proprietary extensions to that standard, then using the adoption of those proprietary extensions to extinguish the original standard's market share. In this case, Microsoft didn't embrace an existing code base or standard, they made one and open sourced it. What would the analagous "ext…
It is quite easy to see that the "embrace" is to release a core into the open source world. They embraced the idea of open source and released something, they extended the user base into the world of the non-free option. The thinking is if they can get a critical mass of folks onto the option that is non-free, they will extinguish the free option by no longer supporting it.
And this is not much different from the things they did this with back in the day. Used to, you wouldn't target open source, as much as you would student audience. The battle used to be more over what corporate workforces would want and use. The open source development scene changed that a bit. Though, it is kind of... interesting to consider how many tools and ideas have been lost in that process.