Live data from Hacker News

PHP in a JavaScript world

blonde.net

11–20 of 61 posts

Re: PHP in a JavaScript world

#11
post #6
post #3

Earlier quoted context omitted.

PHP was cool in the pre-SaaS era, where the only "cloudy" thing was renting webspace or server. You had to install and manage your Wordpress and co. yourself. I think >99% of the people who wanted a website (blog/forum/etc) had to call an IT guy to get this running. Now they just have to register for a SaaS and the most technical they have to do, is linking their domain to it.

I think 99% of the people wanted to link a domain to it, had to call an IT guy.

Probably, but fact is, renting a server and installing Wordpress on it ranges on another level than using a custom domain on a SaaS.

Re: PHP in a JavaScript world

#12
post #7
post #2

Wordpress, drupal, magento, phabricator, mediawiki, sugarcrm... These are vastly popular, feature rich out of the box tools in PHP, aka the "killer apps". As I don't follow the node community, what are the killer apps on the node side? Im talking about a complete piece of software, where I would want to set up an environment not for development but for running an application.

Personally, I'd say that the front-end tooling ecosystem constitutes the "killer app": - Minification: Uglify - Transpilation: Babel/TypeScript/CoffeeScript - JS Module Systems: Require/Browserify/Webpack/JSPM - CSS preprocessors: Less/Sass/Stylus - Linting: JSHint/ESLint/CSSLint If you're using a lot of front-end tools, you're using Node. And if you're using Node, you might as well use it to write your APIs.

That's not true for a simple reason : Many people who use these front-end tools, still use PHP to build website (like I do)

Re: PHP in a JavaScript world

#13
post #7
post #2

Wordpress, drupal, magento, phabricator, mediawiki, sugarcrm... These are vastly popular, feature rich out of the box tools in PHP, aka the "killer apps". As I don't follow the node community, what are the killer apps on the node side? Im talking about a complete piece of software, where I would want to set up an environment not for development but for running an application.

Personally, I'd say that the front-end tooling ecosystem constitutes the "killer app": - Minification: Uglify - Transpilation: Babel/TypeScript/CoffeeScript - JS Module Systems: Require/Browserify/Webpack/JSPM - CSS preprocessors: Less/Sass/Stylus - Linting: JSHint/ESLint/CSSLint If you're using a lot of front-end tools, you're using Node. And if you're using Node, you might as well use it to write your APIs.

I agree.

At this time Javascript's biggest strength is build tools. It may not be as mature as PHP on the server, but there is so much community growth that I don't think it will be long catching up.

Re: PHP in a JavaScript world

#14
post #2

Wordpress, drupal, magento, phabricator, mediawiki, sugarcrm... These are vastly popular, feature rich out of the box tools in PHP, aka the "killer apps". As I don't follow the node community, what are the killer apps on the node side? Im talking about a complete piece of software, where I would want to set up an environment not for development but for running an application.

[deleted]

Re: PHP in a JavaScript world

#15
post #9
post #2

Wordpress, drupal, magento, phabricator, mediawiki, sugarcrm... These are vastly popular, feature rich out of the box tools in PHP, aka the "killer apps". As I don't follow the node community, what are the killer apps on the node side? Im talking about a complete piece of software, where I would want to set up an environment not for development but for running an application.

PHP today is overwhelmingly being used to augment/modify: > Wordpress, drupal, magento, phabricator, mediawiki, sugarcrm... Very few apps are built from scratch using PHP unless the intention is to share the application code like wordpress, drupal, etc. On Node, you're almost always building from scratch, rather than creating plugins for an existing application. Apples and oranges. Different use cases.

Very few? There's plenty of apps out there written in PHP. You can do the same thing in PHP as you can in node. Writing from scratch is no greater of a use case for using node than it is for PHP.

Re: PHP in a JavaScript world

#16
post #7

Earlier quoted context omitted.

Personally, I'd say that the front-end tooling ecosystem constitutes the "killer app": - Minification: Uglify - Transpilation: Babel/TypeScript/CoffeeScript - JS Module Systems: Require/Browserify/Webpack/JSPM - CSS preprocessors: Less/Sass/Stylus - Linting: JSHint/ESLint/CSSLint If you're using a lot of front-end tools, you're using Node. And if you're using Node, you might as well use it to write your APIs.

That's not true for a simple reason : Many people who use these front-end tools, still use PHP to build website (like I do)

Sure. And lots of people that use Rails still use it to communicate with Java-based backend systems. That doesn't mean that Rails isn't Ruby's "killer app."

Re: PHP in a JavaScript world

#17
post #9
post #2

Wordpress, drupal, magento, phabricator, mediawiki, sugarcrm... These are vastly popular, feature rich out of the box tools in PHP, aka the "killer apps". As I don't follow the node community, what are the killer apps on the node side? Im talking about a complete piece of software, where I would want to set up an environment not for development but for running an application.

PHP today is overwhelmingly being used to augment/modify: > Wordpress, drupal, magento, phabricator, mediawiki, sugarcrm... Very few apps are built from scratch using PHP unless the intention is to share the application code like wordpress, drupal, etc. On Node, you're almost always building from scratch, rather than creating plugins for an existing application. Apples and oranges. Different use cases.

well, most node apps rely on many node lib, which is not very different than relying on a framework like symfony.

Re: PHP in a JavaScript world

#18
post #7

Earlier quoted context omitted.

Personally, I'd say that the front-end tooling ecosystem constitutes the "killer app": - Minification: Uglify - Transpilation: Babel/TypeScript/CoffeeScript - JS Module Systems: Require/Browserify/Webpack/JSPM - CSS preprocessors: Less/Sass/Stylus - Linting: JSHint/ESLint/CSSLint If you're using a lot of front-end tools, you're using Node. And if you're using Node, you might as well use it to write your APIs.

I agree. At this time Javascript's biggest strength is build tools. It may not be as mature as PHP on the server, but there is so much community growth that I don't think it will be long catching up.

It's like saying PHP as a great community, we will catching up JAVA soon.. non sense, as the topic said, I want to use node if there are some killer app that I want to use, like the one I know in other languages. Do you know any like drupal for example (multilingual, workflow, content management system, and more) ?
Post reply on HN