Context2d is platform sependent, but from what I heard some modern brossers have gpu accelerated canvas, but it will never be anywhere close to actual webgl
You cak use webgl without glsl if you ise a library, but usually you need to write custom shaders if you want more unusual effects. I think there was also a package in the thi.ng/umbrella repo which compiled a subset of typescript to webgl or something, but don't quote me on thst one
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
Interesting, I had thought about a DSL in ts, this might solve one problem at least. The main problem with glsl is absolutely 0 debugging for V.ES 3.0. there are some tools that I could attempt to port but that's a really big ask for one person. I also have enough projects on the go already. I should really get on with Jess Lang.
Yep, better debugging would be super nice to have, maybe just a sandbox which allows you to see all the variables at any step, or allowing printing to the console, but I'm guessing this would only be possible by compiling glsl itself to a spower js version
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Context2d is platform sependent, but from what I heard some modern brossers have gpu accelerated canvas, but it will never be anywhere close to actual webgl
You cak use webgl without glsl if you ise a library, but usually you need to write custom shaders if you want more unusual effects. I think there was also a package in the
thi.ng/umbrellarepo which compiled a subset of typescript to webgl or something, but don't quote me on thst oneInteresting, I had thought about a DSL in ts, this might solve one problem at least. The main problem with glsl is absolutely 0 debugging for V.ES 3.0. there are some tools that I could attempt to port but that's a really big ask for one person. I also have enough projects on the go already. I should really get on with Jess Lang.
Yep, better debugging would be super nice to have, maybe just a sandbox which allows you to see all the variables at any step, or allowing printing to the console, but I'm guessing this would only be possible by compiling glsl itself to a spower js version