pwf

do you know how gaussian splatting works?

The stuff we used Go for was the right choice for Go for sure, but I don't think the API would have been any easier in Go (though I haven't used those frameworks before...).

We also could have done Django a lot better. And all of the Celery stuff probably should have been Go, especially with the Cassandra driver we were using. Still, I'm using Django today and as long as you don't abuse the ORM and nested DRF serializers too much, it's very scalable. I think as long as you make separate services in other languages at the right time for the right use cases, it's a very valid choice for rapidly building an API.

50k seems like a low bar to start losing messages at. If this was done with Celery and a decently sized RabbitMQ box, I would expect it to get into the millions before problems started happening.

> Of course you design it in such a way, that you can change one of the inputs, which will by definition invalidate the tokens.

I was looking at using JWT to avoid a database read when authenticating a request, but in order to get some sort of variable per-user value I'd have to hit the database to get it, no? Doesn't that kind of defeat the purpose?

I use car2go in Austin, and already love the system. A car2go that could drive itself to my door would make my commute perfect.

I imagine this working a lot like car2go, which I've used to commute in Austin. The cars are rarely at a central depot except for maintenance. They're left wherever you last used them until someone else gets in. This could only be better than that, as users won't have to walk to find one.

There's no reason for the cars to drive back into the city every evening. They could charge themselves while you're at work if they had to charge daily.

That makes sense, thanks!

I should learn to read...

Is there a bug in the train function? Using 'lambda: 1' for the default dict along with '+=' means that the first time a feature is encountered, the value is set to 2.

  In [1]: from collections import defaultdict

  In [2]: d = defaultdict(lambda: 1)

  In [3]: d['foo'] += 1

  In [4]: d['foo']
  Out[4]: 2

A relevant quote from 'Snow Crash':

Gargoyles represent the embarrassing side of the Central Intelligence Corporation. Instead of using laptops, they wear their computers on their bodies, broken up into separate modules that hang on the waist, on the back, on the headset. They serve as human surveillance devices, recording everything that happens around them. Nothing looks stupider; these getups are the modern-day equivalent of the slide-rule scabbard or the calculator pouch on the belt, marking the user as belonging to a class that is at once above and far below human society.

I thought titles were only edited to be less... editorialized.

Who the hell added 'Microscrood'?

Cmd+shift+4 on a retina MBP. Not sure why it does that...