The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
It can be a good tool - especially if you are used to typed languages... But, at the end of the day it translated to JS and that what runs on the clients machine, so using TS does not relieve you from learning JS...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Indeed it doesn't (nor was I suggesting that it does). What you do get from this, is well written examples of the language when the code has been transpiled so it becomes easier for you to grok how certain things should be structured.
It is not that hard nor that bad. w3schools has some good information. I'd suggest doing a project and then just google how to do what it is you need to do. Learn by doing, that's what works best for me.
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
I would highly recommend these[^] videos by Douglas Crockford.
Once you get the hang of it you'll want to probably get going on one of the MV* frameworks. I have used Ember.js (3 years) before but currently I prefer CanJS[^] as I like the design and the fact that it is more library-focused and not so much a framework.
Do yourself a favour, and unless you're given no other choice - avoid NodeJS like the plague. Every other server side technology ranging from Python Applications written in WSGI, ASP.Net and JSP, through to FCGI written in C (no that last one isn't an exaggeration, the logic is easier to follow) are easier to work with and understand.
I want to simulate a virtual mouse ... It doesn't conflict with real mouse
Presumably you already verified that it cannot be run via the command line (no mouse.)
I would guess in general that is not possible. Certainly difficult.
From the debugging point of view you would still want to 'turn on' the real mouse so you could see where the pointer to the application is going. When not doing that then the mouse pointer for the application could not be visible as it would cause confusion.
I know there is automation software that uses the mouse. But it uses the real mouse. If you run it on a client machine you just sit back and watch until it is done.