5 ms·

I agree largely from a development perspective, but the client-side javascript frameworks are ultimately more performant, particularly on mobile, and are not as

by nwah1 8y ago

I agree largely from a development perspective, but the client-side javascript frameworks are ultimately more performant, particularly on mobile, and are not as bad as they used to be. Neither server-side nor WASM are ideal for mobile devices. Downloading many megabytes of .NET dependencies for a WASM app is obscene compared to like 30 kilobytes for React.

thefounder 8y ago
With 5g that won't be an issue anymore...
- sdfsdfsdfsdf3 8y ago
  In 2026 maybe...
- quantummkv 8y ago
  Until they decide that 5g is good enough to allow them to ship the browser with every website. Net speeds have been increasing every year and yet the websites take longer to load.
davidhyde 8y ago
> “30 kilobytes for React” This is just not even close to being true.
- namelosw 8y ago
  There's 3kb Preact with almost identical API.
  - StavrosK 8y ago
    So what's the other 27KB+ for?
    - dmitriid 8y ago
      Fiber, support fo async rendering, suspense, hooks. A different VDOM algorithm.
      - tracker1 8y ago
        Better error handling and messaging...
- nwah1 8y ago
  The compressed size is 31 kb, and other frameworks are smaller. https://gist.github.com/Restuta/cda69e50a853aa64912d https://gist.github.com/Restuta/cda69e50a853aa64912d
manigandham 8y ago
It won't be megabytes, that's only in the experimental phase. Binaries can shrink dramatically once run through a linker and trimmed down to only used APIs. As far as performant, I agree it wont matter in most trivial interactions but large datasets with computations already see an impact (for example we have million row datatables to show sometimes).
- TimTheTinker 8y ago
  > Binaries can shrink dramatically once run through a linker and trimmed down to only used APIs. It's worth pointing out that .NET Core has an assembly/executable generator that can package only the .NET libraries that are actually used.
- nwah1 8y ago
  Rust-based WASM front-end libraries will likely be small and also high performance. Unfortunately, all of the existing ones are highly experimental right now.

by nwah1 8y ago

thefounder 8y ago

With 5g that won't be an issue anymore...

sdfsdfsdfsdf3 8y ago
In 2026 maybe...
quantummkv 8y ago
Until they decide that 5g is good enough to allow them to ship the browser with every website. Net speeds have been increasing every year and yet the websites take longer to load.

davidhyde 8y ago

> “30 kilobytes for React” This is just not even close to being true.

namelosw 8y ago
There's 3kb Preact with almost identical API.
- StavrosK 8y ago
  So what's the other 27KB+ for?
  - dmitriid 8y ago
    Fiber, support fo async rendering, suspense, hooks. A different VDOM algorithm.
    - tracker1 8y ago
      Better error handling and messaging...
nwah1 8y ago
The compressed size is 31 kb, and other frameworks are smaller. https://gist.github.com/Restuta/cda69e50a853aa64912d https://gist.github.com/Restuta/cda69e50a853aa64912d

manigandham 8y ago

It won't be megabytes, that's only in the experimental phase. Binaries can shrink dramatically once run through a linker and trimmed down to only used APIs. As far as performant, I agree it wont matter in most trivial interactions but large datasets with computations already see an impact (for example we have million row datatables to show sometimes).

TimTheTinker 8y ago
> Binaries can shrink dramatically once run through a linker and trimmed down to only used APIs. It's worth pointing out that .NET Core has an assembly/executable generator that can package only the .NET libraries that are actually used.
nwah1 8y ago
Rust-based WASM front-end libraries will likely be small and also high performance. Unfortunately, all of the existing ones are highly experimental right now.