HerroRygar

6 ms·

1. 1.▲
   by HerroRygar 15y ago

   That's interesting...I can't believe I never noticed that.
2. 2.▲
   by HerroRygar 15y ago

   I also had this exact problem. I posted this question on StackOverflow about it, and the accepted answer led me to the solution I use now, which is identical to the one described in the article: http://stackoverflow.com/questions/9405148/h
3. 3.▲
   by HerroRygar 15y ago

   This looks fantastic! It also has the side effect of making me want to get back in to learning Clojure. The idea of the file not being the fundamental unit of code is especially intriguing, but hard to wrap my brain around - that's such a l
4. 4.▲
   by HerroRygar 15y ago

   I seem to remember reading that Facebook was using XHP, which allowed XML literals. That would certainly be an improvement over "warts-and-all PHP", in my opinion. Of course, I'll trust what an actual engineer from Facebook is saying over s
5. 5.▲
   by HerroRygar 15y ago

   Everyone is certainly entitled to their opinions, but I'm puzzled as to whether some of the people claiming that PHP's greatest strength is its deployment model have had significant PHP experience? As with most things, it's both good and ba
6. 6.▲
   by HerroRygar 15y ago

   There's a CoffeScript-ification of PHP called Snow. You can see it here: http://code.google.com/p/php-snow/ Frameworks definitely help a lot. I've done a little work with FuelPHP, and I found that to be pretty pleasant.
7. 7.▲
   by HerroRygar 15y ago

   Quoted from the documentation: "Every request is wrapped in a Node Fiber". So...essentially, this behaves like a traditional web server? A process listens for incoming connections, then spins up a new process/thread/fiber to handle the requ