47

I think you make a mistake in assuming that the choice of technology is a purely technical decision. The customer seems to be concerned about the business implications of picking a particular technology. Given that, you need to present a case that addresses his business concerns at least as heavily as your technology opinions. Employers have to recruit ...


31

Lisp, Smalltalk. Coincidentally, those are also the best languages in the whole bunch. Both Lisp and Smalltalk are languages which are built around strong unifying metaphor. Lisp's metaphor is "everything is a list; this list represents both data and code (as functions)". Smalltalk's metaphor is "everything is an object; the only way to invoke a behaviour ...


28

I understand the desire for a simple, no foolin' around statement of what you intend, but there's no point in having a EULA at all if it's not going to do the job that it's supposed to do, which is to protect your rights and to define what the user is and isn't allowed to do. Legal language is like computer code -- it should unambiguously define your intent ...


27

It's quite simple. It initiates contact between a potential customer and sales. They can then vary their price as they please based on any criteria you care to mention, without affecting the price expectations of other potential future clients.


19

Did you read the license? Because it's pretty short and I think easy to understand. Unless your lawyer tells you otherwise, I'd say that yes, you can use the code, but you have to put their notice & disclaimer in your documentation (about box, whatever).


19

Short Answer: Yes From the MIT License: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell ...


18

If you are the sole copyright holder (i.e., the owner), you can do anything you want with the code, including doing a derivative version of the code where the only change is to the license. Licenses are just descriptions of the conditions placed by the owner(s) on the non-owning users of the code. They do not constrain the owner. When there is multiple ...


17

This is probably best stated by the Public Domain Manifesto. Beyond the theory and such, running a business is simply a pain in the butt. Many developers want to build useful software that gets used by people. Selling and supporting software takes an enormous amount of time, energry, and (most likely) skills that most developers simply do not have.


12

There are as many different reasons as there are programmers who make choices. Here are some: You just need the software to get work done. If you open source the software, other people will add features they need and you will likely get them for free. Contributing to open source projects is fun, boosts your ego, and may improve your prospects for a job. (...


10

No, you don't need any licenses for neither of them. Patents for RSA have expired on September 21, 2000. Even before that, it was also released as public domain. Rijndael was submitted to NIST as Federal Information Processing Standard for AES, and is officially declared by authors to be patent free.


10

They want prospective clients to make contact with sales people. The prices in these cases are so criminally open ended as well that they don't want other customers to know that they gave a STEEP discount to Oracle where they screwed IBM. Developer aversion to these types of pricing models is typically because it is extremely painful being on the phone ...


10

It sounds like what need is to have your programs digitally signed (i.e. Code Signing). This is similar in concept to an SSL certificate, in that it proves that the program is from whomever the certificate was issued to & has not been modified (e.g. malicious code added). The key to understanding Code Signing though, is that the certificates are ...


10

So the first portion of your question with "how do I correctly sub-license" is answered in this former SO link: Can I re-license someone's MIT code. Hat tip to Gallaecio for this link, and please note that SO users with 10k+ reputation can still see the link. And the most relevant part of the answer there is: What you can do is have more than one ...


9

The short answer is "no." The code that your submitters are writing is covered by copyright, and that copyright is assigned to the submitters. Since the project is GPL, they have agreed that the code may be released under the GPL. You will need to get permission from the submitters (all of them!) to release the code under a different license than GPL. (I ...


9

Blender was initially commercial. Update: this answer is far better than mine; upvote it instead.


8

Although GPL does allow for commercial software, you are right in suggesting that this may not be very profitable as your customers are within their rights to distribute the source code of your project for no cost. This article seems to comprehensibly explain GPL's "incompatibility" to commercial software. So most companies who distribute software under ...


8

You can distribute your program for Linux just as you would for Windows, by shipping your compiled code with any resources it will use. You don't need to include the source (unless your product is derived from GPL code). Just build without symbols and distribute the binaries. You'll probably want to statically link libraries to make distribution simpler.


8

For starters, you can direct you client here for a look at the ecosystem that exists around Rails. You can also point to the successful startups like LivingSocial, Shopify, 37signals, etc. that built their businesses with Ruby and Rails. You can mention that massive enterprises like AT&T, SAP, and Symantec are using Rails, too (they were all heavily ...


8

Some "Formerly Commercial-Only" Projects The IntelliJ IDE was originally closed-source A lot of Id Software games, old (like Wolfenstein 3D) and not so old (like Doom 3) A lot of projects released as open-source by Sun Microsystems started as closed-source experiments or products: the JDK and JRE themselves, NetBeans (interesting crossing history lines ...


8

Since you are the author, you can give yourself the library under different terms from what you give the library to others (and you can give it under different terms to various others). As long as you are the only author or get all contributors agree to the special terms for you (you'd need good lawyer to write the agreement so that it's valid across the ...


7

Qt was originally a commercial project by Trolltech, then when they were bought by Nokia it was released as a dual (commercial/LGPL) project. The value to Nokia of having it as the default GUI toolkit of programmers all over the world was more valuable than the extra license fees from a few commercial customers ( or it would have been if Nokia could ...


7

Short answer: Ideas, yes. Source code, no. The source code is protected by copyright and the license only allows you to use the source code if you license the result as GPL. This doesn't block you from selling the result, but requires you to provide the source code to anyone you have sold the application to (and stops you from barring them passing the ...


7

For the regular GPL, the answer is no. Quoth the FSF FAQ: Q: Is there some way that I can GPL the output people get from use of my program? For example, if my program is used to develop hardware designs, can I require that these designs must be free? A: In general this is legally impossible; copyright law does not give you any say in the use of ...


7

TL;DR Use an app store. They do all the hard stuff for you. All you'll need is a simple website to point to your app in the store. You have many questions here, and may issues to resolve... Do I have to produce individual terms of agreement for this program? You don't have to do anything. To be honest, a $1 sudoku solver will not make much of splash in ...


6

The way in which .NET's cross-platform nature is achieved is different from the approach taken by Sun Microsystems with the handling of the Java programming platform. Unlike Java, Microsoft itself does not provide installers of .NET for Mac, Linux, etc. Rather, Microsoft has released a set of formalized specifications that other entities can use as a road ...


6

I need to add an EULA to my (commercial) software but I cannot afford a lawyer. Well, this site isn't a lawyer either. You need to hire one. If you can't afford it, then your project is fundamentally mismanaged and it's not something that can be fixed here. There's a reason that most companies offer EULAs that are six trillion pages long, and it's usually ...


6

I'd explain that it's basically a "Coke" vs. "Pepsi" choice. Both are widely accepted, both have people that will fight and die for each, and they're both perfectly adequate. Point out the reasons you prefer RoR.


6

He's talking about people, you're talking about a language and framework. He is not going to hear any reasons that are purely technical, so you should focus on what people are doing with the language. You can talk about people-power under Rails, how it's easier for one person to do more than a PHP person, faster (if this is what you believe). You can ask ...


6

TeX, the typesetting system, has been very stable since version 3. Since version 3, TeX has used an idiosyncratic version numbering system, where updates have been indicated by adding an extra digit at the end of the decimal, so that the version number asymptotically approaches π. This is a reflection of the fact that TeX is now very stable, and only ...


6

C and Fortran are languages that spring to mind. They are very stable and their syntax is easily contained in one's mind. Other than writing bad code yourself, there are very few suprises when using these languages. But I wouldn't hold them up as great languages for rapid application development. I prefer the rapid advancement of languages with features ...


Only top voted, non community-wiki answers of a minimum length are eligible