I'm now after creating a multi-media framework more because I want something different from the existing tooling around. I don't have an intricate goal anymore, but it's certainly going more towards gamedev and editing/visualization software.

Compared to React.js, it's going to be almost the same function-wise, although it'll have some advantages (including the tooling and UI components), and some native platforms may be more efficient since they don't use a "web browser". (Remember GNOME applets? They also use JavaScript, so I guess we're fine.)

For most platforms, we'd use a runtime based on rusty V8 + Skia + other native stuff; for others that don't fit with V8, we'd use one based on WebView/the web with glues.

Basics:

• TypeScript is "EZMAScript" (same compiler; different name/extension (.tsx => .es))
• APIs are more E4X-like, including the DOM ones (UI components).
• <z:Style> tags (similiar to <fx:Style> tags in Adobe Flex, but represented as actual nodes due to the TypeScript JSX architecture, and using backticks instead of CDATA)
  • If you used Svelte, then it might remind you in case of stylesheet "arguments".
• Module specifiers are close to Java reverse-DNS names. Since ECMAScript modules need to be imported in fine-grained ways, there are trailing item-like module specifiers following the :: punctuator.

And like when you're working with Rust, the tooling looks pretty much like it (how dependencies get installed implicitly, and how the tooling does an implicit machinery around EZMAScript sources, and the analogy to Rust HIR might perhaps be the automatically generated .d.ts that are used like "C++20 module headers" (even though Rust HIR contains impl. code I guess)).

Roadmap of modules to do:

• Runtime
  • Rust base (some pretty generic stuff)
  • Native + Skia + V8 (Rust) (reuses Rust base) (for win-x64/amd64, Linux and OSX)
  • Web (reuses Rust base) (for web, Android, iOS and win-arm64/aarch64)
• Packaging process (e.g. MSI, EXE, DEB, AppImage, Snap, Flatpak, APK and so on)
• Build system/package manager (mostly done, but no registry/Git dep. installer yet)
  • Reuses the TypeScript compiler API
• Package registry
• Language server (EZMAScript and futurely CSS maybe)
• EZMAScript built-in APIs

1 post - 1 participant

Read full topic