solid VS Angular

Looks like its still in the discussion phase, did not see a timeline but also did not read super close. Did learn about the tanstack-router which I had never heard of, so that was worth looking this up right there ;)

https://github.com/solidjs/solid/discussions/2425

Tip Learn why JavaScript frameworks need keys to render arrays. Also learn why SolidJS is an exception to that

You can read more about it and leave your thoughts here: github.com/solidjs/solid/discussions/2294

GitHub | npm | website

The reactivity core, which is in https://github.com/solidjs/solid This is where you'll see the reactivity runtime implementation. Take note that Solid's reactivity doesn't rely on compile-time magic

I did try this but I'm not sure what you mean with the ssrLoadFrom. Is there any documentation on this, all I could find was the examples folder in solidjs: solid-ssr?

This is very true. I really hate svelte single file components. But then I tried JSX for breaking things down. I love solid but I don't feel really good about angle brackets within C style syntax. I saw this Scala library that stick with simple statically typed function syntax than html tags. I don't understand why people still wants to stick with xml like tags. In laminar markup is written like this scala div( h1("Hello world", color := "red"), inputCaption, input(inputMods, name := "fullName"), div( ">>", button("Submit"), "<<" ) ) I wish solid team makes their HyperScript syntax as performant as JSX.

What is Solid?

With both the HTTP Resource (more on that later) and the HTTP Client, we need to build the HTTP Resource request. In the upcoming PR for HTTP Resource, Angular has separated types and exposed a new type called HttpResourceRequest. If this is unavailable at the time of reading, you can take the following interface, which is extracted from the PR:

The PR relevant to httpResource: https://github.com/angular/angular/pull/59876

Selectorless template parsing #60724

@Component({ selector: 'app-root', imports: [ HttpResourceBlobComponent, HttpResourceArrayBufferComponent, HttpResourceTextComponent ], templateUrl: './app.component.html', changeDetection: ChangeDetectionStrategy.OnPush, }) export class App { version = VERSION.full; prs = [ 'https://github.com/angular/angular/pull/59876', ]; name = 'httpResource sub-constructors'; description = 'httpResource functions to query non-JSON data'; }

components bindings

UmiJS is an [extremely] pluggable enterprise-scale React-based web application [meta]framework, offering (as many analogs) routing, build tools, dedicated design system, and everything in between. From what I could see during my reconnaissance, its main market is huge enterprise monorepos for React websites and web applications (something very opposite to tools like, for instance Waku, if you will). Umi itself is not exactly a metaframework though, as I'd say, but rather something React would be if it aimed to resemble Angular as of version 19 — the powerful SPA framework with optional support for SSR/SSG and a whole lot of build options making it very customizable and approachable for performance optimizations specific to each particular use case. Its plugins-driven extensibility is something resembling Vite but for a more dedicated goal of building rich user interfaces. And there's more.

For more information, check out the Angular async pipe implementation on GitHub.

The PR of the feature: https://github.com/angular/angular/pull/57051

I second the Angular-style git commit message convention (https://github.com/angular/angular/blob/main/contributing-do...). Though, it is also art that I have lost.

On a lighter note, I recommend "8 Types of Commit Messages That Show He's NOT the Man for You" https://web.archive.org/web/20210606005031/https://www.codem...