dehora

9 ms·

1.
by dehora 3y ago
CDPR, 2002. Larian, 1996. Valve, 1996. Remedy, 1995. Nintendo 1989. FromSoftware, 1986. Capcom, 1979. That said, before the details, I agree and resonate with your sense of frustration. Every shop you mentioned is one I not just admired for
2.
by dehora 6y ago
> Are there any drawbacks of using a plugin centric approach? Here are some: 1. You're perhaps more subject to Hyrum's law. If plugin devs can see it, they will use it. The general observation here is that it's harder to c
3.
by dehora 6y ago
To the poster's credit, he does frame this in terms of balancing concerns. I'd argue the post overstates the non-technical mitigation, but they seem worth being aware of, and even as a rhetorical device, overstating helps bring th
4.
by dehora 6y ago
I agree with pretty much all of this. The point I'm making and not conveying well is that the state eventually has to be held somewhere. So not that it has to colocate with application services, but that if you want to store something
5.
by dehora 6y ago
Yes for sure, in terms of expansion/adoption. It's not so certain in terms of function/utility. As a Google outsider, gRPC really does seems like Stubby for the rest of us (with balancing left as tradeoff for the community).
6.
by dehora 6y ago
Great to see an answer that provides context and reason for a language preference. By way of reflection on your answers: 1) This is hit and miss for me. I have to read Go code frequently: not every day or even week, and sometimes under inc
7.
by dehora 10y ago
It's great to see Microsoft release these guidelines. It's good work, a broad document with a lot of interesting topics covered. You can always debate the details (the pagination discussion here is very interesting), but having se
8.
by dehora 11y ago
I was wondering, what did you think of the production readiness of Mesos independent of Docker?
9.
by dehora 11y ago
Python is slightly easier in my experience to refactor and manage as the codebase grows, somewhat easier to get performance wins out of, somewhat easier to debug. But it's approximately in the same bucket as Ruby when it comes to tooli
10.
by dehora 13y ago
Agreed. YAML is easy to type, even with the whitespace. So is INI. And as verbose as XML is, it's easier, ime, to type than JSON. Of those four, JSON is the hardest to write by hand; certainly it's the one I make most mistakes wit
11.
by dehora 13y ago
It is a problem with JSON in the sense that it's a JavaScript subset, 'in practice' - modulo the Unicode support that goes beyond JavaScript. So it's to be expected that eval() will be used as a convenience by developers
12.
by dehora 13y ago
Apache's Cassandra deb that a similar behaviour and has a greater impact than ES's super-hero node names. A newly started Cassandra node will absent a token declaration in its yaml file, auto-assign a token. This is never what you
13.
by dehora 14y ago
> It's the only formally proven, No. RDF is formally proven via its Model Theory (as was KIF before it). That's arguably a stronger basis that relational "algebra"
14.
by dehora 15y ago
Quora on MySQL failed outright when AWS EBS failed, companies on AWS using Cassandra like SimpleGeo and NetFlix did not. To their credit, Facebook were clear enough on their reasons for using HBase over MySQL and Cassandra, such as wanting