ditsmod VS Angular

My last measurements were when Fastify was v3.25, Restify v8.6 and Ditsmod v2.0. From that moment on, although Fastify remained in the lead, other frameworks came quite close to its results.

For those users who see this as a problem and want the framework they use to support this feature, I can recommend Ditsmod. This framework solves this issue as follows.

Good application modularity is closely related to the injector tree hierarchy that Dependency Injection (DI) creates. DI injectors are sometimes referred to as DI containers, but since NestJS and Ditsmod have taken many concepts from Angular, this post will use the term "injectors" (since it does in Angular).

This post compares NestJS v9.2.0 and Ditsmod v2.27.0. A finished example of validation with the Ditsmod application can be viewed at github. I am the author of Ditsmod.

A finished example from @ditsmod/cors can be viewed in the Ditsmod repository.

You can view the code with examples of the use of @ditsmod/i18n in the Ditsmod repository, although it is more convenient to view it locally, so it is better to clone it first:

Thanks to the system of extensions, Ditsmod applications are more expressive and with less code. For example, if you compare OpenAPI modules written in Ditsmod and NestJS, the Ditsmod module is 3.5 times smaller in the number of lines of code or the number of files.

Ditsmod є Node.js веб-фреймворком, його назва складається із DI + TS + Mod, щоб підкреслити важливі складові: він має Dependency Injection, написаний на Type*Script, та спроектований для хорошої **Mod*ularity (тобто модульності).

/** * https://github.com/angular/angular/blob/75a186e321cb417685b2f13e9961906fc0aed36c/packages/core/src/render3/reactivity/untracked.ts#L15 * * packages/core/src/render3/reactivity/untracked.ts * **/ export function untracked(nonReactiveReadsFn: () => T): T { const prevConsumer = setActiveConsumer(null); try { return nonReactiveReadsFn(); } finally { setActiveConsumer(prevConsumer); } }

source: https://github.com/angular/angular/issues/46542

Besides the dangers, mentioned by Angular docs (infinite loops, change detection errors), there is another thing, that might be quite nasty: effects are executed in a reactive context, and any code you call in effect, will be executed in a reactive context. If that code reads some signals, they will be added as dependencies to your effect. Here Alex Rickabaugh explains the details.

In June 2023, the Angular team raised a new RFC to implement control flow syntaxes within Angular. They gave the following rationale for introducing control flow syntax:

For scheduling, I use awesome code I found in the Angular source code.

Just to give you more context, I led the migration of several AngularJS applications to the newer Angular Framework. My client finally decided to make that move following the AngularJS deprecation announcement (stay up to date please 🙏)️.

Link — angular/CONTRIBUTING.md

Angular v17 was released some months ago with a ton of new features, a brand new logo and the new blog angular.dev.