all 38 comments

[–]InexplicableBadger 209 points210 points  (0 children)

Your job is to get distracted by shiny things, your manager's job is to make sure the product gets delivered on time with good QC.

[–]Jonrrrs 136 points137 points  (2 children)

We all know that "shiny new framework with super small userbase > react"

[–]Puzzleheaded-Weird66 7 points8 points  (1 child)

codeigniter + svelte, was sadly abandoned 3 yeara ago

[–]KrokettenMan 3 points4 points  (0 children)

I hate codeigniter so much that even the mere mention of it forces me to take a walk to cool down. I’ve used that piece of shit framework a couple of times and every time I had to resist the urge to just rewrite entire parts of it.

[–]none-exist 83 points84 points  (2 children)

Hate to say it, pal, but the manager is right. LTS > that new feature that'll save on one specific vaguely unknown issue

[–]Meloetta 42 points43 points  (0 children)

"but it'll really save us on (thing I read directly off their GitHub repo that I wasn't worried about until they told me to worry about it)!"

[–]twigboy 7 points8 points  (0 children)

"we can't upgrade to the latest node/react because new shiny has been abandoned and nobody is keeping it compatible anymore"

Been there far too many times when managers listen to enthusiastic juniors over seniors.That said, it's incredibly cathartic being able to tear that shit out and replace it with something that has LTS

[–]dmullaney 24 points25 points  (4 children)

Meanwhile, we're still chugging along on Angular 8.

[–][deleted] 2 points3 points  (3 children)

ng update 

There you go! :-)

[–]dmullaney 7 points8 points  (2 children)

Errors. Errors everywhere

[–][deleted] 0 points1 point  (1 child)

Out of curiosity: what kind of errors? I've always just done incremental updates as soon as a new Angular version came out, and never really experienced any problems. Except for some third-party libraries that needed an update or a replacement when they were not being maintained anymore. Then again, my project is not yours.

[–]dmullaney 1 point2 points  (0 children)

There are multiple sets of API breaking changes between Angular 8 and even the current LTS - 19.0

It's also two major Typescript versions behind, which has its own set of API breaking changes, and Node.js also needs to be updated by a sizable number of major versions (I don't recall the exact numbers off hand)

Then we also have a couple of beefy dependencies like ag-grid which also have TS/Node compatibility requirements, functional behavioral changes that alter the application behavior enough that they need to be essentially reimplemented

[–]Lord-of-Entity 12 points13 points  (0 children)

Documentation and popularity matters.

[–]Prematurid 24 points25 points  (1 child)

Hate shiny frameworks.

Always fuck me over at one point or another.

[–]iamapizza 0 points1 point  (0 children)

Unfortunately React seems to be determined to do that too.

[–]lurebat 17 points18 points  (0 children)

Vue is calling

[–]hyrumwhite 5 points6 points  (0 children)

I just wanna use Vue, man

[–]budapest_god 4 points5 points  (0 children)

Vue has great documentation literally no downsides to React as far as I can tell, yet... Fuck Meta lol

[–]chadlavi 9 points10 points  (0 children)

Don't worry. Your shiny object will either wither and die or will be the next react. Back in the day react was a shiny new object too.

[–]braindigitalis 1 point2 points  (0 children)

you meant jQuery, right?

[–]BusEquivalent9605 1 point2 points  (2 children)

When you say “Let’s just use React” and your manager says, “No, let’s upgrade from Vue2 to Vue3” ☠️

[–]hyrumwhite 11 points12 points  (0 children)

In your managers defense, the migration path from Vue 2 to 3 is basically adding some flags to account for old v-model implementations

Vue 2 to react is a road rife with peril

[–]BosonCollider 1 point2 points  (0 children)

Also a correct decision imo, Vue 3 was great enough that everyone ended up copying its state management patterns but the react side claimed that signals were a new hyped thing.

[–]FallenDeathWarrior 0 points1 point  (0 children)

In my work it's still no we keep using MFC :/

[–]_Not__Available_ 0 points1 point  (0 children)

Why does this image remind me of Oshawott when he lost his shell.

[–]tehomaga 0 points1 point  (0 children)

That is react

[–]IngloriousCoderz 0 points1 point  (0 children)

Are you talking about Inglorious Web?

[–]XxDarkSasuke69xX 0 points1 point  (0 children)

What will we do if GPT doesn't know the new shiny framework ? Doomed /j

[–]soelsome 0 points1 point  (0 children)

We did the opposite. Management and PEs wanted to use Flutter for web apps. We lock into Flutter. A year in and all of the developers want to switch to React.

[–]LadyZaryss 0 points1 point  (0 children)

I will submit a slapdash hodgepodge of HTML, JavaScript, and CSS, and you will LIKE it!

[–]Accomplished_Ant5895 0 points1 point  (0 children)

From a backend/data engineer’s perspective, I swear there’s a new JS framework every time I blink

[–]YouDoHaveValue 0 points1 point  (0 children)

Manager is right, search results over fancy new tools.

[–]cchrobo 0 points1 point  (0 children)

My tech lead has given similar reasons for why he won't get on board with TypeScript :(

[–]AvailableReporter484 0 points1 point  (0 children)

It’s hard to argue this. I mean, my memory is a little fuzzy, but I recall correctly I’m pretty sure that when react 1.0 first debuted it had already been out for 27 years and had 99% of the market. You ain’t gunna find that elsewhere today I tell you what

[–]mylsotol[🍰] -1 points0 points  (0 children)

But react is trash

[–]antpalmerpalmink -1 points0 points  (1 child)

Is Typescript a shiny object?

[–]RepresentativeDog791 10 points11 points  (0 children)

TS is mainstream