On Wed, Dec 26, 2018 at 10:26 PM Tom Gillespie wrote:
>
> Neil mentioned Ryan's work on this in the thread about hacker news. There are
> a number of issues with getting jupyter to play nicely with #langs some of
> which I have submitted a pr for, but my solution is partial and very
>
Neil mentioned Ryan's work on this in the thread about hacker news. There
are a number of issues with getting jupyter to play nicely with #langs some
of which I have submitted a pr for, but my solution is partial and very
suboptimal. A drracket-like solution, even just for kernels is likely not
It seems like the better bang for buck might be implementing a Jupyter kernel,
and leveraging that ecosystem.
https://github.com/jupyter/jupyter/wiki/Jupyter-kernels
> On Dec 20, 2018, at 02:46, Neil Van Dyke wrote:
>
> If anyone is looking to avoid relatives over the winter holiday season,
hi:
https://gist.github.com/zhu-fei/14392eb5eae29607db72b1b7a09194d4
I want to compile this piece of code on racket , these code can
compile with chez scheme , but not racket , anyone can help me out?
thank you!
--
You received this message because you are subscribed to the Google
Jason Stewart wrote on 12/26/18 5:25 PM:
Even for blue-sky projects without any legacy lock-in, I don't fancy
our chances with the enterprise/MIS crowd. They tend to favor
straight-jacket languages, and for good reason!
Agreed. (A big-corporate exception being R and "startup-like" units,
Even for blue-sky projects without any legacy lock-in, I don't fancy our
chances with the enterprise/MIS crowd. They tend to favor straight-jacket
languages, and for good reason!
For some guy running a two-man startup, something like Racket is a super
weapon. For a large organization--with
Stephen, thanks for the useful info on adoption in health sector MIS.
Stephen De Gabrielle wrote on 12/26/18 4:50 PM:
PPS I think the Jupyter enhanced REPL idea is worth pursuing and
extending as this might be a way generate interest in the Racket
runtime and associated languages.
BTW, to be
Hi Matthew, Neil,
> the people who are persuadable.
So who are the ‘persuadable’? And where to find them if not on hn?
I’m one of the ‘corporate MIS programmers’, but in the public
sector(health), and I get to interact with a variety of software vendors as
well as and build forms, worklists,
Matthew Butterick wrote on 12/26/18 1:50 PM:
I agree that success stories are helpful. I'll go one better — I think
it would be great to have a section of the main Racket website devoted
to these stories that show who uses Racket and how / why (inside &
outside academia). This could be done in
I agree that success stories are helpful. I'll go one better — I think it would
be great to have a section of the main Racket website devoted to these stories
that show who uses Racket and how / why (inside & outside academia). This could
be done in an interview-style format, like Jesse Alama's
Stephen De Gabrielle wrote on 12/26/18 7:29 AM:
Would this replace ‘interactions’, or would it be a new editor<%>?
UI conceptual-wise, I think it would probably be a mode, in which
Notebook window replaces Definitions and Interactions windows.
Implementation-wise, I suspect it would probably
Stephen De Gabrielle wrote on 12/26/18 7:40 AM:
How did other languages grow their audience? e.g. Ruby-on-Rails, Perl,
Python, PHP, C++, Rust ?
All of those had merits, were right place and at right time, and (except
Rust) really spread when there was *a lot* less noise and sheer mass of
Maybe a high profile social media patron - I’m sure JA is doing wonders for
TiddlyWiki:
https://twitter.com/joeerl/status/1077842077705293824?s=21
How did other languages grow their audience? e.g. Ruby-on-Rails, Perl,
Python, PHP, C++, Rust ?
(All fine languages with many strengths - but there
Like Maxima?
DrRacket interactions already does most of what Jupyter and Maxima does,
but lacks the functionality of cells, and the ability to re-evaluate them.
Would this replace ‘interactions’, or would it be a new editor<%>?
It’s a great idea - it seems a little like ‘code bubbles’, but for
14 matches
Mail list logo
