EraYaN

Well the user certainly doesn't know how to determine trust, otherwise scams and social engineering wouldn't work.

Honestly the sentiment on the streets was WAY different when you guys had Obama, like not even close. Sure some grumblings about your guys love for starting wars in the middle east. But it's not even close now. People really don't like the way the US is behaving right now. The complaining is way more out there, even influencing business decisions and political choices...

At least where I am (the Netherlands) there are plenty of mills still milling.

The actual product people understood it to be paramount to the success of the product and so I feel like from up high there was actual commitment.

Yes, your MDM lets you do almost everything you want to Windows. You can really tell that it is a commercial first offering, or at least used to be. And given that as a company you are also paying them I guess they don't care that much that there are fewer ads.

Some of them can have 1 rpi take down a full 100 node cluster, so sure sev:lo but the cyber insurance often want them fixed anyway. But it will probably take it happening before C-suite decides that 0 revenue is a problem.

And if you happen to be in some parts of Europe they will have a 6 pin connector that will send out data telegrams with all the stuff from the meter. DSMR is the standard that defines it for the Netherlands and port is called P1, seems to be (slowly) spreading. And you can also (wirelessly) pair a gas meter to the electricity meter to read that as well, and the new ones give you up to date data every second. Regulators CAN just make this happen clearly.

I mean being activist is sort of the whole point of the ACLU? And besides it's not like this would be the first time stuff like this happens. You don't have to imagine it, just learn history.

I mean at least the pipelines almost always seem to work...

The real disconnect is that the user doesn't really care all that much. It's mostly the designers who care. And Qt for example but also WPF let you style components almost to unrecognizable and unusable results. So if everyone will need to make do with 8GB for the foreseeable future, designers might just be told "No.", which admittedly will be a big shock to some of them. Or maybe someone finally figures out how to do HTML+CSS in a couple of megabytes.

Because the why can be completely unrelated to the code (odd business requirements etc). The code can be known to be non-optimal but it is still the correct way because the embedded system used in product XYZ has some dumb chip in it that needs it this weird way etc. Or the CEO loves this way of doing things and fires everyone who touches it. So many possibilities, most technical projects have a huge amount of politics and weird legacy behavior that someone depends on (including on internal stuff, private methods are not guaranteed to not be used by a client for example). And comments can guard against it, both for the dev and the reviewer. Hell we currently have clients depend on the exact internal layout of some PDF reports, and not even the rendered layout but that actual definitions.

There are GFIs that can deal with a welder, you will have to swap it at the panel.

No, they will point out that the way to make GCC better is not really in the code itself. It's in scientific paper writing and new approaches. Implementation is really not the most work.

The difference is visibility, with a van you can often see as close as 1,5 m in front of you due to the short hood. The problem is a lot of the newer trucks and SUVs are so tall that a full child (or 5) just disappear in front the car.

Essentially that someone needs to get involved that wants it/uses it and is also willing to pay for it.