Comment

Comment by BeardScript

Hello there! Thanks for stopping by.

There's various reasons for that. First and foremost, the Unity export for the web is quite bloated and very limited. You would use this for the same reasons you'd choose three.js or Babylon.js which are meant for the web.

This is basically an editor for three.js. It provides a framework which simplifies most of the boilerplate and turns three.js into a Unity-like experience with components, prefabs, marketplace, etc.

If you are a web developer, you'd prefer something like this where you can use NPM, Typescript/Javascript and VSCode. If you're a Unity developer wishing to do some WebGL in a web environment most of your skills are easily transferable.

If you're a company building 3D apps/games for the web, it's a lot easier to find and train Javascript/Typescript developers than C# Unity3D developers.

So basically: Multiplatform, meant for the web, familiar environment for web and unty devs, cost efficient and a decade worth of three.js resources along with a big a vibrant dev community.

As a bonus, this is in early development, you can hop on Discord and be a part of the process. I'm always there to assist everyone to the best of my ability.

All the best, and I hope to see you around.

parent BeardScript 5 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton