slyphon

4 ms·

1.
by slyphon 14y ago
finally! someone needed to write this, if only to have something to point junior devs to. :)
2.
by slyphon 14y ago
This idiot just proves most of this: http://two-pi-r.livejournal.com/622760.html If you just want to stick up for your "favorite" PHP framework simply because it's the only f**king thing that you know, then go f**k yourself with a
3.
by slyphon 14y ago
We needed load balancers and at the time, the choices were ZXTM, ServerIron (which I'd used subsequently, and am very grateful we didn't pick) or F5. We'd had a truly terrible experience with an F5 reseller so we decided to meet with the
4.
by slyphon 14y ago
Hah, I didn't know that about the performance publishing. We used nginx for static content and as an fcgi front-end.
5.
by slyphon 14y ago
My bullshit detector is going off so loudly, I think I best go lie down. At my last company, we paid for a Zeus ZXTM license (which was an excellent product and very expensive for our little startup), and they didn't approach the level of
6.
by slyphon 15y ago
Seconded. Ruby has tons of syntax and is a much more complicated language to learn than Javascript. Also Rails is non-trivial these days. I picked up rails back in pre-1.0, and followed it closely until around 2.3. It's way more nuanced tha
7.
by slyphon 15y ago
Ha! Fair point. I thought it was an interesting trial in that all updates to our user data wound up being published into MongoDB. All the other tools we'd tried for this purpose, CouchDB, MySQL with both MyISAM and InnoDB and even "thousand
8.
Go Cry on Somebody Else's Shoulder: MongoDB is fine(blog.slyphon.com)
127 points by slyphon 15y ago|52 comments