rfcs VS BabylonJS

```

We started experimenting with this ling of thought almost 3 years ago:

- First take (ref sugar), Nov 2020: https://github.com/vuejs/rfcs/pull/228

- Take 2, Aug 2021: https://github.com/vuejs/rfcs/pull/368

- Take 3, Nov 2021: https://github.com/vuejs/rfcs/discussions/369

We provided it as an experimental feature and had a decent number of users trying it out in production. The feedback wasn't great and eventually decided to drop it. https://github.com/vuejs/rfcs/discussions/369#discussioncomm...

This is a personal preference, but I use ref almost all the time. Despite tediously writing the .value to access the ref’s value, the Vue team is aware of the problem, and the open RFC - Reactivity Transform, was aiming to solve this issue, however, seems like it was abandoned.

To stay updated, follow the RFC at https://github.com/vuejs/rfcs/discussions/503.

This was a good change. Evan has always been extremely good at putting his finger on the pulse of the frontend community. If there's a feature or paradigm that people love that would fit in Vue, Evan will incorporate it. Over the years, Vue has implemented (and sometimes later deprecated) dependency injection, JSX support, custom elements, Angular-style class components, Svelte-style ref sugar, and now Solid-inspired compiler optimizations. They even changed the order of a Vue file to match that of Svelte: first the script, then the template.

Now the $on has been removed, but the event subject is causing some confusion, see: https://github.com/vuejs/rfcs/discussions/397

The RFC has shown that this feature is very controversial, with lots of implications. Personally, I liked it at first, but now I'm against it.

Here is the Current language: https://github.com/vuejs/rfcs/blob/function-apis/active-rfcs/0000-function-api.md

Plus, even that there is a real possibility that the controversial Reactivity Transform RFC leads to a Vue 4 version, it is likely to bring just minor breaking changes from Vue 3.

It's been around for a while, and we've featured it in the April 2019 and March 2022 Release Radars. It's also been in GitHub Game Bytes and on our latest episode of The Download. Yes, I'm talking about Babylon, the powerful web rendering engine for all kinds of graphics. The newest update includes support for basic Global Illumination, a highly requested feature. Read more about other cool new additions including Gaussian Splatting, Ragdoll physics, Procedural Geometry and all the breaking changes in the Babylon release notes.

Wow that site is super cool! So I see most of the 3D stuff is using canvas, maybe three.js or babylon.js or possibly pixi.js.

Sure; I've used [Phaser](https://phaser.io/) before for a game jam like project and I've heard of [PixiJS](https://pixijs.com/) and [Babylon.js](https://www.babylonjs.com/) as options too. I can't really give a good recommendation either way; Phaser was fun to just write TypeScript and see my game, but it felt like a toy compared to Unreal. I'm sure you could really push it to its limits though. You mentioned you know about LibGDX; I don't have experience with it, but it does seem like a viable option.

I’ve only messed around with it a bit, but https://www.babylonjs.com seems impressive