EmielMols

Part of the reason she apparently speaks Russian pretty well. And Russia's president, mr. Putin, is fluent in German because he was stationed there when younger. Quite the antagonising characters in politics these days, but at least they speak each other's language. :)

The problem with these systems is that batching would make the implementation more complex. Sending say 10m notifications per second in a fire-and-forget manner is easily distributable en requires little state. Batching per user would be do-able but requires thinking about distribution (messages to the same user should at some point go over the same machine) and tracking a bit of in-memory state per user.

In short I can imagine the trade-off of less-optimal support for some edge cases like these.

> If you can make it fast on MySQL, it just means you are doing it wrong on PostgreSQL.

This is quite the statement and inconsistent with your later point. Postgres never updates data in-place, and certain workloads can never be as fast on Postgres as using a different storage engine such as MySQL/TokuDB.

Postgresql's MVCC model (copy complete row on any write, clean up old rows some time in the future) might work decently for read-centric workloads, it's unsuitable for write-heavy stuff.

We're running a setup that employs postgres for a write-heavy (but far from write-only) application, and are experiencing similarly troubling vacuum jobs. We're considering moving back to good old MySQL because of it. Anyone who's been here before and has some insight?

I think this is a valid point. For non-performance-critical code where readability is more important (eg analytics) the additional language features could be nice.

In my experience, 9/10 production use cases are covered using a path as primary key with prefix matching (select path,data from tree where path='a/b' or path like 'a/b/%') - as a side effect your subtree nodes will often be on the same table page (mySQL by default, pgSQL when using CLUSTER).

Used this often and it's a fine service. One feature request: it would be great if they'd chip in a wildcard https certificate (and publish it including private key), so it could be used for https on (local) development setups. This would require supporting an additional naming scheme that only uses single-level subdomains.

It would have been interesting to be able to setup your own stack links (e.g. by collecting Error().stack, and being able to update this at any other point - Error.setStack?). A heap of 3rd party promise/observer/animation/etc libraries could use such a feature to ease debugging. The current implementation does not allow for this [1].

[1] https://code.google.com/p/chromium/issues/detail?id=272416

Windows used to have a "Czech (Programmers)" keyboard layout. As I remember, it was one of the few layouts that _just worked_. First thing I would do on new installs is make it the only available layout.

Detection of the game-over state seems buggy: I had moves left on a full board then got the 'GG' modal.

EWD831 explains zero indexing. http://www.cs.utexas.edu/users/EWD/ewd08xx/EWD831.PDF

No. It equates to returning undefined, which is the same as having no return statement at all.

But one could argue that in many modern societies, empty bellies are never of issue. Given that you could find the means to sustain certain basics (food, love, friendship, etc), reasoning about "what's next" (e.g. pondering about purpose, what would make you happier) could actually be done without considering, say, money.

The interesting thing in posts like these, I would say, is that everyone puts in the "classic" Wall street boys comparison. Are they really all unhappy, money unconsidered? Is money their only measure in life? Sounds rather generalizing to me..

They're probably less screwed, cause they can register their domain today, provided it's still available.

For instance to allow meta-programming (programming code executed at compile time) in the same language as is being interpreted/compiled.

But more formally, a self-hosting compiler says stuff about the language per se, see also http://en.wikipedia.org/wiki/Bootstrapping_(compilers).

That doesn't seem very special or unique to me though. In almost all settings where some in-memory data is pushed on the network stack, you can expect stuff to be network bound.

Wait what.. The problem is that women hackers might not feel welcome, because 'sex has been thrown into it'. Seriously? The author obviously intended it to be funny in a way, so if you don't like it (which of course is subjective), don't come up with over-emancipated crap like this :).

I for one think that people ought to take stuff less seriously, and this writing style seems befitting. Way to go!

So, anybody set up the Auto-Reload yet ;-)?

Sorry, there were some traffic issues. Fixed now!

Sorry, I had some issues with the traffic.. but that's now fixed. Spotify is updating right now, so that might explain the error.

Thanks for the kind words!

It's not about the interface. It's about the technology behind it which can only be showcased by actually using it.

Thanks for your interest. Trying to sustain the traffic now, but I'll upload some screenshots ASAP. Concerning look&feel it's close to the original client.

Hmm, that's weird. Second attempt also fails? For me it's still working.

Agreed. I can't do anything about it though :-( This is a Spotify policy decision.