[racket] General praise for racket

Hi Matthias,

It's inside a commercial product, yes. It's pretty specific and sits above
a fairly expensive OEM part so I don't know that there would be a lot of
call for open-sourcing anything. If you want more details I'd be happy to
provide them, though.

What I did end up implementing that I didn't find available directly were
watchdog threads. I had a thread that should always be able to successfully
loop a query/read-response but might block indefinitely in case of some
problem. It was simple enough to put together but it was a little too ad
hoc for my liking. It looks like there is something similar in the web
server API, where timers fire events to kill a hanging connection (or never
happen if the transaction succeeds); it wasn't immediately obvious to me
how to leverage this, though, and is anyway in "private". In fact I
considered using the web server API in general but it felt too tied to TCP
to be useful for handling byte-streams from input-output-files, even though
the asynchronous nature of these two is otherwise quite similar. That
certainly could have been due to my poor reading of the documents, though.

Deren


On Mon, Aug 19, 2013 at 9:40 AM, Matthias Felleisen <matthias at ccs.neu.edu>wrote:

>
> Thanks for letting us know. Is this a commercial/open source/hobby project
> of yours? -- Matthias
>
>
>
> On Aug 16, 2013, at 7:17 PM, Deren Dohoda wrote:
>
> > Hi Racketeers.
> >
> > I don't know how long I've been using racket/PLT scheme, but I do know
> it has really benefited me in the last year for small helper projects and I
> just wanted to thank everyone involved in the project and the mailing list
> (I learn a lot lurking here).
> >
> > Very recently I started developing an embedded system running a linux
> distribution on an ARM single-board computer, and Racket quite simply has
> saved the day. I can develop so easily in DrRacket on the PC and copy it to
> the embedded computer and everything just works exactly as tested on the
> PC. Zero cross-compiling nightmares as I'd have had if I stuck to C. I
> found the built-in threads to be a major boon and their interface feels
> exactly right to me. About the only hitch was getting serial ports to work
> in Racket as an input-output-file but it does and it didn't require a lot
> of effort. Using byte streams as an input on the PC meant I could simulate
> real behavior and errors very well so that I could have a great set of test
> cases. When the time came to execute on the platform I was confident it was
> right (and, yes, it was!).
> >
> > Right now I was under pressure to complete so I built myself a
> straightforward interpreter, but I already have plans to switch over to a
> language model and I know Racket is going to continue to shine for me and
> build a very robust system.
> >
> > There isn't much more to say on the matter, I've just been so overjoyed
> at both being able to use Racket in a project and at how well it was up to
> the task that I wanted to gush a little bit.
> >
> > Thanks again, everyone.
> > ____________________
> >  Racket Users list:
> >  http://lists.racket-lang.org/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20130819/ad95e8a2/attachment.html>