Now hopefully there will be another outbreak of common sense and they'll actually do some quality control instead, so we don't have a situation where indie games are selling better on a Nintendo console of all things than on PC because it's almost impossible to find good new games on Steam among the flood of terrible, low effort games slapped together with a few pre-made game assets.
Don't you think a bigger factor is that hardware performance improvements outgrew software requirement increases? At this point even a several year old mid-range phone feels fast enough running the latest software, while previously smartphone hardware genuinely struggled to keep up with later more featured/bloated (delete for preference) software.
Same thing happened in the PC space, remember when your PC felt slow, even obsolete every year trying to run the latest software? Now I can use a budget laptop from 2010 and run exactly the same software as a brand new high-end laptop without it even feeling slow.
I don't remember any campaigns against 16:10 monitors, I just remember them slowly disappearing because it was cheaper to use the same 16:9 panels on both TVs and monitors.
Oh look, it's that misquote again! What he actually said was:
"Part and parcel of programming in C/C++ is you’ve got to be prepared for these things, you’ve got to be vigilant, you’ve got to support the coders doing an incredibly hard job. We must never accept buffer overflows being successful, we must never accept that black hats can destroy our life or destroy the way we lead our lives."
Why the blue fuck would someone pay that much money to trade away their privacy
GPS stolen vehicle trackers are already a thing, the real question is why you'd put your vehicle tracker in such an obvious and easy to remove place...
Contrary to the claim of the article, there are some human females with tetrachromatic vision.
Indeed, although their 4th color receptor always lies somewhere between red and green, which gives better color differentiation but doesn't extend the range of visible colors like birds' UV tetrachromacy does.
Well that's a really stupid attitude isn't it? Purposefully create a UI that can take an entire system down without warning or logical reason by leaving a field blank just so you can sit there and smugly wait for someone to inevitably trigger the trap you laid for them?
If you worked for me the person being fired would be you, not the person who left the field blank.
Yeah, but then you don't follow the rules for how regexps work. You have introduced a custom exception, which is almost always a bad thing in programming. You introduce complexity, have to maintain the exceptions through library changes, refactoring and rewrites, regression test them whenever anything that's interfacing change specs, and also (remember to) bring them over to new code when you want to avoid surprises.
I think you might be overthinking this. This is purely a UI behavior issue, nothing to do with changing how the regex function behaves; If you have a mandatory regex field in a multi-field form, don't accept an empty value. If you have an optional regex field in a multi-field form, then leaving it blank should disable the regex call.
Yes you have to remember the UI conventions you use, but you also have to remember things like checking for required fields so it's no more work than you should already be doing.
Making an unintuitive and mistake-prone UI just because it mirrors how an underlying function behaves is asking for trouble, as in this example.
It is often useful to be able to enter regular expressions for filters. And an empty regexp without anchoring matches everything. That's a feature, not a bug. But it is only okay to design it that way if you can safely presume that anyone who will ever add a filter understands regular expressions, or will look it up before attempting to add a filter. Slightly safer (but only slightly) is to always add ^$ anchors, so empty fields only match empty entries.
Given how easy it is to write a non-empty regular expression that matches everything it would seem far more sensible to me to treat an empty regex field as "regex off / match nothing" rather than "match everything".
And what if the obstacle was a fallen tree, or a large animal, or anything else that could be fatal to the car's occupants? I guess they shouldn't be so entitled to expect a self-driving car not to kill them either right?
If that machine is incapable of detecting and avoiding unexpected obstacles and that unexpected obstacles is less squishy than a human it could easily be the occupant of said machine that dies...
Slashdot Mirror
With its giant plugs no AC adapter is too big to fit nicely in UK sockets...
Two 20 mile tunnels full of 100mph individual autonomous sleds is also easier said than done.
Or just add a little extra track at stations to the blue line to allow for express trains...
The Chicago system is expected to be able to handle nearly 2,000 passengers per direction per hour
Capacity's a bit low, isn't it? That's the equivalent of something like a conventional metro train running once every 30 mins...
>> You can buy games on Steam no matter what age you are as long as you set your age to over 18 when a store-page asks for you DoB
> So it pains me to say this, but until they fix this gigantic loophole, they are in the wrong here.
The problem is that's one of those easier said than done things. How do you create a fool-proof age verification system?
Now hopefully there will be another outbreak of common sense and they'll actually do some quality control instead, so we don't have a situation where indie games are selling better on a Nintendo console of all things than on PC because it's almost impossible to find good new games on Steam among the flood of terrible, low effort games slapped together with a few pre-made game assets.
> In Unix, tar does not allow leading "/" or "../" in paths. Is Zip not the same?
Don't forget that if tar only disallowed leading / and ../ then it would still be insecure, as you could do "newfolder/../../../../etc/" and so on.
Don't you think a bigger factor is that hardware performance improvements outgrew software requirement increases? At this point even a several year old mid-range phone feels fast enough running the latest software, while previously smartphone hardware genuinely struggled to keep up with later more featured/bloated (delete for preference) software.
Same thing happened in the PC space, remember when your PC felt slow, even obsolete every year trying to run the latest software? Now I can use a budget laptop from 2010 and run exactly the same software as a brand new high-end laptop without it even feeling slow.
I don't remember any campaigns against 16:10 monitors, I just remember them slowly disappearing because it was cheaper to use the same 16:9 panels on both TVs and monitors.
Pluto's atmosphere is big enough to support its own wikipedia page
Oh look, it's that misquote again! What he actually said was:
"Part and parcel of programming in C/C++ is you’ve got to be prepared for these things, you’ve got to be vigilant, you’ve got to support the coders doing an incredibly hard job. We must never accept buffer overflows being successful, we must never accept that black hats can destroy our life or destroy the way we lead our lives."
Why the blue fuck would someone pay that much money to trade away their privacy
GPS stolen vehicle trackers are already a thing, the real question is why you'd put your vehicle tracker in such an obvious and easy to remove place...
It's also the main system for typing, so much so that some are forgetting how to write the characters by hand.
> During the Cultural Revolution, the leftists wanted to switch to a Latin alphabet, but even Mao couldn't make that happen.
The Latin alphabet is the official way to write Chinese phonetically...
"Look out, they're coming right for us!"
To be fair having javascript be able to dump your kernel memory is a bit of a bummer even if you aren't running a cloud hosting service...
Contrary to the claim of the article, there are some human females with tetrachromatic vision.
Indeed, although their 4th color receptor always lies somewhere between red and green, which gives better color differentiation but doesn't extend the range of visible colors like birds' UV tetrachromacy does.
Well that's a really stupid attitude isn't it? Purposefully create a UI that can take an entire system down without warning or logical reason by leaving a field blank just so you can sit there and smugly wait for someone to inevitably trigger the trap you laid for them?
If you worked for me the person being fired would be you, not the person who left the field blank.
Yeah, but then you don't follow the rules for how regexps work. You have introduced a custom exception, which is almost always a bad thing in programming. You introduce complexity, have to maintain the exceptions through library changes, refactoring and rewrites, regression test them whenever anything that's interfacing change specs, and also (remember to) bring them over to new code when you want to avoid surprises.
I think you might be overthinking this. This is purely a UI behavior issue, nothing to do with changing how the regex function behaves; If you have a mandatory regex field in a multi-field form, don't accept an empty value. If you have an optional regex field in a multi-field form, then leaving it blank should disable the regex call.
Yes you have to remember the UI conventions you use, but you also have to remember things like checking for required fields so it's no more work than you should already be doing.
Making an unintuitive and mistake-prone UI just because it mirrors how an underlying function behaves is asking for trouble, as in this example.
It is often useful to be able to enter regular expressions for filters. And an empty regexp without anchoring matches everything. That's a feature, not a bug. But it is only okay to design it that way if you can safely presume that anyone who will ever add a filter understands regular expressions, or will look it up before attempting to add a filter. Slightly safer (but only slightly) is to always add ^$ anchors, so empty fields only match empty entries.
Given how easy it is to write a non-empty regular expression that matches everything it would seem far more sensible to me to treat an empty regex field as "regex off / match nothing" rather than "match everything".
"we should have more people from Norway." - Trump, Jan 2018
Except we're talking about legal H1B recipients, not illegal immigrants.
And what if the obstacle was a fallen tree, or a large animal, or anything else that could be fatal to the car's occupants? I guess they shouldn't be so entitled to expect a self-driving car not to kill them either right?
If that machine is incapable of detecting and avoiding unexpected obstacles and that unexpected obstacles is less squishy than a human it could easily be the occupant of said machine that dies...
One does not simply invent a space elevator!