"No proprietary firmware". This is a direct quote from where? RTFA. The FSF never claimed that...
The article is confusing, but it seems like the fine is actually $16.03 million. What is infuriating is this is a settlement agreement so that the state will not release the names of the donors. It looks as if they are basically paying off the state so they don't have the deal with the public fallout.
So about $2 million dollars per employee? I doubt it's the people making the software making the majority of that money...
There is a lot of tax payer funded research that is inaccessible to the public despite their hand in its creation. I think that this aspect needs to be discussed, as well.
I don't even see anything to discuss. Seriously, how the hell is this acceptable?
And Swartz's super serious multi-felony crime was trying to fix this situation? Every time I look back at this case, it befuddles me. The only insane people here are the prosecution, and they need to be called out on it and punished along with everyone involved in this travesty of justice.
Producing and documenting open technical and process standards is one exception where corporate collusion is not only acceptable, it is often encouraged.
Am I reading this wrong? It seems that the cost of a print subscription is $3.85 a week but INCLUDES the $35/mo (holy crap that's expensive) digital subscription.
It kind of baffles me 500,000 people paying as much as ISP service for access to a single newpaper? Are they including print subscriptions in that number
You are seriously using the GPL in an argument on why copyright is a good idea? The GPL is designed to use to use copyright to subvert its fundamental purpose! Instead of saying "you can not sure", GPL says "you MUST share". It goes against every argument the copyright minimalists make the purpose for copyright is. That's why it's called a "copyleft license", it turns copyright on its head.
Efficency is were wealth comes from. If everyone is breaking windows the economy will grid to a standstill, there has to people doing actual productive work and software is an important foundation to modern world and shouldn't be squandered or guildified in the name of jobs. I appricate that you don't BS about your motives though.
Anyway as long as there is people still working there will be work for software engineers, actually our job is to put other people out of jobs (regardless of license of the software). I really think "software engineer" will be the last job in existence once we have automated everything else.
Anytime you write software that makes people more productive or automate business processes, you are taking a step down that road.
"FairPlay is cracked by Jon Lech Johansen ("DVD Jon"), previously known for his part in the DeCSS software, which was released four years earlier for decrypting DVDs."
You are talking about a man who is fundamentally against the way the world works and made it his life mission to change it.
"Migrate folks to it" with what authority?
I assure you the system administrator teams running those 21 other e-mail systems will not let you touch it with a 500 foot poll, and no strong leadership compels them otherwise.
The problem is this is exactly how those 21 e-mail systems came to be. I bet they all had the idea of becoming the "one corporate e-mail system", but got mired in politics and insanity along the way.
You can implement reliable transmission over UDP. And you have more options as well: you can do it with error correction algorithms for latency intorelent applications, something TCP can't provide with it's ARQ design.
TCP is simple to use (from the view of someone doing network programming), but under the scenes it is crazy complicated to implement properly.
Fortunately you really only need someone to implement a TCP stack once (in open source) and it can be reused in a multitude of operating systems. BSD pretty much set the standard for a TCP/IP stack (TCP Reno) and everyone went from there.
Stream protocols that offer error, flow and congestion control over heterogeneous datagram networks are NOT trivial.
TCP is not trivial at all. In fact & efficient algorithms to implement features of TCP is still an area of active research. IETF RFCs in various stages of standardization related to TCP probably amount to thousands of pages at this point, and it's still growing. Linux recently got a new algorithm for congestion control for instance: http://www4.ncsu.edu/~rhee/export/bitcp/cubic-paper.pdf