Having a plan to survive interruptions in logistical support is literally a matter of life and death -- not just for interplanetary settlers, but even for ones just crossing an ocean. Rushing things when the support services are not yet developed is not exactly a safe plan. Bold, certainly, but quite possibly bordering on suicidal.
Yes, NVMe provides some real, quite quantifiable benefits. Provided that everything in the path supports it, there is simply no disadvantage other than cost. But it's not a necessity for SSDs to finish eroding the hard drive market, ultrabooks are doing that just fine by themselves. There is no room for a 2.5" drive, only mSATA or M.2. Even if that M.2 slot is SATA III and not NVMe, it still necessitates an SSD rather than spinning rust. Desktop motherboards are also shipping with M.2 slots on them, and if you lack one, a PCIe x4 card can make up for it.
SATA III is definitely getting long in the tooth, though I expect it to be around for many years. Read speeds on SSDs have been constrained by SATA III for at least three years now, and write speeds are as well in many cases. Although I'm pleased enough with my hacked C720 Chromebook, it would have been nice if it had NVMe rather than SATA III for its M.2 slot. (Never mind that I don't think there are any NVMe drives in 2242 form yet -- there will be.)
The whole reason I originally switched to Pale Moon was for a 64-bit build when Firefox wasn't doing them. I really have no experience with 32-bit Pale Moon.
I wasn't trying to "sell" you. On the contrary, I was saying that while Pale Moon solves a certain set of problems, it creates a whole new set to deal with, primarily because it lacks sufficient market penetration for anyone to bother checking for it.
I use Pale Moon, but it has the serious problem that just about every website misidentifies it as a severely outdated version of Firefox and throws warnings all over. Twitter video doesn't work ("This browser does not support video playback"). For a while, 8chan was using code incompatible with Pale Moon and refused to change it because "the lead dev is a furfag." Every time I hit a broken site, I have to check it with something else because half the time, it's incompatibility with Pale Moon.
That said, it has some huge advantages, such as not mutating the user interface every other day, and not breaking plugin compatibility with updates.
You're right, I was thinking full image backups, such as you might use to get the system running again in a pinch. Those would just immediately collapse again.
What would that accomplish other than to make sure there are no players left in the market except for the really, really big ones? You know that if this topples Akamai, the attackers will take on another target and bring them down the same way, and so on, and so on...
Whoever buys them is taking in a white elephant. It will continue to bleed money, and won't be re-sellable for anywhere near what they pay for it. Changes to the service intending to make it less of a money pit could well drive away the few serious users it has.
This isn't like Microsoft acquiring Mojang, where they knew they would make money. They may still not get back what they paid, but at least the division is profitable, and they have done a good job of staying out of the way and letting it do its own thing (plus whatever spinoffs they request). With Twitter, the buyer most likely will lose money on both ends of the deal.
Yahoo is another white elephant. It probably won't be as loss-heavy, but it also offers less potential for turnaround.
Unfortunately, this has always been the case. The whole point of a DDoS is the ability of the attacker to multiply its efforts enormously. The only possible defense against any and all DDoS attacks would be to own more than half the bandwidth of the network, which hopefully nobody ever will -- or at least more than any adversary or group of adversaries can ever point your way. Since the attackers are not paying for the bandwidth, and Akamai is, the attackers win by economic siege.
Either Akamai can bow and take down Krebs, or they can let the whole ship go down in a symbolic gesture. Which one would you do, if you had a business to run?
Quantum teleportation is instantaneous, but first the entangled particles must achieve some distance between them, and this is subject to the usual speed-of-light constraints. In this case the photons achieved that separation over a length of fiber, rather than being sent through free space. Fiber is likely to scale considerably better than line-of-sight transmission.
Entanglement won't survive optical repeaters, so I'm not sure just how well this actually will scale in the real world. Still, 6.2km is a useful distance for some limited applications.
I'd most likely build my stack from the bottom up just as I do now, just without bezels. Foreground task, lower right. Supporting materials (usually a browser and a text editor), lower left. Skype and other messengers, upper right. Quick reference materials, upper left. I have already set up my workflow to spend as little time looking up as humanly possible, but having messengers available at a glance to see whether they're worth responding to -- without actually having to change the foreground task -- is much more valuable than having them in my line of sight. Besides, the most recent messages are always on the bottom.
The main advantage would be the ability to exceed 2048x1152 with a single task and not have bezels in the way. Despite this, I'd probably have it representing itself to user space as four 1080p monitors in an array.
Similarly, my board is specced even now to have a maximum capacity of 16GB (4x4), but in the list of supported memory configurations which still gets updated every few months (kudos to Asus for doing this for a 6 year old mobo), there are a fair number of 4x8 configurations shown. When I upgraded from 8 to 16, I did so by adding a single 8. This means at least one of the sticks will carry over when I eventually max it out at 32. (I see no need to replace a CPU-mobo combo that runs with the mid-tier Core i5 pack now,, five years and counting after purchase.)
I have tested 128GB SD cards in devices that officially support only 32 -- Chromebooks, an Aspire One from 2009, various Merom laptops from circa late 2007. I haven't had a single failure yet. They often come up well short of the rated speed of the SD media, but they still work. My general impression is that SDHC support implies SDXC support, even if it doesn't say so on the tin.
There are many apps where the bezels between monitors make it impractical to allocate more than 2048x1152 to them, but I really wish I could. Notation software with full orchestra scores really benefits, as does Cubase. Image processing also would benefit, though the bezels are a bit less of an issue there. The color calibration not even remotely matching except between the two identical monitors below is a bigger issue.
I might end up flanking a 4k with the two 2048x1152 panels turned to Portrait, though they suffer from poor range of viewing angle on their (normally) vertical axis and rotating them means my eyes are never on the same level with respect to them, leading to color-related fuckery. It would still be a much more versatile setup than what I have now, and software that makes apps think a large screen is actually an array of smaller ones (or vise versa) has been around for years.
The cup never contains anything but water. Sometimes cold, sometimes room temperature, often somewhere in between, but always just water. If I'm drinking coffee or soda, it goes in a normal ceramic mug that is easy to wash.
The junk, well, it's there because it's what I reach for the most. No sense in having it a mile away.
With better compression algorithms than H.264, why is it not possible to fit 4k content onto Blu-Ray discs? They'd need a new name to avoid confusion, but the same physical disc format (and drive) should work fine.
Slashdot Mirror
Let's say I get apache to work.
Nope, network applications are specifically Not Supported.
It's possible than an Indonesian meme has no spoon.
It's equally likely that their spoon is too big, and I am a banana.
Having a plan to survive interruptions in logistical support is literally a matter of life and death -- not just for interplanetary settlers, but even for ones just crossing an ocean. Rushing things when the support services are not yet developed is not exactly a safe plan. Bold, certainly, but quite possibly bordering on suicidal.
Yes, NVMe provides some real, quite quantifiable benefits. Provided that everything in the path supports it, there is simply no disadvantage other than cost. But it's not a necessity for SSDs to finish eroding the hard drive market, ultrabooks are doing that just fine by themselves. There is no room for a 2.5" drive, only mSATA or M.2. Even if that M.2 slot is SATA III and not NVMe, it still necessitates an SSD rather than spinning rust. Desktop motherboards are also shipping with M.2 slots on them, and if you lack one, a PCIe x4 card can make up for it.
SATA III is definitely getting long in the tooth, though I expect it to be around for many years. Read speeds on SSDs have been constrained by SATA III for at least three years now, and write speeds are as well in many cases. Although I'm pleased enough with my hacked C720 Chromebook, it would have been nice if it had NVMe rather than SATA III for its M.2 slot. (Never mind that I don't think there are any NVMe drives in 2242 form yet -- there will be.)
The primary security concern is the balcony not being big enough or strong enough to support Julian's ego.
They really have nothing to fear. After all, hot air is a lifting gas.
No, I can't. The add-on site itself is misidentifying Pale Moon as a really old Firefox.
> Not available for Firefox 24.9
The whole reason I originally switched to Pale Moon was for a 64-bit build when Firefox wasn't doing them. I really have no experience with 32-bit Pale Moon.
I do have Flash installed, but I also have Flashblock, so it must be checking for it, getting blocked, and then throwing the error.
I wasn't trying to "sell" you. On the contrary, I was saying that while Pale Moon solves a certain set of problems, it creates a whole new set to deal with, primarily because it lacks sufficient market penetration for anyone to bother checking for it.
I use Pale Moon, but it has the serious problem that just about every website misidentifies it as a severely outdated version of Firefox and throws warnings all over. Twitter video doesn't work ("This browser does not support video playback"). For a while, 8chan was using code incompatible with Pale Moon and refused to change it because "the lead dev is a furfag." Every time I hit a broken site, I have to check it with something else because half the time, it's incompatibility with Pale Moon.
That said, it has some huge advantages, such as not mutating the user interface every other day, and not breaking plugin compatibility with updates.
Are you saying Frankenferter is not a transexual?
He's from Transsexual, but actually just a sweet transvestite.
You're right, I was thinking full image backups, such as you might use to get the system running again in a pinch. Those would just immediately collapse again.
If X is less than the cost of a recall, we don't do one.
The virus is still there and will immediately re-activate on restoration because the current date is past its activation date.
What would that accomplish other than to make sure there are no players left in the market except for the really, really big ones? You know that if this topples Akamai, the attackers will take on another target and bring them down the same way, and so on, and so on...
Here's an archive.is link for those not wanting to deal with BI's paywall.
Whoever buys them is taking in a white elephant. It will continue to bleed money, and won't be re-sellable for anywhere near what they pay for it. Changes to the service intending to make it less of a money pit could well drive away the few serious users it has.
This isn't like Microsoft acquiring Mojang, where they knew they would make money. They may still not get back what they paid, but at least the division is profitable, and they have done a good job of staying out of the way and letting it do its own thing (plus whatever spinoffs they request). With Twitter, the buyer most likely will lose money on both ends of the deal.
Yahoo is another white elephant. It probably won't be as loss-heavy, but it also offers less potential for turnaround.
Unfortunately, this has always been the case. The whole point of a DDoS is the ability of the attacker to multiply its efforts enormously. The only possible defense against any and all DDoS attacks would be to own more than half the bandwidth of the network, which hopefully nobody ever will -- or at least more than any adversary or group of adversaries can ever point your way. Since the attackers are not paying for the bandwidth, and Akamai is, the attackers win by economic siege.
Either Akamai can bow and take down Krebs, or they can let the whole ship go down in a symbolic gesture. Which one would you do, if you had a business to run?
Quantum teleportation is instantaneous, but first the entangled particles must achieve some distance between them, and this is subject to the usual speed-of-light constraints. In this case the photons achieved that separation over a length of fiber, rather than being sent through free space. Fiber is likely to scale considerably better than line-of-sight transmission.
Entanglement won't survive optical repeaters, so I'm not sure just how well this actually will scale in the real world. Still, 6.2km is a useful distance for some limited applications.
I'd most likely build my stack from the bottom up just as I do now, just without bezels. Foreground task, lower right. Supporting materials (usually a browser and a text editor), lower left. Skype and other messengers, upper right. Quick reference materials, upper left. I have already set up my workflow to spend as little time looking up as humanly possible, but having messengers available at a glance to see whether they're worth responding to -- without actually having to change the foreground task -- is much more valuable than having them in my line of sight. Besides, the most recent messages are always on the bottom.
The main advantage would be the ability to exceed 2048x1152 with a single task and not have bezels in the way. Despite this, I'd probably have it representing itself to user space as four 1080p monitors in an array.
Does this mean I can have a 2 TB M.2 2242 SSD now? (Effectively one of these on each side of the board.)
Similarly, my board is specced even now to have a maximum capacity of 16GB (4x4), but in the list of supported memory configurations which still gets updated every few months (kudos to Asus for doing this for a 6 year old mobo), there are a fair number of 4x8 configurations shown. When I upgraded from 8 to 16, I did so by adding a single 8. This means at least one of the sticks will carry over when I eventually max it out at 32. (I see no need to replace a CPU-mobo combo that runs with the mid-tier Core i5 pack now,, five years and counting after purchase.)
I have tested 128GB SD cards in devices that officially support only 32 -- Chromebooks, an Aspire One from 2009, various Merom laptops from circa late 2007. I haven't had a single failure yet. They often come up well short of the rated speed of the SD media, but they still work. My general impression is that SDHC support implies SDXC support, even if it doesn't say so on the tin.
There are many apps where the bezels between monitors make it impractical to allocate more than 2048x1152 to them, but I really wish I could. Notation software with full orchestra scores really benefits, as does Cubase. Image processing also would benefit, though the bezels are a bit less of an issue there. The color calibration not even remotely matching except between the two identical monitors below is a bigger issue.
I might end up flanking a 4k with the two 2048x1152 panels turned to Portrait, though they suffer from poor range of viewing angle on their (normally) vertical axis and rotating them means my eyes are never on the same level with respect to them, leading to color-related fuckery. It would still be a much more versatile setup than what I have now, and software that makes apps think a large screen is actually an array of smaller ones (or vise versa) has been around for years.
The cup never contains anything but water. Sometimes cold, sometimes room temperature, often somewhere in between, but always just water. If I'm drinking coffee or soda, it goes in a normal ceramic mug that is easy to wash.
The junk, well, it's there because it's what I reach for the most. No sense in having it a mile away.
With better compression algorithms than H.264, why is it not possible to fit 4k content onto Blu-Ray discs? They'd need a new name to avoid confusion, but the same physical disc format (and drive) should work fine.