That wasn't the point. Is the network really "slower by orders of magnitude" than disk? Why is using the network such a silly idea, considering network speeds are more than keeping up. Was the reference just referring to protocols. I was hoping for some accuracy: something to back up the statement.
Not sure that the message really has sunk in. The way to a good reputation is to be good and exceed people's expectations. Not complain that the world isn't a good judge.
I'd go further than this, if this is confusing architecture with development. This is not to say that a senior developer or systems engineer could take on an architecture role: but this wouldn't be the check-list in my view.
An architect is more likely, like his building counterpart, to see the system from the top down. That is given a clean sheet of paper: How can we achieve the availablility and fault-tolerance we need? what is the threading model? how does the system connect to the outside world? etc...
Whoever takes the role of doing this makes sure that the direction of the implementation doesn't loose sight of these goals. He may even create non-functional requirements.
In our neighbourhood we've been calling working with particularly difficult legacy code software archaeology: where it's not not clear what some piece of software was supposed to do.
http://media.pragprog.com/articles/mar_02_archeology.pdf
If copyright were just to protect the investment of a company in development of an artist or product I'd broadly agree with this argument.
Where copyright seems objectionable to me, is where the initial cost of development was non-existent or large profits have been made for years. For example:
For some copyright to last 95 years seems more like profiteering than protection of the creative industries considering creation is often based on the work of others.
I don't condone piracy, but I think piracy would be far less socially acceptable if:
- the creator can be seen to benefit from their work
- copyright better resembled its original intent of protecting investment in the creation of something new and not staking ownership over the work of others.
I remember people being pretty sceptical of android when it first came out, and it took time for the issues to be ironed out. If google are going to use the same gameplan, then the prices will eventually go down and the usability up. It seems to me to be a question of Google's commitment.
I find this unsurprising, companies don't resort to court before having a conversation. Even if the conversation is I think you should pay us licensing. The court actions are born out of disagreement.
An illustration of why some of the software industry wants to be more like the music industry and why the music industry doesn't want to be like the software industry.
Imagine if you were still making money off a program you wrote in 1960. Almost inconceivable in any mass market.
My understanding is the use of Open was used before this by Symbolics and possibly other lisp machine manufactuers. I'd argue too that their systems were more open, where the user could read the system software and patch it in while it was running.
The foundations of the open source movement too stem from these communities (the GPL) not from NeXt. It would appear to me, like other Unix manufacturers, NeXt claimed openness when mostly it was marketing-speak for "based on Unix".
I wouldn't be surprised if this is more about Twitter's other customers rather than Twitter's attitude to Google+. There are many who would pay a lot to get one over Google.
If tax is for anything it ought to be to help the less fortune in society. Once you start discriminating on who is the most deserving of basic medical society you have to start questioning the society you live in.
The state funding some basic form of healthcare for all is civilizing, and has other benefits. Healthcare is not an incentive to do well: it does not work as an incentive at all. Those who want better healthcare pay for it even in countries where there is a basic provision.
It's perfectly possible for state healthcare provision to co-exist with private healthcare providers too.
The specification ( http://tukaani.org/xz/xz-file-format.txt ) reads like this format allows the application of a chain of compression "filters". Perhaps the most interesting, and least portable is the filter that modifies code to make compression easier. (Section 5.2.3) Is this mainly for intel architecures?