> In today’s article, I am going to create a chatroom using Laravel 5.4, Pusher and VueJs. Since these tools are popular and almost every developer has heard of them, I will skip the theoretical introductions and discussions and go straight to the fun part.
I, uh, I don't think almost every developer has heard of them. Even making the names links would help.
I think your information there is quite dated. I can understand if you want PHP4 to die, we all do, but, to say that 'PHP should die', ignores all the benefits PHP has been bringing to the table. You only have to look towards Symfony, Laravel, and the language ever popular CMS is made in to get a better understanding of why its done. Once you know that, make some points about that please, rather than generalized statements with no backing.
And, Why is Django any better? Frankly, I find python to be a terrible language to be productive in due to its syntax and lack of types. PHP has lack of types, too, but atleast the variables are marked.
Also, what is wrong with that explicit construct line? Its a constructor, it says it right there.
Sorry to bust your ignorance and/or biases, but laravel is actually a really powerful modern web framework and PHP7+ is marching right into the modern programming era.
You're making such negative claims.... based on not liking how a php constructor looks?
A php array is pretty standard syntax... ['x' => 'y', 'z' => 'a'..]
I've worked in both Rails and Python and PHP 7.0 is actually equivalent to most modern web languages. Type hinting, lambdas, function chaining, generators, etc., etc.
Spaghetti code is because of the developer not the language. I'm sure even Erlang has it's fair share of spaghetti code apps.
I spend all day sitting on an IRC style 'chatroom' with a bunch of friends, that was written about decade ago.
It uses a combination of javascript ('ajax') on the client side, and crappy ASP on the backend (because the only server at the time that was available was a Windows server).
The comms is very simple asynchronous polling and formatting/parsing javascript. In fact the only updates over time have really been all client side to take advantage of new browser features. It works through firewalls and proxies (which websockets still do not) - basically anywhere you can see a modern webpage.
My rambling point is... you don't need all these frameworks to push a message to a server, and fetch back a list of new ones. In fact for low volume handful-of-users chat traffic you don't even need a database (gasp!).
I know we should all avoid re-inventing the wheel where possible, but are you (not 'you' the OP, but 'you' the fictional reader) really a web developer, if all you are doing is gluing ever changing frameworks together ??
Most applications use SockJS or Socket/Engine.io instead of raw websockets, so you get the latency benefits when websockets are supported while still functioning (probably better than AJAX on a timeout with long polling) when they're not. I know your old architecture was simpler, but fetching periodically from a server is high-latency and bandwidth inefficient.
Most people are here to learn, to build something more advanced, and/or to build something prettier. No need to condescendingly pretend like everyone else should be judged by your needs and nostalgia in a chat room.
I wasn't. I was challenging the modern need to just bolt pre-existing frameworks together. I WAS hoping for a discussion about it. Maybe my intent was not clear. Apologies.
I'd welcome other opinions, but I find Laravel's support for 3rd party tools/frameworks to be genuinely superb. They save me time on ramp up and implementation, which is often the single biggest bottleneck for shipping side projects.
Pusher is one of many Pub/Sub mechanisms laravel supports [1], and Vuejs is included "out of the box".
Point is, these frameworks aren't exactly bolted together any more or less than any other software integration.
I'm not seeing a valid axiom to base that point on, either. I can use a framework and release an MVP in a month, or I can spend an entire year writing the equivalent of a framework and then release an MVP a month later (my custom framework lacking the battle tested stability, security, and peer review from a formal framework's community). Multiple frameworks exist to cater different projects and different opinionated teams. Laravel isn't even a fully reinvented wheel, it uses a lot of symphony components, it is compatible with a lot of generic PHP libraries, it uses some standard tooling like composer and webpack. By not writing my own custom framework, I can pass off my project to another team or my client can hire any random PHP developer.
I think he quite literally means the only server available to host it on was a windows server, although I still don't see why that limits you to asp at all.
> In today’s article, I am going to create a chatroom using Laravel 5.4, Pusher and VueJs. Since these tools are popular and almost every developer has heard of them, I will skip the theoretical introductions and discussions and go straight to the fun part.
I, uh, I don't think almost every developer has heard of them. Even making the names links would help.