I do have a couple of places that I shop at that are insanely fast on credit. Although the new terminals that read the chip have really slowed things down, it seems like the card has to stay in the slot for a decade before the transaction can complete.
Articles like the Herald's are just the first step towards multi-billion dollar public works projects. Politicians and their mega-contractor cronies love these. I predict a lot of high-dollar dirt shuffling in Florida's future.
It doesn't look that great on AV-Test. I just checked and it's 3rd from the bottom on protection, if I'm reading it right. (Note - I use MSE/Defender and am not inherently a basher).
The spec is short-sighted and should've been designed to allow multiple origins. The spec puts the onus of implementing support for multiple origins back on the server-side developer, when it would've been better implemented in the browser.
You buy a new enclosure _if_ one is still available. It's not like you can just slap the drives into any chassis, even inside the same brand. It's definitely an issue worth mentioning, especially considering the OP's zeal, since it's easy to mistakenly overestimate the reliability of data on a NAS.
Migrating away from Oracle is a horrific, expensive task. And, because they'll want the same level of support that they had under Oracle, they'll hand all of the software licensing savings over to a third party vendor to support a free software solution.
It actually does a really great job at gathering data from backend stores and presenting it via web services or vice versa. Once you quit using it for HTML generation it works pretty well.
"Loose" equality has been around since dbase in the 80s and probably prior. Just because you're not familiar with it and it causes problems for you doesn't mean it's bad.
Maybe it's just you, though, because there's no shortage of perfectly functional sites out there that use PHP. Personally, I'd much rather look at PHP code, with explicit subroutine arguments, than Perl with the @_ BS . .
The Kaspersky source code (completely ignoring the presence of any exploitable bugs) wouldn't be much value to anyone other than Kaspersky. The mechanism behind virus scanners is pretty well known.
Slashdot Mirror
I do have a couple of places that I shop at that are insanely fast on credit. Although the new terminals that read the chip have really slowed things down, it seems like the card has to stay in the slot for a decade before the transaction can complete.
That isn't how a US card transaction goes AT ALL...
Card:
"That'll be 27.73"
*get wallet, swipe card*
Enter zipcode
Affirm final amount
Sign
Wait for register to process transaction.
Credit is quicker than cash on maybe 2 in 10 transactions.
I really doubt you can, at least not with networking support.
Articles like the Herald's are just the first step towards multi-billion dollar public works projects. Politicians and their mega-contractor cronies love these. I predict a lot of high-dollar dirt shuffling in Florida's future.
It had a grate originally but there were problems with it getting clogged by jellyfish.
-E
The reconsignment process would potentially draw attention to what was happening, as it's a fairly high-profile thing to do to a shipment.
It doesn't look that great on AV-Test. I just checked and it's 3rd from the bottom on protection, if I'm reading it right. (Note - I use MSE/Defender and am not inherently a basher).
The spec is short-sighted and should've been designed to allow multiple origins. The spec puts the onus of implementing support for multiple origins back on the server-side developer, when it would've been better implemented in the browser.
Makes sense, thanks.
So, after failing ten times, you restore back to the phone from an earlier image?
This, like most rap beefs, is just media whoring.
You buy a new enclosure _if_ one is still available. It's not like you can just slap the drives into any chassis, even inside the same brand. It's definitely an issue worth mentioning, especially considering the OP's zeal, since it's easy to mistakenly overestimate the reliability of data on a NAS.
And what do you do when the NAS fails? A single NAS represents a single point of failure, unless you bought a spare enclosure.
That's part of the experience when you select the lowest cost provider.
The physical store advantage goes to Dollar General. Amazon is decimating Walmart on one demographic and Dollar General is killing them on the rest.
Good point, you're right and I've experienced this firsthand with Oracle.
EnterpriseDB nearly costs as much per server as Oracle does.
Migrating away from Oracle is a horrific, expensive task. And, because they'll want the same level of support that they had under Oracle, they'll hand all of the software licensing savings over to a third party vendor to support a free software solution.
It actually does a really great job at gathering data from backend stores and presenting it via web services or vice versa. Once you quit using it for HTML generation it works pretty well.
"Loose" equality has been around since dbase in the 80s and probably prior. Just because you're not familiar with it and it causes problems for you doesn't mean it's bad.
You consider string escaping, in any form, to be a good mechanism for interacting safely with the database?
In short, you have no idea what you are doing and you're blaming that on the language.
Maybe it's just you, though, because there's no shortage of perfectly functional sites out there that use PHP. Personally, I'd much rather look at PHP code, with explicit subroutine arguments, than Perl with the @_ BS .
.
The Kaspersky source code (completely ignoring the presence of any exploitable bugs) wouldn't be much value to anyone other than Kaspersky. The mechanism behind virus scanners is pretty well known.
One could wonder... if they burned three zero days for essentially nothing... how many zero days do they have?