Re: what kind of non microconroller app are done in forth?
- From: Bruce McFarling <agila61@xxxxxxxxxxxx>
- Date: Sat, 19 Apr 2008 09:33:55 -0700 (PDT)
On Apr 19, 10:40 am, Jonah Thomas <jethom...@xxxxxxxxx> wrote:
= Dead OS.Yes. The point of an OS is to provide a steady interface between
variable/changing apps and variable/changing hardware. In the ideal case
hardware manufacturers would pay for the information they need to write
their own drivers, and application developers pay for the information
they need to write apps for your OS, and Bob's your uncle. But it
doesn't usually work like that unless Bob's your uncle.
Well, unless Bill's your uncle.
You might get a foothold if you have an application that could use a
dedicated platform similar to a PC. If the PC is cheaper than dedicated
hardware, then use it even though it does more than you want. ...
But then, where is the network economy, because if the PC is cheaper
than dedicated hardware, it can more often be done by stringing
together existing libraries plus a little glue code. And it may end up
being overkill in terms of the computing resources devoted to the
task, but *so what*? If the PC is cheaper than the dedicated hardware
that can *just* do the task, then the extra resources to do it by
stringing together libraries written for the PC resources are *free*.
The foothold for this strategy is if you have an application that
could use a dedicated platform that is *massively underpowered*
compared to a PC, and *massively cheaper* than a PC. An order of
magnitude cheaper. Since the cost of a PC is in $100's, then an order
of magnitude means in the $10's. And then the "PC" port is simply
emulating that cheap piece of hardware on the PC, typically with
upwardly compatible expansions of resources (RAM, display space,
etc.), and running the same apps in both the PC and the cheap piece of
hardware.
On this:
Again going by the utterly unreliable TIOBE numbers, if you write other
langauges in Forth and port the Forth, you could theoretically port a
lot of apps easily.
Java 20%
+ C 35%
+ C++ 45%
+ PHP 55%
+ Perl 61%
+ Python 66%
Again, there's no network economy available to any of those languages
in working with Forth. They get the theoretical opportunity to more
quickly port their language base to marginal or not-yet-developed
hardware, assuming the support of an active developer base around the
"Java-in-Forth" implementation that does not in fact exist, while in
practice, due to the size of their language community, they already
get ported reasonably quickly to most of the fringe or not-yet-
developed hardware that is of interest to them for most of their code
base.
Better to target a language with a smaller language community, where
there is more likely to be an actual opportunity to have an actual
network economy from having a "Language-in-Forth" implementation. I
have long used Lua as an example ... another example would be Cobra:
http://cobra-language.com/
.
- Follow-Ups:
- Re: what kind of non microconroller app are done in forth?
- From: Jonah Thomas
- Re: what kind of non microconroller app are done in forth?
- From: Guy Macon
- Re: what kind of non microconroller app are done in forth?
- References:
- what kind of non microconroller app are done in forth?
- From: gavino
- Re: what kind of non microconroller app are done in forth?
- From: jennifer . spykerman
- Re: what kind of non microconroller app are done in forth?
- From: Jonah Thomas
- what kind of non microconroller app are done in forth?
- Prev by Date: Re: what kind of non microconroller app are done in forth?
- Next by Date: Re: what kind of non microconroller app are done in forth?
- Previous by thread: Re: what kind of non microconroller app are done in forth?
- Next by thread: Re: what kind of non microconroller app are done in forth?
- Index(es):
Relevant Pages
|
