I'm using Blazor (C#) WebAssembly and I'm really wishing it could do DOM manipulation. My favorite tool for that is Dart, so I'm working on marrying C# and Dart for my client solutions.
I almost felt like I was trolling by combining the two, but I'm actually using Dart and Blazor to see how they can work together because Blazor Wasm doesn't do DOM manipulation and Dart does it in such a easy to use fashion that the marriage feels natural to me.
I try not to attack back and have a bit of a sense of humor about it, but it does feel like suppression of thought on HN
Still, Dart had everything I wanted in a front end language in 2013. I think JS devs were short sighted to reject it out of hand. It's a shame it never caught on by itself and not as a just a Flutter language. I read that Google is using it in Fuchsia so there is still a chance Dart will be big in the future!
[1] TypeScript and Turing Completeness: https://itnext.io/typescript-and-turing-completeness-ba8ded8...
Some cool features:
1) Type unions
interface A { a: string; }
interface B { b: string; }
type C = A | B;
const c: C = { a: 'a' };
2) Type assertions if ('a' in c) { /* compiler knows c is of type A here */ }
function isA(c: A): c is A { return 'a' in C } // compiler knows c is A if this returns true
3) Nice helper types interface A { ... }
ReadOnly<A> // Like A, but all properties are read-only
Partial<A> // Like A, but all properties are optional
Omit<A, 'someProp'> // Like A, but without 'someProp'
E.g. look at this: https://github.com/telegraf/telegraf/blob/v4/src/telegram-ty...
Might I suggest being less sensitive/that your reasons are overblown?
Edit: I'm thinking of cognitive load too. I like to eliminate load I don't need. Keeping track of this is not something I want to do with my life
https://drpicox.medium.com/reducing-programmers-cognitive-ov...
There's absolutely no reason to make an arrow function a regular function just because it goes past a certain number of lines.
It really seems like you should become more familiar before forming an opinion. There's valid criticism to be made, but those aren't it.
http://www.synergeticapplications.com/ergonomics.htm
By the way, I feel like I'm at a bar and you're negging me
It would be even more interesting if there were a Dart.NET
Do you have any gotchas which isn't really mentioned on MS documentation site? primarily related to performance, since it will be one of my main concerns.
That's not to say it isn't cool and can't work for some projects where say, development speed is more important, but performant it just aint.
https://svelte.dev/blog/virtual-dom-is-pure-overhead
Edit: I didn't answer your question. There's nothing wrong with JS bindings. Both Blazor and Dart use them, which could get awkward going from Blazor -> Dart (as JS) -> JavaScript lib. I'm considering TypeScript again because no port is needed to call JS libs.