I think you're confusing js with node. node typically doesn't run on the frontend, but can be used when developing the front but it won't be running on the users browser.
No confusion here. Node.js is an entire ecosystem, and npm is a child of that mess. It is absolutely famous for the massive gobs of absolutely junk it pulls in to satisfy dependencies a frontend dev could manage with 4 lines of native js.
You may rail on about how npm != node, but everyone considers npm to be 'node package manager', no matter what the initialism actually stands for.
Node.js is a server runtime, it does not run clientside at all. NPM can be used to download server OR client JS packages. A frontend bundler tool (e.g. webpack) can analyze a dependency graph of your client-side entrypoint and bundle all the NPM deps used, which will then be sent and executed on the client. No Node.js components or code are run client-side at any point (caveat - some packages can work server- and client-side).
that's the easier part of eye tracking. eye tracker sensors work by working out where your eyes are and determine where you're looking by calculating the angle of your pupils and approximating the direction.
I was so impressed by Bitwig since the beta. Just couldn't find anything major enough to make the switch from Live. Also, M4L is such an amazing ecosystem, I would miss it.
Any features in more recent Bitwig versions that stand out?
I’m not sure how recently they were added, but the Grid (modular environment) and the modulation sources are really powerful, particularly for adding organic/generative elements to a production. I’ve heard that Bitwig routing is another workflow enhancement, but haven’t used it too extensively.
It would be cool if Bitwig would introduce a scripting environment similar to Max for Live.
If Bitwig would add user-modules to the Grid, along with a scripting language, it would be perfect.
Where they both fall down is in less capability for the piano roll and midi for more complex compositions and styles (orchestration) and although Live has made some moves towards improving that recently, they're both still way behind in that area.
Totally agree regarding the piano roll. Same with the sample editor.
Saying that, DAWs just have different specialization. E.g. for a long time midi support in ProTools was extremely limited. Cakewalk already had an excellent piano roll in the late 90s.
Vivaldi at least is closed source and I had a hard time understanding their revenue model so it's hard to gauge how privacy respecting they actually are.
I prefer my OS in dark but every website in light, it's always a hassle when a website decides for me based on my OS setting which I wouldn't want to extend beyond the OS chrome.
reply