41–50 of 54 posts
Earlier quoted context omitted.
1 instead of zero index based languages such as e.g Julia therefore remove a LOT of cognitive overhead.
Not using indices at all when iterating whenever possible completely eliminates the cognitive overhead.
As an ex-AngularJS developer, who worked on porting a LARGE app to Angular - if you're in that boat, look into just rewriting in Vue. It's similar to AngularJS (more so than Angular) but with some extra niceties.
These days, I just do vanilla JS/HTML/CSS. In some cases we serve our pages using server-side rendering techniques via Blazor, so there is no tricky state synchronization game to play over the wire. But, Blazor is mostly just doing what PHP used to do for us. We aren't diving into their component/binding ecosystem any further than we need to.
Biggest advantage with a vanilla stack is that you will never get trapped on an old version of one of these things and be forced to "migrate" (i.e. "rewrite") your application each time. Vanilla also means you don't have to submit yourself to any arbitrary package manager, build toolchain, et. al. Your entire product can fit inside 1 html document that just instantly works in any browser.
Earlier quoted context omitted.
I worked on AngularJS and moved to Angular ever since 2+. It is a great platform and actually similar to Vue in some respects. No reason to abandon Angular although Vue and others are also good.
Angular is so different some AngularJS that it's really a different framework. At that point, as long as you're switching to a new framework, you should assess them all equally according to your needs.
I'm only a tad familiar with Vue, but it seems like you wouldn't have as many curve balls thrown at you by committing to that framework. Which makes sense with it being essentially 1 guy's project, rather than a giant like Google (who famously is not one to care for backwards compatibility)
Totally correct to discontinue the old AngularJS imho. Google, years ago, made one of the best choice adopting TypeScript for its new framework, Angular. I used to code in both AngularJS and Angular, and the improvement between the two is huge, thanks also to TypeScript. I'm a big Angular fan, even if I tried React, I highly prefer Angular for being more strict, complete and imho more suited for very big projects.
It's insane to me that websites need to be compiled these days. My websites mostly consist of an index.html and a code.js, and then unzipping whatever goofy template into the js, css, images folders etc. I feel like requiring a fluent understanding of the entire node ecosystem build even the simplest websites is a big enough hurdle that a lot of enthusiastic new people are just going to give up and do something else.
Earlier quoted context omitted.
Modern Spring framework (annotation driven, no more XML config hell) offers a lot. Spring Boot is one of the easiest ways to start a backend Java app, microservice or monolith. You get ORM, a web framework, dependency injection, messaging, and a whole lot more just by including the modules you want. You can learn the basics in an afternoon of reading documentation. The major IDEs have very good plugins. A legacy Spri…
> You get ORM, a web framework, dependency injection, messaging But you can get all that stuff without Spring, too. And Spring adds another layer in between you and the ORM, the web framework and the messaging framework - a layer that's heavily reflection-based and makes a ton of undocumented assumptions about how things are set up and throws cryptic error messages when those assumptions are violated.
Like any opinionated framework, it's going to make assumptions that can cause headaches, but it's mature enough that most issues I run into are a Stack Overflow away.
Earlier quoted context omitted.
> I'm a big Angular fan, even if I tried React, I highly prefer Angular for being more strict, complete and imho more suited for very big projects. I agree, I just moved us to Angular 13 and I love every second of it. I've worked on React projects but will take Angular any day of the week.
I'm enjoying Angular development too, although the Angular Material library is... not great. Lots of corner cases that just don't get enough attention.
It's under MIT also which is a bonus depending on your use case.
Earlier quoted context omitted.
You should have talked to an old GWT dev before starting down the road of using a Google maintained framework.
I’ve seen gwt. It smells bad, but it seems supported still. Can you elaborate on your comment so I have conversation points next time I deal with that team?