I played with Ceramic a bit and it was nice to have built-in imgui support out of the box.
Haxe is a fun language. It could have taken TypeScript's place, if they focused on improving the tooling and ergonomics for Web developement instead of game development 15 years ago.
Shrug. I think this is a good illustration: it’s not the language that’s the issue, it’s the DOM. The DOM was and continues to be a terrible UI abstraction for applications.
What we really needed was Flex or XAML or Swing or even XUL, for that matter, to be built on a sandbox functional enough to make users happy but robust enough to run on the web. Instead each framework failed in turn to various platform dependency and/or security flaws until we ended up stuck with the DOM as our endgame.
Have is a nice language, but it doesn't live up to it's promises.
It's really cool that it can compile itself to a bunch of different languages, but the API isn't consistent enough for complex applications to work with all of its backends.
I played with Ceramic a bit and it was nice to have built-in imgui support out of the box.
Haxe is a fun language. It could have taken TypeScript's place, if they focused on improving the tooling and ergonomics for Web developement instead of game development 15 years ago.
> It could have taken TypeScript's place
It was heavily inspired by ActionScript 3 which was the basis for the EcmaScript 4 proposal abandoned around 2008 iirc.
We could have had something close to TS running natively in the browser 17 years ago.
Shrug. I think this is a good illustration: it’s not the language that’s the issue, it’s the DOM. The DOM was and continues to be a terrible UI abstraction for applications.
What we really needed was Flex or XAML or Swing or even XUL, for that matter, to be built on a sandbox functional enough to make users happy but robust enough to run on the web. Instead each framework failed in turn to various platform dependency and/or security flaws until we ended up stuck with the DOM as our endgame.
Ideas are worth communicating clearly. What does "DOM" mean here? You said XUL, but there was never XUL without the DOM.
> it’s not the language that’s the issue
And yet we're drowned in build tools, configs, and whatnot to use TS because JS is not sufficient to write sophisticated client-side apps.
Even if there was something like XAML you'd still need a typed language.
Have is a nice language, but it doesn't live up to it's promises.
It's really cool that it can compile itself to a bunch of different languages, but the API isn't consistent enough for complex applications to work with all of its backends.
That kind of makes sense for a lowest common denominator.
Then what is it good for? Just simple apps?