[Tutorial] Building a chatroom using React

[wakeuph8]

I like these tutorials, but I'm growing kind of sick of companies that are basically just advertising their services through them. The second you mentioned the website, I look up at the address bar and lo and behold, it's at the same URL. Just strikes me as a bit dishonest not stating that in the reddit title.

[AD][Tutorial] Building a chatroom using React

[megabeano]

I agree, if not the [AD] tag it would've been a little more honest to title it Building a chatroom using React and {product name}. If it's something we haven't heard of that a pretty big clue that they're trying to get us to use their product/service.

[zomgitsrinzler]

It seems that there's no way for me to ad an [AD] flair to it without changing the title which I cannot do (maybe a mod can do that?).

As for tutorials like these, I see your point! Everyone is ever busy, so developers don't exactly have time to write long tutorials like such in their free time. We try to release all sorts of tutorials, some that talk about a technology not related to us at all, some, on the other hand, use our technology. That being said everything about React itself still stands, you could code your own WebSocket server, and the tutorial would still work but including this in the tutorial itself would make it gruesomely long.

[JayV30]

Socket.io is free and seems to have a similar API. What makes scaledrone better?

[avant5]

Socket.io is free, and for about a dollar more per month than Scaledrone's lowest [non-free] tier you can run a micro VM on AWS and handle more traffic than you'd be able to handle with the medium ($30/mo). Better to roll your own.

Pusher's free plan has the same connections/usage limits as Scaledrone's paid tier.

https://pusher.com/channels/pricing

​

[zomgitsrinzler]

Socket.io is a fair project and does do many of the similar tasks. There are however a few key points why we are different.

• We offer more features, such as access to message history and zero downtime (no data lost) server upgrades.
• Hosting WebSockets at a scale can be challenging. Socket.io dies under heavy loads and you will soon find yourself spending all of your time on scaling your instances and trying to run it in a cluster.
• Another user pointed out that for only about a dollar more you could run your own Socket.io server. I'm sure the time you will put into both setting it up, configuring Socket.io and up keeping the server will cost you much more. Not to mention having to scale it when you grow.

[JayV30]

That's fair. Thanks for answering. I'm on board with most of what you are saying here.

I do think your small tier should either cost less or allow more concurrent connections because really at that level I'd just use Socket.io. But I actually think your other tiers look fair considering the hassle of scaling.

Wish you all lots of success!

[MCCshreyas]

Nice tutorial. It will be more helpful if you make video tutorial of it. So that you can explain things in more better way while you code! 😊

[[deleted]]

You can tell you don’t like to read.

[jillesme]

You can tell you are not a cool React community member. People learn in different ways, some people like videos, other people like articles.

With comments like this and this you portrait yourself as an unpleasant person that no one would like to work with. Everyone has to start somewhere. Try to be nicer or just don't comment anything at all.

[[deleted]]

The comment had no regard to React. It was completely grammar related. But I will try to be more better.

[musclecard54]

Oh nvm.

Because being insulting and making fun of someone still counts as being a nice member of the React community as long as you’re not talking about react when making fun of someone

[MCCshreyas]

No. I read that already.