The main reason they can build so quickly is that the Chinese government routinely kicks huge numbers of its citizens out of the areas where they want to build their infrastructure. That's not something to envy.
Not just eventually, all at once. We just have no way to extract all that superimposed information.
I half expect the author to eventually come out and say he just made it all up to find out how much nonsense he could get away with by labeling it art.
Part of the problem in this discussion is that your UK gallons are larger
No. I looked up l/100 km and converted that to American gallons.
The iQ at 37 mpg? Then there's something seriously screwy going on with those numbers, because RW it gets closer to 55. You'd have to drive it like a buffoon to get anywhere near 37 mpg. The Mirage RW numbers you quote have sample sizes of 2 and 5 respectively so yes, they are suspect. The numbers I quoted have much larger sample sizes so they're bound to be more accurate.
I chose examples that exclude legislation as the reason lightweight cars aren't built any more. So the reason lightweight cars aren't built any more must be something else. The American fondness for huge cars may have something to do with it.
In Europe, there's an entire class of cars smaller than the Mirage and Fiesta. The VW Up (47 mpg), Suzuki Alto (54 mpg), Toyota Aygo (56 mpg) to name a few (and that's real-world fuel consumption, not a theoretical rating). This site has RW usage of the Metro at closer to 40 than 47.
The XL1 is in production, by the way. Expensive, but definitely not a concept any more.
There's no legitimate reason why cheap, lightweight cars like the Honda CRX (better fuel economy than a modern Prius... in 1988!) are effectively no longer allowed to be made.
Stricter safety regulations mean some weight gain has been inevitable. As for the rest, I remember how austere those lightweight cars used to be. Everything manually-operated, no air con, no soundproofing, minimal dashboard (no cupholders). The reason almost nobody builds cars like that anymore is almost nobody buys cars like that anymore.
Lightweight cars are still possible. Lotus and Smart for example. VW XL1. Austere cars are still available too (in Europe at least, IDK about the States) (a recent Citroen, Dacia).
America has lost the capability of being able to reproduce the original Mercury flight of Alan Shepard.
No they haven't. The US is perfectly capable technology-wise of designing and building manned rockets. They've just chosen to accept (for political, not technological reasons) a gap of a couple of years between the retirement of the Shuttle and the inaugural manned commercial flight.
Last year I came across an old phone, with a button pad, that was switchable between DTMF and pulse dial. The switch was still set to pulse. Better: it could still make calls! I did switch it to DTMF though:)
3 days ago I would have agreed. Then I went to get a new set of tyres for my car and to have its wheel geometry checked/aligned. They handed me a printout with the alignment data, which was clearly made on a dot matrix printer...
I find remote desktops still incredibly frustrating to work with. RDP hiccups causing drag-and-drop to fail intermittently, inaccuracy in mouse position (try dragging a column separator in Windows Explorer: it's almost impossible to hit that 1-px wide target on a remote machine), security restrictions invariably in place on the remote machine (examples on one RDP machine I have the displeasure of having to work on: no command line access, no access to the control panel so I can't even swap my L/R mouse buttons, session gets wiped on logout so I have to change the same settings every time), endlessly copying between the local and remote systems, sessions that terminate with prejudice if there's no input for an hour. Blaugh.
My backups are done on a USB harddisk that's connected to the media server on my home network. Switch the HD on, and it'll appear and backups can be made.
How can I prevent malware from changing my backups? Would it be possible/effective to mount the drive as write-only, making it impossible to change existing files?
Your memory must be better than mine, there's no way I can correctly remember every turn in a 500-km route, nor do I wish to. You're also toast when your memory is off a bit (second or third right?) or you misinterpret an instruction (is that a road or a private driveway?) or a road name sign is missing/vandalized/unreadable in the dark. One missed instruction and you're lost again and up shit creek without a paddle. Honestly, I am astonished people still accept such kludges.
Not this Luddite bullshit again. When I'm on the road, I'm on my way to a destination. When it's for work, I don't care about new places, I just want to get my appointment via the most efficient route. When I'm on vacation, there's a bit more leeway but I still have a destination to get to. At the end of a long journey, I no longer care about the scenery and just want to get to my hotel or campsite already.
The cost of making a mistake is high in lost time and aggravation. Without GPS I'd have to resort to maps, and have you ever driven solo while navigating from a map? You end up either a menace on the road, or having to stop to consult the bloody map every 5 minutes. Not to mention having to buy the map in the first place. So if you enjoy getting lost, fine. But stop whining about people using GPS.
French seems to have a demarcation: using words derived from Latin or Greek origins is okay, deriving words from English is not. Walkman becomes balladeur, computer becomes ordinateur etc.
America's military dominance is still more than enough to ensure no nation will take up arms against the US. The current threat to Pax Americana isn't military action from another nation, but US military actions abroad that foster insurgency and terrorism. Vietnam, Afghanistan and Iraq have shown that military dominance isn't enough to win a war against a determined population.
It is infinitely preferable to the Windows way of doing things, where the update process can basically say (using the default settings) 'Fuck you and your open documents, we're going to reboot NOW'. The mind boggles at the level of disrespect that shows. Can things be improved? Probably. But until they are, I prefer the OS that lets me reboot on MY schedule.
Uh, no. West Germany largely recovered on its own. They didn't have access to Marshall Plan funds until after their economic recovery had started. In fact the US and its allies started the postwar period by removing lots of valuables (coal and steel industry, patents, scientists) from Germany.
Small A-pillars were SOP when behavior in a crash wasn't subject to legislation. As a result, you'd have A-pillars that buckled into the passenger compartment at the slightest provocation. These days, the goal is a door frame strong enough that you can still open the door after a crash.
This drivel is scored +5, Insightful? A text-only terminal is barely adequate for basic data entry, and useless at anything else. Guess what, basic data entry's about 1% of what office workers need to do these days. On an average day I write documents, create and edit drawings, and I create programs and scripts. All of which benefit from having 24" pixel-addressable screens and a decent GUI. Force me to work on a fucking terminal and my productivity goes through the floor.
Your job is to SUPPORT the users, not hinder them at every turn.
The move to 32-layer 3D VNAND 3-bit MLC flash brings pricing down to the.50 to.60 per GiB range, but doesn't adversely affect endurance because the cell structure doesn't suffer from the same inherent limitations of planar NAND, since the cells are stacked vertically with the 3D VNAND.
which didn't make sense to me. Luckily Anandtech has a non-gibberish explanation:
Rather than increasing density by shrinking cell size, Samsung's V-NAND takes a few steps back in process technology and instead stacks multiple layers of NAND cells on top of one another....In the floating gate MOSFET, electrons are stored on the gate itself - a conductor. Defects in the transistor (e.g. from repeated writes) can cause a short between the gate and channel, depleting any stored charge in the gate. If the gate is no longer able to reliably store a charge, then the cell is bad and can no longer be written to. Ultimately this is what happens when you wear out an SSD.
With V-NAND, Samsung abandons the floating gate MOSFET and instead turns to its own Charge Trap Flash (CTF) design. An individual cell looks quite similar, but charge is stored on an insulating layer instead of a conductor. This seemingly small change comes with a bunch of benefits, including higher endurance and a reduction in overall cell size. That's just part of the story though.
V-NAND takes this CTF architecture, and reorganizes it into a non-planar design. The insulator surrounds the channel, and the control gate surrounds it. The 3D/non-planar design increases the physical area that can hold a charge, which in turn improves performance and endurance.
The final piece of the V-NAND puzzle is to stack multiple layers of these 3D CTF NAND cells. Since Samsung is building density vertically, there's not as much pressure to shrink transistor sizes. With relaxed planar space constraints, Samsung turned to an older manufacturing process (30nm class, so somewhere between 30 and 39nm) as the basis of V-NAND.
By going with an older process, Samsung inherently benefits from higher endurance and interference between cells is less of an issue. Combine those benefits with the inherent endurance advantages of CTF and you end up with a very reliable solution. Whereas present day 19/20nm 2-bit-per-cell MLC NAND is good for around 3000 program/erase cycles, Samsung's 30nm-class V-NAND could withstand over 10x that (35K p/e cycles).
Birds are notoriously squishy. A drone carries one or more electric motors and a battery pack, both of which are rather denser and less breakable than bird bones.
The main reason they can build so quickly is that the Chinese government routinely kicks huge numbers of its citizens out of the areas where they want to build their infrastructure. That's not something to envy.
Not just eventually, all at once. We just have no way to extract all that superimposed information.
I half expect the author to eventually come out and say he just made it all up to find out how much nonsense he could get away with by labeling it art.
Part of the problem in this discussion is that your UK gallons are larger
No. I looked up l/100 km and converted that to American gallons.
The iQ at 37 mpg? Then there's something seriously screwy going on with those numbers, because RW it gets closer to 55. You'd have to drive it like a buffoon to get anywhere near 37 mpg.
The Mirage RW numbers you quote have sample sizes of 2 and 5 respectively so yes, they are suspect. The numbers I quoted have much larger sample sizes so they're bound to be more accurate.
I chose examples that exclude legislation as the reason lightweight cars aren't built any more. So the reason lightweight cars aren't built any more must be something else. The American fondness for huge cars may have something to do with it.
In Europe, there's an entire class of cars smaller than the Mirage and Fiesta. The VW Up (47 mpg), Suzuki Alto (54 mpg), Toyota Aygo (56 mpg) to name a few (and that's real-world fuel consumption, not a theoretical rating).
This site has RW usage of the Metro at closer to 40 than 47.
The XL1 is in production, by the way. Expensive, but definitely not a concept any more.
There's no legitimate reason why cheap, lightweight cars like the Honda CRX (better fuel economy than a modern Prius... in 1988!) are effectively no longer allowed to be made.
Stricter safety regulations mean some weight gain has been inevitable. As for the rest, I remember how austere those lightweight cars used to be. Everything manually-operated, no air con, no soundproofing, minimal dashboard (no cupholders). The reason almost nobody builds cars like that anymore is almost nobody buys cars like that anymore.
Lightweight cars are still possible. Lotus and Smart for example. VW XL1. Austere cars are still available too (in Europe at least, IDK about the States) (a recent Citroen, Dacia).
America has lost the capability of being able to reproduce the original Mercury flight of Alan Shepard.
No they haven't. The US is perfectly capable technology-wise of designing and building manned rockets. They've just chosen to accept (for political, not technological reasons) a gap of a couple of years between the retirement of the Shuttle and the inaugural manned commercial flight.
Last year I came across an old phone, with a button pad, that was switchable between DTMF and pulse dial. The switch was still set to pulse. Better: it could still make calls! :)
I did switch it to DTMF though
3 days ago I would have agreed. Then I went to get a new set of tyres for my car and to have its wheel geometry checked/aligned. They handed me a printout with the alignment data, which was clearly made on a dot matrix printer...
I find remote desktops still incredibly frustrating to work with. RDP hiccups causing drag-and-drop to fail intermittently, inaccuracy in mouse position (try dragging a column separator in Windows Explorer: it's almost impossible to hit that 1-px wide target on a remote machine), security restrictions invariably in place on the remote machine (examples on one RDP machine I have the displeasure of having to work on: no command line access, no access to the control panel so I can't even swap my L/R mouse buttons, session gets wiped on logout so I have to change the same settings every time), endlessly copying between the local and remote systems, sessions that terminate with prejudice if there's no input for an hour. Blaugh.
A few dozen Germans, on a workforce exceeding 100,000 at the height of the Apollo program.
My backups are done on a USB harddisk that's connected to the media server on my home network. Switch the HD on, and it'll appear and backups can be made.
How can I prevent malware from changing my backups? Would it be possible/effective to mount the drive as write-only, making it impossible to change existing files?
Your memory must be better than mine, there's no way I can correctly remember every turn in a 500-km route, nor do I wish to.
You're also toast when your memory is off a bit (second or third right?) or you misinterpret an instruction (is that a road or a private driveway?) or a road name sign is missing/vandalized/unreadable in the dark. One missed instruction and you're lost again and up shit creek without a paddle. Honestly, I am astonished people still accept such kludges.
Not this Luddite bullshit again. When I'm on the road, I'm on my way to a destination. When it's for work, I don't care about new places, I just want to get my appointment via the most efficient route. When I'm on vacation, there's a bit more leeway but I still have a destination to get to. At the end of a long journey, I no longer care about the scenery and just want to get to my hotel or campsite already.
The cost of making a mistake is high in lost time and aggravation. Without GPS I'd have to resort to maps, and have you ever driven solo while navigating from a map? You end up either a menace on the road, or having to stop to consult the bloody map every 5 minutes. Not to mention having to buy the map in the first place.
So if you enjoy getting lost, fine. But stop whining about people using GPS.
French seems to have a demarcation: using words derived from Latin or Greek origins is okay, deriving words from English is not. Walkman becomes balladeur, computer becomes ordinateur etc.
Please, not another useless Chrome clone. We already have more than enough browsers with crap UIs, thank you.
America's military dominance is still more than enough to ensure no nation will take up arms against the US. The current threat to Pax Americana isn't military action from another nation, but US military actions abroad that foster insurgency and terrorism. Vietnam, Afghanistan and Iraq have shown that military dominance isn't enough to win a war against a determined population.
It is infinitely preferable to the Windows way of doing things, where the update process can basically say (using the default settings) 'Fuck you and your open documents, we're going to reboot NOW'. The mind boggles at the level of disrespect that shows.
Can things be improved? Probably. But until they are, I prefer the OS that lets me reboot on MY schedule.
Uh, no. West Germany largely recovered on its own. They didn't have access to Marshall Plan funds until after their economic recovery had started. In fact the US and its allies started the postwar period by removing lots of valuables (coal and steel industry, patents, scientists) from Germany.
Small A-pillars were SOP when behavior in a crash wasn't subject to legislation. As a result, you'd have A-pillars that buckled into the passenger compartment at the slightest provocation.
These days, the goal is a door frame strong enough that you can still open the door after a crash.
ISS power budget is 75-90 kW.
This drivel is scored +5, Insightful?
A text-only terminal is barely adequate for basic data entry, and useless at anything else. Guess what, basic data entry's about 1% of what office workers need to do these days. On an average day I write documents, create and edit drawings, and I create programs and scripts. All of which benefit from having 24" pixel-addressable screens and a decent GUI. Force me to work on a fucking terminal and my productivity goes through the floor.
Your job is to SUPPORT the users, not hinder them at every turn.
Listen to yourself
TFA says:
The move to 32-layer 3D VNAND 3-bit MLC flash brings pricing down to the .50 to .60 per GiB range, but doesn't adversely affect endurance because the cell structure doesn't suffer from the same inherent limitations of planar NAND, since the cells are stacked vertically with the 3D VNAND.
which didn't make sense to me. Luckily Anandtech has a non-gibberish explanation:
Rather than increasing density by shrinking cell size, Samsung's V-NAND takes a few steps back in process technology and instead stacks multiple layers of NAND cells on top of one another. ...In the floating gate MOSFET, electrons are stored on the gate itself - a conductor. Defects in the transistor (e.g. from repeated writes) can cause a short between the gate and channel, depleting any stored charge in the gate. If the gate is no longer able to reliably store a charge, then the cell is bad and can no longer be written to. Ultimately this is what happens when you wear out an SSD.
With V-NAND, Samsung abandons the floating gate MOSFET and instead turns to its own Charge Trap Flash (CTF) design. An individual cell looks quite similar, but charge is stored on an insulating layer instead of a conductor. This seemingly small change comes with a bunch of benefits, including higher endurance and a reduction in overall cell size. That's just part of the story though.
V-NAND takes this CTF architecture, and reorganizes it into a non-planar design. The insulator surrounds the channel, and the control gate surrounds it. The 3D/non-planar design increases the physical area that can hold a charge, which in turn improves performance and endurance.
The final piece of the V-NAND puzzle is to stack multiple layers of these 3D CTF NAND cells. Since Samsung is building density vertically, there's not as much pressure to shrink transistor sizes. With relaxed planar space constraints, Samsung turned to an older manufacturing process (30nm class, so somewhere between 30 and 39nm) as the basis of V-NAND.
By going with an older process, Samsung inherently benefits from higher endurance and interference between cells is less of an issue. Combine those benefits with the inherent endurance advantages of CTF and you end up with a very reliable solution. Whereas present day 19/20nm 2-bit-per-cell MLC NAND is good for around 3000 program/erase cycles, Samsung's 30nm-class V-NAND could withstand over 10x that (35K p/e cycles).
Birds are notoriously squishy. A drone carries one or more electric motors and a battery pack, both of which are rather denser and less breakable than bird bones.
Doesn't anyone hibernate their computer at the end of the day? 8 GBx365 days = 3 TB in one year for my main machine.