Hello world! in PHP is simply:
Hello world!
People forget PHP is still a template language for the web.
“Hello, (real) world” in PHP in 2017
61–70 of 144 posts
Re: “Hello, (real) world” in PHP in 2017
#62Earlier quoted context omitted.
Sorry but if you love PHP and use as your main language, why you don't complete any sideproject ? I don't understand your statement.
Side projects are natural places for programmers to get lost in this kind of bike-shedding/yak-shaving/etc., since they're not under the same kind of "this needs to ship on Tuesday or I lose my job" pressure that work projects are.
And in fairness, one of the better reasons to do a side project is to get up to speed on some fashionable technology so you can get a better job; that may well be of more value to you than the nominal deliverable, in which case it could make sense to prioritise it.
Re: “Hello, (real) world” in PHP in 2017
#63I don't mind this article as long as it's classified as satire.
Satire to an extent but also somewhat true.
Re: “Hello, (real) world” in PHP in 2017
#64Everyone's trying to take this literally as the "right way to display plaintext" in modern PHP. In that sense, it is absolutely absurd. But if the idea of a "hello world" is to learn the basic boilerplate that you'll need before you start implementing real features, unfortunately for us web developers, this quite accurately represents the minimum before we can even start implementing business logic. With the baseline…
Then again take a step back and look at what's being achieved. You are delivering, nearly instantly, a sophisticated and responsive fat client application to the user without any installation process. This fat client is running in a nearly universal and quite safe sandbox that is provided by several vendors across different os's, form factors, and architectures. With a good amount of backwards compatibility. Backed by a backend that's almost infinitely scalable. And developers are constantly feeding new features into this system without bringing it down or interrupting anything.
From that perspective, you would expect the tooling and stack to be complex. We really are doing way way more than we were in the "old days." "Write once run everywhere" has arrived and we're doing it, it's just not as simple as it sounds.
Re: “Hello, (real) world” in PHP in 2017
#65well, it is our job as programmers is to waste ... err ... utilize all that hardware power/bandwidth that Moore law has been showering us with...
Re: “Hello, (real) world” in PHP in 2017
#66'old' vs 'modern':
I run a search engine. It is big enough that it needs drives, caches, firewalls, VMs etc.
The front end is php. No classes, no phpadmin, etc. Just pure vanilla php.
Sometimes I tail /var access logs. People try all kinds of urls routinely fishing for weaknesses.
It's 2017. It is slow to code and keep the attack surface that minimal.
0 intrusions so far.
Re: “Hello, (real) world” in PHP in 2017
#67I get that this article is satire, but I think the deepest (perhaps) unintentional insight presented by the author's veiled criticism is that the justification for using these tools is presented as "it's 2017" and not as a solution to any particular problem. The issue isn't the 2017 ecosystem, the issue is the 2017 programmer's deference to vanity instead of engineering. All these individual tools exist for a reason,…
It's called "résumé-driven development."
Well yeah, why would you do anything else? When recruiters and job postings are mostly concerned with what languages and tools you know over software development ability and computer science knowledge why would you voluntarily make your life more difficult?
Re: “Hello, (real) world” in PHP in 2017
#68Using React, TypeScript, and Webpack in this context is ridiculous. Use tools that solve the problem at hand, not just because someone else is doing it...
But we're now using "Agile development", so I guess we have to use those things.
Re: “Hello, (real) world” in PHP in 2017
#69I get that this article is satire, but I think the deepest (perhaps) unintentional insight presented by the author's veiled criticism is that the justification for using these tools is presented as "it's 2017" and not as a solution to any particular problem. The issue isn't the 2017 ecosystem, the issue is the 2017 programmer's deference to vanity instead of engineering. All these individual tools exist for a reason,…
On a similar note, I always find it ridiculous when I have to do things like
apt-get install npm && npm install bower && bower install ...
Why can't npm be turned into ppa:nodejs and pip be turned into ppa:python?
Re: “Hello, (real) world” in PHP in 2017
#70I get that this article is satire, but I think the deepest (perhaps) unintentional insight presented by the author's veiled criticism is that the justification for using these tools is presented as "it's 2017" and not as a solution to any particular problem. The issue isn't the 2017 ecosystem, the issue is the 2017 programmer's deference to vanity instead of engineering. All these individual tools exist for a reason,…
On a similar note, I always find it ridiculous when I have to do things like apt-get install npm && npm install bower && bower install ... Why can't we just use apt-get and Makefiles for everything? Why can't npm be turned into ppa:nodejs and pip be turned into ppa:python?
Different tools specific to their job, they wouldn't be good to combine together. apt-get only exists for linux, requires root and is designed for that, npm doesn't. apt-get installs the latest version, npm expects more specific verisons since it's for code. npm is built for node's ecosystem and apt-get is better for system packages.