131–140 of 162 posts
Earlier quoted context omitted.
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.
>Rust has a huge exposure in the programming community. 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…
Honestly, I ve done all the frameworks at various point, either they help touch your dom or clean your code, and now I teach noobs in JS at the bank to just do their own frigging well cut functions, around jquery and basta. The only thing I allow is a css preprocessor because that's a true progress.
There s so little to gain with a JS framework (I agree typescript is a good initiative tho) and so much to pay in time wasted. And God knows impatient idiots like to "migrate" "legacy", so the least surface you expose to "unmaintained framework", the least you hear those morons steering the company towards non productive migration work to get less than we started with :D
I've found the way to reduce churn the most is discard frameworks and DSLs whenever possible. This morning, I rewrote a page of frontend code for a scheduling webapp. I'd initially built it in TS/React years ago. Switched to Rust/WASM with a custom VDOM-based framework a year ago. I'm reasonably confident I won't rewrite it again in a new framework: the new page is an HTML document with an included JS script that per…
Is this custom VDOM-based framework not a dependency? Doesn’t sound like a web standard.
I hate javascript front-end stuff with a burning passion. I wanted to make a small widget, and somehow I needed 100+ libraries for this. The compilation/build/etc process makes no sense whatsoever, and I just type magic commands and hope it works. I am seriously considering just using something like blazor or phoneix live view so I can ignore front end entirely.
I've recently also played around with adding AlpineJS to it and it solves some of the issues I was having with LV.
I hate javascript front-end stuff with a burning passion. I wanted to make a small widget, and somehow I needed 100+ libraries for this. The compilation/build/etc process makes no sense whatsoever, and I just type magic commands and hope it works. I am seriously considering just using something like blazor or phoneix live view so I can ignore front end entirely.
Earlier quoted context omitted.
Why was the TS/react rewrite needed? Had react or ts broken it’s api?
React didn't substantially improve code flow, and added a dependency, config, a build step, and DSL. Typescript added a build step and config. Stated another way: The new page is a single file written in web standards. The React/TS way is more complicated, requires a bigger download, and is slower.
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…
Unfortunately the market is more driven by the latest FAD rather than rationality. I am of the opinion that the main responsables are WE, the software engineers. I have seen several times that SE in a position of influence will sistematically go for the latest FAD rather than make a rational choice (which in most of the cases IS the "boring stack") for the sole purpose of pumping-up their CVs. At the same time this is allowed by lack of competence and governance on the IT by the business. The bottom line is that our entire sector instead of progressing by leaps and bouds keeps on continuosly reinventing the wheel and makes only very small incremental changes and adaptations. The innovation and progresses in productivity that we had in the last decade pale with respect to the one that we had , just for example, in the nineties and are mostly due to an increase in processing power. And there is still much to be discovered: our sector is still very immature. In some way some of the experimental development environments that were available in the eighties were more advanced than what we have today.
Even if I am not a Ruby user and so my judgement could be superficial I have the impression that in the last two decades the only community that has consistenly tried trying to challenge the status quo and really improve productivity for our profession is in fact Ruby community.
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…
Then javascript framework came out. It was so hard that they move to just a todolist tutorial because even the creator didn't know how to create a blog with their new cool tech.
Some blogger were still able to understand how to use it and release todolist tutorial with authentication to demonstrate authentication, session management and rights.
Then new cool javascript framework came out and now it was even harder to code, creators weren't able to develop a todolist because it was too hard so their tutorial was just a basic counter application.
Now with nextjs we are even a step further. The developers don't know how to use it (is it even possible ?) so the tutorials show just how to "start" an application, load css and how to create a route.
In just a few years we came from create a full application to not even know how to do a todolist. (Imagine form validation, it must be so hard !!!).
Everybody seems happy and very productive. It must be myself.
In 15 years we came from 15 minutes to create a blog with this old tech to a few days of work. That's a lot of progress we don't have to reload the page !
Earlier quoted context omitted.
I enjoyed it while I used it but my main issues with it were with the developer experience and how many files the logic was spread across: actions, action constants, reducers, etc. When you have to edit 4 different files just to add a loading flag then I feel like something has gone wrong. If it solves your problems and you’re happy though, no need to let anyone convince you to change!
On really big frontend apps, redux with 4 files becomes the easiest part of the day. It may be verbose, but it’s the one thing that all the other devs won’t be implementing in some weird, proprietary way.
Recently I changed jobs and moved from being a front end dev to a backend dev role. Less framework chasing, more architectural concerns / long term planning, slower pace of development / expectations from stake holders and double the pay. For reference: I used to do backend dev but I did FE exclusively since 2016.