Includes a bunch of awesome improvements like:
🅰️ New logo, brand, look and feel.
📖 New documentation site at angular.dev.
🛠️ 2.5x faster builds with application builder.
🕹️ New @if, @for, and @Switch@techhub.social control flow statements.
⏲️ New @defer primitive for improved lazy loading.
🔍 Improved debugging of dependency injection with visualization in #AngularDevTools.
💧 Hydration support leading to up to 50% reduction in LCP time.
And so much more I can't keep track of. We're really excited to keep this momentum going!
So I'm hearing issues from my s/o about #Svelte and it honestly sounds exactly like my painful days in #Angular 1, the bugs and issues that drove us as an industry to #React in the first place.
Are we really repeating two way binding mistakes again? Yes it lets you get started quickly but it causes so many issues down the line.
Is Svelte different? I've never used it, just curious what people think. Especially if they wrote old Angular.
The #web has always had "Events"; like clicks and keydowns, but you couldn't create your own at first. So #webDev did what it does and invented hundreds of ways to create custom events; #Angular bindings, #Signals, #Observables, #Rx Streams, etc.
ReactJS "Hooks" are just another form of this; they are just callbacks that are executed at certain times in a component lifecycle.
Thing is; we have #CustomEvent now! It's well supported since IE11 is gone.
@schizanon This is an interesting topic. I can't speak to the other frameworks, but I'm pretty sure #Angular listens to events with the same binding syntax:
<button (click)="handleClick>Click me</button>
So we should be able to consume native events.
As for producing them, I don't think EventEmitter will emit real events, but also I don't think that would be desirable here for two reasons.
First, event propagation: @Output() myEvent = new EventEmitter() isn't namespaced and we wouldn't want to leak that event to transitive parent components. We would need event retargetting which I think is only available in shadow DOM (and not all components use)?
Second, tooling: Declaring @Output is desirable to explicitly declare which events can be emitted by a component to serve autocompletion and such. Ultimately it probably could emit a real event under the hood, but we likely wouldn't want users to directly call dispatchEvent for tooling reasons.
For a long time, I was looking at all the endless IDE plugins and extensions, "must have" configs, Raycast, and I used to wonder: Why is there so much hype around snippets? Even when writing #Django views, I never really felt the need for them; I was fine with typing a few redundant lines myself.
And then I started learning and working with #Angular. I take my skepticism back.
Je cherche des #projets#openSource qui utilisent encore des vieilles version d' #angular.
Et pour ça je cherche un outils de recherche "sémantique".
EParce qu'en gros si je fais une recherche avec un moteur de recherche normal (ddg / qwant et autre ) je ne tombe que sur des listes avec toujours les mêmes projets à succès et avec des versions d'angular à jour.
Long story short: rushed work from external pressures often leads to a hodgepodge of code bolted-in over time, to “just work”, with no time for people to take a minute to improve their craft.
This leads to complex code that’s difficult to maintain, which means further changes not as thoughtfully applied as they should be, which further adds to its bulk and unwieldiness, and so on.
Pytanie do zorientowanych. Chcę zrobić aplikację webową i muszę zdecydować: #Angular czy #React? Tylko proszę bez uwag, że lepiej samemu napisać. Nie umiem tego zrobić i już. Każdy ma jakieś upośledzenie.
I‘m an environmental #physicist by training, but after three years of parental leave I started a new job as a consulting software #developer. I work(ed) with a lot of different technologies: #swiftlang, #java, #csharp, #cplusplus, #angular, #perl, … My preferred computing platform is the #Mac.
I am what I would consider a pretty boring dad to five kiddos, from Lawrence KS. I'm most definitely #introverted, and in a past life I'd much rather be #reading a good book or playing some #JRPG on whatever system is current.
I've been #keto for the last few years, doing maintenance mode for most of that time, with no plans to change any time soon. It's a lifestyle for me, not a diet.
I've got a handful of accounts on the #fediverse, one of which is my single user #mastodon instance. I'm trying different things out to see which I prefer most.
@swrogers -- My First Friendica Account @swrogers -- My Main Friendica Account, and main fedi account @swrogers -- My personal mastodon instance @swrogers -- My personal #FireFish instance @swrogers -- Over on the official Fire Fish instance @swrogers -- Over on Infosec Exchange @swrogers -- My main image uploading section, on #pixelfed social
I'm sure I've got more fediverse account out there, somewhere...it's not quite a #GottaGetThemAll deal, but it sure does seem like it!
Recently I started on a #Vuejs project at my new job. I've only worked with #Angular before.
One thing I didn't like it first, turned out to be an unexpected strength. In Angular, each component has a separate template, typescript & sass file. In Vue.js this is all inside a single file! Ugly and hard to use I thought.
Instead, it's a blessing. When a component reaches 100-150 lines, it already feels like a large component. Any larger? Time to split it up. It helps keep code clean.
@angular and @TauriApps form a robust combination for creating powerful apps.
Together, they offer an interesting blend of features, each balancing the other’s strengths and weaknesses.
👇👇👇
#Angular, is known for its completeness in managing complex applications. 💫
It employs a change detection mechanism and ahead-of-time (AOT) compilation, which optimizes apps by compiling components into highly efficient #JavaScript code before the initial load.
This enhances the performance of #Angular by reducing the need for client-side compilation and minimizing the amount of JavaScript downloaded and parsed by the browser.
However, Angular’s completeness can be a double-edged sword.
While it performs excellently with complex and large-scale projects, it might be overkill for simpler use cases where a more lightweight library could suffice. 🤔 ⬇️