3 ms·

This should be getting more upvotes, not downvotes.

by kgabis 13y ago

Ygg2 13y ago
Saying things like Moore law stopped gets a downvote from me. Moore law will stop, but it's not there yet. NOTE: Moore's law is concerned with number of transistors on a chip. That number has climbed, it's just split into several cores.
- coldtea 13y ago
  >NOTE: Moore's law is concerned with number of transistors on a chip. That number has climbed, it's just split into several cores. We don't care about the pedantic interpretation of Moore law. We care about the mis-interpreation, that was a corellary of having single-core chips: that every 18 months computers got roughly twice as fast. This -- and this was the important attribute of Moore's law -- has stopped.
  - Ygg2 13y ago
    Who's we? You and author/OP? Because I've got good news for you, Moore's law corollary has merely slowed, not stopped. It will stop, just not now. I think Moore's law will work better on mobiles, because they are retreading known grounds and they are way further from reaching, real physical barriers than regular computers.
    - coldtea 13y ago
      >Who's we? You and author/OP? Most people quoting Moore's law. That the misconception is more popular than his original statement, speaks for that.
      - Ygg2 13y ago
        Yeah, marketing is a pita. It still doesn't negate the fact that even the corollary has slowed down, not stopped.
- kllrnohj 13y ago
  > NOTE: Moore's law is concerned with number of transistors on a chip. That number has climbed, it's just split into several cores. Exactly, so now Moore's law is working against JavaScript, since JS doesn't do threading. So let's assume JS somehow magically gets to be ~2x slower than native instead of ~4x slower. With the standard being quad cores now, that makes JS ~8x slower than native doing image processing - you know, that whole "instagram" thing that's insanely popular on smartphones. And during that ~8x longer it's spending processing that image, your UI is completely frozen and unresponsive. Yes I know about WebWorkers, but WebWorkers are hideously inefficient & slow by design. The limitations with them are also absurd, it is not a substitute for threading. The world is better off forgetting that they exist - which it basically has.

This should be getting more upvotes, not downvotes.

by kgabis 13y ago

This should be getting more upvotes, not downvotes.

Ygg2 13y ago

Saying things like Moore law stopped gets a downvote from me. Moore law will stop, but it's not there yet. NOTE: Moore's law is concerned with number of transistors on a chip. That number has climbed, it's just split into several cores.

coldtea 13y ago
>NOTE: Moore's law is concerned with number of transistors on a chip. That number has climbed, it's just split into several cores. We don't care about the pedantic interpretation of Moore law. We care about the mis-interpreation, that was a corellary of having single-core chips: that every 18 months computers got roughly twice as fast. This -- and this was the important attribute of Moore's law -- has stopped.
- Ygg2 13y ago
  Who's we? You and author/OP? Because I've got good news for you, Moore's law corollary has merely slowed, not stopped. It will stop, just not now. I think Moore's law will work better on mobiles, because they are retreading known grounds and they are way further from reaching, real physical barriers than regular computers.
  - coldtea 13y ago
    >Who's we? You and author/OP? Most people quoting Moore's law. That the misconception is more popular than his original statement, speaks for that.
    - Ygg2 13y ago
      Yeah, marketing is a pita. It still doesn't negate the fact that even the corollary has slowed down, not stopped.
kllrnohj 13y ago
> NOTE: Moore's law is concerned with number of transistors on a chip. That number has climbed, it's just split into several cores. Exactly, so now Moore's law is working against JavaScript, since JS doesn't do threading. So let's assume JS somehow magically gets to be ~2x slower than native instead of ~4x slower. With the standard being quad cores now, that makes JS ~8x slower than native doing image processing - you know, that whole "instagram" thing that's insanely popular on smartphones. And during that ~8x longer it's spending processing that image, your UI is completely frozen and unresponsive. Yes I know about WebWorkers, but WebWorkers are hideously inefficient & slow by design. The limitations with them are also absurd, it is not a substitute for threading. The world is better off forgetting that they exist - which it basically has.