| ▲ | tredre3 2 hours ago | |||||||||||||||||||
What else would you use to power the configuration gui frontend? Allow me to eliminate some of the obvious and inevitable answers: - Rust didn't exist at the time - Go didn't exist at the time - nodejs didn't exist at the time - Java and Python likely used too much resources for a once-in-a-while used GUI Irrational hatred aside, that's literally what PHP was designed for. | ||||||||||||||||||||
| ▲ | elevation 14 minutes ago | parent | next [-] | |||||||||||||||||||
> Irrational hatred aside, that's literally what PHP was designed for. Yes, in 2005 you choose PHP, but in 20 years of operation, you don't revisit reconsider your architectural considerations? A fantastic avenue for hardening any product would be to replace a ~2MSLOC component (the PHP interpreter) with a 10K SLOC daemon that does only what you need. When you're a startup, expediency and funding prevent this, but by the time you're selling "solutions" and baking designs into ASICs you could have prevented this attack by putting a fraction of the effort into software. | ||||||||||||||||||||
| ▲ | citrin_ru 16 minutes ago | parent | prev | next [-] | |||||||||||||||||||
Lua? Tcl? both AFAIK have less vulnerabilities than PHP likely thanks to smaller code size. | ||||||||||||||||||||
| ▲ | cesarb 2 hours ago | parent | prev [-] | |||||||||||||||||||
> What else would you use to power the configuration gui frontend? Perl? | ||||||||||||||||||||
| ||||||||||||||||||||