The Real Reason Why SWEs Get Angry By New Tech

[@ScottHess]

Something which bugs me is that frameworks often solve medium-term problems, which leaves you in the world of having arbitrary stuff injected into your build, but also having to work around and behind the framework to address issues the framework doesn't accommodate. It sure is a hard problem, but having 9 similar things solving the easier bits of similar problems is worse for the developer than if those same people threw their time into making one or two options handle deeper issues.

[@username7763]

This is the problem with all frameworks. I first encountered this with MFC (Microsoft Foundation Classes). It solved some problems but it made others harder as we had to work around its limitations. Be very sure the framework you are using actually helps you before adopting. It will always have downsides, so be sure that its upsides are worth it first.

[@mvargasmoran]

angery at "new" tech for getting the exact same results but with a convoluted twist and overhead like React.

[@yuriy5376]

Compared to what?

[@macccu]

As person who grew up on PHP, mootools and jquery - React is pretty cool if you don't bloat it. JS on the backend on the other hand - oh boy. Just give me Rails or Laravel and let's start building actual product.

[@SweetInsanity]

@@yuriy5376 laravel mostly

[@mvargasmoran]

​@@yuriy5376 wondering about the overhead part?

[@atljBoss]

I'm so happy we're back to articles

[@u9vata]

Honestly I like the "its the same bit smaller and faster" libraries. Except that for web its not leaner and faster and they often just change one shit architecture to an other - so it is a subfield skill-issue not a general problem to be honest :D

[@brandonbraner]

It makes finding jobs harder. Do we really need to “know” all this shit

[@fallow64]

no

[@CharleyWright-w1y]

no, I started my current job having never used react or nextJS. I spent a week building a small clock app then proceeded to migrate a nextjs app over to our infrastructure and am now the main dev on it. If you understand programming concepts and are willing to dive into new stuff, you can learn most of this on the fly, at least to a good enough level that you can build something that works

[@codingrules]

I think it helps not learning something before it is something you need. So if suddenly all the jobs you are interested in requires HTMX then you should learn it, but why before unless you want to for its own sake.

[@StandAloneForever]

My experience with his story at the end. Over Xmas 2023 I worked on a new product for the job without being asked to solve a problem they had for years and allowing them to monetize the product, I've been told for hundreds of thousands. I was told good job, it was then given to a different dev, and I was put on a shit job and when my annual review came, I was only given a 2% raise.

[@baejisoozy]

I don't get angry. I get even. By not using the language or framework. Hence, I don't touch javascript. Brother ewww.

[@NiamhNikali]

me

[@codingrules]

Hate all the breaking changes of dependencies. They really need to minimize that.

[@npc-drew]

so bro actually went the harem way and chose both zig and jai. terrific.

[@Novacification]

What I hate, and increasingly so the more experience I get, is the bandwagoning around new tech/ideas. I work with frontend development, I don't mind most javascript frameworks and I work with React at my current job. But the idea that everyone has to replace everything whenever something new happens is exhausting. Lately it's micro frontends. No, our product doesn't need to be split into feature level chunks served individually in s all over our site and bloating our bundle sizes, just because you're annoyed that we currently only do a realease once per month. Our architecture and deployment model is ass. Let's fix that before we start adding 10x complexity for 5% extra flexibility.

[@DevvOscar]

"Super easy barely an inconvenience", deep meta cut.

[@Squashmalio]

RYAN GEOOOORGGEE!!!!!!!!!!!!!!!!!!!!!!!!! reference.

[@TaiGroot]

Yes BUT the changes in gorilla/http were so much better than the stdlib in terms of support for trailing slashe, URL params (not in stdlib originally) etc. that when gorilla abandoned the project, the standard library actually learned from the framework and pulled in all those features, they got merged into the stdlib. we have gorilla to thank for url params today.

[@explorster]

I am still using vanilla js and php. I'm doing great 👍🏻

[@not_a_cool_handle]

C# mentioned. les go

[@aev6075]

If you compare to other frameworks / libraries of same level, sure. If you compare to vanilla js, absolutely no.

[@Justin73791]

What is vanilla js, but the most flexible library of them all?

[@RenXZen]

why was this posted here tho

[@naung01]

he got too distracted playing wow. jk I don't know why either.

[@XDarkGreyX]

Flip consulted the crystal analytics ball

[@The-Dirty-Straw]

Well, you're here so stfu

[@oleksiistri8429]

i am using vanilla go and do not know what is the framework, i do not see a point to use them, they do not really bring something new, just a syntax sugar or +/- 10% orf performance and calling something like js framework - "a new tech" is so laughable. "a new js lib" or "a new bunch of js scripts" would work just fine p.s. there is a big difference comparing C language with Zig language and comparing 2 JS frameworks between each other. One of this cases is called an evolution, the other one is called - wanking

[@majidaldo]

Screw learning tech just to pad resumes. Employers should hire for competency but they are so lazy

[@Turksarama]

The problem is that it is _so, so difficult_ to test for competency with interviews. You can test for a very basic level of competency (can actually program at all) but finding actually good developers without just asking for prior experience is a difficult task.

[@Justin73791]

@@Turksarama So do a 60/90 day trial period, and actually let go of those who don't cut it in 60 days. Companies used to do this on the regular, now for some reason if you hire someone you're stuck with them until an act of congress happens.

[@sillysquirrel9979]

hey flip! Its wrong channel

[@xx-vg5fj]

lol Prime not releasing his websocket implementation means it doesn't work

[@oleksiistri8429]

it is not fully-fledged and has just too narrow purpose that probably not many people will need, especially if there are so many other websocket libs, so yeah, Primagean is right not releasing it, i would have done the same.

[@franciscogerardohernandezR1979]

New crappy frameworks never ready to do any actual work previous tech could do with as many bugs.

[@alekseykostyuk3806]

Am i the only one who can't here anything? Do you have sound?

[@Squashmalio]

javascript is jovian af