Earlier quoted context omitted.
What does not work exactly? Here, everything is as expected.
I just think the site's been slashdotted, or whatever the term is on HN. Hackernewsed?
HN hug-of-death I think?
How to build apps pragmatically
21–30 of 51 posts
Re: How to build apps pragmatically
#22Re: How to build apps pragmatically
#23> Try to build a complex server-rendered web app with PHP because "It's more inclusive" or "it has better frontend performance". See you in 2030. Like Facebook, WordPress and MediaWiki? Bashing PHP is a popular pastime, but front-end performance and inclusion are not to be scoffed at. Especially not if your target audience has a different standard of living than that of a major European city. Personally, I'm much mor…
And no ones builds webapps in plain PHP anymore... there are high-quality modern frameworks like Symfony or Laravel with dependency injection, unit tests, template engines, etc.
Re: How to build apps pragmatically
#24> Try to build a complex server-rendered web app with PHP because "It's more inclusive" or "it has better frontend performance". See you in 2030. Like Facebook, WordPress and MediaWiki? Bashing PHP is a popular pastime, but front-end performance and inclusion are not to be scoffed at. Especially not if your target audience has a different standard of living than that of a major European city. Personally, I'm much mor…
And no ones builds webapps in plain PHP anymore... there are high-quality modern frameworks like Symfony or Laravel with dependency injection, unit tests, template engines, etc.
Tons of folks build apps in plain PHP, more so than use frameworks
Re: How to build apps pragmatically
#25More often than otherwise, I’ve found code duplication preferable over abstraction. I only abstract code when I understand the problem space really, really well (I.e. have solved it before), or when I can have some certainty the wrong abstraction won’t cost me too much time to fix.
Wasn’t it Fred Brooks who said, “Plan to write it twice, you will anyway”?
I fell into the trap of premature abstraction yesterday: I spent an hour breaking down functionality to make it “easier” to implement different backends, only to realise that the “abstraction” was strongly coupled to the structure of the single backend I’d written.
Young me would have forged on regardless because “abstractions”. Old me threw it away.
Re: How to build apps pragmatically
#26It's odd the author chose Django because it's "popular" and dismissed PHP because it's "old".
Laravel is far newer and more popular than Django and PHP is both newer and more popular for web dev than Python.
Why would the author insinuate Laravel (and presumably WP and the rest of PHP) will be dead by 2030? For that matter, is it pragmatic for a startup to worry at all about what the best choice ten years in the future will be?
Re: How to build apps pragmatically
#27It's odd the author chose Django because it's "popular" and dismissed PHP because it's "old". Laravel is far newer and more popular than Django and PHP is both newer and more popular for web dev than Python. Why would the author insinuate Laravel (and presumably WP and the rest of PHP) will be dead by 2030? For that matter, is it pragmatic for a startup to worry at all about what the best choice ten years in the futu…
> Why would the author insinuate Laravel (and presumably WP and the rest of PHP) will be dead by 2030?
I think the author meant that writing a complex server-rendered webapp in PHP would take very long, hyperbolically saying it would take until 2030.
Re: How to build apps pragmatically
#28It's odd the author chose Django because it's "popular" and dismissed PHP because it's "old". Laravel is far newer and more popular than Django and PHP is both newer and more popular for web dev than Python. Why would the author insinuate Laravel (and presumably WP and the rest of PHP) will be dead by 2030? For that matter, is it pragmatic for a startup to worry at all about what the best choice ten years in the futu…
> Why would the author insinuate Laravel (and presumably WP and the rest of PHP) will be dead by 2030? I think the author meant that writing a complex server-rendered webapp in PHP would take very long, hyperbolically saying it would take until 2030.
Ah, ok. That's slightly less strange, but still very strange given the productivity and ecosystem size of Laravel vs that of Django.
Re: How to build apps pragmatically
#29It's odd the author chose Django because it's "popular" and dismissed PHP because it's "old". Laravel is far newer and more popular than Django and PHP is both newer and more popular for web dev than Python. Why would the author insinuate Laravel (and presumably WP and the rest of PHP) will be dead by 2030? For that matter, is it pragmatic for a startup to worry at all about what the best choice ten years in the futu…
To be fair, per their About page, the author is 18 :)
Re: How to build apps pragmatically
#30More often than otherwise, I’ve found code duplication preferable over abstraction. I only abstract code when I understand the problem space really, really well (I.e. have solved it before), or when I can have some certainty the wrong abstraction won’t cost me too much time to fix.
"duplication is cheaper than the wrong abstraction"
i think i read that in POODR by sandi metz