Laravel is fine and used as the backend for lots of apps. The main change over the last few years is that the frontend is usually decoupled from it and has some kind of JS framework executing in the browser making requests to an API running Laravel (or some other framework).
Yeah but that's fucking gay. I've worked with Node and I fucking hate it. Trying to set up Elixir and laravel echo is GAY NIGGER AIDS. I want something that actually just works. Laravel Echo crashing all the fucking time was the main reason sockets sucked on 9.
You're mixing up lots of different things. Go has nothing to do with Rust.
I am mixing up nothing homie. Try reading. I am saying that PHP has no sponsorship.
I can find nothing about Rocket being a Mozilla project.
Sadly, Node has it's dick stuck into almost anything browser-facing in current year.
Person who writes PHP for a living here. The argument that "PHP is dying" is one I hear from one of my clients who pays me to write PHP all day, and even more ironically, his proposed replacement would be done in Python, which is even older than PHP.
As a PHP pro, what are your thought on Hack, Facebook‘s PHP clone?
Their decision to stop parity with PHP was retarded. The KF ran on HHVM for a brief period of time before the launch of PHP7, at which point the PHP team shoved its foot into Faceberg's hostile takeover attempt and after that they just gave up to make their own thing.
Have you looked at Discourse? I don't know how it will handle the traffic load, but it's FOSS
I haven't really paid any attention to it. I don't really understand why every tech company has to invent their own Yet Another Programming Language nowadays (Google and Go, Mozilla and Rust, Apple and Swift - at least each of those has seen some spread outside of their parent companies, unlike Hack). I don't know, maybe Hack is the greatest thing in the world, but I'm already pretty invested in the PHP ecosystem and not in a great hurry to re-learn something new.
I've actually never heard of it before today. It looks cool if something really low-level is necessary, but I gladly work in much higher-level frameworks where it's just a given that efficiency will lose out to flexibility sometimes. I can understand that your priorities are quite a bit different from my clients', but I still would not be looking forward to writing a full-featured forum system starting with basically a framework for serving TCP responses. I'd start with the forum system and try to get it running as efficiently as I need it to; it seems like much more productive work. But that's just my perspective.
I would not recommend a Node.js backend in Current Year. It's dying a slow, miserable death in enterprise settings because people are starting to catch on that a single thread of control waiting on a million "async" callbacks is a nightmare. We probably use npm for some package management for our UIs since it's pretty unavoidable with a lot of JavaScript frameworks but we've purged any NodeJS services from our ecosystem.
No idea, but that's pretty crappy. If they really want to claim DB agnosticism, they should have their tests test against all of the DBs they claim to support.
Discourse is bad software, irritating as fuck to use and runs like shit. Speaking from long experience of using TDWTF forums back when they were a testbed for Jeff Twatwood's crappy designs.
I have no experience with admining it or using it in a large scale. I just know it's free (as in freedom) and plenty of orgs and communities set it up. Convenient "worse is better"?
