71–80 of 162 posts
Earlier quoted context omitted.
Hello! Thank you for pointing that out! I was a bit silly and somehow came to the (wrong) conclusion that "Lucas" (the first commenter) was the name of the author... I don't even know what to say lol. I just went a bit derp there.
Stop assuming that names are indicative of gender, dude.
Haha. I ignored the web dev scene for a year or two to work on something else. Angularjs vanished and nobody will hire you unless you have worked with react. Rest is gone and everyone is obsessed with graphql. Kubernetes really took off. React alone isn’t enough though, it’s nextjs and everyone is looking into trendy redux replacements now. Typescript is everywhere. Everyone assumes you can’t code your way out of a p…
A lot of people are probably soured on redux forever (that's how these things tend to work) but they've done a really great job with their hooks based API and especially the redux toolkit/RTK Query. Getting started today using the toolkit is so much more straightforward and easier to understand that it feels like a totally new library. If you're still living in the old school redux world of trying to explain containers vs components, mapStateToProps, how to build reducers from scratch, how to organize ducks, etc., you really should take a look at the newer tooling.
Earlier quoted context omitted.
How often do you see Rust mentioned here? Rust's actual use in the industry is minimal. Yes, it's growing, but it's relatively unknown. The small academic team I was on wrote a stats app package using Mithril. Nobody's using mithril, it's hardly discussed here, even though the author posts often. I truly believe that mithril is better than React or Vue people just don't know about it, it's not part of the hype cycle.…
Rust has a huge exposure in the programming community. I may not know how to write it, but I sure know what it is. It's not just limited to HN in awareness.
And it's used exactly nowhere. Can you name one project that is rust based and isn't part of the rust toolchain?
Haha. I ignored the web dev scene for a year or two to work on something else. Angularjs vanished and nobody will hire you unless you have worked with react. Rest is gone and everyone is obsessed with graphql. Kubernetes really took off. React alone isn’t enough though, it’s nextjs and everyone is looking into trendy redux replacements now. Typescript is everywhere. Everyone assumes you can’t code your way out of a p…
The speed with which Google moved things around 2012 was just stupid. Gwt to angular was fast and left basically no real migration path. Or recompense for having jumped on in the first place. I believe angular got better, but I didn't stick around to find out. React has at least been steady. It has some parts that I'm personally in the camp is over engineered. But, I think that is more that the scene encourages highl…
Huh? I did a bunch of React work a few years ago when everything was classes. Then I went off and did other stuff for a bit, and when I came back to React, everyone was using hooks.
Haha. I ignored the web dev scene for a year or two to work on something else. Angularjs vanished and nobody will hire you unless you have worked with react. Rest is gone and everyone is obsessed with graphql. Kubernetes really took off. React alone isn’t enough though, it’s nextjs and everyone is looking into trendy redux replacements now. Typescript is everywhere. Everyone assumes you can’t code your way out of a p…
What's wrong with redux? I've been using it in my last 2 companies, it scales amazingly and I think that's one of the stack in react that I'm comfortable with
What's not fine is having poured resources into a framework over the course of a few years, only for that framework to first cease to be necessary, and eventually become a barely-supported ball-and-chain.
This applies to almost everything released prior to HTML5. The problem is that re-writing isn't always an option, but the old stuff permeates almost every source file and is extremely expensive to decouple.
I suspect this will sooner or later apply to everything released immediately after HTML5. Eventually, everything used today will face the same fate.
There's something to be said for rejecting frameworks that aggressively inject themselves into code bases and which can't easily be extracted.
Earlier quoted context omitted.
The speed with which Google moved things around 2012 was just stupid. Gwt to angular was fast and left basically no real migration path. Or recompense for having jumped on in the first place. I believe angular got better, but I didn't stick around to find out. React has at least been steady. It has some parts that I'm personally in the camp is over engineered. But, I think that is more that the scene encourages highl…
> React has at least been steady. Huh? I did a bunch of React work a few years ago when everything was classes. Then I went off and did other stuff for a bit, and when I came back to React, everyone was using hooks.
Earlier quoted context omitted.
AKA, be a backend developer, because tech changes less frequently there and backend devs get more respect than front end and "full stack" devs, regardless of how talented they are. Sorry I said it, but it's true.
> backend devs get more respect than front end This has not been my experience. FE are expected to know a lot, and most backend devs I've known respect that.
I've performed both roles in my career but have always been impressed by talented frontend devs ability to make some otherwise batshit ui spec come to life ... but regardless, I was always paid more when I worked on the backend, and so was every other backend dev I knew. Maybe I'm the outlier.