Slashdot Mirror


End of Moore's Law Forcing Radical Innovation

dcblogs writes "The technology industry has been coasting along on steady, predictable performance gains, as laid out by Moore's law. But stability and predictability are also the ingredients of complacency and inertia. At this stage, Moore's Law may be more analogous to golden handcuffs than to innovation. With its end in sight, systems makers and governments are being challenged to come up with new materials and architectures. The European Commission has written of a need for 'radical innovation in many computing technologies.' The U.S. National Science Foundation, in a recent budget request, said technologies such as carbon nanotube digital circuits will likely be needed, or perhaps molecular-based approaches, including biologically inspired systems. The slowdown in Moore's Law has already hit high-performance computing. Marc Snir, director of the Mathematics and Computer Science Division at the Argonne National Laboratory, outlined in a series of slides the problem of going below 7nm on chips, and the lack of alternative technologies."

275 comments

  1. Rock Star coders! by Anonymous Coward · · Score: 5, Insightful

    The party's over. Get to work on efficient code. As for the rest of all you mothafucking coding wannabes, suck it! Swallow it. Like it! Whatever, just go away.

    1. Re:Rock Star coders! by Z00L00K · · Score: 4, Insightful

      Efficient code and new ways to solve computing problems using massive multi-core solutions.

      However many "problems" with performance today are I/O-based and not calculation based. It's time for the storage systems to catch up in performance with the processors, and they are on the way with SSD disks.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    2. Re:Rock Star coders! by lgw · · Score: 5, Interesting

      I think the next couple of decades will be mostly about efficiency. Between mobile computing and the advantage of ever-more cores, the benefits from lower power consumption (and reduce heat load as a result) will be huge. And unlike element size, we're far from basic physical limits on efficiency.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    3. Re:Rock Star coders! by jones_supa · · Score: 1

      But efficiency is largely based on element size.

    4. Re:Rock Star coders! by gweihir · · Score: 1

      You still do not get it. There will be no further computing power revolution.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    5. Re:Rock Star coders! by K.+S.+Kyosuke · · Score: 4, Insightful

      There hasn't been a computing power revolution for quite some time now. All the recent development has been rather evolutionary.

      --
      Ezekiel 23:20
    6. Re:Rock Star coders! by Forever+Wondering · · Score: 4, Interesting

      There was an article not too long ago (can't remember where) that mentioned that a lot of the performance improvement over the years came from better algorithms rather than faster chips (e.g. one can double the processor speed but that pales with changing an O(n**2) algorithm to O(n*log(n)) one).

      SSD's based on flash aren't the ultimate answer. Ones that use either magneto-resistive memory or ferroelectric memory show more long term promise (e.g. mram can switch as fast as L2 cache--faster than DRAM but with the same cell size). With near unlimited memory at that speed, a number of multistep operations can be converted to a single table lookup. This is done a lot in a lot of custom logic where the logic is replaced with a fast SRAM/LUT.

      Storage systems (e.g. NAS/SAN) can be parallelized but the limiting factor is still memory bus bandwidth [even with many parallel memory buses].

      Multicore chips that use N-way mesh topologies might also help. Data is communicated via a data channel that doesn't need to dump to an intermediate shared buffer.

      Or hybrid cells that have a CPU but also have programmable custom logic attached directly. That is, part of the algorithm gets compiled to RTL that can then be loaded into the custom logic just as fast as a task switch (e.g. on every OS reschedule). This is why realtime video encoders use FPGAs. They can encode video at 30-120 fps in real time, but a multicore software solution might be 100x slower.

      --
      Like a good neighbor, fsck is there ...
    7. Re:Rock Star coders! by Anonymous Coward · · Score: 3, Insightful

      (e.g. one can double the processor speed but that pales with changing an O(n**2) algorithm to O(n*log(n)) one).

      In some cases. There are also a lot of cases where overly complex functions are used to manage lists that usually contains three or four items and never reaches ten.
      Analytical optimizing is great when it can be applied but just because one has more than one data item to work on doesn't automatically mean that a O(n*log(n)) will beat a O(n**2) solution. The O(n**2) solutions will often be faster per iteration so it is a good idea to consider how many items one usually will work with.

    8. Re:Rock Star coders! by gweihir · · Score: 1

      Indeed. Just my point. And that evolution is going slower and slower.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    9. Re:Rock Star coders! by VortexCortex · · Score: 1

      However many "problems" with performance today are I/O-based and not calculation based. It's time for the storage systems to catch up in performance with the processors, and they are on the way with SSD disks.

      Now, I want you to imagine the CPU being part of the storage system itself. That's right. Welcome to FPGA city where the RAM is persistent and the chipset doesn't exist. You will get here eventually. It's just a matter of time until the general purpose processor becomes a free form Von Neumann machine. What's a Cores? Ah, you mean read/write "heads". Screw the prime directive, it's almost painful to watch this crap.

    10. Re:Rock Star coders! by ObsessiveMathsFreak · · Score: 2

      Amen. The most used CPU architectures in the world today are directly descended from microcontroller architectures designed in the late 1960s and early 1970s, based on the work of a handful of designers. None of those designers could have planned for or envisaged their chips as being the widely used CPUs of today.

      --
      May the Maths Be with you!
    11. Re:Rock Star coders! by Anonymous Coward · · Score: 0

      The party's over. Get to work on efficient code. As for the rest of all you mothafucking coding wannabes, suck it! Swallow it. Like it! Whatever, just go away.

      You mean learning an hour of code doesn't magically produce awesome coders? But Google said...

    12. Re:Rock Star coders! by geekmux · · Score: 2

      I think the next couple of decades will be mostly about efficiency. Between mobile computing and the advantage of ever-more cores, the benefits from lower power consumption (and reduce heat load as a result) will be huge. And unlike element size, we're far from basic physical limits on efficiency.

      Efficiency in consumer products will have to outweigh greed first.

      I never asked for anyone to put a 10-million app capability on my phone, or any of the other 37 now-standard features that suck the life out of my phone battery just by looking at it.

      If today's smartphone hardware had to run with functions circa 10 years ago, the batteries would likely last for weeks. Our technology even today is far better than we think. The only thing we're better at, is greed feeding excess.

    13. Re:Rock Star coders! by complete+loony · · Score: 2

      TFA is more about the problem of using commodity parts in high performance super computers. Since most of the industry is now more focussed on smaller and lower power chips.

      --
      09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
    14. Re:Rock Star coders! by Anonymous Coward · · Score: 0

      You got a point there. There is little need for faster hardware, there is a huge need for more efficient translation from "telling the processor what to do" to "whatever the processor really does". I'd bet that 95% of the cycles your processor spends (either SmartPhone or PC) is spent on inefficiencies.

    15. Re:Rock Star coders! by Anonymous Coward · · Score: 1

      Do you actually know anything about FPGAs? Because I do. They're great for cheap development, but you'd never call them....efficient. Or high performance. If you can get enough performance out of them for the need, and they don't suck too much power doing it, then great, use them. But they'll never complete with ASICs in any arena other than cost. That's just by sheer definition, they're generic, programmable logic arrays. As such, they need to be laid out in such a way to be generic, which always inserts inefficiencies. Throw in that programming them is basically putting bits into a massive shift register, which adds extra complexity at no computational gain and.....yeah. Remember, FPGA stands for Field Programmable Gate Array, they're a specific type of logic device that can be reprogrammed.

    16. Re:Rock Star coders! by Anonymous Coward · · Score: 0

      You can still buy dumb phones. Mine stays charged for about 2 weeks. They offer what they do because people buy them.

    17. Re:Rock Star coders! by fatphil · · Score: 1

      True, but some of the evolutionary steps have permitted an order of magnitude improvement. For example, the invention of excimer laser lithography has permitted chip density to increase by a factor of several hundred (i.e. by well over a factor of 10, but in 2 dimensions).

      --
      Also FatPhil on SoylentNews, id 863
    18. Re:Rock Star coders! by martin-boundary · · Score: 3, Insightful

      However many "problems" with performance today are I/O-based and not calculation based. It's time for the storage systems to catch up [...]

      Meh, that's a copout. IO has always been a bottleneck. Why do you think that Knuth spends so much time optimizing sorting algorithms for tapes? It's not a new issue, solve it by changing your algorithm (aka calculation).

      The current generation of programmers are so used to doing cookie cutter work, gluing together lower level libraries that they do not understand in essentially trivial ways, that when they are faced with an actual mismatch between the problem and the assumptions of the lower level code, there is nothing they know how to do. Here's a hint: throw away the lower level crutches, and design a scalable solution from scratch. Most problems can be solved in many ways, and the solution that uses your favourite framework is probably never the most efficient.

      /rant

    19. Re:Rock Star coders! by K.+S.+Kyosuke · · Score: 1

      Now, I want you to imagine the CPU being part of the storage system itself. That's right.

      I don't have to imagine that, the Connection Machine was invented in the 1980s.

      --
      Ezekiel 23:20
    20. Re:Rock Star coders! by ShanghaiBill · · Score: 3, Insightful

      I never asked for anyone to put a 10-million app capability on my phone

      Yet you bought a phone with that capability.

      or any of the other 37 now-standard features that suck the life out of my phone battery

      You can buy a dumb phone with a battery that lasts a week or more, for a lot less than you paid for your smart phone.

      The only thing we're better at, is greed feeding excess.

      It was silly of you to pay extra for features that you didn't want. It is even sillier to then whine that you were somehow a victim of "greed".

    21. Re:Rock Star coders! by Anonymous Coward · · Score: 0

      Or just produce large amount of new code without the legacy cruft hampering scaling to multicore. Lots of good, well verified but not scalable code has to go, or be re-purposed eventually.

    22. Re:Rock Star coders! by zerk14351 · · Score: 2

      It's not that there are no opportunities left: there's plenty of inefficiency all around. For example, this recent email details a floating-point formatter that is 4-6 times faster than glibc printf: http://gcc.gnu.org/ml/libstdc++/2014-01/msg00017.html Yes, that's right, it's that much faster than the C printf function that everyone has been using for decades.

    23. Re:Rock Star coders! by slew · · Score: 1

      I would disagree with this. Although most of the CPU instruction set designs and programmer paradigms are directly descended from microcontroller architectures in the 60's and 70's, but most of the lineage of CPUs today is from the early super-scalar designs from the '80s...

      Some might credit the CDC6600 (a early generation super-computer, not a microcontroller) as the first super scalar design that inspired this, but it was more akin to a unified instruction stream with several non-pipelined functional units (kind of like how early CPU's dispatched instructions to an FPU or other co-processor device).

    24. Re:Rock Star coders! by lgw · · Score: 1

      Yes, exactly. The limiting factor on built-from-commodity-parts supercomputers is in fact the heat from what I hear. You pack in the CPUs as tight as you can, but that limit is the ability to transfer the heat out at that density. A 4 GHz core with half the heatload of the current would more-or-less double the number of cores you can shove in a given cabinet (without the ceiling catching fire).

      --
      Socialism: a lie told by totalitarians and believed by fools.
    25. Re:Rock Star coders! by lgw · · Score: 1

      Yes, today, but really there hasn't been much focus on anything except ways to reduce element size for decades. If the goal becomes "half the heat at the same frequency" rather then "double the frequency" in N years, with the same brainpower and funding thrown at the problem, there's certainly many doublings-of-efficiency available before "I canna break the laws of physics Captain", without going smaller.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    26. Re:Rock Star coders! by unixisc · · Score: 1

      I thought that ASICs were cheaper per die. In other words, you develop something on an FPGA, use the FPGA in production as long as volumes are low and all the kinks/bugs are yet to be found. Once demand escalates and pricing pressure increases, then ASICs based on that demand are made, which don't include any unused logic. Those ASICs then tend to be smaller than equivalent FPGAs, w/ reduced die size & test time on the same process, thereby resulting in a cost reduction.

      It's analogous to how flash memory is sometimes used in initial designs of certain electronic goods, and switched over to ROMs once the code is frozen. Same principles here

    27. Re:Rock Star coders! by ImprovOmega · · Score: 1

      Or just do some kind of bog simple test to see how many elements you're sorting. 100 or less? Insertion Sort. More than 100 but still small enough to fit in L1 cache? Heapsort. Bigger than cache allows for? Quicksort time. And conveniently this hybrid algorithm still guarantees O(n*log(n)) run time (assuming you don't frig up your implementation of quicksort by allowing it to pick bad pivots) because Insertion Sort for a fixed number of elements is technically O(1) time.

    28. Re:Rock Star coders! by ultranova · · Score: 3, Interesting

      Yes, today, but really there hasn't been much focus on anything except ways to reduce element size for decades.

      True but misleading. A smaller element has less surface area to dissipate its heat, thus it must either generate less or run hotter. And silicon ran into the upper limits of the material years ago, which is why processors have required active cooling for a long time now. But that has practical limits, so the TDP of new flagship processors stays around the same (100-200 W) and after a few generations their tech gets recycled into a power-optimized model.

      In other words, you can't reduce element size without also reducing power usage or the damn thing will melt.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    29. Re:Rock Star coders! by Anonymous Coward · · Score: 0

      Ha, your head will be on a pike, when the majority get tired of your elitism and come after you. It doesn't really matter that you have an inflated programmer ego and think that most people aren't as good as you, because those people will still code and get paid for it because what they do is just good enough, not the best, of which there is no single definition. Maybe some of those people will write code for wimpy processors too because they are just good enough, meaning available and cheap, not because they need your hand optimized code. So come off it!

    30. Re:Rock Star coders! by Pseudonym · · Score: 1

      The System/360 model 91 doesn't count, in your opinion?

      All CPU design is evolutionary. Even the Tomasulo algorithm was an evolutionary design.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    31. Re:Rock Star coders! by Pseudonym · · Score: 1

      More than 100 but still small enough to fit in L1 cache? Heapsort.

      No way. Heapsort is historically very important (it was the first O(n log n) sorting algorithm), but it's useless in practice except as a fallback. The constant factors are enormous, and it requires O(n log n) time no matter what, even when the collection is almost sorted. Even Shell sort typically does better than heapsort on this size of data.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    32. Re:Rock Star coders! by Anonymous Coward · · Score: 0

      or any of the other 37 now-standard features that suck the life out of my phone battery

      You can buy a dumb phone with a battery that lasts a week or more, for a lot less than you paid for your smart phone.

      You missed the point.
      Someone may want a "smartphone" to only play Candy Crush Saga or Angry Birds ... either way, they only need a nice screen and touch functionality - the 37 other features could be removed - battery life improved.... :)

  2. Moore's Law isnt a law you know by Osgeld · · Score: 5, Insightful

    Its more of a prediction, that has mostly been on target cause of its challenging nature

    1. Re: Moore's Law isnt a law you know by crutchy · · Score: 3, Funny

      now now don't you go spreading propaganda that laws aint laws... next there will be idiots coming out of the woodwork claiming that einstein may have got it wrong and that it's ok to take a dump whilst being cavity searched by the police

    2. Re: Moore's Law isnt a law you know by Anonymous Coward · · Score: 0

      Its challenging nature...and the fact that the company that originated felt a need to make it a reality to stay competitive and be the leading edge of computer technology. It worked.

    3. Re: Moore's Law isnt a law you know by Anonymous Coward · · Score: 0

      It was originally an extrapolation of what came before. It then became a guidepost. With designers actually using it as a target, can you really call it self fulling?

    4. Re: Moore's Law isnt a law you know by Anonymous Coward · · Score: 0

      now now don't you go spreading propaganda that laws aint laws... next there will be idiots coming out of the woodwork claiming that einstein may have got it wrong and that it's ok to take a dump whilst being cavity searched by the police

      On the other hand, I feel that taking a dump while being cavity searched is the BEST time to take a dump. What better way to prove the cops claims are full of shit after all?

    5. Re: Moore's Law isnt a law you know by DRJlaw · · Score: 1

      Its more of a prediction, that has mostly been on target cause of its challenging nature

      No. Moore's Law is meta. Moore's Law is not in fact a law that IC transistor density will double every 18-24 months. That's Moore's observation. Moore's Law is this: Some pedant will pop up and be modded +5 insightful for stating, for the millionth time in recent memory, that Moore's observation isn't a law.

      And there you have Moore's Law.

  3. Blind ants, now need to search more branches by ka9dgx · · Score: 3, Insightful

    Now the blind ants (researchers) will need to explore more of the tree (the computing problem space)... there are many fruits out there yet to discover, this is just the end of the very easy fruit. I happen to believe that FPGAs can be made much more powerful because of some premature optimization. Time will tell if I'm right or wrong.

    1. Re: Blind ants, now need to search more branches by jarfil · · Score: 2

      So true. I also happen to believe that adding an FPGA coprocessor to general purpose CPUs, that applications could reconfigure on the fly to perform certain tasks, could lead to massive increases in performance.

    2. Re:Blind ants, now need to search more branches by crutchy · · Score: 4, Funny

      just need to shoot more advanced alien spaceships down near roswell

    3. Re: Blind ants, now need to search more branches by gweihir · · Score: 4, Interesting

      As somebody that has watched what has been going on in that particular area for more than 2 decades, I do not expect anything to come out of it. FPGAs are suitable for doing very simples things reasonably fast, but so are graphics cards and with a much better interface. Bit as soon as communication between computing elements or large memory is required, both FPGAs and graphics cards become abysmally slow in comparison to modern CPUs. That is not going to change, as it is an effect of the architecture. There will not be any "massive" performance increase anywhere now.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    4. Re: Blind ants, now need to search more branches by InvalidError · · Score: 3, Interesting

      Programming FPGAs is far more complex than programming GPGPUs and you would need a huge FPGA to match the compute performance available on $500 GPUs today. FPGAs are nice for arbitrary logic such as switch fabric in large routers or massively pipelined computations in software-defined radios but for general-purpose computations, GPGPU is a much cheaper and simpler option that is already available on many modern CPUs and SoCs.

    5. Re: Blind ants, now need to search more branches by linearz69 · · Score: 2

      FPGAs are relatively expensive compared to graphics chips, actually most chips. Its still not clear what FPGAs can accomplish in a general computing platform that will be of value, considering the other lower cost options available.

      The other half of the problem here is that, in comparison to GPU programming interfaces such as OpenCL and Cuda, there is relatively little effort in bringing FPGA development beyond ASIC-Lite. The tool chains and development processes (what FPGA vendors like to call "design flow") are miles apart between FPGA and software code. Right now, SystemC is the only thing close to software develpment for FPGAs (mainly because of C++ syntax) , but it really isn't that close. Also consider that there are really no common architectures - RTL synthesis can vary from part to part, and place & route is different for every flippen part number. This makes it nearly impossible for any third party, beyond pricey CAD vendors with cozy relationships to the FPGA Mfgs, to develop the libraries required to cleanly integrate FPGAs into software development.

      The FPGA manufactures have done quite well on the low volume, high margin game. They have no incentive to drop the cost required for consumer volumes. GPUs are a completely different story....

    6. Re: Blind ants, now need to search more branches by Anonymous Coward · · Score: 0

      FPGAs are relatively expensive compared to graphics chips, actually most chips. Its still not clear what FPGAs can accomplish in a general computing platform that will be of value, considering the other lower cost options available.

      The other half of the problem here is that, in comparison to GPU programming interfaces such as OpenCL and Cuda, there is relatively little effort in bringing FPGA development beyond ASIC-Lite. The tool chains and development processes (what FPGA vendors like to call "design flow") are miles apart between FPGA and software code. Right now, SystemC is the only thing close to software develpment for FPGAs (mainly because of C++ syntax) , but it really isn't that close. Also consider that there are really no common architectures - RTL synthesis can vary from part to part, and place & route is different for every flippen part number. This makes it nearly impossible for any third party, beyond pricey CAD vendors with cozy relationships to the FPGA Mfgs, to develop the libraries required to cleanly integrate FPGAs into software development.

      The FPGA manufactures have done quite well on the low volume, high margin game. They have no incentive to drop the cost required for consumer volumes. GPUs are a completely different story....

      Yummm... $15 part....Zynq 7015. Is that what everyone is talking about? Need more space, try Zynq 7100. If you are not that motivated to get performance, compile system C code:

      http://www.xilinx.com/products/silicon-devices/soc/zynq-7000/

    7. Re: Blind ants, now need to search more branches by viperidaenz · · Score: 1

      The Zynq 7100 is 4 grand at digikey.

    8. Re: Blind ants, now need to search more branches by ka9dgx · · Score: 2

      All of this points out what I'm saying... they've optimized for small(ish) systems that have to run very quickly, with a heavy emphasis on "routing fabric" internally. This makes them hard to program, as they are heterogeneous as all get out.

      Imagine a grid of logic cells, a nice big, homogenous grid, that was symmetric. You could route programs in it almost instantly, there's be no need for custom tools to program it.

      The problem IS the routing grid... it's a premature optimization. And for big scale stuff it definitely gets in the way.

      I would have a 4 bits in, 4 bits out lookup table as the basis of this, and I call it the "bitgrid".... I've been writing about it for years, feel free to make the chip, and send me an email (or preferably a sample, please)., because that puppy is disclosed as far as patents go.... I have none, and can't now.

      You should be able to get a 64k x 64k grid on a chip for a few bucks, in any kind of quantity. It should do Exaflops, or consume almost nothing if you idle it.

    9. Re: Blind ants, now need to search more branches by TheRaven64 · · Score: 4, Informative
      Speaking as someone who works with FPGAs on a daily basis and has previously done GPGPU compiler work, that's complete nonsense. If you have an algorithm that:
      • Mostly uses floating point arithmetic
      • Is embarrassingly parallel
      • Has simple memory access patterns
      • Has non-branching flow control

      Then a GPU will typically beat an FPGA solution. There's a pretty large problem space for which GPUs suck. If you have memory access that is predictable but doesn't fit the stride models that a GPU is designed for then an FPGA with a well-designed memory interface and a tenth of the arithmetic performance of the GPU will easily run faster. If you have something where you have a long sequence of operations that map well to a dataflow processor, then an FPGA-based implementation can also be faster, especially if you have a lot of branching.

      Neither is a panacea, but saying a GPU is always faster and cheaper than an FPGA makes as much sense as saying that a GPU is always faster and cheaper than a general-purpose CPU.

      --
      I am TheRaven on Soylent News
    10. Re: Blind ants, now need to search more branches by Anonymous Coward · · Score: 1

      Gentlemen what we have to realise is that there is no such thing as a "general-purpose computation~" any more. Moore's Law (speed variant) only kidded us into thinking there was.

    11. Re: Blind ants, now need to search more branches by TheRaven64 · · Score: 1

      This is the much more important point. And the dark silicon problem emphasises it: the number of transistors you can fit on a chip is still increasing, but the number you can have powered at any given time is increasing a lot more slowly. Special-purpose silicon optimised for different categories of algorithm is likely the way forward.

      --
      I am TheRaven on Soylent News
    12. Re: Blind ants, now need to search more branches by InvalidError · · Score: 1

      Only if your problem is important enough to justify the extra development time and cost.

      For very common or urgent problems, there is enough motivation to go all the way to full-custom ASIC which is several times faster and also much cheaper to mass-produce than FPGA. For one-off problems, there may not even be enough budget and development time to accommodate an FPGA-based prototype.

      The problem space where FPGAs are an economically viable option is wildly circumstantial.

    13. Re: Blind ants, now need to search more branches by ka9dgx · · Score: 0

      My solution to the dark transistor problem came to me back around 1982... I call it the BitGrid. It's a Cartesian grid of 4 bit input, 4 bit output look up tables. each cell can replicate any logic function, and those tables are the basis of modern FPGAs. The thing that makes the BitGrid different is the total lack of routing fabric. This makes the grid homogeneous and symmetric. As long as you know of a defect in a cell, you can route around it trivially, at load time. You can shift any given logic configuration left, right, up, down, without having to do any work. You can rotate and mirror it.

      The down side is that you have to pass through every cell to get from one side to the other... which could be a waste of logic, or a tremendous opportunity to do computing in parallel.

      Imagine a big enough grid (lets say 64k * 64k), implemented in CMOS. You could take a program, unwrap all the instructions into their logical equivalents, and then mape all that out into the grid. This would let you run the entire program all at the same time.

      Exaflops... here we come.

    14. Re:Blind ants, now need to search more branches by antdude · · Score: 1

      Only three/3 blind ants like mice. ;)

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
    15. Re: Blind ants, now need to search more branches by Anonymous Coward · · Score: 0

      As long as defense contractors are buying $20k (hardened) FPGAs, sticking them on missiles that fly for 30 seconds and blow themselves up, leaving you the taxpayer to foot the bill, I can't see any incentive for FPGA vendors to drop their price and margin.

      Things might change if a new Commodore/MOS technologies came along and ruthlessly sold FPGAs for close to what they cost to manufacture. This has been my hope for some time, but imagine trying to go to a VC and say you want to develop a whole new FPGA architecture (at latest 22nm process), with open source toolchain, and nearly give them away, selling them way below market prices.

      FPGAs are not complex devices, they are largely repeating structures, more complex than DRAM or SRAM cells but far simpler and less expensive to design than CPUs. The toolchains for them are far more expensive to design, and without an effective toolchain they are useless (and all commercial FPGA toolchains are useless for general purpose computing).

    16. Re: Blind ants, now need to search more branches by Anonymous Coward · · Score: 0

      So instead of most of your device being consumed by routing muxes and metal layers, most of your device will be consumed during use by LEs being repurposed for routing instead of logic.

      You end up with the same or worse unusable area, but since you don't have long travel nets, you have much worse propagation delays between the LEs that *are* being usefully utilised, so your timing closure will be worse.

      I don't see how this buys any goodness.

    17. Re: Blind ants, now need to search more branches by ka9dgx · · Score: 1

      Fair enough... the propagation delays would suck, yes... but we're talking about general purpose computing here, not picosecond timing. The main goal is throughput, and if you can get most of the transistors in the thing doing computation, instead of waiting for the 100 picoseconds they are actually needed, you've solved the "dark transistor" problem.

      The gain is from being able to process all parts of a given problem in parallel, so you get at least 1 result per clock.... imagine being able to do 1024 bin FFTs at 1 Ghz, or faster.

      You have to route signal, but at least in the bitgrid, that's flexible, and not he huge constraint on things that existing FPGAs force you to work around. You should be able to get 90% usage... I'm writing a simulator to try to figure that out, in Delphi for Windows, it's on GitHub.

  4. Ends of Moore's Law in software ? by Taco+Cowboy · · Score: 5, Insightful

    The really sad thing regarding this "Moore's Law" thing is that, while the hardware had kept on getting faster and even more power efficient, the software that runs on them kept on becoming more and more bloated.

    Back in the days of pre-8088 we already had music notation softwares running on Radio Shack TRS-80 model III.

    Back then, due to the constraints of the hardware, programmers had to use every trick on the book (and off) to make their programs run.

    Nowadays, even the most basic "Hello World" program comes up in megabyte range.

    Sigh !

    --
    Muchas Gracias, Señor Edward Snowden !
    1. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      Thank you Unicode!

    2. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      Spending 10x the man hours for a 10% performance gain, only to have to refactor the code shortly after, is not beneficial. If slow code causes more servers to be purchased, they will start to balance the cost of servers compared to man hours optimizing. I wouldn't mind a job doing optimizations, I already do that to a slight degree.

    3. Re:Ends of Moore's Law in software ? by lister+king+of+smeg · · Score: 4, Insightful

      Would you rather that your CPU and memory were always underutilized by software, going to waste?

      yes more efficient and fast code would be much better

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    4. Re:Ends of Moore's Law in software ? by bloodhawk · · Score: 4, Insightful

      I don't find that a sad thing at all. The fact people have to spend far less effort on code to make something that works is a fantastic thing that has opened up programming to millions of people that would never have been able to cope with the complex tricks we used to play to get every byte of memory saved and to prune every line of code. This doesn't mean you can't do those things and I still regularly do when writing server side code. But why spend man years of effort to optimise memory,CPU and disk footprint when the average machine has abundant surplus of both.

    5. Re:Ends of Moore's Law in software ? by MightyMartian · · Score: 3, Insightful

      Pointless cycles because of poor code and compiler optimizations is hardly what I would call "utilization".

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    6. Re:Ends of Moore's Law in software ? by HiThere · · Score: 1

      If you use utf8, then unicode is as efficient as ascii...for everything you can do with ascii. Nobody should be required to use utf32 except when it's the most convenient choice. (And there's never a good argument for using utf16, unless you're on a computer with 16 bit words.)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    7. Re: Ends of Moore's Law in software ? by jarfil · · Score: 2

      The sad part is not that it's easier to code, but that many people have grown complacent with their code executing at abysmal performance rates. And I also blame compilers/interpreters that don't mind bloating things up.

    8. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      Why is that not sad? Many programmers don't even do the bare minimum to make their code decent. The situation is truly appalling.

    9. Re:Ends of Moore's Law in software ? by jones_supa · · Score: 3, Interesting

      Would you rather that your CPU and memory were always underutilized by software, going to waste?

      Of course, because then we would either save in power consumption or alternatively do more interesting stuff with the extra free resources that we get.

    10. Re:Ends of Moore's Law in software ? by phantomfive · · Score: 1

      Back in the days of pre-8088 we already had music notation softwares running on Radio Shack TRS-80 model III.

      In 4-bit color on a 640x480 screen, with ugly fonts (if you could even get more than one!) and lousy, cheap sounding midi playback. Seriously, TRS-80 music notation software was severely limited compared to what we have today.

      --
      "First they came for the slanderers and i said nothing."
    11. Re: Ends of Moore's Law in software ? by jarfil · · Score: 1

      Yes, reducing energy consumption, heat dissipation, hardware lifetime, and being able to swiftly react to sudden spikes of activity, would be excellent.

    12. Re:Ends of Moore's Law in software ? by Guy+Harris · · Score: 2

      Nowadays, even the most basic "Hello World" program comes up in megabyte range.

      The most basic "Hello World" program doesn't have a GUI (if it has a GUI, you can make it more basic by just printing with printf), so let's see:

      $ ed hello.c
      hello.c: No such file or directory
      a
      #include <stdio.h>

      int
      main(void)
      {
      printf("Hello, world!\n");
      }
      .
      w
      67
      q
      $ gcc -o hello -Os hello.c
      $ size hello
      __TEXT __DATA __OBJC others dec hex
      4096 4096 0 4294971392 4294979584 100003000

      I'm not sure what "others" is, but I suspect there's a bug there (I'll take a look). 4K text, 4K data (that's the page size), which isn't too bad; the bulk of the work is done in a library, though - it's a shared library, and this OS doesn't support linking statically with libSystem, so it's hard to tell how much code is dragged in by printf. The actual file size isn't that big:

      $ ls -l hello
      -rwxr-xr-x 1 gharris wheel 8752 Jan 7 21:58 hello

    13. Re: Ends of Moore's Law in software ? by jarfil · · Score: 4, Insightful

      How about spending 20x the man hours for a 10,000% performance gain? That is what I've recently experienced myself, in the reverse: an embedded device interface getting rewritten to require 20x less man hours to mantain... at a 100x performance hit. Suffice to say it went from quite snappy, to completely useless, but it seems like it's my fault for not upgrading the hardware.

    14. Re:Ends of Moore's Law in software ? by aztracker1 · · Score: 1

      Most software is one-off software written as utilities and services in corporate environments.. where working is more important. Much of the time from a business perspective, hardware isn't shared in practice.. that little HR app that only a half dozen people use gets its' own server (no proper backup/redundancy mind you, but it's own box).. it's going to be under-utilized regardless of how well the code is written.

      Where it becomes more important is in very large scale systems.. supporting a few dozen, or even a few hundred users at a time is pretty easy to do with even modest hardware today. Servicing a million+ simultaneous users, that takes some effort, and even a lot of that is getting easier to do.. just look at node.js and golang for example... or the increased interest in erlang, F# and other functional languages. It's going to be a very slow shift, but honestly, the types of and extend of optimizing programs for large scale is about as rare as the people who are needed for writing enhanced drivers. Around the time we hit 1ghz computers, the cost of more computers or faster computers became less than development time.. If you have a development team that costs the company around $150-200k/year (salary + bonus + benefits), would you rather a team of four devs spending 3-6 months optimizing, or buy a few servers for less than half the cost?

      --
      Michael J. Ryan - tracker1.info
    15. Re:Ends of Moore's Law in software ? by K.+S.+Kyosuke · · Score: 2

      Where it becomes more important is in very large scale systems.. supporting a few dozen, or even a few hundred users at a time is pretty easy to do with even modest hardware today.

      Yeah, you say "support users", but supporting users *well* can be more than enough computationally expensive to warrant diligent programing. Think automated knowledge systems, for example.

      --
      Ezekiel 23:20
    16. Re:Ends of Moore's Law in software ? by jones_supa · · Score: 1

      How do you know how much memory to allocate for a chunk of text if the character width varies?

    17. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      Would you rather that your CPU and memory were always underutilized by software, going to waste?

      yes more efficient and fast code would be much better

      Then you should be using a 20 years old computer, with its lean software and scarce resources. Why buy more powerful hardware if you have no use for its inward capabilities? The rest of us will keep using hardware that allow possibilities that were unheard a few years ago.

    18. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      Back in the days of pre-8088 we already had music notation softwares running on Radio Shack TRS-80 model III.

      In 4-bit color on a 640x480 screen, with ugly fonts (if you could even get more than one!) and lousy, cheap sounding midi playback. Seriously, TRS-80 music notation software was severely limited compared to what we have today.

      Model III, youngster. Monochrome with 128x48 graphics and maybe an internal thing that went "beep".

    19. Re: Ends of Moore's Law in software ? by aztracker1 · · Score: 1

      What I mean is that using abstractions where they make sense is not always the most performance code, but can be far more easily understood. Breaking apart larger methods into smaller ones and exercising modularity are not better performing, but are better for ensuring desired results and reducing the chances of side effects and bugs. The most optimized code is not the same as the best code for a given system.

      --
      Michael J. Ryan - tracker1.info
    20. Re:Ends of Moore's Law in software ? by JanneM · · Score: 1

      What do you suggest we do with all the computing power we've gained then? It seems perfectly reasonable to use it to make software development easier and faster, and make more beautiful and more usable user interfaces.

      --
      Trust the Computer. The Computer is your friend.
    21. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      How do you know how much memory to allocate for a chunk of text if the character width varies?

      The same way as you would with ASCII, measuring the length of the text before allocating memory. Unless you have a crystal ball, there's no other way.

    22. Re: Ends of Moore's Law in software ? by clickclickdrone · · Score: 1

      Agreed. Seems amazing now that you could get spreadsheets and word processors running in 8 to 48k. The only time in recent years I've seen amazing efficiency was a graphics demo that drew a fully rendered scene using algorithmically generated textures. Demo ran for about 5 minutes scrolling about the buildings and hills and was only about 150k

      --
      I want a list of atrocities done in your name - Recoil
    23. Re:Ends of Moore's Law in software ? by petermgreen · · Score: 1

      If you use utf8, then unicode is as efficient as ascii.

      For storage.

      But when you actually come to display stuff rendering engines that can handle massive character sets, variable byte count encodings of code points, converting mixed directionality text from logical order to physical order, combining elements in various ways to apply arbitary diacritics to a character and so-on doesn't come free. Having those things in your text rendering engine comes at a price even if you don't actually use them.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    24. Re:Ends of Moore's Law in software ? by Greyfox · · Score: 2
      I did a static-compiled hello world program a while back and found that it was only a few kilobytes, which is still a lot but way less than I expected. A C function I wrote to test an assembly language function I also wrote recently came it at about 7000 bytes. That's better...

      There have been several occasions where I've seen a team "solve" a problem by throwing another couple gigabytes at a Java VM and add a task to reboot the system every couple of days. I've lost count of the times where simply optimizing SQL I was looking at (Sometimes by rewriting it, sometimes by adding an index) has resulted in hour-long tasks suddenly completing in a minute or two. There's plenty of room to get more performance out of existing hardware, that's for sure!

      --

      I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

    25. Re:Ends of Moore's Law in software ? by smash · · Score: 1

      Most software is one-off software written as utilities and services in corporate environments.. where working is more important.

      ... which eventually becomes entrenched, undocumented, the original author leaves and it gets scaled to far beyond its original intent.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    26. Re:Ends of Moore's Law in software ? by ppanon · · Score: 1

      that little HR app that only a half dozen people use gets its' own server (no proper backup/redundancy mind you, but it's own box).

      Apparently you've been under a rock for the last 5 years and completely missed the move to virtualization. Can you guess what the main business driver is? More efficient use of computing resources, power, and data centre infrstructure resulting from consolidation.

      --
      Laissez lire, et laissez danser; ces deux amusements ne feront jamais de mal au monde. - Voltaire
    27. Re:Ends of Moore's Law in software ? by purpledinoz · · Score: 2

      It's cheaper to buy more computers than hire more programmers.

    28. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      Would you rather that your CPU and memory were always underutilized by software, going to waste?

      yes more efficient and fast code would be much better

      and you could use the extra remaining CPU power to help find a cure for cancer, hiv/aids, arthritis, etc.

    29. Re:Ends of Moore's Law in software ? by lister+king+of+smeg · · Score: 4, Insightful

      Would you rather that your CPU and memory were always underutilized by software, going to waste?

      yes more efficient and fast code would be much better

      Then you should be using a 20 years old computer, with its lean software and scarce resources. Why buy more powerful hardware if you have no use for its inward capabilities? The rest of us will keep using hardware that allow possibilities that were unheard a few years ago.

      To quote an old adage What Moore's law giveth Gates Taketh away

      I would prefer to use lean software on powerful hardware so as to actually gain the advantages of said hardware rather than bad code and bloat roll back the advantages new hardware has given.

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    30. Re:Ends of Moore's Law in software ? by mwvdlee · · Score: 1

      The text contains 100 characters.
      How much memory should I allocate for UTF8, without wasting memory?

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    31. Re:Ends of Moore's Law in software ? by lister+king+of+smeg · · Score: 2

      lets look at that, will more computers make a mcaffy or norten security suits run appreciably faster? No because they are badly written programs that are resource hogs the eat processing power and can pull a workstation to a crawl. A faster more effencent and less resource hogging code would be better in this case then throwing hardawre at it. For many problems throwing hardware at a problem is just like throw money at a problem you are ignoring the root issue and will eventually run out of resources to throw.

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    32. Re:Ends of Moore's Law in software ? by viperidaenz · · Score: 1

      Where did the text come from? You had to read it from somewhere, so you know what it contains already.

    33. Re:Ends of Moore's Law in software ? by gnasher719 · · Score: 1

      The text contains 100 characters.
      How much memory should I allocate for UTF8, without wasting memory?

      Beginner's question. The text contains 100 bytes, how much memory should you allocate? You rarely care how many characters there are.

    34. Re:Ends of Moore's Law in software ? by freeze128 · · Score: 5, Funny

      yes more efficient and fast code would be much better

      I like this guy. He doesn't stop for punctuation.

    35. Re:Ends of Moore's Law in software ? by lister+king+of+smeg · · Score: 1

      No I would use it to do whatever I am trying to do more quickly. Have you ever have to wait for a program to compile, a video to transcode, a archive compress, or something as simple as wait for a document to render. For example there was a bug a while back in open/libre office that caused .rtf documents to take a long time to render. Worst part was the time to render grew exponentially with the length of the document, my first encounter with it was when I opened a ebook saved that format it took over ten minutes to render! it did not matter how powerful the hardware was it was rendering it still took to long because the code was bad and no increase in hardware would fix that. Would I have donated that cpu time to charity as you suggest? No but it was still a problem because it wasted not my computers time but because it wasted my time which is infinitely more valuable.

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    36. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      choose your battles. i always optimize the inner core / inner loops of things. what doesn't happen often doesn't get optimized much.

    37. Re:Ends of Moore's Law in software ? by u38cg · · Score: 1

      Have you seen GNU's hello.c? Worth a look.

      --
      [FUCK BETA]
    38. Re:Ends of Moore's Law in software ? by MrL0G1C · · Score: 1

      1. Is hello world easier to code now? When I had an a bit the program was

      (type)
      print "Hello world" (hit enter)

      That didn't seem hard, now - what steps to you have to go through on a modern PC you've just bought. Not as easy is it.

      2. Agree with other poster, why are compilers throwing 99.999% of redundant code in to the software? Pathetic.

      --
      Waterfox - a Firefox fork with legacy extension support, security updates and better privacy by default.
    39. Re:Ends of Moore's Law in software ? by Sique · · Score: 1

      But there still goes the old saying (as in the Perl documentation): A program is correct if it solves the problem before the boss fires you. You always have to compare the man-hours it saves with the man-hours necessary to reimplement it on a clean base. And in many cases, the reimplementation will eat much more highly paid man-hours than the reimplemented program will ever save compared to the kludge version where one knows all the quirks already.

      --
      .sig: Sique *sigh*
    40. Re:Ends of Moore's Law in software ? by TheRaven64 · · Score: 1

      On OS X, printf is pretty huge. It is locale aware and so will call localeconv() to find out various things like currency separators. This, in turn, may load character set definitions and so on. For your example, you should use puts(), which will just write the string as-is, without trying to parse it and insert tokens.

      --
      I am TheRaven on Soylent News
    41. Re:Ends of Moore's Law in software ? by evilviper · · Score: 2

      There's plenty of room to get more performance out of existing hardware, that's for sure!

      But that's exactly the point... For decades, Moore's Law has made it seem like a crime to optimize software. No matter how inefficient the software, hardware was cheaper than developer time, and the next generation of hardware would be fast enough to run the bloated, inefficient crap.

      The end of Moore's Law... if it actually happens this time, unlike the last 1,000 times it was predicted... will mean good people who can write more efficient code will be worth far more, and the code monkeys who got by only thanks to a culture that was utterly unconcerned with performance/optimization, will be seen as the hacks they are...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    42. Re:Ends of Moore's Law in software ? by TheRaven64 · · Score: 4, Insightful

      You can still write software that efficient today. The down side is that you can only write software that efficient if you're willing to have it be about that complex too. Do you want your notes application to just store data directly on a single disk from a single manufacturer, or would you rather have an OS that abstracts the details of the device and provides a filesystem? Do you want the notes software to just dump the contents of memory, or do you want it to store things in a file format that is amenable to other programs reading it? Do you want it to just handle plain text for lyricst, or would you like it to handle formatting? What about unicode? Do you want it to be able to render the text in a nice clean antialiased way with proportional spacing, or are you happy with fixed-width bitmap fonts (which may or may not look terrible, depending on your display resolution)? The same applies to the notes themselves. Do you want it to be able to produce PostScript for high-quality printing, or are you happy for it to just dump the low-quality screen version as a bitmap? Do you want it to do wavetable-based MIDI synthesis or are you happy with just beeps?

      The reason modern software is bigger is that it does a hell of a lot more. If you spent as much effort on every line of code in a program with all of the features that modern users expect as you did in something where you could put the printouts of the entire codebase on your office wall, you'd never be finished and you'd never find customers willing to pay the amount it would cost.

      --
      I am TheRaven on Soylent News
    43. Re:Ends of Moore's Law in software ? by dacut · · Score: 2

      This guy managed to get it into 145 bytes (142 on his website, but he printed "Hi World" instead of "Hello world") with no external dependencies.

      The smallest ELF executable I've seen is this 45 byte example. It doesn't print anything and it violates the ELF standard, but Linux (or at least his version) is still willing to execute it.

      That said, there isn't much point in optimizing away libc except as an academic exercise. Yes, it's a few megabytes in size, but it's shared across every running userspace program (likely including init). Sluggish and bloated programs, in my experience, are almost always the result of poorly thought out algorithms, data structures, and use cases. (That said, the analysis on how to achieve the 45 byte ELF program is very interesting and educational.)

    44. Re:Ends of Moore's Law in software ? by Guy+Harris · · Score: 1

      On OS X, printf is pretty huge. It is locale aware and so will call localeconv() to find out various things like currency separators.

      printf appears to be locale-aware on, for example, FreeBSD as well; I don't think that's particularly OS X-specific.

    45. Re:Ends of Moore's Law in software ? by geekmux · · Score: 1

      Would you rather that your CPU and memory were always underutilized by software, going to waste?

      You're going to try and make that argument as we discuss how technology can't keep up with demand?

      In the future there will be no underutilized systems. If we don't find a massive breakthrough via other technologies, then it only makes sense to bring parallel computing to a massive scale with distributed computing. Idle time will be an object of the past.

    46. Re:Ends of Moore's Law in software ? by geekmux · · Score: 1

      Pointless cycles because of poor code and compiler optimizations is hardly what I would call "utilization".

      If you're the one selling new hardware, I'd say you've maximized the "utilization" of your manufacturing line by promoting poor code (read: Windows).

      Greed allows you to look at things in funny ways.

    47. Re:Ends of Moore's Law in software ? by SuricouRaven · · Score: 1

      A good part of the reason modern video compression is so much better than it used to be is the hardware - algorithms in common use crawl along at a frame every second, but that would have been a frame every minute on old hardware: Half an hour to encode one second of video is not going to be worthwhile.

    48. Re:Ends of Moore's Law in software ? by SuricouRaven · · Score: 1

      It came from a TCP connection where users submit comments. Most of them are only a few hundred characters, but occasionally someone will submit an in-depth analysis the size of a book.

    49. Re:Ends of Moore's Law in software ? by SuricouRaven · · Score: 1

      The tidier solution would be to teach the entire world english, or at least a modified form of their old language that can be properly represented with the latin alphabet alone. Throw in upper-ascii for a few accents.

    50. Re:Ends of Moore's Law in software ? by SuricouRaven · · Score: 1

      I wrote that in c#. It took about five lines of code.

      And twenty megabytes of RAM to execute. Mostly, I assume, used to hold the .net libraries and garbage collector.

    51. Re:Ends of Moore's Law in software ? by SuricouRaven · · Score: 1

      I would agree with you, if I hadn't just wasted ten minutes standing around waiting for Windows to boot up and get to the login prompt on a computer I was supposed to be fixing. It did get there, eventually.

    52. Re:Ends of Moore's Law in software ? by TheRaven64 · · Score: 1

      Indeed (I wrote a chunk of the FreeBSD locale code), but the grandparent specifically talked about OS X. My comment holds for almost any platform, outside of embedded systems or Solaris (where you can easily turn off locale support with a #define).

      --
      I am TheRaven on Soylent News
    53. Re: Ends of Moore's Law in software ? by K.+S.+Kyosuke · · Score: 1

      There's seldom an actual clash between abstractions and performance. In fact, abstractions and performance go often hand in hand in the world of today's quality compilers. The more abstractions the environment allows you to express, the more invariants the code has. The more invariants the code has, the more aggressive optimizations can be performed. (Inter-procedural deforestation, for example. That's something you'll never do by hand without getting insane in the process.)

      --
      Ezekiel 23:20
    54. Re:Ends of Moore's Law in software ? by Waffle+Iron · · Score: 1

      The text contains 100 characters.
      How much memory should I allocate for UTF8, without wasting memory?

      If you try to allocate 100 characters, you're probably wasting something like 28 bytes on the heap without even knowing it. You could be wasting even more if your usage pattern fragments the heap.

      In the real world, you just use a vector, waste about 33% of the space on average (not a huge deal), and move on. Moreover, you probably end up with fewer buffer overflow bugs by not doing hand-crafted buffer allocation.

    55. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      1. Is hello world easier to code now? When I had an a bit the program was

      (type)
      print "Hello world" (hit enter)

      That didn't seem hard, now - what steps to you have to go through on a modern PC you've just bought. Not as easy is it.

      2. Agree with other poster, why are compilers throwing 99.999% of redundant code in to the software? Pathetic.

      Now you have to find and open the terminal first because only grognards and students who don't know better yet use the command line when they can avoid it, but otherwise the steps are the same.

      Now if you mean write Hello World in an IDE that was designed for writing and maintaining enterprise level software projects than yes, it will by default involve things like creating a class file, defining a namespace, possibly creating a source repository, or stubbing out unit tests, etc. Much like using an engineering CAD toolset to draw stick figures, or a recording studio to make fart noises involves a lot of underutilized tools.

    56. Re:Ends of Moore's Law in software ? by Kielistic · · Score: 1

      That's pretty much irrelevant. But yes an appreciably faster computer will still run appreciably faster.

      Throwing money at making software "more efficient" can definitely be a waste. Software becomes outdated fairly quickly whereas hardware is always getting faster. The process of improving hardware is global, constant and iterative. Software very often needs complete rewrites to stay current. Spending a few million dollars to make $slow_antivirus_strawman "more efficient" is a terrible waste of money over buying better hardware because it's already there.

    57. Re:Ends of Moore's Law in software ? by Kielistic · · Score: 1

      Judging programming languages, environments and compilers on how easy it is to make a useless program is one of the worst metrics I've ever seen.

      Want to print letters to a screen? Use a text document.

    58. Re:Ends of Moore's Law in software ? by geekoid · · Score: 1

      It depends on the language. If you want to write a simple and small hello world program, you don't use a program tool design for full featured large application.

      You sound like an old whiners who has stopped applying critical thought to a problem. You son't need .net to solve the problem you propose and no one has taken away other tools. For example:

      section .text
      global _start
      _start:

              mov edx,len
              mov ecx,msg
              mov ebx,1
              mov eax,4
              int 0x80

              mov eax,1
              int 0x80

      section .data
      msg db 'Hello, world!',0xa
      len equ $ - msg

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    59. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      It is cheaper to hire 3rd world programmers than buying new computers.

    60. Re:Ends of Moore's Law in software ? by celle · · Score: 1

      " Do you want your notes application to just store data directly on a single disk from a single manufacturer, or would you rather have an OS that abstracts the details of the device and provides a filesystem? "

            How about manufacturers making their shit to a standard instead tweaking to differentiate their bits from the rest. The fact is we are virtualizing everything to death for no reason than we can. Stop that. We do a lot of the same shit we did twenty years ago with 1000x more complex software. Back then, we ran a program on the real bare metal and now it's on a virtual machine that's running on a virtual machine and so on eventually getting to bare metal. Everybody is creating their own standard reinventing the wheel adding to the library of useless standards to be referenced so that now we have software layers piled to the moon running on multi-GHz multi-cores possibly in the cloud to get the functionality a dedicated C program got on a 25 MHz 80386, 8 MHz Mac or an Amiga got in 1988. I agree that programmers have gotten lazy and sloppy as many only know frameworks and nothing else. Not that the frameworks are bad but much of what they encouraged has been somewhat good and the rest just plain awful.

            If you've noticed there's very few manufacturers of really differing hardware anymore, so why hasn't the software centralized and become simpler as the old esoteric hardware goes away? Because we keep virtualizing up. Web browsers are bigger than some operating systems now. Uhh! We've abstracted away hardware complexity to ever increasing software complexity that requires ever more hardware complexity just to use at all. And what have we really ended up with again? Ahhh!!! /psycho rant I hope

    61. Re:Ends of Moore's Law in software ? by HiThere · · Score: 1

      If you know you can handle it in ASCII, then you can handle utf8 just like the ASCII. If you don't know you can handle it in ASCII, then you can handle it in utf8 more easily.

      I will agree than handling utf8 in C++ is difficult, which is a part of why I said that it was poorly implemented. And nobody EVER displays enough text for the difference between speed of utf8 and ascii display to make any difference. I don't think it's possible, due to lags in non-computational parts of the system. I will agree that for some embedded systems the difference in the amount of memory required by the code can be significant. The number of cases where that is significant, however, is so small that it's irrelevant, and should be handled in some other way. (There are already dialects that strip out some parts of the language, so it's not an insuperable problem.)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    62. Re: Ends of Moore's Law in software ? by bloodhawk · · Score: 1

      performance vs time to create is a trade off that depends significantly on the task at hand and the end requirements. Sometimes it really is cheaper to buy faster hardware than spend more time optimising. We did exactly that over xmas for a web farm with some poorly written transactional code. The code worked 100% perfectly but was inefficient. It was calculated out that tuning and testing the code would take approximately $250,000 in programmer and testing time. Hardware to compensate for the bad code came to $50,000 plus maintanence and freed up the programmers to work on more critical tasks.

    63. Re:Ends of Moore's Law in software ? by viperidaenz · · Score: 1

      And that TCP stream has specified its own character encoding anyway - because you're obviously talking about HTTP, so you don't know how many ASCII characters it contains either, unless that's the encoding its using.

      There many not even be a Content-Length header either, so you don't even know how many bytes you can read before the request ends.

    64. Re:Ends of Moore's Law in software ? by SuricouRaven · · Score: 1

      I wasn't talking about HTTP specifically.

      If you want to see character encoding mess in communications, you want to look at IRC.

      - No character encoding specified, because it predates the introduction of such things.
      - No pre-definition of message length: The line continues until a CRLF appears.
      - No limits in the specification of maximum message length: It's up to the server operator when to truncate.
      - Different clients may use different character sets. One may use ASCII, another one of the obscure pre-unicode codepages, another unicode in UTF-8.
      - Additional control characters may be included to specify text color or font. These are defined not in any specification but by an informal consensus, an agreement that whatever mIRC does the others should probably copy.

      Only communications I've seen less character-set-friendly are mucks, and that's because the 'protocol' was originally designed to be accessed via telnet client. Incidentally, you can telnet IRC with a little practice and some fast typing.

    65. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      I guess I'm just boss, because I can do anything you can do in Perl just as quickly in C, and get a fast executable out of it.

    66. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      You should use puts or better: write, but modern versions of GCC will automatically replace printf("literal without directives terminated by\n"); with puts("literal without directives terminated by"); automatically with -O.

      Also 8k is fucking huge. I wrote a hello world for Linux in 118 bytes using FASM. And that's not even the smallest Hello World. It's also noticably faster than one written in C, particularly a dynamically linked one.

    67. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      That said, there isn't much point in optimizing away libc except as an academic exercise.

      Actually there is. Using dynamic linking adds many pages of memory usage to your program (it takes additional pages in both user and kernel memory to handle dynamic linkages, and each library requires at a bare minimum three pages: text, rss and rodata), and statically linking against libc uses even more. For the average program, the used parts of libc consume less than a page of memory when properly optimised, which is much less than the memory consumed per-process by dynamic linking. The operating system as a whole could be much faster and consume much less memory if dynamic linking was removed entirely.

      For dynamic libraries to be shared between applications, they must use indirect addressing, they can't remove unused functions, and each page consumes a TLB line, misses in which are one of the biggest slowdowns in modern code. For the most part, copying all used functions into a programs own text segment consumes less memory and more importantly TLB lines, than dynamic linking.

      Sun did a study when they first implemented dynamic linking in SunOS (to support X11 bloat), and they found that it both made the OS slower, consume more memory and larger, but they kept it anyway, because customers wanted it.

    68. Re:Ends of Moore's Law in software ? by Guy+Harris · · Score: 1

      Also 8k is fucking huge.

      That's what happens when you have demand-paged shared-text executables; the section sizes are padded up to the page size, even if there isn't that much code in them, and the text and data might be put on separate pages (without copy-on-write, you'd make the text never be writable and the data writable, on separate pages; with copy-on-write, you could let one page contain both text and data, and have it copy on write if you store into the data, but that's probably not worth bothering with).

    69. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      so you evaluate development tools and languages based on a meaningless "hello world" example. geez it must suck to work on large scale projects where you work being stuck with nothing more than a command prompt to develop with.

    70. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      Nope.

      You are correct that they are padded when they are loaded in memory. but on disk (at least with ELF) the size of segments is specified in bytes, not pages. OTOH GCC and Gnu LD fill ELF files with lots of 0byte tables. I have disassembled GCC+glibc Hello world, and mostly what it consists of is big link tables to functions which are not used, or are used by the code that sets up argc and argv, environ, communicates with nss, initialises the heap, and a bunch of other stuff Hello World does not use, but is mandatory when compiling with glibc.

      The entry point of an elf executable is not main(), it is a function called _start() which is provided by gcc or glibc (I can't recall), which makes a bunch of syscalls to setup things required by the C and POSIX standards which the kernel doesn't do (basically the kernel zeros registers, initialises the stack and jumps to the entry point) and then calls main(), and when main() returns it calls exit() with the return value of main, which in turn calls each entry added to the exit table by atexit() calls, and then calls _exit(), which makes the syscall SYS_EXIT.

    71. Re:Ends of Moore's Law in software ? by viperidaenz · · Score: 1

      If that's the case it's even easier since you've had to read every byte from the stream anyway to find the CRLF combination, so what's the pain in converting the stream to UFT8? You know what all the characters are and how many bytes are required to encode them so you know how much storage to allocate.

      The text contains 100 characters.
      How much memory should I allocate for UTF8, without wasting memory?

      So the answer is you started counting the bytes as you were reading the buffer from the TCP stack.
      That's the same processing required for plain ASCII, except there's a little "if bit 7 is set, call UTF8 encoding function to determine extra bytes".

    72. Re:Ends of Moore's Law in software ? by Guy+Harris · · Score: 1

      Nope.

      You are correct that they are padded when they are loaded in memory. but on disk (at least with ELF)

      You are making an incorrect assumption here. (Hint: I said "libSystem", not "libc".)

      the size of segments is specified in bytes, not pages.

      OK, let's look in a little more detail:

      $ size -m hello
      Segment __PAGEZERO: 4294967296
      Segment __TEXT: 4096
      Section __text: 77
      Section __stubs: 12
      Section __stub_helper: 36
      Section __cstring: 14
      Section __unwind_info: 80
      Section __eh_frame: 72
      total 291
      Segment __DATA: 4096
      Section __program_vars: 40
      Section __nl_symbol_ptr: 16
      Section __la_symbol_ptr: 16
      Section __common: 32
      total 104
      Segment __LINKEDIT: 4096
      total 4294979584

      The Mach-O specification says:

      For best performance, segments should be aligned on virtual memory page boundaries—4096 bytes for PowerPC and x86 processors. To calculate the size of a segment, add up the size of each section, then round up the sum to the next virtual memory page boundary (4096 bytes, or 4 kilobytes). Using this algorithm, the minimum size of a segment is 4 kilobytes, and thereafter it is sized at 4 kilobyte increments.

      And that's not necessarily space in the file:

      Segments that require more memory at runtime than they do at build time can specify a larger in-memory size than they actually have on disk. For example, the __PAGEZERO segment generated by the linker for PowerPC executable files has a virtual memory size of one page but an on-disk size of 0. Because __PAGEZERO contains no data, there is no need for it to occupy any space in the executable file.

      although if a segment is being paged in from the file, it'll be padded on disk so that you don't get extra cruft from the following segment when you fault in the last page of the segment.

      It's been ages since I dealt with ELF (back in 1988), but I suspect that the same is done there. This version of the ELF specification seems to suggest that it is.

      I.e., they may be specified in units of bytes, but they might also be padded to a number of bytes that's a multiple of the page size.

      The entry point of an elf executable is not main(), it is a function called _start()

      That dates back well before ELF, all the way to PDP-11 UNIX's a.out format.

      which is provided by gcc or glibc (I can't recall)

      On Solaris with Sun C^W^WOracle Studio, it's provided neither by GCC nor by glibc; on *BSD, it's definitely not provided by glibc, and if clang is used, it's obviously not provided by GCC.

    73. Re:Ends of Moore's Law in software ? by SuricouRaven · · Score: 1

      If bit 7 is set... is that character unicode, or an old upper-ascii accent?

    74. Re:Ends of Moore's Law in software ? by Anonymous Coward · · Score: 0

      *zero filled tables.

    75. Re:Ends of Moore's Law in software ? by smash · · Score: 1

      My point was that writing throw away code on the ASSUMPTION that it is single use is often misguided, and a trap. Software has a habit of spreading and becoming mission critical. I'm not saying everything needs a full workflow analysis done prior to writing code, but far too many people fall into the trap of not refining the original design a little bit before it escapes into the wild.

      I'm currently working for a company which is using a broken old ERP solution because they have hacked so much stuff onto it over the years, the cost to migrate to something that actually works better and is supported by more than one vendor is too difficult.

      The limitations inherent in the original design are causing major scaling problems.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    76. Re:Ends of Moore's Law in software ? by viperidaenz · · Score: 1

      How do you know its not an EBCDIC character?

    77. Re:Ends of Moore's Law in software ? by SuricouRaven · · Score: 1

      EBCDIC strings are prepended with a magic number. It's the EBCDIC representation for "GETOFFMYLAWN".

  5. And best of all... by pushing-robot · · Score: 4, Insightful

    We might even stop writing everything in Javascript?

    --
    How can I believe you when you tell me what I don't want to hear?
    1. Re:And best of all... by Anonymous Coward · · Score: 1

      You fool! There must always be a Javascript.

    2. Re:And best of all... by Anonymous Coward · · Score: 0

      Like that matters. Javascript is already only 1.5 - 3x slower in non-vectorized code ( that plain C/C++. And the difference is shrinking all the time, I understand many JS engine developers are working now on autovectorization. There's little reason why Javascript can't eventually achieve performance parity with C/C++.

    3. Re: And best of all... by jarfil · · Score: 1

      Fun thing about JavaScript, it's possibly the single language that got most optimized as of late. From a sluggish thing at the dawn of the century, to a snappy language for developing web apps, and an even snappier node.js on the server side.

    4. Re:And best of all... by Urkki · · Score: 5, Funny

      We might even stop writing everything in Javascript?

      Indeed. JavaScript is the assembly language of the future, and we need to stop coding in it. There already are many nicer languages which are then compiled into Javascript, ready for execution in any computing environment.

    5. Re:And best of all... by smash · · Score: 1

      Of course, once it's burned the CPU to be JIT-ed.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    6. Re: And best of all... by Anonymous Coward · · Score: 0

      This is true. Massive engineering efforts have been put behind JavaScript to make it really fast.

    7. Re:And best of all... by Anonymous Coward · · Score: 3, Insightful

      We might even stop writing everything in Javascript?

      Indeed. JavaScript is the assembly language of the future, and we need to stop coding in it. There already are many nicer languages which are then compiled into Javascript, ready for execution in any computing environment.

      You were modded insightful rather than funny. I weep for the future.

    8. Re:And best of all... by Anonymous Coward · · Score: 0

      We might even stop writing everything in Javascript?

      Indeed. JavaScript is the assembly language of the future, and we need to stop coding in it. There already are many nicer languages which are then compiled into Javascript, ready for execution in any computing environment.

      Platform ubiquity is your excuse? Worst fucking one ever. Just because everyone can kind of understand ebonics doesn't mean we should all re-learn English phonetics, or more importantly, feel the need to.

      Learn to hire coders that can write specific to the platform if you want efficiency. And good luck when Java finally dies. I'll feel as bad for you as I do for those too cheap to run their business off anything but Facebook.

    9. Re:And best of all... by Anonymous Coward · · Score: 0

      *Woosh*

    10. Re:And best of all... by Anonymous Coward · · Score: 0

      Your tears will dry up when you get to program portable GPGPU software using Javascript.

    11. Re:And best of all... by celle · · Score: 1

      "Indeed. JavaScript is the assembly language of the future, "

          Get off the hard drugs will ya. You're delusional.

      "There already are many nicer languages which are then compiled into Javascript, ready for execution in any computing environment."

            And the world dreams of faeries runs off of unicorn farts.

    12. Re:And best of all... by Urkki · · Score: 1

      My post was obviously written tongue in cheek, but there's a grain of truth in it. Languages like Coffeescript and Typescript are gaining ground, and there are multiple fiercely competing and very talented teams working on Javascript engines. If you want to write an app once, and run it everywhere, it's going to be Javascript (or something which compiles to it) and HTML. And once you've learned (or been brainwashed to) code in Javascript, node.js is pretty great for backend (esp. if you code in another language which is then compiled to Javascript). JSON document databases are also increasing on popularity, and JSON seems to be preferred over XML in many cases which otherwise have nothing to do with Javascript.

      World does not care what you or I think of Javascript, it just takes the road of least resistance to quarterly profits. And Javascript seems to be a highway today.

  6. Not really a 'law' anyway by Anonymous Coward · · Score: 0

    They should have called it "Moore's Trend" or "Moore's Observation."

    1. Re: Not really a 'law' anyway by Anonymous Coward · · Score: 0

      "Moore's Self-fulfilled Prophecy" would be also spot on.

    2. Re:Not really a 'law' anyway by weakref · · Score: 1

      More like "Moore's Promise/Contract"

    3. Re:Not really a 'law' anyway by TheloniousToady · · Score: 1

      They should have called it "Moore's Trend" or "Moore's Observation."

      With that kind of thinking, I foresee the following headline: "Will Calling Betteridge's Law an 'Observation' End It Forever?"

  7. Mmm. Skynet. by xtal · · Score: 2

    ..took us in directions we hadn't considered.

    Forget the exact quote, but what a time to be alive. My first computer program was written on a Vic-20. Watching the industry grow has been incredible.. I am not worried about the demise of traditional lithographic techniques.. I'm actually expecting the next generation to provide a leap in speed as now there's a strong incentive to look at different technologies.

    Here's to yet another generation of cheap CPU.

    --
    ..don't panic
    1. Re:Mmm. Skynet. by Anonymous Coward · · Score: 0

      I not confident it will happen any time soon ... because the ones who need to be doing the experimenting and research are waiting for someone else to provide that leap in speed.

  8. Imagine that... by ItMustBeEsoteric · · Score: 1

    We might stop seeing ridiculous gains in computing power, and might have to start making gains in software efficiency.

  9. Demand shifted? by Tablizer · · Score: 1

    Perhaps the focus on portable computing has pulled research money away from high-end chips. The demand for high-end PC's is flattening out, and so R&D money is being pulled out of there and into ARM-level chips to have existing CPU power in smaller, battery-friendly boxes.

    1. Re:Demand shifted? by Anonymous Coward · · Score: 1

      Once upon a time I updated my computer every time new ones were 4x faster. And it was often in the nineties! But suddenly the progress stopped last decade. I'd guess single threaded performance was 4x slower in 2000 than today. In the nineties, that happened occasionally in a year or less.

    2. Re:Demand shifted? by Billly+Gates · · Score: 1

      Still in mobile. Very large difference between Galaxs1 and the GalaxyS4. Galaxy1 was painfully slow. Iphone 5s is probably a good 10x or maybe 15x as fast as iphone1

  10. Ridiculous by Anonymous Coward · · Score: 0

    Ridiculous, talking about Moore's law as if it were a part of nature. When in fact it is the product of innovation and ingenuity, which you say it hampers. Its not Moore's law that's slowing down innovation, its lack of innovation that is invalidating Moore's law.

  11. Software improvements matter more than hardware by JoshuaZ · · Score: 3, Interesting

    This is ok. For many purposes, software improvements in terms of new algorithms that are faster and use less memory have done more for heavy-dute computation than hardware improvement has. Between 1988 and 2003, linear programmng on a standard benchmark improved by a factor of about 40 million. Out of that improvement, about 40,000 was from improvements in software and only about 1000 in hardware improvements (these numbers are partially not well-defined because there's some interaction between how one optimizes software for hardware and the reverse). See this report http://www.whitehouse.gov/sites/default/files/microsites/ostp/pcast-nitrd-report-2010.pdf. Similar remarks apply to integer factorization and a variety of other important problems.

    The other important issue related to this, is that improvements in algorithms provide ever-growing returns because they can actually improve on the asymptotics, whereas any hardware improvement is a single event. And for many practical algorithms, asymptotic improvements are occurring still. Just a few days ago a new algorithm was published that was much more efficient for approximating max cut on undirected graphs. See http://arxiv.org/abs/1304.2338.

    If all forms of hardware improvement stopped today, there would still be massive improvement in the next few years on what we can do with computers simply from the algorithms and software improvements.

    1. Re:Software improvements matter more than hardware by Taco+Cowboy · · Score: 3, Interesting

      Between 1988 and 2003, linear programmng on a standard benchmark improved by a factor of about 40 million. Out of that improvement, about 40,000 was from improvements in software and only about 1000 in hardware improvements (these numbers are partially not well-defined because there's some interaction between how one optimizes software for hardware and the reverse).

      I downloaded the report at the link that you have so generously provided -http://www.whitehouse.gov/sites/default/files/microsites/ostp/pcast-nitrd-report-2010.pdf - but I found the figures somewhat misleading

      In the field of numerical algorithms, however, the improvement can be quantified. Here is just one example, provided by Professor Martin GrÃtschel of Konrad-Zuse-Zentrum für Informationstechnik Berlin. GrÃtschel, an expert in optimization, observes that a benchmark production planning model solved using linear programming would have taken 82 years to solve in 1988, using the computers and the linear programming algorithms of the day. Fifteen years later â" in 2003 â" this same model could be solved in roughly 1 minute, an improvement by a factor of roughly 43 million. Of this, a factor of roughly 1,000 was due to increased processor speed, whereas a factor of roughly 43,000 was due to improvements in algo-rithms! GrÃtschel also cites an algorithmic improvement of roughly 30,000 for mixed integer programming between 1991 and 2008

      Professor GrÃtschel's sighting was in regard of "numerical algorithm", and no doubt, there have been some great improvements achieved due to new algorithms. But that is just one tiny aspect out of the whole spectrum of the programming scene.

      Out of the tiny segment of the numerical crunching, bloatwares have emerged everywhere.

      While the hardware speed has accelerated 1,000x (as claimed by the kind professor), the speed of the software in solving the myriad problems hasn't exactly been keeping up.

      I have invested more than 30 years of my life in the tech field, and comparing to what we had achieved in software back in the late 1970's, what we have today are astoundingly disappointing.

      Back then, RAM was counted in KB, and storage in MB were considered as "HUGE".

      We had to squeeze every single ounce of performance out of our programs just to make them run at decent speed.

      No matter if it's a game of "pong" or numerical analysis, everything had to be considered and more than often we get down to the machine level (yes, we code one step lower than the assembly language) so to minimize the "waste", counting down to each and every single cycle.

      Yes, many of the younger generation will look at us as though we the old farts are crazy, but our quest in fighting against the hardware limitation was, at least to us who went through it all, extremely stimulating.

      --
      Muchas Gracias, Señor Edward Snowden !
    2. Re:Software improvements matter more than hardware by Anonymous Coward · · Score: 1

      Unfortunately, in some cases (e.g. linear algebra systems solution) we have obvious lower bounds - good luck ever coming up with a general dense matrix-vector multiply that's faster than n^2, it's down to 2.307 formally I think - with no possibility of ever improving them.

      But it's true that where possible algorithmic improvements improve everything now and forever. The widespread use of multigrid methods as preconditioners & solvers in implicit CFD and Poisson solvers, typically replacing (I believe) ADI methods, was earth shattering... Going from n log n to just n for a system of size n is gigantic when N is billions.

      ps, parent's PCAST pdf refers to his quoted figures on document page 71 = pdf page 98.

    3. Re:Software improvements matter more than hardware by Anonymous Coward · · Score: 0

      Between 1988 and 2003, linear programming on a standard benchmark improved by a factor of about 40 million. Out of that improvement, about 40,000 was from improvements in software and only about 1000 in hardware improvements

      Yes, but if those programmers back in 1988 were smart, they could have written a program that was 40,000 times faster already.
      That would leave us now with a measly 1x improvement in software and a 1,000x improvement in hardware.

      (Back in the 80s, hardware designers were limited by all sorts of technological constraints.)

      (Posting anonymously because of Slashdot's poor submission form)

  12. Implications by Animats · · Score: 3, Interesting

    Some implications:

    • We're going to see more machines that look like clusters on a chip. We need new operating systems to manage such machines. Things that are more like cloud farm managers, parceling out the work to the compute farm.
    • Operating systems and languages will need to get better at interprocess and inter-machine communication. We're going to see more machines that don't have shared memory but do have fast interconnects. Marshalling and interprocess calls need to get much faster and better. Languages will need compile-time code generation for marshalling. Programming for multiple machines has to be part of the language, not a library.
    • We're going to see more machines that look like clusters on a chip. We need new operating systems to manage such machines. Things that are more like cloud farm managers.
    • We'll probably see a few more "build it and they will come" architectures like the Cell. Most of them will fail. Maybe we'll see a win.
    1. Re:Implications by Anonymous Coward · · Score: 0

      >We're going to see more machines that look like clusters on a chip.

      What part of "we can't squeeze any more transistors onto a chip" do you not understand?

    2. Re:Implications by Anonymous Coward · · Score: 0

      Don't be so nasty...you could have just said "it's getting impossible to squeeze any more transistors onto a chip".

    3. Re:Implications by dkf · · Score: 1

      What part of "we can't squeeze any more transistors onto a chip" do you not understand?

      If you drop the requirement to have them all work together on a single problem in a coordinated fashion, you can squeeze more on. For example, you can use larger chips (duh!) and have a way to cope with some of the cores being non-functional due to manufacturing flaws (as the number of defects per wafer is approximately constant). But that's a very different way of working.

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
    4. Re:Implications by dkf · · Score: 1

      Some implications:

      • We're going to see more machines that look like clusters on a chip...
      • We're going to see more machines that look like clusters on a chip...

      Looks like you had a parallelism problem right there!

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
    5. Re:Implications by Anonymous Coward · · Score: 0

      What part of 'architectures like the Cell' don't you understand?

      http://en.wikipedia.org/wiki/Cell_%28microprocessor%29#Synergistic_Processing_Elements_.28SPE.29

      ^Start researching here

      Here's an earlier example: http://en.wikipedia.org/wiki/Atari_Transputer_Workstation#Description

      You don't squeeze more transistors on, you make the cores simpler so they use less transistors and have them specialize (The PPU of the Cell processor doesn't even have out of order execution IIRC or any other optimizations and just runs the OS, and neither does the SPE, it does the SIMD heavy lifting).

      Hope that helped

    6. Re:Implications by Anonymous Coward · · Score: 0

      >If you drop the requirement to have them all work together on a single problem in a coordinated fashion, you can squeeze more on.

      We already have that. How do you think virtualization works, for pity's sake?

      >For example, you can use larger chips (duh!)

      Photomask reticles for making chips are already as large as they can practically be made (duh!). Chips can't be much larger than they are and keep a reasonable price point.

      >and have a way to cope with some of the cores being non-functional due to manufacturing flaws

      Wafer scale integration all over again. Spoiler: it never worked out despite smart people like Amdahl (yes, *that* Amdahl) spending a lot of effort on it.

    7. Re:Implications by Anonymous Coward · · Score: 0

      Don't be so nasty...you could have just said "it's getting impossible to squeeze any more transistors onto a chip".

      Yeah, sure, but where's the fun in that?

  13. Re:Anonymous Coward's Law by Anonymous Coward · · Score: 5, Funny

    Moore's yawn ... er, law. It has ended, again again. It must be the co-joined twin of Voyager which has left the solar system 78 times in the past 14 years.
    Wake me up when some real news gets in.

  14. dumbest thing I've read all day by phantomfive · · Score: 1

    This quote from the article: " But it may be a blessing to say goodbye to a rule that has driven the semiconductor industry since the 1960s." is surely the dumbest thing I've read all day.

    Seriously? It's like, people wake up and say, "it would be such a blessing if I could never get a faster computer." Does that make sense at all?

    --
    "First they came for the slanderers and i said nothing."
    1. Re:dumbest thing I've read all day by Billly+Gates · · Score: 2

      Tell that to the XP holdouts.

      No newer technology means no change and using the best ever made soley because they are familiar.

    2. Re:dumbest thing I've read all day by phantomfive · · Score: 1

      I can understand the XP holdouts, sort of. They have some features they like or something.

      With Moore's law, we're talking about faster processors. No changes necessary, other than your motherboard. I've never met anyone who was in love with their motherboard.

      --
      "First they came for the slanderers and i said nothing."
    3. Re:dumbest thing I've read all day by Chuck+Chunder · · Score: 1

      That may have been the dumbest thing you've read all day but to be fair that was before your comment was written.

      The intent behind that sentence seems fairly clear, that the end of predictable speed increases may lead to greater focus on whole other avenues of development and other unpredictable and exciting ideas popping up.

      --
      Boffoonery - downloadable Comedy Benefit for Bletchley Park
    4. Re:dumbest thing I've read all day by Billly+Gates · · Score: 1

      I love mine compared to last.

      Anything with a chip including chipsets, i/o controllers like thunderbolt, gpu etc, all benefit and change.

      There is a reason Sata and thunderbolt 2 did not exist in 1999. Chips and power for them would be impossible or very size and cost prohibitive

    5. Re:dumbest thing I've read all day by phantomfive · · Score: 1

      The intent behind that sentence seems fairly clear, that the end of predictable speed increases may lead to greater focus on whole other avenues of development and other unpredictable and exciting ideas popping up.

      Yes, why don't we go back to the abacus, and see what new ideas come up!

      Seriously, do you remember when microcomputers came out? Academics complained that they were setting the computer world back three decades. That's basically how you sound.

      --
      "First they came for the slanderers and i said nothing."
    6. Re:dumbest thing I've read all day by Urkki · · Score: 1

      Yes, why don't we go back to the abacus, and see what new ideas come up!.

      Logical fallacy, nobody is suggesting going back. If you want to take abacus as example, then what you are saying is, let's just keep adding beads and rows to our abacuses, and come up with ingenious bead sliding mechanisms to allow faster and faster movement of beads.

      Now we're soon hitting the diminishing returns limit of this road, need to start inventing something else to make calculations faster, and perhaps open entire new ways of doing calculations, analogous to what you can do with a slide rule.

    7. Re:dumbest thing I've read all day by Chuck+Chunder · · Score: 1

      That's basically how you sound.

      How I sound? You really should work on your reading comprehension, I was merely explaining what the article was saying.

      --
      Boffoonery - downloadable Comedy Benefit for Bletchley Park
    8. Re:dumbest thing I've read all day by phantomfive · · Score: 1

      Logical fallacy, nobody is suggesting going back.

      It's not a fallacy, you didn't understand. People are saying that limited computation facilities will encourage innovation. If limited computation facilities encourage, nay, force innovation, then limiting it even more should force even more innovation.

      Or maybe you can think of some line where, if computation facilities are limited beyond a certain point, they will suddenly stop forcing innovation? Otherwise the entire article is idiotic (along with your post.....seriously, do you think people haven't been inventing new things to make calculations go faster? Have you seen how multiplication gets done inside an Intel chip?)

      --
      "First they came for the slanderers and i said nothing."
    9. Re:dumbest thing I've read all day by Urkki · · Score: 1

      What I take it to mean is, diminishing returns direct investment in other avenues of research. What ever is most likely to produce increase in computing capacity (and hence enable sales of new tech down the line) is going to get research funding. Totally new tech and risky innovations will not get as much funding if same money gives better returns if it is spent on building a refined chip fan with mostly proven tech.

      So for past decades we have been making better and better abacuses. What we'll invent when that road becomes too steep, I don't know, but I don't think we have found the ultimate tech in computing.

    10. Re:dumbest thing I've read all day by geekoid · · Score: 1

      It does if you understand Moore's law and the fact that increased speed is a by products of Moore's Law and the speed in no way equals power.

      WIthout the speed chase of the 90's and 00' we would have been more focus on parallelization; which could me better usage of the cycles, and a computer that can get more done per cycle at a slower freq. Having a billion Cycles as second isn't worthwhile if you only use 10 cycles.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    11. Re:dumbest thing I've read all day by geekoid · · Score: 1

      In a lot of respects they did. A lot of tech form the 70's didn't start getting used in the PC until the 21st century.
      In a lot more ways, we found ways to use them that didn't need the technology.

      Also, did you actual understand what he wrote? Lets put it another way:
      The way we have been doing things is ending, so we will need to find other ways to move forward. I can't wait to see what that technology will be.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    12. Re:dumbest thing I've read all day by phantomfive · · Score: 1

      The way we have been doing things is ending, so we will need to find other ways to move forward. I can't wait to see what that technology will be.

      Because the technologies that have been invented over the past decade aren't fascinating and incredible?

      --
      "First they came for the slanderers and i said nothing."
    13. Re:dumbest thing I've read all day by phantomfive · · Score: 1

      WIthout the speed chase of the 90's and 00' we would have been more focus on parallelization; which could me better usage of the cycles, and a computer that can get more done per cycle at a slower freq. Having a billion Cycles as second isn't worthwhile if you only use 10 cycles.

      You can always do more between frames of a video game. That's how I look at it.

      --
      "First they came for the slanderers and i said nothing."
    14. Re:dumbest thing I've read all day by phantomfive · · Score: 1

      but I don't think we have found the ultimate tech in computing.

      I hope you are right.

      --
      "First they came for the slanderers and i said nothing."
    15. Re:dumbest thing I've read all day by Chuck+Chunder · · Score: 1

      It's not a fallacy, you didn't understand. People are saying that limited computation facilities will encourage innovation. If limited computation facilities encourage, nay, force innovation, then limiting it even more should force even more innovation.

      Why should it? That seems like an obvious fallacy. Limiting us to abacuses would just mean people would be looking to improve on the abacus. Limitations in silicon means people looking at alternatives to silicon (just as limitations with vacuum tubes meant people looked for better alternatives and the transistor).

      Perhaps in 60 years the basic components of today's technology will look as quaint and old timey as vacuum tubes do today. If we are just using iteratively improved versions of todays integrated circuits then that might be somewhat disappointing.....

      --
      Boffoonery - downloadable Comedy Benefit for Bletchley Park
    16. Re:dumbest thing I've read all day by phantomfive · · Score: 1

      In addition, it ignores the incredible advances in manufacturing we've see over the past decade. Saying, "there hasn't been innovation" is just a display of ignorance on the part of the writer.

      --
      "First they came for the slanderers and i said nothing."
  15. Moore's "law" & AI by globaljustin · · Score: 3, Interesting

    In my mind it was an interesting statistical coincedence, *when it was first discussed*

    Then the hype took over, and we know what happens when tech and hype meet up...

    Out of touch CEO's get hair-brained ideas from non-tech marketing people about what makes a product sell, then the marketing people dictate to the product managers what benchmarks they have to hit...then the new product is developed and any regular /. reader knows the rest.

    It's bunk. We need to dispel these kinds of errors in language instead of perpetuating them, because it has tangible effects on the engineers in the lab who actually do the damn work.

    Part of what made the Moore's "Law" meme so sticky is how it was used, usually in a simple line graph, by "futurists" who barely can check their own email to pen mellodramatic, overhyped predictions about *when* we would have 'AI'.

    AI hype is tied to computer performance, and Moore's "Law" was something air-head journalists could easily source, complete with a nice graph from a tech "expert"

    I know my view of AI as a fiction is in the minority, but IMHO we need to grow up, stop with the reductive notion that computing is progressing towards some kind of 'AI' singularity and focus on making things that help people do work or play.

    Our industry looses **BILLIONS** of dollars and hundreds of thousands of work-hours chasing a fiction when we could be making more useful, powerful, and imaginitive things that meet actual, real world human needs.

    To bring this back to Moore's Law, let's work on better explaining the value of tech to non-techies. Let's give air-headed journalists something to sink their teeth into that will help our industry progress, not play the bullshit/hype game like every other industry.

    --
    Thank you Dave Raggett
    1. Re:Moore's "law" & AI by Anonymous Coward · · Score: 0

      "Moore's Law" was expliclity marketing from the very fucking beginning!

      Go look at the original paper, it actually has a cartoon of a very Steve Jobs-esque salesmen with a table of Mac Mini-sized computers. The paper was about the economic trajectory of computers, not boring ass material science.

      Meanwhile you can shove airhead journalists up your expansive rectum, while you consider Intel's historical stock prices.

    2. Re:Moore's "law" & AI by fatphil · · Score: 1

      > To bring this back to Moore's Law, let's work on better explaining the value of tech to non-techies.

      We can now do stupid things more quickly and in vaster quantity?

      --
      Also FatPhil on SoylentNews, id 863
    3. Re:Moore's "law" & AI by Anonymous Coward · · Score: 0

      Our industry looses ...

      The word you are looking for is "loses", not "looses". Loser.

    4. Re:Moore's "law" & AI by Anonymous Coward · · Score: 0

      To bring this back to Moore's Law, let's work on better explaining the value of tech to non-techies. Let's give air-headed journalists something to sink their teeth into that will help our industry progress, not play the bullshit/hype game like every other industry.

      Ironically, Moore's law doesn't exist in certain areas of business.

      There was certainly no evidence of companies trying to "keep up" as they're scrambling to replace the decade-old XP systems they fought long and hard not to replace...

    5. Re:Moore's "law" & AI by khallow · · Score: 1
      Moore's Law is a model, not an error. And it worked out quite well for more than fifty years (including some period of time before it became more or less official). That deflates most of your argument.

      Part of what made the Moore's "Law" meme so sticky is how it was used, usually in a simple line graph, by "futurists" who barely can check their own email to pen mellodramatic, overhyped predictions about *when* we would have 'AI'.

      AI hype is tied to computer performance, and Moore's "Law" was something air-head journalists could easily source, complete with a nice graph from a tech "expert"

      I know my view of AI as a fiction is in the minority, but IMHO we need to grow up, stop with the reductive notion that computing is progressing towards some kind of 'AI' singularity and focus on making things that help people do work or play.

      Moore's law is a demonstration that these ideas aren't completely fiction. Merely having faster, higher density computing did greatly improve the ability to design future faster, higher density computing machines.

      It strikes me that what you're really talking here is not that "the Singularity" or similar iterative development scenarios are fiction but rather that any such process which builds on itself can be naively directed into an extreme, not particularly useful direction by obsessive focus on a few metrics.

      And that could have nasty repercussions for us, if we develop something that is obsessively focused on and quite capable of increasing those few metrics at the expense of everything else.

    6. Re:Moore's "law" & AI by Anonymous Coward · · Score: 0

      And stop playing video games... We are wasting billions of dollars chasing after fake pixels on the screen. We could have cured cancer by now if we only had done 'practical' work.

      Yeah screw AI screw it right in the ear... it has 0 practical uses.

      http://en.wikipedia.org/wiki/Google_driverless_car
      http://www.20q.net/
      http://en.wikipedia.org/wiki/Applications_of_artificial_intelligence

      We never use it anywhere.

    7. Re:Moore's "law" & AI by geekoid · · Score: 1

      Define AI.

      By the standard we would define it 40 years ago, we have achieve it, it's just the bar keeps moving.
      Every time some one solve a problem regarding AI suddenly it goes from being AI to just being an algorithm.
      AI is not a fiction, the amount of free will we thing we have is the fiction.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    8. Re:Moore's "law" & AI by geekoid · · Score: 1

      Moorels law isn't about speed. The fact that you don't understand that makes me want to disregard your entire post.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    9. Re:Moore's "law" & AI by Anonymous Coward · · Score: 0

      AI means "artificial intelligence." Like Hal from 2001, an actual intelligence & personality on the scale of a person.

      Chess-playing computers was never perceived as the end goal of AI, and such advances just come from processors being vastly more powerful and able to brute-force their way through specific, narrow-scoped objectives.

    10. Re:Moore's "law" & AI by Anonymous Coward · · Score: 0

      looks more like Ronald Regan than Steve Jobs

      course we all know where your head is at if you think the first subcompact desktop was a fucking mac mini

    11. Re:Moore's "law" & AI by khallow · · Score: 1

      Moorels law isn't about speed.

      It's about transistor density. Integrated circuits with higher transistor densities happen to be useful when you're designing integrated circuits with higher transistor densities. Speed of computation is one reason why.

    12. Re: Moore's "law" & AI by Anonymous Coward · · Score: 0

      The paperclip problem

  16. Feature size vs "Feature size" by radarskiy · · Score: 3, Interesting

    The defining characteristic of the 7nm is that it's the one after the 10nm node. I can't remember the last time I worked in a process where the was a notable dimension that matched the node name, either drawn or effective.

    Marc Snir gets bogged down in an analysis of gate length reduction which is quite besides the point. If it gets harder to shrink the gate than to do something else, then something else will be done. It worked on processes with the same gate length as the "previous" process, and I've probably even worked on a process that had a larger gate than the previous process. The device density still increased, since gate length is not the only dimension.

    1. Re:Feature size vs "Feature size" by Anonymous Coward · · Score: 0

      I can't remember the last time I worked in a process where the was a notable dimension that matched the node name, either drawn or effective.

      I think 180nm was the last, but I can't find the source paper any more. 180nm as in "early-2001 Pentium 3".

  17. feature bottlenck by globaljustin · · Score: 1

    We might stop seeing ridiculous gains in computing power, and might have to start making gains in software efficiency.

    I agree in sprit but you perpetuate a false dichotomy based on a misunderstanding of *why* software bloat happens, in the broad industry-wide context.

    Just look at Windows. M$ bottlenecked features willfully because it was part of their business plan.

    Coders, the people who actually write the software, have always been up to the efficiency challenge. The problem is the biggest money wasn't paying for ninja-like efficiency of executing user instructions.

    It was about marketing and ass-backwards profit models forced onto the work of making good code.

    I've often observed that in order to do the most desirable work, a coder would have to sacrifice the very thing that made them want to work on the best software in the first place...

    --
    Thank you Dave Raggett
    1. Re:feature bottlenck by Anonymous Coward · · Score: 0

      Coders, the people who actually write the software, have always been up to the efficiency challenge.

      The minority of coders, you mean. Most coders are and always have been very, very crappy.

    2. Re:feature bottlenck by celle · · Score: 1

      "It was about marketing and ass-backwards profit models forced onto the work of making good code."

            Thanks for hitting the nail on the head. Now we just need a law that allows coders to kill business types who interfere with proper code writing. (Should clean out the marketing staff quick)

      "Just look at Windows. M$ bottlenecked features willfully because it was part of their business plan."

            Is there a reason the US government and/or businesses can't sue because MS intentionally caused economic limitations by limiting their software?

  18. Goovernments? Nonsense! by gweihir · · Score: 1

    If, just if anything can be done, Governments will not play any significant role in this process. They do not even seem to understand the problem, how could they ever be part of the solution? And that is just it: It is quite possible that there is no solution, or that it may take decades or centuries for that one smart person to be in the right place at the right time. Other than blanket research funding, Governments cannot do anything to help that. Instead, scientific funding is today only given to concrete applied research that promises specific results. That is not going to help making any fundamental breakthrough, quite the opposite.

    Personally, I expect that is it for computing hardware for the next few decades or possibly permanently. I do not see any fundamental issue with that. And there would be quite a bit of historic precedent for a technology to slowly begin to mature.

    As software is to incredible unrefined these days, that would be a good thing. It would finally be possible to write reasonable standard components for most things, instead of the bloated, insecure mess so common these days. It would also be possible to begin restricting software creation to those that actually have a gift for it, instead of having software created by the semi-competent and the incompetent (http://www.codinghorror.com/blog/2010/02/the-nonprogramming-programmer.html). In the end, the fast process of computing (which burned a few centuries of fundamental research) was not a good thing. Things will be moving much slower while new fundamental research results will be created instead of merely consumed.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    1. Re:Goovernments? Nonsense! by geekoid · · Score: 1

      YOu don't understand how the government works, do you?

      A) It as RnD working on stuff, cutting edge stuff.
      B) It creates goals and then asks people to solve those goals, this drive innovation.

      For example: The military find out that the types of boots they have no longer fill the mission. So they put out a request for bids that fit what they need. A private company gives a bid and then builds the boots.

      The Goverment is a driver.
      Of course there are exceptions, and a lot of really good things have come out of Government RnD projects.

      "Governments cannot do anything to help that"
      IT can lay out the platform for such people to have an avenue to appear. Good cheap schooling would be a nice start.

      ", scientific funding is today only given to concrete applied research that promises specific results."
      false; however there are some people in congress trying to make it that way. Mostly becasue they are either scientifically illiterate, or are just fishing for things that sound good so they can destroy the government.

      If the government put proper engineering standards as a requirement for software bids, that would go a long way to maturing the industry; which desperately needs it.

      " Things will be moving much slower while new fundamental research results will be created instead of merely consumed."
      mmm, probably not. Of course you need to be more specific then 'things'.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  19. cubes by Billly+Gates · · Score: 1

    One of the reasons our brains are more powerful is because we are 3d and a chip is still stuck in 2d.

    When will we see 3d or many layered chips turning simple instructions into complex ones similar to a neural net?

    Or if machines are fast enough (witness those on 10 year old XP boxen hold outs) no one will care? When can we have our own 3cpos?

    1. Re:cubes by Anonymous Coward · · Score: 0

      It turns out that building 3D chips is actually sort of difficult. The entire (exquisitely refined) process of building 2D chips based on altering the surface of a nearly flawless silicon monocrystal that is perfectly flat - not a single atomic layer out of place - on hand-sized dimensions. Once it's been through several hundred lithiography steps that may have dropped literally dozens of layers of exotic insulators and metal interconnects and embedded dopant ions all over the place, you can't exactly do that again to create layer #2.

      That and the fact that layer #1 already has a heat output density comparable to nuclear reactor fuel...

    2. Re:cubes by smash · · Score: 1

      intel is already doing it.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  20. Slides were kind of cool by Demonantis · · Score: 1

    Picture a super computer so massive that components fail as fast as we can replace them. Now that is a big super computer. This is the issue. Super computers have a physical limit. If the node power doesn't grow we will reach a limit on simulation power. It will be interesting to see how the CPU matures. That means more features will be developed beyond raw power.

    1. Re:Slides were kind of cool by Anonymous Coward · · Score: 1

      Fault-tolerant versions of MPI are already under draft.

      In the future expect to see hardware fault-detection that triggers the entire MPI process to pause while the entire memory image on the failed node copies itself to a hot spare node and resumes from there.

      There is room for even further MTBF improvement in computer hardware. The move to solid state storage (assuming $/TB can ever catch up to rotating disks) and the move to hydrodynamic bearings in fans will eliminate the last points of moving-contact wear out, albeit at the price of introducing the SSD's finite-write-cycles problem. Following that, anticipate the phase-out of liquid dielectric and even "solid tantalum" capacitors in favor of bigger and bigger MLCCs which basically leaves nothing other than electrothermal migration within chips to cause failure-to-execute.

      Long term installation/reliability presents other hazards - ROM/EEPROM/SSD memory cell depolarization, board thermal cycling, mechanical mounting stress, vibration from the power supply regulator coils, etc - but these are unlikely to impact supercomputer installations that will probably be thrown out as "no longer worth the power to run" before then.

  21. Re:Anonymous Coward's Law by JWSmythe · · Score: 1

    I thought they finally killed that off last month. Or the other 7K times it was declared dead.

    --
    Serious? Seriousness is well above my pay grade.
  22. Re:Software improvements matter LESS than hardware by Anonymous Coward · · Score: 2

    Misleading.

    Yes, I've got 100 fold improvments on a single image processing algorithm. It was pretty easy as well.
    However, that only speeds up that one algorithm, 10x faster hardware speeds everything 10x.

    Use of interpretted languages and bloated code has more than equalled the point gains in algorithms.

    The net result overall is that 'performance' increase has been mostly due to hardware, not software.

  23. Time to start putting money back into R & D. by jzatopa · · Score: 1

    It feels like we have been coasting a bit with technology the past few years so this doesn't surprise me. Everything is just a smaller/faster version of the year before.

  24. well then... by smash · · Score: 1

    ... time to stop writing garbage in visual basic, man up, and use proper languages again that are actually efficient, isn't it?

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  25. 50s-90s by Anonymous Coward · · Score: 0

    From the 50s-90s businesses ran fine with basically no PCs or 8086 machines.
    Once the wall hits businesses will run fine too.
    What I expect to see more of refinements of technology that make things work better.
    Example: in the 70s you could buy a small portable tire repair kit. Problem was there was a metal seal across the opening of the tube of vulcanizing material, on the street it was a bitch to open. By the 80's the dsmr kit was available but on the outsige edge of the cap was a small spike. You unscreded the cap put it on backwards and pushed in. The spike would puncture the metal seal.

    On possible future example. A build process for a linux kernel that scans equipment and creates the optimal kernel configuration.

  26. Carbon Nanotubes == End of Moore's Law? by nateman1352 · · Score: 1

    So... TFA says that the end of Moore's law will result in a ton of new innovations aimed at... making computers faster??? Last time I checked making computers faster is what Moore's law is all about.

    I think a better title would be "End of Traditional Silicon/CMOS Technology Forcing Radical Innovation to Keep Moore's Law Going!"

  27. End of Moore's Law? by Alex+Vulpes · · Score: 1

    Come on now, someone always predicts an end to Moore's Law every so often, but it never happens.

    There is no beginning. There is no end. There is only Moore.

  28. wrong again by Anonymous Coward · · Score: 0

    https://www.youtube.com/watch?v=cugu4iW4W54

    This year, she and her team announced they had made the first ever single atom transistor.

  29. What's old is new again. by Ultracrepidarian · · Score: 1

    Perhaps writing efficient code will come back into style.

  30. From the road less travel ... by Anonymous Coward · · Score: 1

    Coders, the people who actually write the software, have always been up to the efficiency challenge

    The minority of coders, you mean. Most coders are and always have been very, very crappy

    Back in the bad old days when hardware constrains were REAL only crazy people with diamond-hardened will dared to code.
     
    For every project we undertook it had been an uphill battle, and for every project completed we had that rush of fulfillment, knowing that we had accomplished another impossibility.
     
    Nowadays, the rocky and windy road that we used to travel on, has become a 6-lane highway. Every Tom, Dick and Harry (and with Mary Anne thrown in) can code with minimal difficulties.
     
    They no longer have to be challenged by all the impossibilities, that is why, most coders of today can't even begin to compare to the coders back then.

  31. 3D chips, memristors, photonics, spintronics, QC by Katatsumuri · · Score: 5, Informative

    I see many emerging technologies that promise further great progress in computing. Here are some of them. I wish some industry people here could post some updates about their way to the market. They may not literally prolong the Moore's Law in regards to the number of transistors, but they promise great performance gains, which is what really matters.

    3D chips. As materials science and manufacturing precision advances, we will soon have multi-layered (starting at a few layers that Samsung already has, but up to 1000s) or even fully 3D chips with efficient heat dissipation. This would put the components closer together and streamline the close-range interconnects. Also, this increases "computation per rack unit volume", simplifying some space-related aspects of scaling.

    Memristors. HP is ready to produce the first memristor chips but delays that for business reasons (how sad is that!) Others are also preparing products. Memristor technology enables a new approach to computing, combining memory and computation in one place. They are also quite fast (competitive with the current RAM) and energy-efficient, which means easier cooling and possible 3D layout.

    Photonics. Optical buses are finding their ways into computers, and network hardware manufacturers are looking for ways to perform some basic switching directly with light. Some day these two trends may converge to produce an optical computer chip that would be free from the limitations of electric resistance/heat, EM interference, and could thus operate at a higher clock speed. Would be more energy efficient, too.

    Spintronics. Probably further in the future, but potentially very high-density and low-power technology actively developed by IBM, Hynix and a bunch of others. This one would push our computation density and power efficiency limits to another level, as it allows performing some computation using magnetic fields, without electrons actually moving in electrical current (excuse me for my layman understanding).

    Quantum computing. This could qualitatively speed up whole classes of tasks, potentially bringing AI and simulation applications to new levels of performance. The only commercial offer so far is Dwave, and it's not a classical QC, but so many labs are working on that, the results are bound to come soon.

  32. Don't assume by govett · · Score: 1

    The end of Moore's law is a concern only if it is assumed that transistors will be used indefinitely.

  33. The Way Ahead by yrrah · · Score: 2

    The International Technology Roadmap for Semiconductors is published regularly and has information on the maturity of emerging technologies like carbon. There are many possibilities for "more than Moore" improvement. http://www.itrs.net/Links/2012ITRS/Home2012.htm

    1. Re:The Way Ahead by Katatsumuri · · Score: 1

      As far as I understood from skimming the summary, their "more than Moore" concept is not about faster-than-Moore CPU scaling improvements, but about identifying and optimizing the most important use cases in the industry (automotive, mobile, health care, etc.)

      What I found neat in their analysis is that they take a broader view than the media hype about the "Moore's Law". They mention a whole set of improvement trends:

      Integration Level: Components/chip, Moore’s Law

      Cost: Cost per function

      Speed: Microprocessor throughput

      Power: Laptop or cell phone battery life

      Compactness: Small and light-weight products

      Functionality: Nonvolatile memory, imager

  34. Re: 3D chips, memristors, photonics, spintronics, by gweihir · · Score: 4, Insightful

    You may see them, but no actual expert in the field does.

    - 3D chips are decades old and have never materialized. They do not really solve the interconnect problem either and come with a host of other unsolved problems.
    - Memristors do not enable any new approach to computing, as there are neither many problems that would benefit form this approach, nor tools. The whole idea is nonsense at this time. Maybe they will have some future as storage, but not anytime soon.
    - Photonics is a dead-end. Copper is far too good and far too cheap in comparison.
    - Spintronics is old and has no real potential for ever working at this time.
    - Quantum computing is basically a scam perpetrated by some part of the academic community to get funding. It is not even clear whether it is possible for any meaningful size of problem.

    So, no. There really is nothing here.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  35. Time to revisit architecture... by KonoWatakushi · · Score: 2

    The refinement of process has postponed this for a long while, but the time has come to explore new architectures and technologies. The Mill architecture is one such example, and aims to bridge the enormous chasm of inefficiency between general purpose CPUs and DSPs. Conservatively, they are expecting a tenfold improvement in performance/W/$ on general purpose code, but the architecture is also well suited to wide MIMD and SIMD.

    Another area ripe for innovation is memory technologies, which have suffered a similar stagnation limited to refinement of an ancient technology. The density of both cache and main memory can be significantly improved on the same process with Thyristor-RAM or Z-RAM. Considering the potential benefits and huge markets, it is vexing that more resources aren't expended toward commercializing better technologies. Some of the newer technologies also scale down better.

    Something to replace the garbage which is NAND flash would also be welcome, yet sadly there appears to be no hurry there either. One point is certain, there is a desperate need to find a way to commercialize better technologies rather than perpetually refining inferior ones. Though examples abound, perhaps none is more urgent than the Liquid fluoride thorium reactor. Molten salt reactors could rapidly replace fossil fuels with clean and abundant energy while minimizing environmental impact, and affordable energy is the basis for all prosperity.

    1. Re:Time to revisit architecture... by celle · · Score: 1

      "Something to replace the garbage which is NAND flash would also be welcome, yet sadly there appears to be no hurry there either. "

          Of course not. Business has to milk it for all it's worth and then some first.

  36. Re: 3D chips, memristors, photonics, spintronics, by Anonymous Coward · · Score: 0

    I would put a big star next to the energy efficiency claim for photonics. It is currently limited greatly by the electrical-to-optical conversion efficiency of the source, e.g. a semiconductor laser. Where photonics really shines (pun intended) at the moment is in longer links. On the other hand, there is a lot of ongoing research that promises to improve efficiency and bring it in line with the decreasing efficiency of electrical interconnects at higher data rates and the physical densities required by such.

  37. doggerel by Forget4it · · Score: 1

    No more Less is More

    No more Moore's Law

    We're more or less

    Left only multi-core.

    --
    Artificial intelligence is the study of how to make real computers act like the ones in the movies.
  38. Re: 3D chips, memristors, photonics, spintronics, by Katatsumuri · · Score: 3, Insightful
    It may not be an instant revolution that's already done, but some work really is in progress.

    - 3D chips are decades old and have never materialized.

    24-layer flash chips are currently produced by Samsung. IBM works on 3D chip cooling. Just because it "never materialized" before, doesn't mean it won't happen now.

    - Memristors do not enable any new approach to computing, as there are neither many problems that would benefit form this approach, nor tools. The whole idea is nonsense at this time. Maybe they will have some future as storage, but not anytime soon.

    Memristors are great for neural network (NN) modelling. MoNETA is one of the first big neural modelling projects to use memristors for that. I do not consider NNs a magic solution to everything, but you must admit they have plenty of applications in computation-expensive tasks.

    And while HP reconsidered its previous plans to offer memristor-based memory by 2014, they still want to ship it by 2018.

    - Photonics is a dead-end. Copper is far too good and far too cheap in comparison.

    Maybe fully photonic-based CPUs are way off, but at least for specialized use there are already photonic integrated circuits with hundreds of functions on a chip.

    - Spintronics is old and has no real potential for ever working at this time.

    MRAM uses electron spin to store data and is coming to market. Application of spintronics for general computing may be a bit further off in the future, but "no potential" is an overstatement.

    - Quantum computing is basically a scam perpetrated by some part of the academic community to get funding. It is not even clear whether it is possible for any meaningful size of problem.

    NASA, Google and NSA, among others, think otherwise.

    So, no. There really is nothing here.

    I respectfully disagree. We definitely have something.

  39. Re:Anonymous Coward's Law by Anonymous Coward · · Score: 0

    Oh boy have I got news for you! Apple is rumoured to be releasing something shiny! A random weather event happened and people used it to support their arguments! A government did an IT project and it overran! A new tool/language/paradigm holds promise for people who weren't using the previous one properly! Quantum computing! AI! Flying cars! Mars rocket! Someone just found out we're getting them all in 2014! Or at least we'll DEFINITELY make an important step toward them in 2014 or VERY SOON afterwards!!!

  40. Screw moore's law, I want performance! by Anonymous Coward · · Score: 0

    Regardless of Moore's Law ending or not, new generations of processors had being more and more closer in performance to it's predecessors for years... I recently replaced my six year old Core 2 Quad Q6600 for a brand new i5 4670K to gain about 38% of overall system performance. I mean... WHAT? Try comparing the performance difference from a AT-386 to a AT-486 or from a Pentium to a Pentium II... there where massive improvements in performance from one generation to another. I can't understand why information like that doesn't make headlines.

  41. Can we de-bloat-ify software? by Anonymous Coward · · Score: 0

    Why not de-bloat-ify software by removing the bloat layer (Java JVM, .NET runtime) and getting back to compiling binaries for the processors they run on? Oh, that's right, a decade and a half of en-bloat-ing software has made us reliant on the library functions supplied by the bloat layer. We'd have to start from scratch building native APIs. I'm a low-level C programmer, but haven't written any C in years because no one uses it (outside of embedded systems programming, which is its own self-contained world). The only way I can get paid is to write Java.

  42. Re: 3D chips, memristors, photonics, spintronics, by Anonymous Coward · · Score: 1

    Well, because I'm lazy, I won't look up all of them, but:

    3D chips, yes, they're used in storage, but storage capacity has never been an issue. To increase storage now, you always have the option of simply making it bigger. Can you use 3D chips to make logic devices?

    If memrisistors are only useful in neural networks, then they're worthless. Neural networks are what's called a supervised learning method which was all the hot new rage in the 90s, but since they're difficult to design and are not easily adaptable, and become extremely complex for not terribly complex problems, they're almost never used except for the most remedial cases. They're largely being replaced by Support Vector Machines as they're simpler to design, more flexible, and so far there have been no problems which NNs can do that SVMs can't.

  43. Re: 3D chips, memristors, photonics, spintronics, by Kjella · · Score: 2

    I respectfully disagree. We definitely have something.

    That there's research into exotic alternatives is fine, but just because they've researched flying cars and fusion reactors for 50 years doesn't mean it will ever matrialize or be usable outside a very narrow niche. If we hit the limits of copper there's no telling if any of these will materialize or just continue to be interesting, but overall uneconomical and impractical to use in consumer products. Like for example supersonic flight, it exists but all commercial passengers go on subsonic flights since the Concorde landed. You can't have exponential growth forever, not even in computers.

    --
    Live today, because you never know what tomorrow brings
  44. Moore's law says something else by Anonymous Coward · · Score: 1

    Moore's law does not predict performance gains, but an increase of the number of transistors per chip. And it's not yet dead. The problem is how to get performance increases out of this transistor count increase, given that frequencies are stagnating and that "sequential" processors have reached their limits.

  45. Re:Anonymous Coward's Law by RaceProUK · · Score: 2

    Moore's Law can be applied to Moore's Law (if you generalise it): the rate at which Moore's Law is declared dead doubles roughly every two years.

    --
    No colour or religion ever stopped the bullet from a gun
  46. Re: 3D chips, memristors, photonics, spintronics, by Katatsumuri · · Score: 3, Interesting

    It's true that we may not see another 90s-style MHz race on our desktops. But there is ongoing need for faster, bigger, better supercomputers and datacenters, and there is technology that can help there. I did quote some examples where this technology is touching the market already. And once it is adopted and refined by the government agencies and big data companies, it will also trickle down into consumer market.

    I/O will get much faster. Storage will get much bigger. Computing cores may still become faster or more energy-efficient. New specialized co-processors may become common, for example for NN or QC. Then some of them may get integrated, as it happened to FPUs and GPUs. So the computing will most likely improve in different ways than before, but it is still going to develop fast and remain exciting.

    And some technology may stay out of the consumer market, similar to your supersonic flight example, but it will still benefit the society.

  47. Re: 3D chips, memristors, photonics, spintronics, by Anonymous Coward · · Score: 0

    Memristors... The whole idea is nonsense at this time. Maybe they will have some future as storage, but not anytime soon.

    They're slated to come out with DDR3 of these this year and SSDs next year as 3 major manufactures have been finishing up their final phase of retooling to start mass production. What do you mean "not any time soon"?

  48. Re: 3D chips, memristors, photonics, spintronics, by Anonymous Coward · · Score: 0

    Photonics is a dead-end.

    IBM showed off a fully functioning prototype of a 2tb/s/fiber integrated photonics with 90nm tech with a 1km range. They said it directly integrates easily into CPUs, and it's CHEAPER than copper. The only issue is retooling board manufactures to manage fiber instead of traces, but IBM says this is still cheaper because the board designs are much less complex.

    IBM said to expect these in cell phones in the near future, because it will cut down on cost and power usage while increasing speed.

  49. Re: 3D chips, memristors, photonics, spintronics, by RabidReindeer · · Score: 1

    You may see them, but no actual expert in the field does.

    - 3D chips are decades old and have never materialized. They do not really solve the interconnect problem either and come with a host of other unsolved problems.
    - Memristors do not enable any new approach to computing, as there are neither many problems that would benefit form this approach, nor tools. The whole idea is nonsense at this time. Maybe they will have some future as storage, but not anytime soon.
    - Photonics is a dead-end. Copper is far too good and far too cheap in comparison.
    - Spintronics is old and has no real potential for ever working at this time.
    - Quantum computing is basically a scam perpetrated by some part of the academic community to get funding. It is not even clear whether it is possible for any meaningful size of problem.

    So, no. There really is nothing here.

    And all that does is remind me of the times when a previously-useless technology suddendly became mainstream because someone finally found a proper use for it.

  50. link to original paper by globaljustin · · Score: 1

    I'd like to see a link to the original paper you speak of, AC

    --
    Thank you Dave Raggett
    1. Re:link to original paper by geekoid · · Score: 1

      http://web.eng.fiu.edu/npala/EEE6397ex/Gordon_Moore_1965_Article.pdf

      That's the original paper, plus an interview. Anyone who even says Moore's law should read it.
      AC was wrong about the marketing aspect, but they are correct regarding the illustration.

      Moore's Law ended about 5 years ago.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  51. bullshit/hype by globaljustin · · Score: 1

    bullshit/hype exists everywhere humans are communicating about something...

    I think you misunderstood what I meant when I said, "To bring this back to Moore's law"..."this" is my comment...not sure what you thought I was saying...

    --
    Thank you Dave Raggett
  52. Re: 3D chips, memristors, photonics, spintronics, by Katatsumuri · · Score: 3, Informative

    I looked up some companies by name (too bad you posted as AC and didn't mention them), and here is what I found:

    Intel reveals a neuromorphic chip design based on memristors and spintronics

    HP and Hynix postpone memristor-based memory to avoid cannibalizing their flash business

    This pearl deserves to be quoted:

    "In terms of commercialization, we will have something technologically viable by the end of next year. Our partner, Hynix, is a major producer of flash memory, and memristors will cannibalize its existing business by replacing some flash memory with a different technology. So the way we time the introduction of memristors turns out to be important," said Stan Williams, Hewlett-Packard senior fellow and director of the company's cognitive systems laboratory, during a conversation at the Kavli Foundation.

    SanDisk and Toshiba are testing a ReRAM (memristor memory) chip

    HP working with AMD, Intel, ARM and others to release memristor-based "nanostores".

    A working memristor has already been proven in the lab by HP and they are now working with AMD, Intel, ARM and others to release what they call "nanostores". A chip that combines the memristor and logic of the CPU can prove to replace all current microprocessors and memory architectures.

    A startup named "Crossbar" will try to beat HP to market with memristor-based ReRAM.

  53. Re:Anonymous Coward's Law by kelemvor4 · · Score: 1

    Moore's yawn ... er, law. It has ended, again again. It must be the co-joined twin of Voyager which has left the solar system 78 times in the past 14 years. Wake me up when some real news gets in.

    It took me several moments to realize you weren't talking about Star Trek. I need to go rethink my life.

  54. RE: bothering to explain it to luddites by Anonymous Coward · · Score: 0

    Well yes, but he was asking how to do it BETTER as well as quicker and in vaster quantity.

  55. '7nm' will not be the end... by Junta · · Score: 1

    When someone says '22 nm', it doesn't resemble at all what one would have assumed it to mean 15 years ago. It means 'roughly equivalent' to what 15 year old technology would do if it hypothetically 22 nm. For example, the slide refers to different structures, and those are already happening (Intel 22 nm is kind of '2 and a half D'). If the argument is 'that won't count', then that statement has come way too late since the node name has already cease to mean anything particularly specific.

    A bigger challenge will be whether the phenomenon of computing pretty much being 'good enough' for the mass market will make it unprofitable to do the R&D to advance the state of the art in semiconductors to keep pushing things forward. I know there is significant demand in a lot of places, but will that demand be tempered if that market has to bear the cost of those advancements on their own without the mass market to help justify the cost.

    --
    XML is like violence. If it doesn't solve the problem, use more.
    1. Re:'7nm' will not be the end... by unixisc · · Score: 1

      How many nm is an Si atom?

    2. Re:'7nm' will not be the end... by Junta · · Score: 1

      The point being even that needn't be the end. It's like saying you measure people per square foot of land to assess the efficiency of a building. If you have a skyscraper, you can have multiple people per square foot of land because you stacked them. When thinking was defined particularly to one-story buildings, that would seem an odd concept because you are fitting more than one person into a spot that's not even quite big enough for one person. This is the state of semiconductors today, terminology/lay discussion based on 'single story' design, and current state of the art is basically a split-level home (very roughly) with a non trivial chance of more levels to come..

      --
      XML is like violence. If it doesn't solve the problem, use more.
    3. Re:'7nm' will not be the end... by unixisc · · Score: 1

      Maybe, but the moment you get to the point where a gate, source, drain of a FET is just a couple of atoms, you're now talking about something totally different. Even if it does do what is required from digital circuits - switching fast b/w zeros & ones while consuming the least power, it'll no longer be a shrink as such; it will be something totally different. Particularly if they decide to start mucking around w/ a Si nucleus

    4. Re:'7nm' will not be the end... by Areyoukiddingme · · Score: 1

      7 nm is 30 Si atoms, give or take, according to the slides.

  56. This is the Xeon Premium Tax, a Marketing problem. by Anonymous Coward · · Score: 0

    GPU is the rational market response to the Xeon premium. DEC would be shipping kilo-socket, kilo-core Alphas, 256 way threaded, with no GPU, and kilo serial memory channels. Think 4096 1 Ghz cores per socket at 100 W.

  57. Re: 3D chips, memristors, photonics, spintronics, by interkin3tic · · Score: 3, Funny

    Hmm... yes good points. A bit off topic, but flying machines too are nonsense. No expert in the field sees them happening. People have been talking about flying machines, and we've had balloons for decades, but flying contraptions didn't materialize. And they don't solve any problem really that we don't already have a solution to, but do introduce new problems, like falling. The whole idea is nonsense. It's a dead end too! Ships and trains are far too cheap to ever let flying machines even be competitive. It's old and has no real potential for ever working. It's basically a scam prepetuated by some bike builders, and it's not clear it will ever be useful for any meaningful problem.

    In conclusion, you're right. There's no chance of any revolutionary computing technology coming forward, and there's no chance that humans will ever fly.

  58. Re:Anonymous Coward's Law by Anonymous Coward · · Score: 0

    Yep. I remember reading articles with exactly this tone (the imminent end of Moore's law) in the technology trades back in the late 1980s.

  59. Re:Time to start putting money back into R & D by geekoid · · Score: 1

    Everything is just a smaller/faster version of the year before with slight improvements, just like always.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  60. Re: 3D chips, memristors, photonics, spintronics, by Anonymous Coward · · Score: 0

    wow, you must be a hoot at parties

  61. Choke point by John+Bayko · · Score: 1

    The problem with software efficiency has always been this: There are millions of applications, programs, libraries, etc. created, often redundant and amateur. They all run on one of a handful of CPU core designs. Spending the effort to optimise a CPU speeds everything that runs on it. Spending the effort to optimise a program speeds up one program (most libraries, maybe a handful, and only sometimes).

    There are still possibilities for CPU improvement. Transfer triggered architectures, dataflow, counterflow, asynchronous, content addressable memory, smart memory - many ideas had promise, but Moore's Law (and incompatability) meant that established techniques improved CPU speeds faster than the new ones could be commercialised (you might remember RISC as the only one that made it, barely). Without Moore's Law, there will be opportunty to work on the alternatives.

  62. Re:Anonymous Coward's Law by MickyTheIdiot · · Score: 1

    The "computing power" trend of doubling is fairly constant throughout history, but just the medium went from marks on the cave wall, to marks in sand, to marks on paper, etc up to silicon wafers.

    So "the end of Moore's Law" cry is really quite silly. If we get to the limits of silicon then someone will come up something else.

  63. Re: 3D chips, memristors, photonics, spintronics, by Anonymous Coward · · Score: 0

    Thanks, I was feeling lazy. I've had to correct others on this same topic, I was tired, didn't feel like looking the info up again. +1 informative.

  64. Re: 3D chips, memristors, photonics, spintronics, by Anonymous Coward · · Score: 0

    The problem with 3D chips, let's assume TSV, as that is the example you listed:

    TSV (through silicon via) chips are made on conventional process lithography lines, which have up to 15~30 mask expose steps and hundreds of process steps per layer. The difference is that vias are drilled through the wafer and plated with metal. The scaling of this is basically:

    number of steps per device = number of steps per layer * number of layers + wafer bonding + packaging.

    When you consider that most of the cost is in those photolithographic steps, and that this cost scales almost linearly* with number of layers, and the defect rate increases with number of layers, it's kind of obvious that this process will not scale to thousands of layers. This is ignoring the enormous problem of heat dissipation in a large stack, not as much a problem with NV memory, but hugely problematic with CPU or DRAM devices.

    * as with all mask based photolithographic processes, the cost decreases with unit quantity, as each photomask can cost more than $100k.

  65. I hate to poin this out, but we already have AI. N by Anonymous Coward · · Score: 0

    I hate to point this out, but we already have AI. Not HAL mind you, but we have cars that drive themselves and neural nets that break captcha's (Google Google's house address images or something). That stuff didn't exist 10 years ago. Look. I shouldn't really care what you say because I know the truth is the business are going to spend the billions because they want to resolve the most expensive cost on their spreadsheets. Labor. Its why you talk to automated voice prompts. They will make AI and it will have your job.

  66. Re:Software improvements matter LESS than hardware by Anonymous Coward · · Score: 0

    Most importantly, 10x faster hardware makes optimal code faster (ideally 10x, but let's be realistic). Nothing you can do in software can make optimal code more optimal.

  67. Are you sure ? by Anonymous Coward · · Score: 0

    Nothing you can do in software can make optimal code more optimal.

    As the saying goes ... "There are more than one way to skin a cat" there are more than one method to accomplish a certain task in software.

    Just because Mr. A is the world champion in skinning a cat in a particular way doesn't mean Mr. B couldn't be faster by using another method.

  68. links by marauder-2c · · Score: 1
    1. Re:links by Forever+Wondering · · Score: 1

      Thanks for this. It could [very easily] be the one I was thinking of.

      --
      Like a good neighbor, fsck is there ...
  69. Analog Computers by Dante1321 · · Score: 1

    How is the name of any and all is Moore's law dead... The size of the electron is the only thing that can delimit lithography, uh.... we have ,in fact, achieved photon based computers. That means resonance channels that can be carved much smaller than electrical pathway-thus extending Moore's Law. And according to 'Bell Labs' we shouldn't even need to abandon POSIX classical computing... what the Itanium was trued designed for. Since when did morons in computer science and programming think that digital was all there was, when they undermined the true 60yr road map back to analog computer. SPECTRUM NOT SIGNAL... calculator bandwidth of under heard of proportions... thinking machines... brain and biological augmentation... wicked cool stuff that make your 'puter look like a tablet...wait... So the answer to my original question is the 'Pentium D' my friends... think about it techogeeks.

  70. Why gives a $hit about Moore's law? by Anonymous Coward · · Score: 0

    Why are there so many articles about Moore's law and how the industry need to speed up or slow down? Moore's law is an observation, Gordon E. Moore, saw a trend back in the 60's. So F-ing what? Why does anyone care? So what if the processor speed is "on pace" with the law or not?