10 ms·
While VS Code will support ARM, paid solutions such as Sublime Text aren't. This is why I love FOSS.
by brunoluiz 10y ago
While VS Code will support ARM, paid solutions such as Sublime Text aren't. This is why I love FOSS.
- swah 10y agoSublime is like 2 people. VSC is an open source project with a strong backing from Microsoft.
- headmelted 10y agoI should mention that I don't work for Microsoft. I just wanted this for a long time. Although it does speak to the benefits of FOSS in this case I guess :-)
- swah 10y agoYep, but you are building on top of stuff built by paid people, I guess.
- icemelt8 10y agoFOSS is communism
- bhouston 10y agoVS Code is subsidized by Microsoft. Sublime Text is a single guy. FOSS in this case is a big company copying a single individual and destroying their business by doing a better job than that single individual. I'm using VS Code (and I also bought Sublime) but I am a little reserved about championing FOSS here. Maybe if Sublime had gone open source it might be different, but then what would his revenue source be?
- wazanator 10y agoOne could make an argument that you could get enough via a donation subscription service like patreon and offer your backers something extra like a set of plugins or the newest build compiled for their platform.
- gruez 10y ago>FOSS in this case is a big company copying a single individual and destroying their business by doing a better job than that single individual. That's competition for you. Also, I like how you use the word "copying", as if the guy was the original creator of the text editor.
- zackbrown 10y agoWhat's more, the VS product line predates Sublime Text by over a decade.
- hibbelig 10y agoI think VS and VS Code are about as similar to each other as Java and JavaScript. In other words, the names are similar, but everything else is not so similar.
- zackbrown 10y agoUX defines products, not underlying tech. VS & VS Code share default keyboard shortcuts, UI look & feel, Intellisense, refactoring tools, and in-editor debugging. As a long-time, long-ago user of VS, VS Code immediately felt familiar to me. That's no accident.
- bhouston 10y agoAs a long time user of VS.NET and VS before (yes, I started coding a long time ago), VS Code is clearly patterned on Sublime's and Atom.io's UI concepts.
- zackbrown 10y ago> As a long time user of VS.NET and VS before (yes, I started coding a long time ago) ^ Same here. VB5, ASP ("Classic,") FoxPro... up to ASP.NET MVC & C#4.0. Then Sublime was my primary editor for several years after I left the Windows ecosystem for Mac. > VS Code is clearly patterned on Sublime's and Atom.io's UI concepts. It'd be more accurate to say that it's a hybrid of VS & Sublime/Atom's UI concepts. An elegantly executed hybrid, at that. My original (if implicit) claim was simply that VS Code is a member of the VS product line. I stand by that.
- rodorgas 10y ago> if Sublime had gone open source it might be different, but then what would his revenue source be? The revenue would be the same of today. You can sell licenses of an open source software. One might argue that nobody would buy because you can get for free, but it's not different today with the infinite trial.
- nilliams 10y agoSublime, last time I used it, had a nag window every x saves(?) if unlicensed, which I'm sure encouraged a lot of people to pay. I doubt so many users would convert if it was totally open source and they could easily install a nag-free build.
- carussell 10y agoJust because the code might be opened up doesn't mean the nagware would have to go away. One underlooked option is to keep it and release under GPL. It's not well known, but GPL more or less protects nag screens. No one would be able to patch and distribute modified versions for the express purpose of disabling the nag screen without violating the license. The author would be able to sell his or her own builds without the nag screen, just like today.
- nilliams 10y agoNice in theory but in reality, top Google result for 'no nag sublime' would be a snippet of how to git clone and patch out the nag, widely distributed from day one. At least with current ST the 'tutorials' for this tend to involve hex editors or scripts that can be quietly subverted by the author.
- carussell 10y agoSure. And how much of a dent in revenue to the author would this lead to? Keep in mind the context of this conversation is a conjecture that Sublime's nag screen led to purchases out of convenience for the users making those payments (who could've easily patched the binaries but didn't). Disagree with that premise if you want, but if so, clarify that you're doing that.
- betageek 10y agoInteresting that everybody has instantly forgotten TextMate, which was the original inspiration for Sublime, and also suffered from the 'single developer === single point of failure' issues as Sublime.
- pingec 10y agoI wouldn't say you can really compare the two. Sublime Text is different in many ways, not my cup of tea even if it were free. I was using Brackets before and Monaco in the browser and when I saw the VSCode preview I knew that was what I had been waiting for. Of course it helps a lot that Microsoft is behind it as they can spend a lot of resources on polish and features while they also have a strong history in making good tooling (VS).