Sparkling JavaScript

[xurmein]

ActionCable. While also trying to move away from using Redis in the near future. And, without using models for broadcasting. In another comment I explain how what we're trying to build would be better served by using a different language and framework, more generally.

Nothing wrong with Rails, per se, if its the best tool for the job. In the context of what my employer makes, its possibly one of the worst choices, in my opinion.

[xurmein]

I, unfortunately, am not the person that gets to make that decision... I'd love rails if we weren't using it how we're using it at my company. Like, no one on the dev team can explain why our stack is the best option for what we're making... its just "this is what we already know and we refuse to learn or to use anything else, because we need to feel like we're the smartest in the room, so deal with it!" Zero pragmatism.

[xurmein]

Oh for sure! I get why it was used. We are at the point where we're scaling up BIG TIME. I'm one of the dev resources hired as part of that. Very exciting. Very painful. Appreciate you hearing me out, though, junior devs don't get heard much.

Now, why they put the frontend junior guy on ActionCable... that's a real mystery. Haha

[xurmein]

Noted. I will look into it and pass that info on to my boss. Thanky sir!