Re: [Embedlets-dev] Re: HDL

[Holger B. <ho...@bi...>]

>> Differences between Hardware and Software are simply not existent. 
>> Show
>> me the if they exist.
>>
>> Mostly the hardware today _is_ in fact Software. Not only the
>> micrcodes, but in the process of development and construction. I am 
>> not
>> able to construct any thing more complicated than a binkenlight 
>> without
>> Software in it.
>>
> Agreed that there is a great deal of overlap. The general concept of a
> declarative language that generates an operational system is also a 
> common
> theme. As I stated in an earlier post there are a number of synergies. 
> The
> key differences that I have picked up on are:
>
> 1. The Embedlets specification is about how to package Java objects so 
> that
> they behave like hardware, with defined inputs and outputs, triggers
> (events) etc, while retaining an object oriented environment within the
> component.

This met the behavioral concept in VHDL.

> HDL is about generating fast and compact systems from predefined 
> components
> (logical building blocks etc).

This maps to the architectural concept of VHDL, the entities.

> 2. The Embedlets specification defines extended services that allow 
> embedded
> systems to integrate with enterprise systems, each other and hardware 
> in
> standardized re-usable ways.
>
> You could do this in HDL but you would have to come up with the same 
> type of
> services and standards.

Here met VHDL JHDL. We may take the wave and define services (which i 
expect mostly FSM are in the so called 'embedded world' - not the fair 
;) and standards in a emerging standard way - in pure Java.

> 3. The embedlet configurations are based on XML which provides a 
> parsable,
> self documenting, open standards format.

uppps, where is the task for providing the schema (xsd) for this?
Whithout this, XML degrades to a textfile with '<', '<' and '/'.

> HDL is dependent on the 'C' preprocessor and compiler and requires 
> learning
> (yet) another language.

Wrong, have a look at the opensourced JHDL project.

> The Embedlets space is different and compelling enough to justify a 
> distinct
> specification utilizing enterprise standards and techniques.

This is the exact sentence my marketing manager say to me if he want to 
have it proprietary, not standard compliant, or simply does not know 
what argument should provide enough power otherwise.

Sorry, for being frankly :)

> My suggestion is that we look for commonality and areas where
> interoperablility is possible. JHDL looks like a move in that 
> direction.

yeap, last sentence. But enough todo even, it is Version 0.3.

bax