Earlier quoted context omitted.
> The only thing actually wrong with PHP, is that it's popular but not cool. Hey now, we're all human. Even engineers. As soon as something becomes popular, it is no longer cool. Cool is the next popular. Cool is being different. That's just how things work. Apache is slooooow (NGINX is cool!). MySQL is retarded (Postgres is cool!). PHP sucks (Python is cool!). Red Hat is lame (Ubuntu is cool!). See a trend? The tech…
Ubuntu is more popular than RedHat Linux
PHP Addiction
101–110 of 320 posts
Re: PHP Addiction
#102If you're a really good PHP developer and are considering using another language, you should ask yourself one question: Why do I need to switch? You've already gone through the pain of learning how to work around all of its warts, and you will lose a ton of productivity immediately after switching to a new language. This may seem trivial if you are just programming as a hobby (and fun, even, to learn something new) b…
Re: PHP Addiction
#103Re: PHP Addiction
#104PHP is good. I'm living proof of that. I'm a very successful developer and PHP does just about everything I ask of it. I also find it enjoyable (when you don't use crap frameworks or CMS' like Drupal). For those of you that do struggle with PHP, then what on God's green Earth makes you think you'll do any better with the next language? There comes a point when you've rifled through everything saying they are all junk that you gotta look in the mirror and ask yourself what's really the problem?
Re: PHP Addiction
#105Re: PHP Addiction
#106-Bjarne Stroustrup
Re: PHP Addiction
#107So if I was operating in the capacity of a recruiter for a project/company/startup, I'd definitely pick a skilled RoR dev over a skilled PHP dev, because the frameworks and the language themselves are handicaps for the PHP dev. Even if PHP is faster for a very small project, as soon as you move into a decent sized project, the frameworks start paying handsome returns for using them.
Note: I don't particularly love RoR/Django. Substitute with your favorite framework. It's just to illustrate a point.
Re: PHP Addiction
#108Earlier quoted context omitted.
Flask is not built for smaller web apps. The idea of Flask is to build a good foundation for all applications. Everything else is up to you or extensions. http://flask.pocoo.org/docs/design/#what-flask-is-what-flask... There's even an entire section in the docs about scaling your application up: http://flask.pocoo.org/docs/becomingbig/#becomingbig
You're completely right -- I phrased that badly. What I meant was that it lends itself well to small apps because the lack of code/architectural overhead, as opposed to Django, where coding small apps often feels like only furnishing one room in a five-bedroom house.
Django is good for getting small, simple apps up and running quickly. It all gets overly complex very quickly when you need anything more than that. For a big app, it's better to start with something small that can grow to meet your needs rather than starting with something big that you'll have to fight to do what you need to do.
Re: PHP Addiction
#109Re: PHP Addiction
#110Tumblr, Wordpress, Facebook, Instapaper, Wikipedia... PHP has a stronghold, an opensource equivalent implementation for each platform would take forever