Show HN: Realtime Chatroom Built with Laravel and VueJS

Show HN: Realtime Chatroom Built with Laravel and VueJS(github.com)

53 points by azazqadir 8 years ago | 20 comments

cwyers 8 years ago |

From the article that this code is from:

> 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.

prophesi 8 years ago | |

I'd say if you're a PHP dev, you'd know what Laravel is. And Vue is up there with React/Angular in popularity for Javascript devs.

Pusher is the only odd one; You'd probably only hear about it if you've looked into real-time communication technologies.

Jaruzel 8 years ago |

I must be so old.

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 ??

1ba9115454 8 years ago | |

You're friends were replaced by chat bots long ago. We've all been watching you like a mini ascii truman show.

Jaruzel 8 years ago | | |

I had suspected that actually.

fenomas 8 years ago | |

It's not a "here's the best way to make a chatroom" article.

It's a "here's how you can use Laravel and Vue" article.

yunyu 8 years ago | |

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.

Can_Not 8 years ago | |

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.

Jaruzel 8 years ago | | |

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.

rakoo 8 years ago | |

Then that's good, because you already understand perfectly what is being built so you can focus on the how. Which is the point of the article.

sfilargi 8 years ago | |

> and crappy ASP on the backend (because the only server at the time that was available was a Windows server).

I don't think there was ever a time that people didn't have alternatives to windows server and ASP.

Maybe there was a time that ASP was more popular than the alternatives, but I personally haven't observed such thing.

NTripleOne 8 years ago | | |

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.

Jaruzel 8 years ago | | |

I didn't write it - so I do not know the logic behind using ASP.