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.
If gun owners are actively advertising to people they perceive to be likely mass shooters: Yes.
There's just so much here. They actively encouraged the practice, they made hundreds of millions of dollars on it, and the perverse incentive of a bidding war caused by all these scammers mean that despite knowing about the problem, Google had no desire to fix it.
> If gun owners are actively advertising to people they perceive to be likely mass shooters
That's an extraordinarily absurd setup legally. How do you perceive someone to be a likely mass shooter exactly? What the hell is likely? Perceive what? Your entire concept is legally broken top to bottom, it would never stand up to a challenge.
And how do you define that they're specifically advertising to that person?
So: first, you have to magically perceive that someone is "likely" to be a mass shooter. Then the company has to be caught having identified someone as a likely mass shooter. Then the company has to intentionally advertise to them. Then it has to be shown that they intentionally advertised to them. Beyond being a non-functioning legal premise, in the best case scenario you just narrowed the risk for the gun maker down to zero.
That is my point, that the parent of my comment was not making a really comparable example to the one I was giving of Google's actions and how Section 230 absolves them of responsibility they truly should share in.
Your analogy is not quite right. Google in this example isn't the gun manufacturer, they are simply the building owner that somebody else is selling guns out of.
The GP wants that building owner to be liable for the actions of the person that their tenant sells to.
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.
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).
> As far as I can tell, there isn't anything remotely illegal or unethical about this project
This applies to the other Vault 7 releases as well. It is very odd as there is no clear message or motive on their end, just dumping of info which could potentially cause harm (diplomatically, or to actual personnel in the two cases where they did not properly redact CIA employee names).
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.
>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.
None of the "unlimited" plans are actually unlimited. They just use soft caps where you're throttled to 2G speeds after you exceed your allotment, rather than charging you overages. Some carriers are starting to do this for all their plans, so "unlimited" is now just becoming a weird and misleading term for one particular data cap. At least on AT&T, the "unlimited" plan isn't even the one with the largest cap, so it's particularly bizarre.
No doubt Comcast's "unlimited" offering will be similar. You may not get charged overages, but good luck watching more than a few movies per month with it.
Be thankful you have that option. Comcast is the only real broadband provider in my area. My only option to avoid caps would be to switch to a Comcast Business account.
Just bought one of these for home last week $593CAD + sales tax (~ $457USD)
It is certainly good value, and a fraction of the price of the one I had for work a few years ago (different brand totally). It can feel a little flimsy/wobbly when raised, but certainly not dangerously so.
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.
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.