So, if we made such a radical change, we’d have to fully restructure the existing sales model and, what’s more, the entire platform architecture. Unfortunately, it’s not feasible right now, mainly because the WebStorm functionality is included in a lot of other JetBrains IDEs. We’d lie if we said that we’d never thought about introducing a community edition of WebStorm. I'm merely pointing out that in client-side web application development, VS Code is eating your lunch, at least as far as public perception goes. Without a WebStorm community edition, like almost everyone else, I'll simply use VS Code in my talks, thus moving students and attendees farther away from JetBrains.įwiw, I have a full, every-tool-included, annual JetBrains subscription, so I'm not saying this to save a few bucks myself. I'll never send them to a non-GA, EAP version and hope that everything is stable enough for them not to stumble because of an unreleased tool. I understand there are ways to work around this, as the answer above shows, but again, that would never be a "trick" I'd recommend to an audience. This represents lost mindshare.Īs someone who does these talks and who is planning to post some online videos and training, I simply cannot expect someone to shell out money for a tool to use in the class or to follow along in a presentation. In fact, I'm not sure I've ever seen a conference talk or YouTube tutorial that used WebStorm. I can't count the number of online classes, YouTube videos, conference demos, and other presentations I've seen over the last year that used the free VS Code IDE.
I think it's a mistake not to have a community edition for WebStorm.
0 kommentar(er)
