253 karma · joined October 3, 2010
Having said that, the intention is, I imagine, noble. You want to be, and be seen, to be flexible and willing to work with your customer. But I think the way its presented will come across as wishy-washy.
I like the design, thought it may be a little busy at times. But certainly eye catching.
In the 80's as investment banks discovered the joy of trading profits, they realised they could then leverage capital (pun intended). That therefore led to their finding more capital, in one of three ways, all which started to happen in the next 10-15 years : merging with commercial banks (which in turn allowed commercial banks to earn larger returns on their capital ... much better than lending to the neighbourhood convenience store); going public; and pressuring regulators to allow higher debt/capital ratios.
So, as with everything, a simple matter of incentives.
I was about to order one, even though I had to wait a long time for my wakemate. However, after reading this thread, I've decided against it. Too much drama.
Also, I'm quite astonished by the fact that that 60 of the 66 charges have been resolved by guilty pleas or verdict. In many of these high profile cases, detractors claim 'witch hunt', and a quite often win on appeal. However, with these statistics, anyone who claims that there isn't something rotten going on is on doesn't have much to stand on.
All in all however, a 63 year old man who was something of a personal icon is going to jail. Sad, particularly for his family, but count me impressed by Preet Bharara.
Even assuming that no email address has been taken, the fact that this list of passwords is now seeding rainbow tables across the world is a quite harmful, I think (and this is true irrespective of any advice to users to use unique passwords). Also, for a site as large and supposedly sophisticatd as linkedin, not using salts is inexcusable.
I have been a long time user of linkedin, and have no plans to stop using it. I certainly dont want to hang them, but an acknowledgement of mistakes are expected, otherwise declarations that it wont happen again have no weight. Disappointed.
https://groups.google.com/forum/?fromgroups#!searchin/julia-...
So one of the claims of Julia is that you write code in the most natural manner, and depend on the compiler to make it fast. So, for example, the claim is that adding the optional type parameters do not necessarily make your code faster... type inference is good enough in most cases (there are obvious counterexamples, eg with global variables, but its true in the majority of cases). Also, unlike for eg. Matlab or R, vectorising your code does not necessarily produce performance gains, arrays are good enough. One of the side effects is that the standard library is implemented in the language itself, and thus extending built-in types is a breeze.
Therefore, I think its a very interesting effort in itself. Whether it is good enough to displace any other language is a completely separate issue. As said below, the base of useful libraries in languages such as R is phenomenal. But that should not, I think, preclude admiring a very interesting new language, for the possibilities that it hints at, if only as a highly engaging mental activity.
Personally, and subjectively, I think the combination of the above, and multiple dispatch, causes the language to have a highly pleasing sense of elegance.
There are a couple of things I'd add. If you're more than just a couple of founders, ensure you have a watertight no-solicitation agreement, in addition to an NDA. More than information, employees who know the domain are valuable to the competitor.
Finally, the one overriding thing to keep in mind for all offers -- dont let it be a time or energy sink. Its easy to fall into that trap, if the first couple of conversations are productive.
The reason for this, I suppose, is that flickr was an independent entity, with its own user database, before being acquired by yahoo. It was long after the acquisition that yahoo insisted on linking it to your yahoo ID. Some will remember the brouhaha that caused.
Post purchase dissonance reduction is a well known cognitive bias[1]. And what can be better for dissonance reduction than someone telling you that you have good taste, and anyone who buys the competition is a philistine?
I should point out that this does not impute anything to the quality of the products themselves. I just posit that blogs such as Gruber's play a active part in the ecosystem due to our cognitive biases. They are not merely a passive observer.
[1] http://en.wikipedia.org/wiki/Post-purchase_rationalization
While this leaves me with an icky feeling, being a java developer, I'm also cognizant of the fact that one of the major criticisms of Sun from the financial markets was that they could not monetize java very well.
It'll be interesting to look back in 10 years and see how Java has fared under Oracle.
We (the internets :D) spend all this time getting out of the AOL walled garden, only to go back to the Facebook walled garden. Seems like an utter waste of effort.
But maybe the glass is half full, and we will be out of here soon.
Moody's in its latest assessment says:
"The global role of the dollar, which underpins continued demand for U.S. dollar assets, .... provides unmatched access to financing, meaning that the U.S. government can support higher debt levels than other governments"
http://economix.blogs.nytimes.com/2011/08/08/moodys-why-the-...
So I'm left puzzled at the recent debate about the US debt.
Google+ lets you approve all tags.
Not sure why a third level reference is being passed around.
I suppose I'm unsympathetic since every authenticated web app I've done in the last 10 years has been SSL only. But that was too 'enterprisey' perhaps :). Also I imagine that this is such an obvious thing, it wasn't a case of being unaware of the issue, just taking a conscious risk-reward decision on being SSL-only. Particularly for the really smart developers at github. One could argue that since nothing bad (that we know of) happened before firesheep, it was a valid decision.
All in all, I think Firesheep has done a big favour to the web as a whole.
PS. this thread has degenerated to using github as an example, I should probably point out that I love and respect github. really.
And, in a practical sense, who would you have expected the creators of firesheep to have warned? The top100 sites? the top500? At what point should github have entered the list? Again, this is not a vulnerability in a specific app, its a well known design error.