Xorlev

39 ms·

391.
by Xorlev 12y ago
20% projects maybe? If nothing else, it's a nice perk.
392.
by Xorlev 12y ago
PHP can run as CGI, original Apache deployments ended up being that way. Then everyone switched to mod_php/fcgi deployments.
393.
by Xorlev 12y ago
The author just mentioned that there were 140 servers in his account. I do know how expensive the servers can be.
394.
by Xorlev 12y ago
I thought new AWS accounts came by default with a 20 instance limit...
395.
by Xorlev 12y ago
Java also has arrays. And on heap/off heap RAM allocation. We deploy all our services as uberjars, we have a single Amazon AMI with JDK 8 installed. It's pretty frictionless. It goes from a simple Gradle project, to a single jar o
396.
by Xorlev 12y ago
Pretty much any and all data can be cached locally. Any modern application running in a web browser will have state that can change external to the application.
397.
by Xorlev 12y ago
It's a nice to have, but it's not priced with respect to value. I'd also be hesitant to route somewhat confidential emails through a one-man band development shop who may or may not be snooping them out of interest.
398.
by Xorlev 12y ago
> If you're offering JSON you have to provide SDKs for all the languages, since there's not even a standard IDL. I disagree. It's best to, but if someone wants to hack together something with python/requests it's
399.
by Xorlev 12y ago
And a Scala one ( https://github.com/twitter/scrooge , idomatic Scala generated models/parsers) when paired with Finagle/Thrift is pretty great.
400.
by Xorlev 12y ago
I found out the other day that Packetbeat supports decoding Thrift structs: http://packetbeat.com/docs/configuration.html#thrift-configu... Which makes debugging Thrift-based architectures significantly easier.
401.
by Xorlev 12y ago
The unfortunate part of public Thrift APIs is that you must either provide the IDL and hope your consumers are smart enough to work with Thrift, or you have to take the Evernote route and provide SDKs for all the languages you care to sup
402.
by Xorlev 12y ago
I think you mean HTTP+JSON. REST as a philosophy while applied mostly to HTTP isn't really tied to it. We personally decided to stick with HTTP (even though Thrift would be "superior") since tools are numerous and simple. It&
403.
by Xorlev 12y ago
RDS is just a database though. All the standard tools work with it. Unless you start dipping into more exotic services, it's pretty hard to become locked in. EC2+ELB+RDS are fairly independent. Even autoscaling doesn't lock you in
404.
by Xorlev 12y ago
Mixpanel helped Mixpanel get their $865M valuation. Mixpanel is solving a huge problem with a bunch of software, gobs of data, and smart people. Beyond that, they're pulling in revenue. Regardless of how good, or how brief your deck is
405.
by Xorlev 12y ago
If the decoder wasn't in JS, that might not be the case. It'd undoubtably be a more efficient native implementation (possibly with hardware support) were it integrated.
406.
by Xorlev 12y ago
Having been on both sides of the coin, once you hit 600 reqs/s without a prior arrangement, that almost qualifies as a DoS attack. If they'd maintained 200-300 req/min would have been pretty acceptable.
407.
by Xorlev 12y ago
For me it was the closed-source new test cases. That marked a turning point for the direction of MySQL (IMO).
408.
by Xorlev 12y ago
Wondering if any CitusData folks can speak to whether this is being used for production workloads anywhere yet. If so, could you speak to the size/throughput of those deployments?
409.
by Xorlev 12y ago
I wonder if you used a Google account in good standing for a bot, at what point would they start to detect it was a bot? I imagine if you used it for more than a few CAPTCHAs daily you'd probably end up having to do additional validati
410.
by Xorlev 12y ago
Github has gone through great lengths to begin supporting diffs on all sorts of files, 3d volumes, images, and all sorts of assets. I'd be willing to bet that some sort of bundled asset management is someone's dream project at Git
411.
by Xorlev 12y ago
I love Java 8 streams, but they're still awkward compared to Clojure.
412.
by Xorlev 12y ago
Once you get used to working in Java (and have a relatively stable toolchain you can depend on), it's realistic to develop applications in Java almost as quickly as Clojure, though complex aggregations that Clojure makes one-liners wil
413.
by Xorlev 12y ago
OCaml might be mainstream to armchair FP developers on HN and language theorists at Facebook, but it remains a fairly unpopular choice for developing software outside academia. Even Haskell is pretty unpopular relative to the amount of soft
414.
by Xorlev 12y ago
They do offer free SSL with SNI. But that's not viable for most people given the number of popular older browsers missing SNI support.
415.
by Xorlev 12y ago
It'd be a lot more valuable if it offered some initial organization (e.g. by primary language, or by author). Otherwise I'm left with several hundred stars to categorize. The interface is gorgeous, but doesn't really do much.
416.
by Xorlev 12y ago
You can just use RDS m1.smalls then. We have databases that are 20-40GB running off smalls with relatively high throughput (more than I expected when builiding it for sure). $200/mo minimum pricetag is extremely high for 300mb of data,
417.
by Xorlev 12y ago
You probably aren't the target audience if your database fits in RAM.
418.
by Xorlev 12y ago
I think Go has a long way to (forgive the pun) go before it can really start to compete with the entire Erlang ecosystem. Only having a modest knowledge it both, Erlang is still built around stability. Hot code patching, an extremely instru
419.
by Xorlev 12y ago
You need quorum writes and reads. Like Cassandra you can use timestamps even though vector clocks would be much preferred.
420.
by Xorlev 12y ago
You should assume you're compromised regardless. More than researchers could have known about the vulnerability.

More ›