jpollock

69 ms·

751.
by jpollock 14y ago
I would have used sharding, and then normal failure handling and resynchronisation between nodes. If you have the requirement that two adjacent versions have to be able to resynchronise after failure upgrades (and rollback) become equivale
752.
by jpollock 14y ago
That's very nifty, I learned a bit about hardware in there. C64 modding wikipedia page has more: http://en.wikipedia.org/wiki/Commodore_64_demos VSP (Variable Screen Positioning), also known as HSP, allows arbitrary x-placement
753.
by jpollock 14y ago
According to the documentation, it does this by preventing callbacks from initiating transactions on the same SpaceBase store? :) :) :) Isn't that a constraint on the application? :) :) :) I think I'm going to have to look at the demo and s
754.
by jpollock 14y ago
It doesn't sound like a lot if it is processed linearly. However, 10,000 reader/writers on a single shared resource is a lot. Naive implementations would have a single global lock on the resource, resulting in lots of contention. They app
755.
by jpollock 14y ago
A felony charge would have seriously impacted his ability to travel. This would have impacted his earning prospects both as an entrepreneur and as a researcher. For example travel to Canada: http://www.wikihow.com/Travel-to-Canada-with-a-
756.
by jpollock 14y ago
The amount in the tank is entirely different from the range it represents, which is also modified by environmental conditions such as altitude and temperature. The difference between the two situations is the number of places that you can r
757.
by jpollock 14y ago
Thanks for the pointer, I'll go check it out.
758.
by jpollock 14y ago
Everyone points at make and says, "use something better". They point at Rake, they point at Maven. However, Make has one feature that I really need, that I rely on to speed up builds: parallel dependency construction. The last time I chec
759.
by jpollock 14y ago
It's computation that you can't see with a debugger, or with any sort of tracing.
760.
by jpollock 14y ago
Isn't version control better?
761.
by jpollock 14y ago
If you're not charging per call, how are you funding the servers?
762.
by jpollock 14y ago
The next problem will be when they get to having large numbers of servers in a region. Then two problems will manifest themselves. 1) The client will take long enough to work through the list of servers that the wrong server is chosen simpl
763.
by jpollock 14y ago
I've always architected systems such that restart time didn't matter - the systems were able to fail over. However, in flight operations would fail, which meant that a restart would, in fact, cost >$50k - regardless of the length of ti
764.
by jpollock 14y ago
I love how he said that NFC was equivalent to a QR code, and then said how it was awesome that they could be rewritten. If a rental car (or any car) had a rewritable NFC chip in it, how quickly do you think it would be before it was pointe
765.
by jpollock 14y ago
In prepaid and other live billing systems the cost to bill a data session is higher than the cost to bill a phone call. This is due to data sessions having longer hold times (months) compared to phone calls (3-5 minutes). Since a session
766.
by jpollock 14y ago
After spending a week ripping out someone's poorly thought out floating point code, the lesson I learned is that you just shouldn't use floating point unless you really need to. For example, if you're working with money, you don't need floa
767.
by jpollock 14y ago
Distributed state machines are all about deciding in what order things happened in. That A happened before B. If you had a clock that everyone agreed on, much of the problems would go away. The problem is that we don't have one that ever