Hi spdegabrielle, no apologies please.
Actually, I did not or probably could not make myself clearly when I wrote
that reply. I had felt depressed since this mail-list is not as active as
before. At the first sight I saw your topic, I thought there should be more
topics like this, but not only con
OK I've started with:
https://github.com/racket/racket/wiki/Low-risk-ways-you-can-use-Racket-at-work
Please feel free to edit/delete/move/rearrange as you see fit.
S.
PS Davids thing sounds awesome!
PPS I'm sorry Ju. Please accept my apologies - I don't understand your
response. Can you try ag
For the record: I am cofounder of a biotech startup, and we're writing the
software in Racket. I hadn't actually thought to mention it here, but this
seems like a good opportunity: we haven't launched yet, but we're looking
to line up beta testers. The first piece we'll be releasing is a
peer-to
Do you mean to write a Racket version for this? I think that would be amazing!
> On Sep 29, 2016, at 4:43 AM, Stephen De Gabrielle
> wrote:
>
> Hi all,
>
> I was listening to a podcast about F# That mentioned an article like this
> As I've used a racket at work a number of times for small
27. Racket is in the nature of a preprocessor;
28. Besides the literate programming, Racket is a "programmable
documentation".
Any point in the two (and those 26) is not as good as it's sound if it's
not the important part in the project or team. However if all of these can
work together in a syst
Hi all,
I was listening to a podcast about F# That mentioned an article like this
As I've used a racket at work a number of times for small job, it occurs to
me that this might be a nice thing to pop on the wiki. Please let me know
if you have any objections.
Kind regards,
Stephen
Ref
https://f
6 matches
Mail list logo
