Re: How to develop a random number generation device

On Sep 19, 7:01 am, John Larkin
<jjlar...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
On Wed, 19 Sep 2007 05:04:34 -0700, Martin Brown



But in proper synchronous design, controlled by
state machines, immensely complex stuff just works. It's sort of
ironic that in a big logic design, 100K gates and maybe 100 state
machines, everything happens all at once, every clock, across the
entire chip, and it works. Whereas with software, there's only one PC,
only one thing happens, at a single location, at a time, and usually
nobody can predict the actual paths, or write truly reliable code.

4G of RAM * 8 Bits is a lot more bits than a 100K gates. You need to
keep your sizes equal if you want to make a fair comparison.




On Sep 19, 7:01 am, John Larkin
<jjlar...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
On Wed, 19 Sep 2007 05:04:34 -0700, Martin Brown



<|||newspam...@xxxxxxxxxxxxxxxxxx> wrote:
On 18 Sep, 17:12, John Larkin
<jjlar...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
On Tue, 18 Sep 2007 07:05:25 -0700, Martin Brown

<|||newspam...@xxxxxxxxxxxxxxxxxx> wrote:
On Sep 18, 2:30 pm, MooseFET <kensm...@xxxxxxxxx> wrote:
On Sep 17, 7:55 pm, John Larkin<jjlar...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

[....]

Programmers have pretty much proven that they cannot write bug-free
large systems.

In every other area, humans make mistakes and yet we seem surprised
that programmers do too.

In most other areas of endeavour small tolerance errors do not so
often lead to disaster. Boolean logic is less forgiving. And fence

Software programming hasn't really had the true transition to a hard
engineering discipline yet. There hasn't been enough standardisation

Compare a software system to an FPGA. Both are complex, full of state
machines (implicit or explicit!), both are usually programmed in a
heirarichal language (C++ or VHDL) that has a library of available
modules, but the FPGAs rarely have bugs that get to the field, whereas
most software rarely is ever fully debugged.

I think that hardware engineers get a better grounding in logical
design (although I haven't looked at modern CS syllabuses so I may be
out of date).

Hardware can be spaghetti too, and can be buggy and nasty, if one does
asynchronous design. But in proper synchronous design, controlled by
state machines, immensely complex stuff just works. It's sort of
ironic that in a big logic design, 100K gates and maybe 100 state
machines, everything happens all at once, every clock, across the
entire chip, and it works. Whereas with software, there's only one PC,
only one thing happens, at a single location, at a time, and usually
nobody can predict the actual paths, or write truly reliable code.





But it is mostly a cultural thing. Software houses view minimum time
to market and first mover advantage to gain maximum market share as
more important than correct functionality. And it seems they are
right. Just look at Microsoft Windows vs IBMs OS/2 a triumph of superb
marketting over technical excellence!

And I have bought my fair share of hardware that made it onto the
market bugs and all too. My new fax machine caught fire. Early V90
modems that only half work etc.

So, computers should use more hardware and less software to manage
resources. In fact, the "OS kernal" of my multiple-CPU chip could be
entirely hardware. Should be, in fact.

You are treating the symptoms and not the disease. Strongly typed
languages already exist that would make most of the classical errors
of C/C++ programmers go away. Better tools would help in software
development, but until the true cost of delivering faulty software is
driven home the suits will always go for the quick buck.

No, I am making the true observation that complex digital logic
designs are usually bug-free, simple software systems have a chance of
being so, and complex software systems never are.

John


.

Relevant Pages

  • Re: New claim CI131: Machines come from intelligent agency
    ... agency causing "biological machines". ... "biological machines" could hardly be simply assumed to be the result ... but we don't see them in the same way the IDiots ... Genetic algorithms are used to design or help design many kinds of ...
    (talk.origins)
  • Re: A snapshot of the LuxAsm developments
    ... The other simple point to note is that Wannabee has grabbed posts off the ... Perhaps in Rene's "dictatorship" there is no arguing or disputing with the ... virus that can disable any Windows machine because most machines are ... that's also a principle of the internet's design too...designed to survive ...
    (alt.lang.asm)
  • Re: Charles Murray "The Plan" ends poverty
    ... I was more concerned about the synchronization of the data path and the control portion that in the original PDPs were separated and had a special circuit to synchronize them at after reset and power up. ... We probably should have simulated the design in an environment with some code, but if we had tried to do that at that time, we would have never completed the project. ... For the first decade of my career I was building special purpose machines -- very high performance, highly parallel machines used primarily to attack foreign cyphers. ... One thing that I didn't mention about Dan Dobberpuhl was that he developed a circuit simulator while a 2nd Lt on duty at NSA in the late '60s. ...
    (soc.retirement)
  • Re: New claim CI131: Machines come from intelligent agency
    ... result of intelligent agency. ... Machines are the result of intelligent agency. ... they'll show me the design specs. ... Man-made machines have cast or formed metal parts, ...
    (talk.origins)
  • Re: New claim CI131: Machines come from intelligent agency
    ... result of intelligent agency. ... Machines are the result of intelligent agency. ... they'll show me the design specs. ... Man-made machines have cast or formed metal parts, ...
    (talk.origins)
Loading