Searching for "Node.js Jobs"
Result:
- PHP
- PHP
- BPO
- PHP
- Call Centre
- PHP
- PHP
- Node.js with PHP (wtf?)
- .NET
- Call Centre
- PHP

It's not like you should care about the majority of the companies out there anyway. Aim for the good ones that actually know what they are doing, that way you'll learn why more on your job too

@Zennoe There's a lot of multi language projects. Once you grow to a certain size, it's even stupid to say "we only use language x" — because you're forcing teams to work with tech they're less comfortable with, sometimes even less suited for the job.

At work we mainly use VueJS with a Laravel (PHP) backend, a whole bunch of Go and NodeJS microservices, R and Python for statistics & tensorflow, and Rust for some custom devops/database stuff.

@bittersweet ++ for R 😊
Always happy to see a fellow R user

Thank God. I though me learning php in this age would lead to no avail. I guess not!

It's funny because my two main languages right now see php and node

@eArshdeep Learning PHP in this day and age is like learning to ride a horse to be a courier 😁. It works but I mean... Why?

@Froot No reason. I followed a learning path on Lynda because I didn't went to stretch my attention to everything that was out there. It happened to start with php, go to ruby and than finish with node and some packages. I learned php and then skipped on to node.

@eArshdeep Oh nice. Having knowledge of many languages never hurts :)

Yeah. At my job we use Java, PL/SQL, C#, and COBOL

What is the problem with PHP and NodeJs togather ?? I'm actualy working on a project using both techs ?

@Froot because there is a huge equine industry with a lot of rich people willing to pay for horseback riding lessons.

@Froot PHP is organic, ugly and full of muddy shit, but it's resilient and works for many companies. It's one of the easier OOP languages to learn, so it's relatively easy to recruit juniors for.

Yeah, it's messy, but add enough style checkers, type hints and unit tests and it's quite "usable". Not always a pleasure to work with, but good enough.

Our opinions as developers about language quality actually matters much less than we often think.

It influences long term market trends. Really long term. Hip languages and frameworks might be objectively better, but are they resilient? Will Rust replace C? Will NodeJS people flock to Go, Elixir, or whatever tickles their concurrent threads? There's so much uncertainty, devs keep hopping, and PMs want to core of the project built using a common, old, boring language.

20 years ago people liked PHP better than C++ CGI scripts, and in 20 years people will probably still start new PHP projects — it's awful, I'd pick any hipster language over PHP, but I know PHP will keep sticking to the backend development market like a piece of chewing gum to hair.

@bittersweet too much hate for PHP un one comment haha :D :P

@Baguette Not hate, tough love.

Woah! BUT Laravel looks amazing!

@nikolatesla It is the best PHP framework in my opinion — as long as you're aware of how badly it breaks OOP principles.

It makes a lot of things easy with dirty magic.

That doesn't always scale well, so for large projects it pays off to move functionality to nicely isolated services within the framework, or completely separate microservices.