3 ms·

This is why I fully moved to flutter. Everything, including styling, is just a widget. It’s surprisingly liberating to write boring C# looking code that accurat

This is why I fully moved to flutter. Everything, including styling, is just a widget. It’s surprisingly liberating to write boring C# looking code that accurately describes a UI component without inheritance, overrides, style compiling, etc

b0m 2y ago
Hi. C# dev here. Would you please elaborate a bit how do you use flutter and C#?
- baueric 2y ago
  I think he means Dart code resembles C# pretty closely.
amonith 2y ago
Same, as C# dev I love Flutter. However I just know in my bones that Google will ditch it some day. It's been too many years without significant adoption and it will stop making sense in the corporate spreadsheet one day.
- frou_dh 2y ago
  At least according to this post which was on HN recently, Flutter lacking significant adoption is a myth: https://shorebird.dev/blog/dart-macros/#:~:text=Flutter%20has%20been%20%E2%80%9Cdying%E2%80%9D%20or%20%E2%80%9Cabout%20to%20be%20canceled%20by%20Google%E2%80%9D%20since%20we%20started%20the%20project%2010%20years%20ago.%20So%20I%20guess%20if%20%E2%80%9Caccounting%20for%201/3rd%20of%20app%20submissions%20to%20AppStore%20or%20Play%E2%80%9D%20is%20what%20%E2%80%9Cdying%E2%80%9D%20looks%20like%2C%20I%E2%80%99m%20here%20for%20it. https://shorebird.dev/blog/dart-macros/#:~:text=Flutter%20ha...
pjmlp 2y ago
Basically why Flash ruled back in the day.
notpushkin 2y ago
It also throws away HTML and throws everything on a canvas instead, which means three things: 1. Accessibility is now an afterthought 2. Giant runtime you have to download for every website 3. Bewildering non-native behaviour on mobile
- ripped_britches 2y ago
  Agree with you on the runtime. Things are better with wasm and wasmgc, but still you can’t use flutter for any website that cares about SEO. However for the “app” part (after sign in) it’s a one-time download, cached by service worker, only takes a split second. It would be really nice if flutter could produce a AOT compilation of the “semantic” HTML for the initial page and then hydrate it. Then it’d be pretty similar to waiting for JS bundles for interactivity.
  - notpushkin 2y ago
    My main gripe is that the DOM backend never took off. The WASM <-> DOM interop is cheaper than ever, especially if you bundle operations so that you don’t need to cross it as often. Still, they decided to implement everything from scratch :-(
llama_drama 2y ago
> Everything, including styling, is just a widget. And that's the downside. What would be just two or three nested <div>s in HTML+CSS turns into several screens of widgets, making navigation and debugging much harder. I once had an issue with extra margin in one of Flutter's built-in widgets and spent hours trying to figure out why - without success.

b0m 2y ago

Hi. C# dev here. Would you please elaborate a bit how do you use flutter and C#?

baueric 2y ago
I think he means Dart code resembles C# pretty closely.

amonith 2y ago

Same, as C# dev I love Flutter. However I just know in my bones that Google will ditch it some day. It's been too many years without significant adoption and it will stop making sense in the corporate spreadsheet one day.

frou_dh 2y ago
At least according to this post which was on HN recently, Flutter lacking significant adoption is a myth: https://shorebird.dev/blog/dart-macros/#:~:text=Flutter%20has%20been%20%E2%80%9Cdying%E2%80%9D%20or%20%E2%80%9Cabout%20to%20be%20canceled%20by%20Google%E2%80%9D%20since%20we%20started%20the%20project%2010%20years%20ago.%20So%20I%20guess%20if%20%E2%80%9Caccounting%20for%201/3rd%20of%20app%20submissions%20to%20AppStore%20or%20Play%E2%80%9D%20is%20what%20%E2%80%9Cdying%E2%80%9D%20looks%20like%2C%20I%E2%80%99m%20here%20for%20it. https://shorebird.dev/blog/dart-macros/#:~:text=Flutter%20ha...

pjmlp 2y ago

Basically why Flash ruled back in the day.

notpushkin 2y ago

It also throws away HTML and throws everything on a canvas instead, which means three things: 1. Accessibility is now an afterthought 2. Giant runtime you have to download for every website 3. Bewildering non-native behaviour on mobile

ripped_britches 2y ago
Agree with you on the runtime. Things are better with wasm and wasmgc, but still you can’t use flutter for any website that cares about SEO. However for the “app” part (after sign in) it’s a one-time download, cached by service worker, only takes a split second. It would be really nice if flutter could produce a AOT compilation of the “semantic” HTML for the initial page and then hydrate it. Then it’d be pretty similar to waiting for JS bundles for interactivity.
- notpushkin 2y ago
  My main gripe is that the DOM backend never took off. The WASM <-> DOM interop is cheaper than ever, especially if you bundle operations so that you don’t need to cross it as often. Still, they decided to implement everything from scratch :-(

llama_drama 2y ago

> Everything, including styling, is just a widget. And that's the downside. What would be just two or three nested <div>s in HTML+CSS turns into several screens of widgets, making navigation and debugging much harder. I once had an issue with extra margin in one of Flutter's built-in widgets and spent hours trying to figure out why - without success.