Angular feels like frontend framework built by backend java Spring developers, that hate frontend development.
Angular v8.0
41–50 of 210 posts
Re: Angular v8.0
#42Earlier quoted context omitted.
When a typical application spends multiple megabytes just for the webfonts and logo JPGs on the front page, I don't really care whether my application bundle is 200k or 500k, though. I care more about productivity. Now, this clearly needs SOME boundaries, but let's not start a whole "Electron" thread again :)
I think it's still worth paying attention to size of the JS download. If you download 500k of JS, it means that after ungzipping it, it will be 2mb or more. Your browser needs to parse and execute that code, which also takes time, and it impacts the user experience. Also it's easier (at least from developer's perspective) to deal with a big image than to deal with big JS codebase. You can't just replace it with somet…
Definitely, this is also why it's important that Angular is making strides towards reducing the total download size. This is, in fact, exactly what is happening with this release (and it will only improve when Ivy is released).
This does not mean the frontend community should continually be bending over backwards reinventing wheels just so the claim can be made that a certain package is now "only 1.6k GZipped!", imho.
Re: Angular v8.0
#43Earlier quoted context omitted.
Apart from being verbose, why is that a bad thing? Spring is used to successfully build massive applications. You can meme about Spring's AbstractFactoryBeans all day, but in the end it does what it's supposed to do.
I maintain a class library that is highly depended upon in the rest of our company. I don't like to introduce dependencies at my later because of that. So things like DI are all factory patterns / builder patterns. It's explicit and has kept my object lifecycle super manageable. It feels like the people who meme about EnterpriseFactoryFactory at times just haven't hit the right use case for it.
And if they do ever hit it, having never seen a reason to use it before, they instead layer over it with poorly thought out abstractions leading to unmaintainable code that they'll probably hoist onto the next dev.
Re: Angular v8.0
#44Angular feels like frontend framework built by backend java Spring developers, that hate frontend development.
https://github.com/jhipster/generator-jhipster/issues/9817 :)
Have to be honest, had to double check if this project was not satire.
Re: Angular v8.0
#45Congratulations on the release! For all the talk of React and Vue I still like the 'batteries-included' approach of Angular. I mostly do Kotlin in my day job so Angular aligns fairly nicely with the way applications are structured. I don't get the militant need for terseness that's seen in approaches like React Hooks. I also don't need the choice between multiple backwards-incompatible (or competing) routers, nor do…
I've been burnt by the non-Euclidian enormity of ExtJS, so I understand the desire for something simpler. On the other hand, when you leave the world of progressive enhancement and widgets (ie. jQuery), you find yourself needing a lot of common infrastructure and picking and matching that can be quite tedious (never mind dependency hell), which is something that react always had issues with -- and that seems to exten…
WebAssembly is still a couple of years away, sadly.
Re: Angular v8.0
#46Angular feels like frontend framework built by backend java Spring developers, that hate frontend development.
It feels familiar to Java developers, due to Typescript which is also statically typed (but much better IMHO) and due to the use of decorators and classes, which are an awesome way to describe a component. Being familiar to a large base of existing developers is a huge feature.
React has also been using classes for a long time (although the trend is to move away from them for performance and simplicity reasons). There is also a huge upward trend of people using TypeScript with React. Personally, after using TypeScript & Angular at work, I've preferred switching to TypeScript when using React in personal projects.
My main gripe with Angular (vs. React) has been the lack of first class support for patterns (higher order components) that have been a boon for React. It does look like Angular will have more 1st class support with Ivy[1], however, higher order components are so simple with React (and even better with TS/React).
[1]: https://blog.nrwl.io/metaprogramming-higher-order-components...
Re: Angular v8.0
#47Angular feels like frontend framework built by backend java Spring developers, that hate frontend development.
This feels like an argument made by somebody who has never built a serious project in either, and has instead formed an opinion based on quick glance at the respective syntaxes. To me, Angular is what HTML and the DOM would look like if they had been designed from the beginning for application development: - Custom elements backed by controller classes. - Data-binding and event-binding syntax baked into HTML - Compon…
Why does having a different opinion to you mean someone has no idea what they’re talking about, or has never used a thing “seriously“?
I used to love angular, then I got a job which was a “| async” dumpster fire and spent a year watching a team of smart c# developers wallow in a mire of disaster so bad it became a two week regression to change a text field on a form. So full of amazing functional statement no one, even the original authors, could touch it without breaking something in the process.
so.
Your milage may vary. I no longer particularly like angular, personally, because I find it a chore to herd inexperienced FactoryInjectorConstructorFactoryPattern angular developers into not screwing things up.
...but talented team can do well with it too, and I’ve seen people screw up react projects too.
It really is more about good practice and experience than framework, your personal preference is probably, like mine, basically irrelevant.
Re: Angular v8.0
#48I was recently at a Microsoft heavy tech conference and spoke to at least 50 .Net developers. Anyone who also did front end did so in Angular. I was surprised at how popular it is!
We're not doing .NET, however i suppose besides the fact that it uses TypeScript it is popular with MS developers, because it gives you a structure that allow to develop enterprise applications in larger teams.
If you know your application will have to be enterprise grade, will be large, will be developed by enterprise devs and has to be supported for years to come, Angular is still the definitive choice (IMHO). Mainly because it gives your team a clear structure to operate in combined with known concepts.
Re: Angular v8.0
#49Earlier quoted context omitted.
It feels familiar to Java developers, due to Typescript which is also statically typed (but much better IMHO) and due to the use of decorators and classes, which are an awesome way to describe a component. Being familiar to a large base of existing developers is a huge feature.
React has also been using classes for a long time (although the trend is to move away from them for performance and simplicity reasons). There is also a huge upward trend of people using TypeScript with React. Personally, after using TypeScript & Angular at work, I've preferred switching to TypeScript when using React in personal projects. My main gripe with Angular (vs. React) has been the lack of first class suppor…
> although the trend is to move away from them for performance and simplicity reasons
I do not think that react classes will go away anytime soon. you can't represent state without them.
Re: Angular v8.0
#50Earlier quoted context omitted.
https://github.com/jhipster/generator-jhipster/issues/9817 :)
Have to be honest, had to double check if this project was not satire. https://www.jhipster.tech/
The name does have a certain https://html9responsiveboilerstrapjs.com/ vibe to it, yes.