5 ms·

This is pretty cool. First I was wondering what for, but its great for their use case (embedded devices). Why not use a language for the web interface the devel

This is pretty cool. First I was wondering what for, but its great for their use case (embedded devices). Why not use a language for the web interface the developer is familiar with. Unfortunately, they're a bit late. Nowadays it would probably be cooler to use JS, if language popularity is the focus. Or maybe python. (Aside: I learned web development in the good old LAMP times. My silly gut feeling is still that PHP is pretty fast and flexible compared to Python which seems slow (on the server), and JS which is way too slow and fragile. I know it's completely backwards nowadays, but funny how what you've learned sticks. When I hear "JS on a Arduino" I always think "yeah sure....", but it's actually a clever idea, just like this.)

Kiro 13y ago
Is it Python really slower than PHP? If you could notice the slowness it seems like the difference would be pretty large.
- camus2 13y ago
  > compared to Python which seems slow This sentence doesnt mean anything. What Python task? What library ? what framework ? on what server? with which version ? ect... I can say PHP is slow too, just look at any PHP framework, lowest scores according to techempower benchmarks : http://www.techempower.com/benchmarks/#section=data-r8&hw=ec2&test=plaintext http://www.techempower.com/benchmarks/#section=data-r8&hw=ec...
- RussianCow 13y ago
  In my experience the difference in performance of the languages is negligible (assuming you have a solid PHP config). I run sites written in each, and I can't say one has caused me more performance problems than the other; it just depends on what you're doing with them.
- TheZenPsycho 13y ago
  "I know it's completely backwards nowadays, but funny how what you've learned sticks."
webjprgm 13y ago
I usually see arguments like this about language performance, but do people also argue about the difference from having a server process launch, configure itself, and stay open handling requests, like Ruby or Node.js, versus re-running initialization on each request like PHP? A lot of that initialization code is hooking together objects, reading misc config flags, and setting up request routing. But what about ORM? Ruby's ActiveRecord has to query the database for a schema, right? In PHP that query would be done every request rather than just once when the server restarts. Could this architecture issue have a larger performance impact than the minor differences in Python / PHP / Javascript / Ruby performance? (There were also plenty of discussions about event-based programming versus blocking + multi-threading back when Node was becoming popular. That is another example of architecture being more important than execution speed.)

Kiro 13y ago

Is it Python really slower than PHP? If you could notice the slowness it seems like the difference would be pretty large.

camus2 13y ago
> compared to Python which seems slow This sentence doesnt mean anything. What Python task? What library ? what framework ? on what server? with which version ? ect... I can say PHP is slow too, just look at any PHP framework, lowest scores according to techempower benchmarks : http://www.techempower.com/benchmarks/#section=data-r8&hw=ec2&test=plaintext http://www.techempower.com/benchmarks/#section=data-r8&hw=ec...
RussianCow 13y ago
In my experience the difference in performance of the languages is negligible (assuming you have a solid PHP config). I run sites written in each, and I can't say one has caused me more performance problems than the other; it just depends on what you're doing with them.
TheZenPsycho 13y ago
"I know it's completely backwards nowadays, but funny how what you've learned sticks."

webjprgm 13y ago

I usually see arguments like this about language performance, but do people also argue about the difference from having a server process launch, configure itself, and stay open handling requests, like Ruby or Node.js, versus re-running initialization on each request like PHP? A lot of that initialization code is hooking together objects, reading misc config flags, and setting up request routing. But what about ORM? Ruby's ActiveRecord has to query the database for a schema, right? In PHP that query would be done every request rather than just once when the server restarts. Could this architecture issue have a larger performance impact than the minor differences in Python / PHP / Javascript / Ruby performance? (There were also plenty of discussions about event-based programming versus blocking + multi-threading back when Node was becoming popular. That is another example of architecture being more important than execution speed.)