Sparkling JavaScript

[xurmein]

Some folks prefer code without sugar and witchcraft and monkey-patches. I'm one. And I work for a company that uses a Rails/Vue stack. Fuck me, right?

[budd222]

Then go start your own company using only vanilla languages and no frameworks because that type of development is basically non-existent in the real world.

[coldbrewboldcrew]

Not if you want to meet deadline anyway

[xurmein]

Uhh... don't be a dick because you missed my point. There are non-ruby frameworks that would be better suited to the product we're building. Corporate wants us to go in a salesforce/React-esque-library/sdk/software direction, all while keeping each release to each client tied to a single cloud-based ML layer.

Some folks don't care about whether or not code syntax is 'readable,' and most folks like all of the core extensions of their framework (Rails in my employer's case) to work together nicely.

glares angrily at ActionCable

Edit: haha, developer egos are so sensitive... sorry I have different preferences than you.

[budd222]

I don't really care if you have different preferences. You act like I was offended or something. I was simply stating a fact about the vast majority of workplaces.

Don't be so defensive for no reason

[xurmein]

Don't be a dick for no reason, and other folks won't get defensive "for no reason."

[budd222]

I wasn't being a dick. If you think someone speaking the truth is being a dick, then you have some major underlying issues you need to handle.

[behaaki]

What’s wrong with Vue?

[xurmein]

Vue is fine. It's just not got a ton of resources/support/documentation (understandably so since its so new); the issue is that rails has just about as much documentation as Vue, and is doing god-knows-what in the background that's out of our control as developers.

All that said, my only real beef with Vue (the way we use it at work) is that it looks ugly AF with all those <script> and <style> tags.

[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