Comment Random bright object in the sky? Probably ISS. (Score 3, Funny) 19
That's no moon. It's a space station.
That's no moon. It's a space station.
Yeah, as if we needed any more reason to consider this bloated "security" software to be malware. I really don't understand why anyone in their right minds would install it or allow it to be installed on their systems. Giving some third-party company complete control over what software can run on your machines basically screams "I don't understand anything about security" better any almost anything else you could possibly do as a system administrator, IMO, short of posting the shared-across-all-machines root password on USENET.
For most IT administrators, having complete control over what users can run is the idea. There's no need for your work PC to be able to run anything and everything - most work can be done using a limited set of applications. If your job involves doing nothing but paperwork and filing stuff all day, you generally only need access to an office package and a web browser for the online components. You don't need them running things like music players or chat apps beyond the company required one.
Having control is very different from allowing a third-party company to send down arbitrary definitions at any time that suddenly render arbitrary software nonfunctional. The whole concept of Crowdstrike can be summarized as "McAfee Antivirus on steroids". I mean, this sums it up.
Cppcheck apparently knows "hundreds of other rules covering a multitude of language aspects" so you don't "have to mentally apply against every single line of code you write."
Cppcheck doesn't flag anything in Waffle Iron's example.
It also doesn't find anything wrong with:
std::vector<int> vec = {1, 2, 3, 4, 5};
auto it = vec.begin();
vec.push_back(6);
std::cout << *it << std::endl;
Which is another common example of how you can write memory errors without using C++ pointers.
The 'explanation' is that the demo triggered all the devices within earshot because apparently a device designed to perform possibly-sensitive actions on your behalf was assigned a model line wide, public audio trigger in order to make it feel more 'natural' or something; rather than some prosaic but functional solution like a trigger button/capacitive touch point/whatever; and that the device just silently fails stupid, no even informative feedback, in the even of server unresponsiveness or network issues. Both of these seem...less than totally fine...for something explicitly marketed for public use in crowded environments on what we euphemistically refer to as 'edge' network connectivity.
This. The "someone says 'Hey Siri/Okay Google' on TV/radio/loudspeaker" problem is a well-known failure mode, and if they don't have reasonable mitigation in place by now, they don't know what they're doing, and their product shouldn't be taken seriously. Whether that mitigation is blocking it during meetings, doing handshaking to limit commands to the nearest device when multiple nearby devices detect the hot word at exactly the same time, making it recognize your voice and not other random people's voices, or any of dozens of other strategies for coping, having some mechanism in place to handle this should be considered a base requirement for any voice-based assistant.
In the sort of places where MISRA and similar coding guides apply, yes, never allocating memory is expected, because once dynamic allocation exists you can't guarantee that you won't die with an out-of-memory error and similarly can't guarantee any time bounds on how long an alloc and dealloc will take.
Sure, so C++ is safe as long as it's used in a way that makes it incredibly painful. Sounds good. Let's just require all C++ code everywhere to be written that way. Rust usage will skyrocket overnight.
Unintentionally
He unintentionally used Signal? How drunk was he?
It is hard to have fair democracy with winners take it all.
For a really rigorous definition of "fair", it's impossible to have fair democracy at all. Arrow's Theorem demonstrates this to a large degree, although many have argued that some of his fairness axioms are excessive. More recent research has concluded that fairness is the wrong standard, because there's no way for an electorate's "will" to really be fairly represented by any electoral system, not in all cases. Some systems can do better most of the time (and "winner take all" is particularly bad), but all systems fail in some cases.
What we need to aim for instead of fairness is "legitimacy", which is more about building broad acceptance of the system than about fixing the system itself, though it's easier to build acceptance for better-designed systems.
Having the country's top politicians continually claiming the system is unfair and rigged is, of course, the worst possible thing to do if you want to build support for the legitimacy of the system.
Precisely none of those books were ever banned.
I decided to check
According to the Book Censorship Database from the Every Library Institute, both "Of Mice and Men" and "Adventures of Huckleberry Finn" have been challenged, but only "Of Mice and Men" was removed, though "restricted" is more accurate. The Birdville Independent School District in Texas removed the book from general access, allowing access only to the AP English class, and the Indian River County Schools in Florida restricted it to high school students.
No Doctor Suess books were banned, although Suess Enterprises voluntarily ceased publication of six books.
It's perfectly reasonable a new OS version has higher system requirements. It's just in this case MS is pushing them to ensure manufacturers create PCs that can support certain security features. For example I understand TPM can help enforce boot security and disk encryption key storage. Good stuff to keep secure.
It is possible for Microsoft to do both, you know.
Then they just have to make sure the price difference is high enough to destroy any profit benefit from cutting corners on the hardware.
Yeah, as if we needed any more reason to consider this bloated "security" software to be malware. I really don't understand why anyone in their right minds would install it or allow it to be installed on their systems. Giving some third-party company complete control over what software can run on your machines basically screams "I don't understand anything about security" better any almost anything else you could possibly do as a system administrator, IMO, short of posting the shared-across-all-machines root password on USENET.
ve never seen a software distribution mechanism as careless and sloppy as NPM. Bazillions of dependencies and no signing of packages. [
... ]
Rust's cargo packaging system is almost exactly the same way. And the last time I looked, Go's packaging was very similar. And package signing won't help if the maintainer's key/cert has been exfiltrated and cracked.
This is what you get when you embrace DLL Hell -- the idea that you should pin your program to a single specific revision of a library, rather than, y'know, doing the engineering work to ensure that, as an app author, you're relying only on documented behavior; and, as a library author, to be responsible for creating backward compatibility for old apps linking to old entry points. Sticking to that principle lets you update shared system libraries with the latest enhancements and bug fixes, while remaining relatively sure none of the old clients will break.
"Sometimes you have to break backward compatibility." Agreed, but the interval between those breaks should be measured in years, not days.
Ish.
I would not trust C++ for safety-critical work as MISRA can only limit features, it can't add support for contracts.
There have been other dialects of C++ - Aspect-Oriented C++ and Feature-Oriented C++ being the two that I monitored closely. You can't really do either by using subsetting, regardless of mechanism.
IMHO, it might be easier to reverse the problem. Instead of having specific subsets for specific tasks, where you drill down to the subset you want, have specific subsets for specific mechanisms where you build up to the feature set you need.
Oh, absolutely. These days, I spend so much time checking the output from computers, it would normally have been quicker to do searches by hand. This is... not useful.
I can fully understand that.
fill a 100k job with an h1-b worker and only pay them 50k, it's still back to profit after 2 years
That one is actually illegal. The minimum on a H-1B salary is $60,000. But there is an additional requirement that the salary has to be at or higher than the prevailing wage for the job in question.
Government: So I see that your H-1B jobs are all for "Computer Programmer (I)" and your U.S. hires are all for "Software Engineer (III)" or "(IV)".
Company: Yes. We haven't had much luck in hiring level one programmers here in the U.S. We put the jobs out there, but nobody is applying.
Prevailing wage for the job doesn't mean what you think it does. A bunch of sleazy outsourcing firms made sure of that.
Remember to say hello to your bank teller.