While VS Code is a great IDE, a lot of this article is simply untrue. Node has had an interactive debugger (and corresponding API) for years.
Prior to --inspect, --debugger gave developers the abilities to step through code and to jump into a REPL to examine and manipulate the application state. Beyond this, there were tools like node inspector(https://github.com/node-inspector/node-inspector) which provided a chrome inspector-like tool.
On top of that, these tools adhere to the chrome debugger API (https://chromedevtools.github.io/devtools-protocol/) which provides the ability to dump comprehensive data like the memory graph for those wishing to make profiling tools.
Should gun manufacturers be liable for shootings? Car manufacturers for hit and runs? What about the USPS for when people ship drugs or other illegal contraband?
This seems like an awfully slippery slope where companies are are not only responsible for their own actions, but also for the actions of their customers as well.
Why do the euro models feature completely different (and arguably better) configurations?
I have one of these from a couple generations back and absolutely love it. My only regret is getting the high end model with the touch screen and high-res screen. I've heard 1080p has better battery life and I've spent more time I'm proud to admit dealing with the hell of configuring apps to not look like garbage on a high-res screen.
That might be a little extreme. Vault 7 demonstrated that the US government has been hoarding vulnerabilities to consumer electronics which allows spying without warrants and leaves the owners at risk.
I'm generally in support of WikiLeaks, but this is a really good example of why they often get such a bad rap. As far as I can tell, there isn't anything remotely illegal or unethical about this project (aside from war itself but that's an entirely different argument).
In this day and age its absolutely essential that we hold our governments accountable when they infringe on our liberties or engage in illegal activity. That said, I can't see any reason to leak sensitive documents regarding technical details of how missiles operate (even if the project was ultimately canned).
>To me, the fact that Node has to add a library with custom semantics just to allow a basic 'open' on a file handle is a huge warning flag to me
What do you mean? The fs module shipped with node is pretty much just a wrapper for libc. Hell, it even links to the open(2) manpage in the docs for usage information.
You can cut the irony with a knife. I left Comcast after they imposed data caps in my area which I struggled to stay under.
I have several roommates and we generally consume media via streaming services; primarily twitch and netflix. It seems to me that Comcast is using data caps as a 'streaming tax' for cord cutters.
Have you tried using an equivalent amount of water and/or fiber supplements as a control? It seems reasonable to conclude that eating additional food would cause you to feel satiated for longer.
I think the problem I (and most people) have with IoT is that the marketing is coming before the UX. Sure, you can spend 100 bucks on a lightbulb that can be controlled by your email, but will it really be usable? There is a lot of potential for zigbee/zwave/thread/BTLE/etc, but until there is an actual use case that will hold water it will only be over commercialized gadgets.
Prior to --inspect, --debugger gave developers the abilities to step through code and to jump into a REPL to examine and manipulate the application state. Beyond this, there were tools like node inspector(https://github.com/node-inspector/node-inspector) which provided a chrome inspector-like tool.
On top of that, these tools adhere to the chrome debugger API (https://chromedevtools.github.io/devtools-protocol/) which provides the ability to dump comprehensive data like the memory graph for those wishing to make profiling tools.