We've just never found the demand or a reasonable UI for exposing the underlying complexity to users.
1,471 karma · joined January 15, 2012
[ my public key: https://keybase.io/rohansingh; my proof: https://keybase.io/rohansingh/sigs/FYqfP0wJErPun-vsVRQ2fAEqahFzGh-6AGFTFN5MRYE ]
We've just never found the demand or a reasonable UI for exposing the underlying complexity to users.
No need to prematurely optimize as long as you set yourself up to prevent lock-in.
This is entirely true. We are big users/consumers/fans of Cassandra at Spotify. We have approximately one crap-ton of Cassandra clusters with several metric crap-tons of data. But we have an entire team that provides support and tooling around Cassandra. We contribute upstream, and have employed core Cassandra contributors in the past.
In return we get a datastore that scales pretty much infinitely with our data sets, has performance characteristics that we are now well aware of and are able to reason about, and provides us cross-DC replication and topology-awareness. It took years to get to this point though, and to build the operational expertise required to run Cassandra. Only recently have we gotten to the point where teams are able to self-service provision their own Cassandra clusters.
This is a resilient, scalable solution, but if I were to quit tomorrow and start a five-person startup, there is no way I would consider C* as a workable solution.
cp
mv
rm
cat
grep
find
ln
head
tailAs you can see in the Wikipedia article, there are actually many different interpretations and views on whether or not that rebuilding adds value to the economy.
The difference with crtauth is that you don't need an SSH server running in tandem, everything is handled by the crtauth library. Our main use case for this is for bots that need to access secure services.
Protocol spec: https://github.com/spotify/crtauth/blob/master/PROTOCOL.md
git bisect, git log, and git blame are all indispensable tools. To counter your anecdote, I use them all the time and see others do so.
There's really no reason to leave dead imports in a file.
> The act I committed to put me here was not just heinous, it was senseless. But the person that committed that act is no longer here - I am. I'm not going to struggle physically against any restraints. I'm not going to shout, use profanity or make idle threats. Understand though that I'm not only upset, but I'm saddened by what is happening here tonight. I'm not only saddened, but disappointed that a system that is supposed to protect and uphold what is just and right can be so much like me when I made the same shameful mistake. If someone tried to dispose of everyone here for participating in this killing, I'd scream a resounding, "No." I'd tell them to give them all the gift that they would not give me...and that's to give them all a second chance. I'm sorry that I am here. I'm sorry that you're all here. I'm sorry that John Luttig died. And I'm sorry that it was something in me that caused all of this to happen to begin with. Tonight we tell the world that there are no second chances in the eyes of justice...Tonight, we tell our children that in some instances, in some cases, killing is right. This conflict hurts us all, there are no SIDES. The people who support this proceeding think this is justice. The people that think that I should live think that is justice. As difficult as it may seem, this is a clash of ideals, with both parties committed to what they feel is right. But who's wrong if in the end we're all victims? In my heart, I have to believe that there is a peaceful compromise to our ideals. I don't mind if there are none for me, as long as there are for those who are yet to come. There are a lot of men like me on death row - good men - who fell to the same misguided emotions, but may not have recovered as I have. Give those men a chance to do what's right. Give them a chance to undo their wrongs. A lot of them want to fix the mess they started, but don't know how. The problem is not in that people aren't willing to help them find out, but in the system telling them it won't matter anyway. No one wins tonight. No one gets closure. No one walks away victorious.
http://www.tdcj.state.tx.us/death_row/dr_info/beazleynapoleo...
Of course, it won't collapse into a black hole, but the amount of energy needed to accelerate further will increase asymptotically.
> Without access to a lot of source code I can’t tell exactly what is going on, but...
> Until Microsoft fixes their compiler to not load their web browser it seems impossible to avoid this problem when doing lots of parallel builds.
In my past life developing applications and services on Windows, this scenario was too common — something is broken, you can't quite tell why because you don't have the source, and you can't do anything but wait for it to be fixed or find some hacky workarounds (which is tougher to do without the source).
This has been the real win on switching to an open source stack for me: you can take your tools apart, look inside them, and fix any issues. I know Microsoft has come further in this in the past few years, but it still sucks to be stuck in that kind of situation.
If we stick with Debian, we'll find ourselves back in this situation fairly soon, since Debian's security team only supports oldstable for one year after a new stable is released (approximately — there isn't a set timeline available).
Ubuntu LTS releases, on the other hand, give us predictability and five years of support. That makes me very happy from an infrastructure standpoint. And the more up-to-date packages in Ubuntu repos make our feature devs happier, versus having to maintain backports for modern software.
One other fun problem Spotify is going to tackle is how we're going to handle systemd vs. upstart if/when we transition from straight-up Debian to Ubuntu.
> Now, whenever I think I know what’s happening, I temper my thoughts: Might be wrong, Cliff…
Secondly, while Stoll is wrong on many points in this essay, what's amazing is that he hits on things that were definitely broken or deficient in 1995 and had to be fixed to get us to where we are today:
* difficulty of reading on CRT screens
* lack of online payments infrastructure
* difficulty in searching and filtering through Web pages (i.e., search)
These were all very tough problems, and stacks of money have been minted by Amazon, PayPal, and Google by tackling them. I'm impressed by Stoll's ability to identify these problems clearly as early as 1995.
[1]: http://boingboing.net/2010/02/26/curmudgeony-essay-on.html#c...