Fair enough point, but they already have a logo... the word "node" followed by a little cloud then the letters JS. There's not really anything wrong with the old logo, but it's more the wording around the announcement of the new logo that irks me the most I guess... feels so "corporate".
I really like node.js, but I'm afraid I can't say the same for the logo or even the statement that someone needs to "jettison preconceived notions about what Node should look like". I mean, really? For a revolution that was engineer led, sounds a bit like marketing bs to me. And that's something node.js doesn't need.
PS. Do not consider this a troll comment. It's just my opinion.
The interchangeable use of 'Ruby' and 'Rails' in the original article (and some of the comments) is indicative of someone who has not taken the time to understand either. Conjecture like that is not worth the GET.
I wonder if anyone will take this research and look at the appetite suppressing qualities of nicotine in light of this... perhaps a totally natural drug is already available to block CB1 receptors!
When presented with '1 + 1 = 2', some people will be interested enough to ask why, and others won't give a fuck. Same goes for 'Hitler invaded Poland'. It doesn't mean one person is better or worse than the other, they're just different.
The real problem will arise when people stop being interested. And when that happens it won't be the fault of the Khan Academy or wikipedia or the Internet or TV or video games or religion or <insert favoured target here>.
I have these tiger repellent shoes. They're just standard black/black Adidas Superstars, but I have never seen a tiger while wearing them (and i have travelled a lot).
I'm not sure age discrimination actually exists in the startup industry, and certainly anyone who equates correlation with causation doesn't have any place attempting to do anything that requires a modicum of intelligence IMHO. Nor would i want to work with a VC who made such an error.
What I find funny is that people just throw these stats out there without any acknowledgement of this, nor any discussion of confounding variables - at least David Lee is acknowledging that he should have done so during his presentation rather than after. I bet there is significant correlation between the founders of successful companies and their families socio-economic background too - look at how many are Ivy League graduates or dropouts. How about their marital status? Number of children? Personal debt? Tenure related benefits? These factors are likely much more significant than age in determining the amount of time and effort a person can put into something, and how much risk one is willing to take doing anything. However since age has a strong correlation with these other attributes it's just easier for people use age as a kind of summary statistic. Recognition of this is severely lacking, especially amongst the media types (who I'm sure actually do know better, but it's a pretty boring headline isn't it?).
Anyone can do anything they want with enough time and effort. Some people need less of these than others, and timing has a lot to do with success. But it has precisely fuck all to do with age alone.
I agree with ehutch79, x86 virtualisation is well over 10 years old. There are many free (both as in freedom and as in beer) virtualisation options available currently, does FAUmachine cream everything else in terms of performance or ease of management or something?
I don't mean to detract from the academic aspects, nor from the effort that must have been put in. But "next cool thing"?
An interesting move given AWS' current core market (web based companies, startups, students etc - ppl who generally have no interest in Oracle databases)... wonder what kind of uptake there will be. AWS still has too many ToS issues to be seriously usable by large enterprises, who else is going to be using RDS for Oracle in earnest?
I'm not sure what the author of the article is trying to prove... that trademark law can be (and is being) abused? At least he had the integrity to quote the EMI lawyer throwing examples back of Bloomberg engaging in similarly questionable legal action.
As several people have already pointed out, there is Windows, there is Time. Oddly no-one has yet mentioned Face and Book.
Proving once again, an idea without execution is worth precisely fuck all. All the non-technical founders out there trying to rip the executors in terms of equity, take note.
Sure, but I'm sure Roy Fielding would argue you can't have REST without HATEOAS. So on some level yes, it is great in theory, but on another level I would also argue that's where the 'ful' comes in ala 'RESTful'. I guess you could look at it in a 'spirit of the law vs letter of the law' kind of way - REST without HATEOAS is certainly in the spirit, but perhaps so is XML-RPC with HATEOAS. Neither are the letter though.
The website example below is a good one, but as I'm and infrastructure oriented kind of guy I'll give another one which is the Sun Cloud API, under the now defunct project Kenai http://kenai.com/projects/suncloudapis/pages/Home. For example, doing a GET on a VM resource will return a payload that contains a URI for a power operation on the VM. What that power operation is obviously depends on what the power state of the VM at the time of the GET. The AWS API's provide a SOAPy interface, but they return information about objects that much more adheres to HATEOAS than the Rackspace API for example, which goes to _great_ lengths to espouse it's RESTy virtues (even consisently, and incorrectly, lowering the 'E' in the API docs lol).
So yeh, of course it all comes down to the infinite scales of grey, I wasn't trying to imply that I know any better than anyone or that REST-without-HATEOAS is wrong or suboptimal or whatever (and I know you're not interpreting it that way either), just that I have sometimes wondered how many REST implementors actually took the time to understand what Fielding was/is on about. And I certainly don't believe you or the author of the post fall into that category!
Nice post. The single biggest criticism I usually level at REST implementations is the lack of HATEOAS - the discoverability aspect of REST is about more than just an easily understood URI. As the author of this post states in his 2nd bullet point (emphasis mine):
"It’s expressive, REST paths and CRUD requests are easy to understand _and hypermedia makes it easy to navigate_"
It's that second part that so many implementations gloss completely over, it's probably worth discussing that separately in the same way that authentication is discussed in the post.
The US is probably out - due to VISA requirements you can't stay there for any length of time. But if you do go there, I would advise setting yourself up with HSBC Premier in the UK first, then getting USD bank accounts setup via them (they are real, local US accounts with cheque books and debit cards - not just a "currency account"). In fact that advice probably applies irrespective of where you move - get a local account setup from here first if you can. Setting up local bank accounts as a foreigner can be a real pain in the arse, and yet they are so essential if you want to get any kind of income (or even just to avoid wild exchange rate fluctuations).
Start going minimalist now, if you are not already. The worst thing you can do is lug all this useless shit with you around the globe, or move somewhere and start accumulating crap. Yes I am speaking from experience.
Finally, if you are not that well travelled, start by actually travelling :). By that I mean use the net to target some places, then take yourself on a holiday and hit all those places. Don't plan any of the usual touristy crap, just try to take in the environment you are in. See if the place gels with you or not, as much as something can in a week.
In my experience Windows ops/admins don't have anywhere near the depth nor breadth of infrastructure knowledge that *nix ppl do, and I have yet to meet a .NET web developer who knew anything about OS internals.
I'm not ragging on MS devs, just an observation from personal experience. The well-roundedness of the FOSS based software engineers makes them a much better suit for startups than MS people. I don't believe technology superiority really comes into it.
I guess technically they don't qualify, but surely Microsoft's web properties have to be right up there. Billions later, they have yet to turn a profit.