News for hackers. Stuff that matters.
Re:Show HN: Visual Studio Code for ARM, submitted to core by brunoluiz on Tuesday April 18, 2017 @07:43AM (#14138012)
While VS Code will support ARM, paid solutions such as Sublime Text aren't. This is why I love FOSS.
Re:Show HN: Visual Studio Code for ARM, submitted to core by bhouston on Tuesday April 18, 2017 @08:20AM (#14138198)
VS 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?

Re:Show HN: Visual Studio Code for ARM, submitted to core by gruez on Tuesday April 18, 2017 @09:55AM (#14138802)
>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.

Re:Show HN: Visual Studio Code for ARM, submitted to core by bhouston on Tuesday April 18, 2017 @11:48AM (#14139818)
Atom and VS Code are copies of the successful Sublime app. Although it may be more accurate to say that VS Code is a copy of Atom and Atom is a copy of Sublime.
Re:Show HN: Visual Studio Code for ARM, submitted to core by jsmthrowaway on Tuesday April 18, 2017 @12:43PM (#14140351)
Which ones copy TextMate and Notepad++ in this scenario?
Re:Show HN: Visual Studio Code for ARM, submitted to core by sigzero on Tuesday April 18, 2017 @01:40PM (#14141001)
Textmate yes, Notepad++ not a bit.
Re:Show HN: Visual Studio Code for ARM, submitted to core by zackbrown on Tuesday April 18, 2017 @10:23AM (#14139018)
What's more, the VS product line predates Sublime Text by over a decade.
Re:Show HN: Visual Studio Code for ARM, submitted to core by hibbelig on Tuesday April 18, 2017 @10:49AM (#14139244)
I 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.
Re:Show HN: Visual Studio Code for ARM, submitted to core by zackbrown on Tuesday April 18, 2017 @01:41PM (#14141007)
UX 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.
Re:Show HN: Visual Studio Code for ARM, submitted to core by bhouston on Tuesday April 18, 2017 @01:51PM (#14141113)
As 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.
Re:Show HN: Visual Studio Code for ARM, submitted to core by zackbrown on Tuesday April 18, 2017 @02:26PM (#14141466)
> 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.

Re:Show HN: Visual Studio Code for ARM, submitted to core by betageek on Tuesday April 18, 2017 @12:04PM (#14139955)
Interesting 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.
Re:Show HN: Visual Studio Code for ARM, submitted to core by rodorgas on Tuesday April 18, 2017 @10:46AM (#14139211)
> 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.

Re:Show HN: Visual Studio Code for ARM, submitted to core by nilliams on Tuesday April 18, 2017 @12:10PM (#14140002)
Sublime, 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.
Re:Show HN: Visual Studio Code for ARM, submitted to core by rodorgas on Tuesday April 18, 2017 @09:05PM (#14144608)
A custom license may forbid nagware removal. It would make forks impractical while granting SublimeHQ benefit from contributions.
Re:Show HN: Visual Studio Code for ARM, submitted to core by carussell on Tuesday April 18, 2017 @02:42PM (#14141614)
Just 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.
Re:Show HN: Visual Studio Code for ARM, submitted to core by dragonwriter on Tuesday April 18, 2017 @03:52PM (#14142285)
> It's not well known, but GPL more or less protects nag screens

What provision of the GPL, specifically, provides this supposed protection?

Re:Show HN: Visual Studio Code for ARM, submitted to core by carussell on Tuesday April 18, 2017 @07:18PM (#14143949)
Sections 1 and 2 of GPLv2.
Re:Show HN: Visual Studio Code for ARM, submitted to core by dragonwriter on Tuesday April 18, 2017 @07:47PM (#14144164)
Section 1 is the verbatim copies permission, section 2 merely requires your derived version to have an appropriate copyright notice (and the creator of a derivative work is the copyright owner of the derivative), not to preserve the pre-existing copyrigut notice of the original one, much less to include any other information besides a notice of copyright that might appear in a pre-existing a "nag screen".

So, no, it doesn't protect nag screens at all.

Re:Show HN: Visual Studio Code for ARM, submitted to core by carussell on Wednesday April 19, 2017 @10:11AM (#14147809)
I'm not sure why you think your slanted summary is a better argument than what the license actually says. If it supports your position, just point to the text of the license itself where that support comes from. Your words are not an adequate substitute.

> Section 1 is the verbatim copies permission, section 2 merely requires [...]

To clarify an important point of fact: Section 2 is additive. It builds upon the terms enumerated in Section 1. You only get to exercise the right to make modifications if you satisfy the extended provisions from Section 2 on top of your obligations from Section 1. To wit, Section 2 allows you to "distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions".

That is, you cannot perform actions under Section 2 without also fulfilling your obligations from Section 1.

> not to preserve the pre-existing copyrigut notice of the original one

This is not true. It would be true if the GPLv2 required that you merely maintain some form of fair attribution. But that's not what it says.

You are obligated under Section 1 to "keep intact all the notices that refer to this License". (And you are not allowed under Section 2 to shirk your obligations from Section 1. See above.) If the original author includes a notice as simple as, "This copy of Sublime Text Community Edition is based upon Sublime Text Pro and made available to you under the GNU General Public License, version 2", then no provision of the license permits you to distribute modifications where you've replaced the notice with one of your own, even if you think it's fair. Anyone getting away with this today is only able to do so in cases where the original author is looking the other way because the downstream modifications are more or less in the spirit of the license, even if they aren't technically following it to the letter.

That GPLv2 allows for this should not even be surprising—it's similar to the philosophy behind including provisions for Invariant Texts in the GFDL. It's only if you view things through the hazy lens of history where licenses like Creative Commons have shown up and maybe distorted one's general understanding that this comes off as unexpected.

Finally: I constantly find that I want to kick myself when I get involved in licensing discussions here that deal in anything other than the most blunted, obvious aspects of FOSS licensing. So this will be my last comment in this thread.

Re:Show HN: Visual Studio Code for ARM, submitted to core by sangnoir on Wednesday April 19, 2017 @06:22AM (#14146714)
> No one would be able to patch and distribute modified versions for the express purpose of disabling the nag screen without violating the license

This is wrong - the GPL only requires that the source code of the modified versions be made available. The nag text could be put in the license notice text itself (the original license should be preserved in modified versions), but that might change the license from GPL to GPL-based/GPL-compat. IANAL.

Re:Show HN: Visual Studio Code for ARM, submitted to core by nilliams on Tuesday April 18, 2017 @03:50PM (#14142268)
Nice 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.

Re:Show HN: Visual Studio Code for ARM, submitted to core by carussell on Tuesday April 18, 2017 @07:26PM (#14144008)
Sure. 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.

Re:Show HN: Visual Studio Code for ARM, submitted to core by nilliams on Wednesday April 19, 2017 @04:04AM (#14146212)
Huh, I started that premise and I'm continuing to argue it. You might be thrown off by HN's busted comment nesting.

If my last comment wasn't clear, I think the dent in revenue would be considerable for fully open-sourcing Sublime as it would make it too easy for people to patch out the nag.

Re:Show HN: Visual Studio Code for ARM, submitted to core by carussell on Wednesday April 19, 2017 @09:00AM (#14147371)
Distributing those patches would be against the license. I'm looking for any indication that the set of people willing to a) download a patch; and b) use tools to apply it on their own; and c) build it; and d) be unmoved about the ethical implications of the whole thing; is at all significantly larger than the set of people willing to open a hex editor to poke at some bytes for the same purpose.

> Huh, I started that premise and I'm continuing to argue it. You might be thrown off by HN's busted comment nesting.

I'm asking that your argument is internally consistent—that you're not trying to advance some thought, and the backtrack to a position where you advance another one that's at odds with the original. I don't see how this suggests that there's confusion about how to read threaded comments.

Re:Show HN: Visual Studio Code for ARM, submitted to core by wazanator on Tuesday April 18, 2017 @08:41AM (#14138318)
One 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.
Re:Show HN: Visual Studio Code for ARM, submitted to core by swah on Tuesday April 18, 2017 @08:05AM (#14138120)
Sublime is like 2 people. VSC is an open source project with a strong backing from Microsoft.
Re:Show HN: Visual Studio Code for ARM, submitted to core by headmelted on Tuesday April 18, 2017 @08:08AM (#14138137)
I 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 :-)

Re:Show HN: Visual Studio Code for ARM, submitted to core by swah on Tuesday April 18, 2017 @08:19AM (#14138194)
Yep, but you are building on top of stuff built by paid people, I guess.
Re:Show HN: Visual Studio Code for ARM, submitted to core by pingec on Tuesday April 18, 2017 @09:10AM (#14138497)
I 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).