4 ms·
The reason why I checked both out was because I wanted to try my hand at Python and see what all of the hoopla was about. Unfortunately for me, the most memora
by rmrfrmrf 13y ago
The reason why I checked both out was because I wanted to try my hand at Python and see what all of the hoopla was about.
Unfortunately for me, the most memorable part of the experience was repeatedly calculating how many times I could have coded the exact same solution in PHP in the time it took me to finish a Flask project.
- wldlyinaccurate 13y agoI've had similar experiences with Ruby - I used Sinatra to write a really simple REST API, and while getting the core stuff working was relatively simple, there were many times towards the end when I wished I'd just written it in PHP. Oh, and don't even get me started on deployment.
- rmrfrmrf 13y agoI think we should get started on deployment considering how often it's swept under the rug as something that the "lowly sysadmins" have to deal with.
- TylerE 13y agoPHP deployment gets really painful at decent scales. The process model is very poor leading to both high memory usage and high server load.
- elbear 13y agoSo you're saying that you would be more productive in a language that you've been using for longer.
- deleted 13y ago[deleted]
- poulsbohemian 13y agoI actually have the same sensation, only for me it is about how much faster I could crank out a solution if I was using Flask or Tornado. Django is probably fine for proof-of-concept style applications within a certain set of requirements, but too often it gets used for applications beyond its scope.