Even if cellphone radiation increased risk of head and chest cancers (and there is no evidence to demonstrate that, despite questionable and biased documentaries on the subject), such increased risk would have nothing to do with the lady's claimed symptoms, which include real-time maladies like headaches, nausea, fatigue, etc.
Yeah, and Sculley hasn't been CEO of Apple for more than two decades.
Anyhow, non-competes here in Quebec are only valid here if they are pretty carefully worded (they're legal, but courts have voided non-compete clauses that were considered unreasonably broad). Even if somebody working for Apple in Quebec had a non-compete clause, and went to work for a smartphone company in Quebec making low-end phones, the employee could probably argue successfully that the new smartphone company did not operate in the same market segment as Apple, and as such did not compete.
Pretty much that. Ours were RAID arrays on Linux, and we induced it without being quite as close as he was, but pretty much the same deal. This was more than ten years ago, so maybe modern disks would handle it better, but it looks like a few years later that guy in your video was still seeing the same behaviour.
Then the MIT paper ignores reality, and is therefore useless.
You can prove your system is technically correct all you want, but if it doesn't work in the real world (where most hardware lies about write commits), then it's going to work in theory and fail in practice.
You joke, but I've seen IOPS drop in a RAID array because somebody was talking loudly next to the server. It was kind of fun to shout at the server and watch the disk activity drop. For testing purposes, of course.
How do you know the write was complete? Most storage hardware lies about completing the write. The ZFS folks found this out the hard way: their filesystem was supposed to survive arbitrary power failures, and on a limited set of hardware that was true. In reality, most drives/controllers say they've committed the write to disk when it's still in their cache.
Any filesystem that claims to survive crashes needs to take into account that any write confirmation could be a lie, and that any data it has written in the past may still be in a volatile cache.
Which is a fair criticism, but ZFS was designed for use in modern desktop and server computers, not embedded devices with tiny amounts of RAM. This was no secret, when they designed ZFS they clearly stated that they wanted to take advantage of the resources available in modern computers, whereas most existing file systems had been designed when computers had far more limited resources.
Is there still? In the early days of Chrome, there was no way to stop content from loading, so AdBlock only removed ads after they were displayed (they'd flash briefly on-screen). So back then, it wasn't very good. At some point (years ago) they added APIs to filter content before it loads, which basically solved that problem (although there was a transition period where AdBlock was a bit buggy as they worked the kinks out). Nowadays, it's been quite some time since I've used FireFox, but AdBlock seems to work as well as I remember AdBlock working when I used FireFox.
But in terms of my previous reply, I specifically was referring to there being methods to do stuff in the DOM while it's still loading, which contradicts the claim that you can't do anything until after it loads. I don't know if you can do anything before it loads at all, but you can definitely do stuff before it finishes.
Boeing is still making new 747s, still actively delivering them. They still have orders for future planes. Korean Air just last month announced they had placed an order for ten more of them. How the heck does that equate to "heading for retirement"?
The chiclet keyboards of today have little in common with the chiclet keyboards that caused inssues in the 80s. The complaint back then had more to do with the physical mechanism (often a single rubber membrane for the whole keyboard and very poor quality/design) rather than the fact that the keytops were flat with a little space between the keys.
Sorry, yes, I meant even if it was identical to RAM.
Memory management would be tougher because now you're using the same device for both long-term storage (which still requires file systems and all the usual stuff) and working RAM (which needs to be directly accessible by the CPU without any sort of thing like a filesystem). Dynamically sharing the two doesn't sound simple to me. Certainly no simpler than managing what pages get swapped in or out.
If you put a bunch of constraints on the setup, like always using the same pre-determined areas as RAM and storage, then it'd be simpler... but what would have been the point of merging the two in the first place?
With this particular technology, never... but even if it performed identically to flash, you would need a radical shift in computer architecture (both software and hardware) to support such a thing, and it would actually substantially increase complexity rather than decrease it. Memory management would become far more complex, I don't know why you think it wouldn't be needed at all.
1000x the endurance, but since it's also 1000x faster, you can wear it out just as fast assuming you're maxing out the IO long enough, and assuming that they use similar wear leveling.
I get that technically-oriented people like those on Slashdot are opposed to automatic updates, but this product isn't targeting you. Most people are going to get their wifi router either from their ISP (where the ISP will manage updates) or something they bought at BestBuy and never touched again after they got it working. Most people will never go out of their way to update anything unless it's either done for them automatically or they're prompted to do so.
Wifi routers are absolutely a place where, for most people, security updates should happen automatically, because for most people, the alternative is for wifi routers to spend their entire lifetime running the same version they shipped with, whatever security updates that may entail.
Because nobody who has a quad-core processor in their notebook would ever want to watch a movie anywhere they might not have power... Obviously anybody who wants to do more than one thing with their notebook should carry around multiple notebooks so that they can have a dedicated one for each task.
DC has lower loss for transmission lines, but nearly all power plants produce AC, so you're going to suffer additional losses converting the AC from your turbines to DC for transmission, and then back to AC for local distribution (to avoid the massive losses of low voltage DC), and then back to DC for the actual appliances.
HVDC has its place, but it would be very inefficient to switch from HVAC to HVDC everywhere...
You can buy a laser printer for under $40, or a color laser for $100. Ink jet printers have their place, but for most people, a cheap laser is a far better (and cheaper) option.
Slashdot Mirror
So install Ubuntu Minimal, which can get down as low as a 5MB install image.
Even if cellphone radiation increased risk of head and chest cancers (and there is no evidence to demonstrate that, despite questionable and biased documentaries on the subject), such increased risk would have nothing to do with the lady's claimed symptoms, which include real-time maladies like headaches, nausea, fatigue, etc.
Yeah, and Sculley hasn't been CEO of Apple for more than two decades.
Anyhow, non-competes here in Quebec are only valid here if they are pretty carefully worded (they're legal, but courts have voided non-compete clauses that were considered unreasonably broad). Even if somebody working for Apple in Quebec had a non-compete clause, and went to work for a smartphone company in Quebec making low-end phones, the employee could probably argue successfully that the new smartphone company did not operate in the same market segment as Apple, and as such did not compete.
If my employers wanted to pay me 25 years of salary for a non-compete clause... I'd be happy to oblige.
Both my Canon S95 camera and my Apple iPhone 6 use Sony camera sensors, so... they do, pretty much.
Pretty much that. Ours were RAID arrays on Linux, and we induced it without being quite as close as he was, but pretty much the same deal. This was more than ten years ago, so maybe modern disks would handle it better, but it looks like a few years later that guy in your video was still seeing the same behaviour.
Then the MIT paper ignores reality, and is therefore useless.
You can prove your system is technically correct all you want, but if it doesn't work in the real world (where most hardware lies about write commits), then it's going to work in theory and fail in practice.
You can never be sure that a write is committed to disk, because most hardware lies about that.
You joke, but I've seen IOPS drop in a RAID array because somebody was talking loudly next to the server. It was kind of fun to shout at the server and watch the disk activity drop. For testing purposes, of course.
> When write is complete, signal application.
How do you know the write was complete? Most storage hardware lies about completing the write. The ZFS folks found this out the hard way: their filesystem was supposed to survive arbitrary power failures, and on a limited set of hardware that was true. In reality, most drives/controllers say they've committed the write to disk when it's still in their cache.
Any filesystem that claims to survive crashes needs to take into account that any write confirmation could be a lie, and that any data it has written in the past may still be in a volatile cache.
Except Mozilla already explicitly stated they were adding an API call specifically so that NoScript would be possible.
Which is a fair criticism, but ZFS was designed for use in modern desktop and server computers, not embedded devices with tiny amounts of RAM. This was no secret, when they designed ZFS they clearly stated that they wanted to take advantage of the resources available in modern computers, whereas most existing file systems had been designed when computers had far more limited resources.
Is there still? In the early days of Chrome, there was no way to stop content from loading, so AdBlock only removed ads after they were displayed (they'd flash briefly on-screen). So back then, it wasn't very good. At some point (years ago) they added APIs to filter content before it loads, which basically solved that problem (although there was a transition period where AdBlock was a bit buggy as they worked the kinks out). Nowadays, it's been quite some time since I've used FireFox, but AdBlock seems to work as well as I remember AdBlock working when I used FireFox.
But in terms of my previous reply, I specifically was referring to there being methods to do stuff in the DOM while it's still loading, which contradicts the claim that you can't do anything until after it loads. I don't know if you can do anything before it loads at all, but you can definitely do stuff before it finishes.
Chrome does provide support for modifying the DOM before it finishes loading.
Boeing is still making new 747s, still actively delivering them. They still have orders for future planes. Korean Air just last month announced they had placed an order for ten more of them. How the heck does that equate to "heading for retirement"?
Epson's $28,000 64" solvent printer begs to differ.
The two companies don't overlap in all the types of printers they offer, but they're both making both consumer and enterprise printers.
Did you not notice that all of Apple's 2015 notebooks are missing from the list you linked? They're on the corresponding lists for Win8 and Win10.
The only current mac that is listed as supporting Win7 is the mid-2015 Retina 5K iMac.
The chiclet keyboards of today have little in common with the chiclet keyboards that caused inssues in the 80s. The complaint back then had more to do with the physical mechanism (often a single rubber membrane for the whole keyboard and very poor quality/design) rather than the fact that the keytops were flat with a little space between the keys.
Sorry, yes, I meant even if it was identical to RAM.
Memory management would be tougher because now you're using the same device for both long-term storage (which still requires file systems and all the usual stuff) and working RAM (which needs to be directly accessible by the CPU without any sort of thing like a filesystem). Dynamically sharing the two doesn't sound simple to me. Certainly no simpler than managing what pages get swapped in or out.
If you put a bunch of constraints on the setup, like always using the same pre-determined areas as RAM and storage, then it'd be simpler... but what would have been the point of merging the two in the first place?
With this particular technology, never... but even if it performed identically to flash, you would need a radical shift in computer architecture (both software and hardware) to support such a thing, and it would actually substantially increase complexity rather than decrease it. Memory management would become far more complex, I don't know why you think it wouldn't be needed at all.
1000x the endurance, but since it's also 1000x faster, you can wear it out just as fast assuming you're maxing out the IO long enough, and assuming that they use similar wear leveling.
I get that technically-oriented people like those on Slashdot are opposed to automatic updates, but this product isn't targeting you. Most people are going to get their wifi router either from their ISP (where the ISP will manage updates) or something they bought at BestBuy and never touched again after they got it working. Most people will never go out of their way to update anything unless it's either done for them automatically or they're prompted to do so.
Wifi routers are absolutely a place where, for most people, security updates should happen automatically, because for most people, the alternative is for wifi routers to spend their entire lifetime running the same version they shipped with, whatever security updates that may entail.
Because nobody who has a quad-core processor in their notebook would ever want to watch a movie anywhere they might not have power... Obviously anybody who wants to do more than one thing with their notebook should carry around multiple notebooks so that they can have a dedicated one for each task.
DC has lower loss for transmission lines, but nearly all power plants produce AC, so you're going to suffer additional losses converting the AC from your turbines to DC for transmission, and then back to AC for local distribution (to avoid the massive losses of low voltage DC), and then back to DC for the actual appliances.
HVDC has its place, but it would be very inefficient to switch from HVAC to HVDC everywhere...
You can buy a laser printer for under $40, or a color laser for $100. Ink jet printers have their place, but for most people, a cheap laser is a far better (and cheaper) option.