3 ms·

Thanks for that insight. I hadn’t considered the connection mechanics with MySQL as a usability point for PHP. I often cite the traceability of early PHP and i

Thanks for that insight. I hadn’t considered the connection mechanics with MySQL as a usability point for PHP. I often cite the traceability of early PHP and it’s one-file-per-url policy as usability features. Many of these features have been lost in modern PHP. A similar thing has happened with JS. There seems to be an opportunity for a back-to-the-roots platform that brings these things back.

brightball 8y ago
Before I discovered Elixir, I actually had every intention of building something along those lines. I was going to have an index.php that was only used in dev for routing, but when you wanted to go to production it would generate paths that you'd load into nginx...which when directly to each individual .php file behind the scenes. Entire goal was back-to-the-roots speed.
- erikpukinskis 8y ago
  If you can stomach JavaScript, I wrote a pretty aggressively don't-move-any-data-you-don't-have-to based web application server... https://github.com/erikpukinskis/browser-bridge https://github.com/erikpukinskis/browser-bridge ... with exactly that intention, of "ok just religiously only move exactly the memory I have to to feed a web browser". I need to take another look at Elixir....