naizarak

Nice marketing pitch. In reality it was probably parked at an empty crossroads 10 miles behind the frontline, taking potshots at "suspected" enemy positions.

Isn't that the point? What's the benefit of blacking-out a display instead of putting it in no-signal standby?

For anybody interested in the use-case underlying this article, mainly disabling peripheral displays in a multi-monitor setup, this is already built into Windows via the Win+P hotkey. It's also possible to turn off all displays by reassigning the functions of the computer's physical power/sleep buttons in Control Panel -> Power Options.

The reasons are obvious but acknowledging them is taboo. It's much easier and politically convenient to blame everything on funding, despite the fact that some school districts have the budget of a small country.

I'm using an old version of Postman with their servers blocked through the system hosts file. I keep meaning to migrate to whatever the next best thing is but this setup just works for me.

NTA is an absolute legend

this is really microsoft's fault for handing out kernel access to random 3rd parties, none of which are doing anything special that microsoft couldn't implement themselves (AV, anti-cheat, security)

Use LTSC, it's marketed for "enterprise" but it's functionally identical to the regular versions with the bonus of advanced configuration that lets you disable AV, forced updates, telemetry, ads, etc.

I just block Postman servers in my hosts file and run an old version that still allows offline/anonymous mode. Works perfectly for my needs.

That's just a decorative shell. You really think they drilled into their pressure hull?

SEO spam is gonna be nothing compared to the AI-generated web. And it's going to be the perfect excuse to finally mandate internet-ID.

DI isn't what you think it is. What you're describing is the old imperative vs OOP debate.

Not sure why the author decides to single out DI frameworks as a problem. In most cases DI is just an implementation detail for how the framework serves up its abstraction layer over the underlying mechanisms. For example, Spring is built around injecting beans so it can wrap them in proxies which provide transaction managements, security, etc. Sounds like he's really just criticizing frameworks in general.

On the topic of DI, it's such a simple and common-sense design "pattern" that it shouldn't even have a buzzword label. All it means is that, given service A which uses service B, it's not service A's job to instantiate B and provide B with its required sub-dependencies (DataSource, config params, etc). A should only consume B without concerning itself as to how B was created in the first place. This is usually handled by some "container" service whose job is to build-up every other service and make them accessible to one another so they may be strict consumers without transitive dependencies.

There's a hundred ways to mask your selling identity, this law won't change anything except, as usual, placing more bureaucratic baggage on honest sellers.

JPMS allows for exactly this, but that entire project was so poorly implemented that no one uses it.

It really is stupefying how Amazon has turned into a dumping ground for cheap chinese junk. Surely they realize the long term damage they're causing to their own brand?

At the same time, they're constantly tightening KYC and other regulations which only hurts honest small-time merchants.