But that's not my problem anyway. You can't clone the card, so I would know it's gone. And I'm not going to be responsible for purchases made on the card anyway.
It's true that signatures offer no great security - but a lot of card numbers are stolen by skimming the mag stripe during a live in-person transaction.
Banks and even stores are dragging their feet enough on chip and signature that the whole argument is moot anyway. I only got chip cards for my primary debit and credit cards in the last month and only 2 stores that I visit regularly even have their chip slot enabled. The rest have upgraded their hardware but the chip slot is disabled.
As another web developer, I wish they would stop trying too. HTML/JS is just not for this. I foresee some kind of convergence between the likes of QT and HTML in the future, but with something a lot better than JS as glue (though it's amazing what current JS engines can do).
What I mean is VGA surviving into the era of large digital screens, despite being an analog signal and having poor contrast, poor black level and some noise. It's all visible at that size and picture quality and not necessary. SVGA is only different on the software side - the connector and everything else is the same.
DVI is the one with so many variations. It can carry either analog or HDMI-compatible video and there is also a dual-link variation for higher resolutions.
Literally just connect a patch cable between them. If they are gig ethernet they will auto-negotiate as crossover. You don't even need to involve the WLAN/LAN.
The backend patch panel / switches do not need smaller connectors. For wall jacks, you have plenty of rear space for putting wires in. So you just need premade patch connectors with the new ports. For that matter, the wall-end could still be RJ-45.
You're out of luck for Windows 7 if you're not halfway expert. You have to convert a standard Windows 7 ISO to Universal or acquire a premade one and use the OEM key from the sticker.
[...]and can choose to not install the Windows 10 upgrade or remove the upgrade from Windows Update (WU) by changing the WU settings."
And then do the same every single time Windows finds new updates. You can't hide it once forever. And if you miss the next update cycle because you were in bed sleeping, too bad.
And yes, that would mean Dropbox would probably have to write their own implementation of ZIP. Or at least re-arrange an existing library so that its output is not a single, monolithic file.
If Dropbox attempts to build the entire.zip in memory before sending it over the wire, you could be hitting RAM limitations on the server. If Dropbox builds the.zip on disk before sending it, you might be running into a connection timeout.
You don't have to hold it all in-memory. You can not enable HTTP byte-range requests and generate it on-the-fly - flushing it out of memory as it goes out the wire. Zip and tar are both the same in that you have to read in a whole file to calculate the checksum for each file's header before sending the file. This isn't as resource-friendly as a running checksum that can be computed and stuck in a head at the end of a file's data since you'd have to read every file twice if you don't want higher memory requirements. I don't think ZIP64 changes this.
The one downside of sending on-the-fly is that the download will not have a progress bar, because you can't send a Content-Length HTTP header.
I don't see how TAR doesn't have the same limitations. Both have a per-file checksum header at the beginning. Unless you just mean 32-bit zip files, but 64-bit zip has wide enough support..
You caught me on semantics. I wasn't using the phrase "direct correlation" mathematically. I meant that there are other factors and that you can't infer the rolling resistance from the weight of the vehicle alone, making that exact measurement relatively meaningless.
OK. Direct correlation is the wrong phrase. To be extremely specific, I meant that you can't infer the number of newtons of force from the vehicle weight alone. All other things being equal, the weight has a direct correlation on rolling resistance but all sorts of other factors would be involved such as the type and tread and age of tire, number of wheels, distribution of weight and all that. The weight alone is relatively meaningless.
Slashdot Mirror
But that's not my problem anyway. You can't clone the card, so I would know it's gone. And I'm not going to be responsible for purchases made on the card anyway.
It's true that signatures offer no great security - but a lot of card numbers are stolen by skimming the mag stripe during a live in-person transaction.
Banks and even stores are dragging their feet enough on chip and signature that the whole argument is moot anyway. I only got chip cards for my primary debit and credit cards in the last month and only 2 stores that I visit regularly even have their chip slot enabled. The rest have upgraded their hardware but the chip slot is disabled.
2. If Trader Joe gets hacked, the credit card number behind your NFC card is in their database and gets sold en masse to carders.
That doesn't happen with NFC
Apple Pay is an NFC implementation of EMV (i.e. Chip and PIN or Chip and Signature). Just like a card with a built in NFC chip.
And Jurassic Park also showed fsn as a file system viewer on IRIX. Not exactly the best example to support using a mainstream OS.
Oh, sorry. I'm sure Node.js and MongoDB are much better performing.
As another web developer, I wish they would stop trying too. HTML/JS is just not for this. I foresee some kind of convergence between the likes of QT and HTML in the future, but with something a lot better than JS as glue (though it's amazing what current JS engines can do).
But why not go for the recursive bacronym and call it ZFS File System? So that you're using the correct name in the process, too?
What I mean is VGA surviving into the era of large digital screens, despite being an analog signal and having poor contrast, poor black level and some noise. It's all visible at that size and picture quality and not necessary. SVGA is only different on the software side - the connector and everything else is the same.
DVI is the one with so many variations. It can carry either analog or HDMI-compatible video and there is also a dual-link variation for higher resolutions.
And the attenuation of 5GHz actually helps rather than hurts in a large installation. Because there is less interference from neighboring APs.
The only shortcoming it has is the fragility of the catch mechanism when pulling cables through walls
You're supposed to be pulling unterminated cable through the walls.
And across the US, too. I think they're mistaking congestion problems for infrastructure problems.
Literally just connect a patch cable between them. If they are gig ethernet they will auto-negotiate as crossover. You don't even need to involve the WLAN/LAN.
They're saying if the small connector is small enough to fit inside an RJ-45 adapter, it would still fit inside the existing RJ-45 wall jack.
They missed the much easier option of just having RJ-45 on one end of the patch cable and the new standard on the other end.
The infrastructure cabling wouldn't change. Just a new patch cable from the wall with RJ-45 on one end and the new connector on the other end.
Don't worry, corporations don't change standards for the fun of it, they do so because they need to.
Except Sony.
Or,
tl;dr I'm glad to be done with VGA signals. Don't know what parent poster had against HDMI (variations requiring adapters aside)
The backend patch panel / switches do not need smaller connectors. For wall jacks, you have plenty of rear space for putting wires in. So you just need premade patch connectors with the new ports. For that matter, the wall-end could still be RJ-45.
Windows Media Creation Tool
And for Windows 8.1 too
You're out of luck for Windows 7 if you're not halfway expert. You have to convert a standard Windows 7 ISO to Universal or acquire a premade one and use the OEM key from the sticker.
With just that screenshot to go on, my first guess is a GUI-based driver installer, not a full blown distribution.
Actually, read the summary again... carefully.
[...]and can choose to not install the Windows 10 upgrade or remove the upgrade from Windows Update (WU) by changing the WU settings."
And then do the same every single time Windows finds new updates. You can't hide it once forever. And if you miss the next update cycle because you were in bed sleeping, too bad.
And yes, that would mean Dropbox would probably have to write their own implementation of ZIP. Or at least re-arrange an existing library so that its output is not a single, monolithic file.
If Dropbox attempts to build the entire .zip in memory before sending it over the wire, you could be hitting RAM limitations on the server. If Dropbox builds the .zip on disk before sending it, you might be running into a connection timeout.
You don't have to hold it all in-memory. You can not enable HTTP byte-range requests and generate it on-the-fly - flushing it out of memory as it goes out the wire. Zip and tar are both the same in that you have to read in a whole file to calculate the checksum for each file's header before sending the file. This isn't as resource-friendly as a running checksum that can be computed and stuck in a head at the end of a file's data since you'd have to read every file twice if you don't want higher memory requirements. I don't think ZIP64 changes this.
The one downside of sending on-the-fly is that the download will not have a progress bar, because you can't send a Content-Length HTTP header.
I don't see how TAR doesn't have the same limitations. Both have a per-file checksum header at the beginning. Unless you just mean 32-bit zip files, but 64-bit zip has wide enough support..
What AC said.
You caught me on semantics. I wasn't using the phrase "direct correlation" mathematically. I meant that there are other factors and that you can't infer the rolling resistance from the weight of the vehicle alone, making that exact measurement relatively meaningless.
OK. Direct correlation is the wrong phrase. To be extremely specific, I meant that you can't infer the number of newtons of force from the vehicle weight alone. All other things being equal, the weight has a direct correlation on rolling resistance but all sorts of other factors would be involved such as the type and tread and age of tire, number of wheels, distribution of weight and all that. The weight alone is relatively meaningless.