![](/static/253f0d9b/assets/icons/icon-96x96.png)
I don’t see a lot of people worrying about their cars devaluing. Except for the recent blip, most cars devalued fast, and the cars that held value before didn’t retain it because of their utility.
I don’t see a lot of people worrying about their cars devaluing. Except for the recent blip, most cars devalued fast, and the cars that held value before didn’t retain it because of their utility.
A cogent argument. I’m convinced!
You specifically said you chose the MIT license because you wanted to use it in commercial projects. That’s business, no matter how small. As the owner of the property, you could have used any and all licenses available to you. Also, if you wanted to require users of your code to attribute or notify you, you could have. If you want to be disappointed in their behavior that’s perfectly fine, too. Corporations usually disappoint if you have any altruistic expectations of them.
Here’s the core issue. The developer didn’t know his rights, and made a mistake. I’m not criticizing, people make a career dealing with crap like this. But if you want to make a business out of something, it’s worth it to do some research or talk to a lawyer. I believe the MIT license has its place but, from what the OP said, this isn’t it.
I think you mean the 2010 G20 summit. The 2011 summit was in Cannes.
Even the RPi, which has major Linux support has a blob for its graphics driver (at least the last time I checked). And I wouldn’t exactly say Broadcom is falling over themselves to support Linux. Qualcomm, less so.
I’ll remember this whenever someone says you’ll run out of things to do when you retire.
There is nothing stopping a GPL project using MIT-licensed code except for lack of desire to do the work. They are one-way compatible.
It really depends. If the contract gives ownership of the work created to the purchaser, he has no rights to it whatsoever. Moreover, trying to do a clean room implementation of your own code is almost impossible without help. A permissive license would give the purchaser unlimited use of the product, including resale while still allowing the producer unlimited use, as well. If the contract is written correctly, the producer might even retain ownership, with the right to use different licenses, while the purchaser would have few or no restrictions.
I’ll throw my opinions in here.
If you’re publishing a standard or a reference application, a permissive license makes sense. What better way to guarantee compatibility than being able to use the reference code in your product. This is what happened with the TCP/IP stack, and it was used in its original form in Windows for years.
If you’re making something that you want to build a community around, something more akin to the GPL may be more aligned with your goals. The nice part is, you can include MIT licensed projects as part of your GPL project. This means there is nothing stopping you from building your standard with a MIT license while building your community-driven application using GPL, maximizing the reach of your standard while reducing the risk to your community.
Note that either option opens you to EEE (Embrace, Extend, Extinguish), the GPL option just takes an extra step (clean room implementation of a published standard).
That’s not what “at the root” means. The guy selling himself and his country is the final part, the branch as it were. The root is the source of the money.
As for your reasoning, being able to further track intermediaries and see what else they have their fingers in is good security policy, as is sending back disinformation until such time as it becomes known the subject is compromised. Throwing these guys under the bus is usually the last step in the process.
I’m perfectly aware of how it works. My whole comment was a proposed way to manage it that doesn’t assume that everyone who uses outlook wants to use MS’s cloud service just because they also happen to use Outlook. I’m not sure how you missed that.
As for emphasis, “Press fucking backspace!” has a whole lot of it. I certainly would consider that, and not your hypothetical, as actively aggressive.
If you wish to talk about critical thinking, look at your own statements with respect to mine. Not once did I say cancel thenlink attachment, but this thing I didn’t say sure got you upset. Moreover, I wasn’t writing a formal specification. I’m sorry your assuming the worst and least likely meaning of what I thought was a pretty simple statement triggered you so badly.
Yeah, it sure does sound like it would be hard to have a notification if the attachment is going to fail due to size policies, and then have an option to use the link or cancel the attachment (and have you choose another way). It would also be unheard of for there to be a setting in that dialog to say to always do whatever action you take so it only inconveniences those who go with the default once.
User-hostile software is never a “you” problem. This applies to a number of FOSS products, as well.
Esperanto isn’t the only constructed language, and I think it is more Western-oriented, for good or ill. It does do a lot of things right within that framework, though, with certain rules that make everything explicit while removing other rules for structure that are no longer needed due to the explicit nature of the language.
Kids these days! Back in my day we stacked the corpses high enough to have gravity squeeze the juices out!
Yeah, I don’t feel a need to block people who are behaving badly around me. Perhaps I would if I had been inundated like you were. That said, I fully support you, me, or anyone else doing what they have to to maintain perspective and mental health, and I’m glad there are tools to facilitate that even if I never feel the need to use them.
No definition I’ve ever heard requires an exodus to be initiated by the people leaving. Also, if you read the comment that started all this, I was explicit that I didn’t mean employee-led. So thanks for stopping by weeks later to display your ignorance and/or lack of reading comprehension.
Shit, and my ex just divorced me!