6 ms·
C# is not different enough to Java to warrant the effort. There would need to be a killer differentiator, something only C# can do, and Java can't. Cross-platfo
by barrkel 11y ago
C# is not different enough to Java to warrant the effort. There would need to be a killer differentiator, something only C# can do, and Java can't. Cross-platform including iOS might be it, but it's a bit of a stretch. I don't see C# displacing Java where Java is currently used in server-side development.
- heartsucker 11y agoLicensing could be enough alone. We're auditing everything we use for license issues because we don't have to get bit by the GPL and have to opensource all our proprietary software. Even if C# was noticeably worse (for some arbitrary definition or worse), if it had a more permissible license, that alone could draw people to it. (Note: I don't know anything about the Java / C# licenses. This is just talking in general.)
- jimktrains2 11y ago> get bit by the GPL and have to opensource all our proprietary software The tone here sounds very angry. You aren't "bit" by the GPL, you choose to participate in the usage of the license and the community of code that comes with it. It's not some unknown, nasty thing you need to constantly defend yourself against (as implied by "being bit" like it's a dog you need to watch out for everywhere). "We're auditing everything we use for license issues because we activly choose not to participate in the GPL community and would rather abuse and profit from other people's good will" is closer to realitiy
- coldtea 11y ago>The tone here sounds very angry. You aren't "bit" by the GPL, you choose to participate in the usage of the license and the community of code that comes with it. It's not like you had a _choice_ if there's software you want to use and it's only available as GPL. You'd have only chosen if there were 3-4 license options for the same software, and you went with GPL willingly.
- pdonis 11y ago> It's not like you had a _choice_ if there's software you want to use and it's only available as GPL. Sure you do; if you don't want to accept the GPL license terms, you can write your own software that fulfills whatever function you wanted the GPL code for.
- nsgi 11y agoYou also have the option to not use the software, if it's software you want, not need.
- st3v3r 11y ago"It's not like you had a _choice_ if there's software you want to use and it's only available as GPL." Sure you do. Write it yourself.
- coldtea 11y agoNot much of a choice, if one involves: 1) begrudgingly adopting a licence you don't like or want over: 2) re-creating man years (or decades) of effort to reproduce a certain project Especially if you lack the programming skills or money, it's not a choice at all -- you only have one option. So in those cases you "don't chose GPL" -- you chose the project you want to use, AND have to necessarily suffer GPL too because of that choice.
- cyphar 11y agoHave you considered why the original authors chose the GPL? It's so people who use their code will never take away the freedom of users of the code. If you're complaining about not being able to take their code and make it proprietary, you're missing the point that THAT'S WHY THEY CHOSE THE GPL.
- coldtea 11y agoThat's orthogonal to whether the prospective user of the package has an actual choice or not (besides using as GPL it or going without). WHATEVER THE ORIGINAL AUTHORS' REASONS FOR CHOOSING THE GPL (sic), it doesn't change the situation that one might not be happy for a project they want to use being in GPL -- including people who don't intend to make it proprietary, but who prefer BSD licenses nevertheless.
- twblalock 11y agoIt would be trivially easy for an engineer to add a GPL-licensed dependency to a project without realizing it, perhaps via a transitive dependency, thereby causing the company to be in breach of the GPL. If you don't audit, you don't know if you are in breach of the GPL or not. Your corporate counsel will want you to audit. You can't reasonably take any action, including open sourcing your project or even posting code snippets on a company engineering blog, until you know which licenses you actually use.
- klodolph 11y agoIt's not just that corporate counsel will want you to audit. I worked at a company where I found a GPL violation and wanted to comply, but if we started complying with the GPL it would have shown that we knew that we previously hadn't been complying, so I was told to not comply. Ugh. Just for redistributing a couple binaries, there were no libraries involved.
- belorn 11y agoIts about as trivial as for a web developer to accidentally use a proprietary image they found on the web, a game developer that use the unreal engine, or a marketing using someones music in a commercial. Its quite common to find commercial copyright infringement in all of those (except for the unreal engine, since I don't know publicized case of that), and there are artists who earn a fair income by contacting infringes and demand payment or a cease and desist. I wouldn't however describe that as being bitten by the rightful author, but put the blame on the developer who is using someone else work without permission, especially if they their own business model is based on copyright.
- cyphar 11y ago> It would be trivially easy for an engineer to add a GPL-licensed dependency to a project without realizing it, perhaps via a transitive dependency, thereby causing the company to be in breach of the GPL. Just as easily as it is for a designer to use a copyrighted work. The GPL isn't a boogieman, every project that's under the GPL says so. If a developer isn't mindful enough to realise that they shouldn't randomly copy-paste library dependencies without knowing anything about them isn't a very good developer.
- heartsucker 11y agoA few days late on the response here, but I'm going for it anyway. I was using "bit" colloquially, and my tone wasn't angry. We "choose not to participate in the GPL community" because we sell software, and if that software could be requested for free, we couldn't exactly stay in business trying to sell it. I have nothing against the GPL, and I'm pretty certain the management and rest of engineering don't either. In fact, I/we aren't trying to abuse and profit form other people's good will. That's why we check the licenses of software/libraries we use: to respect the way in which it was licensed. We have to keep our software closed source, so we obey the licenses that could require us to make it open source.
- st3v3r 11y agoThat would only affect you if you were making your own JVM/.NET runtime.
- TelAviv 11y agoWhy don't you learn C# and then come back and see if you feel the same way. It's a MUCH better language and environment than Java.
- barrkel 11y agoI first started using C# professionally in 2003, after starting out with the betas. I helped implement some key .NET support for the Delphi compiler when I worked at Borland. I'm quite familiar with the evolution since then too. For example, back in 2006, I advocated implementing a CPS transformation to make better use of async code in .NET: http://blog.barrkel.com/2006/07/fun-with-asynchronous-methods-and.html http://blog.barrkel.com/2006/07/fun-with-asynchronous-method... It only took 7 years for async methods to come out, but they're there now; and I understand their utility in no small part because I was one of the people asking for them.