4 ms·
Title is misleading. Not getting excited about a new Next.js version doesn't mean you don't care about new technology. Maybe it just means that you don't feel
by ilaksh 3y ago
Title is misleading. Not getting excited about a new Next.js version doesn't mean you don't care about new technology. Maybe it just means that you don't feel like reorganizing your code or something. Relatively speaking it's still an incremental upgrade to your approach overall.
I am 45 and stopped caring much about new web frameworks many years ago. It's not that I don't find them interesting or even advantageous in some ways, I just don't feel compelled to bother learning in detail about most of them. Although I usually do look into them enough to get the gist.
You just can't pick up every single new thing. If you try then you won't ever get any real work done.
But some things you really have to take notice of. And this is subjective and usually not one right answer. For me, image and text generation was something I felt compelled to jump into.
A big part of this calculation is also social. If you are looking to pick up contracts or jobs, your choice of technology is important. And often picking up the latest trend will make that easier.
It really depends on the technology and what it offers you. I would say that getting familiar with the OpenAI API provides much more bang for your buck (depending on what you are trying to do) versus upgrading Next.js versions. That's much easier to get excited about.
- pitaj 3y agoHell, I stopped carrying about new web frameworks when I was 25.
- zabzonk 3y agoi have never cared about them
- sambapa 3y agoAnd I always despised them!
- spacecadet 3y agosame, complexity for complexity's sake.
- vsareto 3y agoTo be fair, some of those frameworks were compensating for JavaScript which had real issues as a quickly-becoming-popular language. SPAs were an answer to cross platform and device issues, given the web browser was the best cross platform piece of software used by the largest population. It made sense to try that vs making native apps on all the different platforms. The fundamental problem in the web space spawning all of these tools has always been JavaScript’s weaknesses though.
- spacecadet 3y agoI was there friend. I didnt agree, but hey, I left and we to "apps" for 10 years...
- onetokeoverthe 3y ago[dead]
- lawkwok 3y agoGenuine question, as someone who got exhausted and is out of the industry for the foreseeable future. How do you stay competitive or job hop when every post is looking for the latest web framework?
- googlryas 3y agoStop looking for work in tech places. It may require you to take a pay cut and work in a place viewed as a cost center though.
- danielvaughn 3y agoI'm honestly thinking about just picking up c++ or something and turning my attention to embedded systems. I'm sure there's a wealth of old tech sitting around that needs to be maintained.
- Shikadi 3y agoI'm in embedded, there's also cutting edge stuff to work on. The nice thing is you can be mostly detached from annoying web apis and frameworks and databases. The not so nice stuff is dealing with crappy vendors, using crappy tool chains, and spending a ton of time setting up automated builds. Sometimes I think about switching to true embedded (I do embedded Linux) but that tends to pay less
- vijucat 3y agoDon't choose hamster-wheel career tracks in the first place. Try to find Lindy paths [1], [2]. For example, SQL experts and DBAs. The rise and (mostly) demise of NoSQL actually cemented SQL's reputation as an irreplaceable technology. The latest Web framework is by definition non-Lindy: it's the new kid in town who think they know it all. grep is lindy, Unix is lindy, the qwerty keyboard is lindy, C++ is lindy, Computer Science is lindy, algorithms and data structures are lindy. Knowledge of the real world, whether it be finance or shipping, is lindy. Sorry, verbose reply, but I hope it helps. 1. https://luca-dellanna.com/lindy/ https://luca-dellanna.com/lindy/ 2. https://en.wikipedia.org/wiki/Lindy_effect https://en.wikipedia.org/wiki/Lindy_effect
- zitterbewegung 3y agoYea, either you pick the tool that is most suited to the job or pick the tool that you are most productive is. I agree about your sentiment about learning this that are important . I made a natural language network scanner and I got to speak about it at defcon. I never intended for people to find it interesting I just wanted to learn to apply LLMs . The source code is at https://github.com/zitterbewegung/saturday https://github.com/zitterbewegung/saturday and you can interact with it at +1 (825) 251-9142
- jodrellblank 3y agoHow do you know the tool which is most suited to the job if you never spend time learning new tools? And the tool that you are most productive in suffers from the Innovator's Dilemma - a new tool might make you more productive in the long term but will be a drop in your productivity in the short term; if you switch you'll lose what makes you competitive today, if you don't switch you'll lose out to people who are more competitive than you.
- deleted 3y ago[deleted]
- tgv 3y agoOnce you've seen 3 frameworks, you've seen them all. The novelty wears off, rather quickly. That's the difference between your first encounter and the 10th.
- angarg12 3y agoI don't care about new tech per se, I care about solving problems for me and my customers. When new versions of libraries/frameworks/whatever do that. That's exciting.
- danielvaughn 3y agoI'm just exhausted by it. I've been writing front-end code since 2009 so I've been here from the early jQuery days, and I don't have the energy to keep rummaging through docs to figure out how this new special thing (next13/astro/alpine/blah/blah/blah) deviates from standard web technology. I'd much rather conserve my limited energy for things that are inherent to the platform and actually exciting, like WASM or WebGPU.
- c0balt 3y agoMaybe offtopic but jQuery still kinda rocks for small proejcts. It's not the fastest nor does it do fancy compile steps to avoid the DOM but instead just provides an easy-to-use API for most common tasks. And as a bonus the documentation is awesome compared to mpst other new-ish JS frameworks.
- s__s 3y agoThere’s really no reason to use jQuery at this point. It made sense when the native APIs were lacking and inconsistent between browsers. That’s not the case anymore. Just use vanilla JavaScript.
- JeremyNT 3y agoThe big reason to use it now is that there are useful libraries built of top of it, and you already know it. The value proposition has changed though and there isn't a compelling reason to start using jQuery now, but if you are somebody who just stuck with it this entire time it still works and you are still as productive as you ever were. And as a bonus you didn't waste any time chasing failed fads along the way...
- deleted 3y ago[deleted]
- tim333 3y agoDoes anyone really care about Next 12 -> Next 13? On the other hand the rise of AI is an interesting thing. And Mars rockets and ebikes are cool.