Wait, who says node.js sucks? I mean, JavaScript has its warts... they've been a part of the language since its inception, and well documented, but node has been the direction the web has been going in for the last, oh, 4-5 years, for a variety of reasons, the biggest being that web apps can now be written with a single language code base, as the MEAN (MongoDB, Express.js, Angular, Node.js) stack, among others, demonstrates. Outside of enterprise-level concerns, like it being single-threaded, and it being JavaScript, which certain developers have an irrational hatred for, how does it suck?
Regarding innerText, assuming you're talking about this: https://developer.mozilla.org/en-US/docs.../innerText (which is a property, not a directive), then, yes, it's in node. Node is JavaScript.
Finally, with absolutely 0 malice intended, yeah, IE6 and IE9 are old. Tech moves fast, and is driven by the big world economies - US, China, certain EU countries (Germany), Japan, etc. A 6 year old mobile phone is ancient by today's standards. Ditto any PC with less than 4GB RAM. Now, obviously, you need to build your website(s) according to who your audience is, but if you're looking to grab any kind of international audience, you need to realize that most of them/us have been conditioned to a certain level of speed, functionality, and aesthetic quality. Test in Chrome. Test in Firefox. Test in Safari (if possible). Test in Edge (if possible). Anything else really isn't worth the time unless you know for a fact that your audience is using legacy tech.
Regarding innerText, assuming you're talking about this: https://developer.mozilla.org/en-US/docs.../innerText (which is a property, not a directive), then, yes, it's in node. Node is JavaScript.
Finally, with absolutely 0 malice intended, yeah, IE6 and IE9 are old. Tech moves fast, and is driven by the big world economies - US, China, certain EU countries (Germany), Japan, etc. A 6 year old mobile phone is ancient by today's standards. Ditto any PC with less than 4GB RAM. Now, obviously, you need to build your website(s) according to who your audience is, but if you're looking to grab any kind of international audience, you need to realize that most of them/us have been conditioned to a certain level of speed, functionality, and aesthetic quality. Test in Chrome. Test in Firefox. Test in Safari (if possible). Test in Edge (if possible). Anything else really isn't worth the time unless you know for a fact that your audience is using legacy tech.
"I was thirsty for everything, but blood wasn't my style" - Live, "Voodoo Lady"