Re: [racket-users] Intro and projects inquiry

> > > Racket doesn't play well with existing code bases (except C things) > > and so my hypothesis is simply that to gain adoption of Racket, you > > need to solve problems that aren't in the "production path." Good > > thing there are *lots* of those! All those Python scripts you have? > >

Re: [racket-users] Intro and projects inquiry

Am 13.10.2017 um 00:20 schrieb Andrew Gwozdziewycz: > Racket doesn't play well with existing code bases (except C things) > and so my hypothesis is simply that to gain adoption of Racket, you > need to solve problems that aren't in the "production path." Good > thing there are *lots* of those! All

Re: [racket-users] Intro and projects inquiry

On Thu, Oct 12, 2017 at 2:27 PM Andrew Gwozdziewycz wrote: > I love seeing all of these project ideas, but I really don't think > Racket needs a "killer app." I think what it needs is the people > passionate about it building tools in it, and *using* those tools in > the work

Re: [racket-users] Intro and projects inquiry

On Thu, Oct 12, 2017 at 09:07:48AM +1100, Daniel Prager wrote: > Great topic! > > Providing examples and tutorials around data analysis and visualisation in > Racket (and filling gaps and simplifying) gets my vote. The biggest problem wth almost all free software is documentation. Sometimes it's

Re: [racket-users] Intro and projects inquiry

In this case, I'm thinking of the unfortunate JVM error messages from Clojure. As far as I know, the main reason to suffer through Clojure's attachment to the JVM is that no other Lisp has the same level of support for web applications. The second reason may be something about performance, but we

Re: [racket-users] Intro and projects inquiry

On Oct 13, 2017, at 9:44 AM, 'Royall Spence' via Racket Users wrote: > Since we're bikeshedding here, I think we'd benefit from having a web > toolkit on par with Clojure's Luminus. We only need a few more packages, > a website documenting their interoperation, and a project skeleton to > create

Re: [racket-users] Intro and projects inquiry

In my experience, it means two seemingly opposite things that unify to create bad software. On the one hand, it's an extreme conservatism and fear of attempting new things. Don't try a new language, just keep using PHP. Don't install the new PHP version with better features, it could be risky.

Re: [racket-users] Intro and projects inquiry

So someone should organize a loosely connected group to port the core of Racket to the JVM: — racket — the macro system — all non-GUI libraries and provide a Clojure-style way to leverage the GUI libraries. -- You received this message because you are subscribed to the Google Groups

Re: [racket-users] Intro and projects inquiry

On Fri, Oct 13, 2017 at 2:27 AM, Eric Griffis wrote: > On Thu, Oct 12, 2017 at 9:31 AM David Storrs wrote: >> > Web dev culture is a bigger issue. > > Eric How so? -- You received this message because you are subscribed to the Google Groups "Racket

Re: [racket-users] Intro and projects inquiry

On Thu, Oct 12, 2017 at 9:31 AM David Storrs wrote: > My suggestion would be that the single largest thing that would make > Racket take off is if it could become a replacement for Javascript. RacketScript Playground does not optimize tail calls. If it turned ES6 strict

Re: [racket-users] Intro and projects inquiry

I think a prominent cross platform GUI application which demonstrates the quality of interface you can get with relatively little effort in Racket would go a long way. I find JAVA GUI s to be painful. There is also a Python cross platform GUI but, judging by PgAdmin 4, I'm not impressed. A

Re: [racket-users] Intro and projects inquiry

On Thu, Oct 12, 2017 at 10:02 PM, David Storrs wrote: > On Thu, Oct 12, 2017 at 5:27 PM, Andrew Gwozdziewycz wrote: >> We need people building tools and blogging about why using Racket made > I agree that talking about how great Racket is will be an

Re: [racket-users] Intro and projects inquiry

On Thu, Oct 12, 2017 at 5:27 PM, Andrew Gwozdziewycz wrote: > I love seeing all of these project ideas, but I really don't think > Racket needs a "killer app." I think what it needs is the people > passionate about it building tools in it, and *using* those tools in > the work

Re: [racket-users] Intro and projects inquiry

I love seeing all of these project ideas, but I really don't think Racket needs a "killer app." I think what it needs is the people passionate about it building tools in it, and *using* those tools in the work place, and sharing the experiences of using those tools more vocally. We need people

Re: [racket-users] Intro and projects inquiry

On Thu, Oct 12, 2017 at 4:09 PM, James wrote: > > 5. #lang R or some other method to combine Racket and R - We need to go to > R for computational work because that's what is trusted in the field. I published a package called opencpu (

Re: [racket-users] Intro and projects inquiry

> Does a killer app or library sorely need a Racket alternative? Let me throw out a few things which we would use in our business even if they are not the most pressing needs in general. We have ways to work around these things but It would be much nicer to have a Racket native solution. I

Re: [racket-users] Intro and projects inquiry

> I enjoyed following the graph drawing thread a few weeks ago. A serious > attempt at "better than graphviz" could be fun and worthwhile. I was going to reply to that thread as well but didn't get to it. There is a great need for something like this in bioinformatics. Down the road a bit,

Re: [racket-users] Intro and projects inquiry

David’s reference is to Vishesh’s RacketScript. Please see (seventh RacketCon). Contributions welcome. > On Oct 12, 2017, at 1:00 PM, 'Royall Spence' via Racket Users > wrote: > > Unfortunately, Whalesong's current fork requires an old version of Racket and

Re: [racket-users] Intro and projects inquiry

Unfortunately, Whalesong's current fork requires an old version of Racket and hasn't seen a commit to master in several months. Racketscript is under active development, though, and provides a mostly- complete implementation of Racket for Javascript. Seems comparable to Clojurescript in its

Re: [racket-users] Intro and projects inquiry

Apparently Whalesong is such an alterntiave. https://github.com/jashkenas/coffeescript/wiki/list-of-languages-that-compile-to-js A Lisp dialect, Clojure, has caused a lot of young folks to ask questions/to think about Lisp ( https://m.oursky.com/why-i-chose-clojure-over-javascript-24f045daab7e).

Re: [racket-users] Intro and projects inquiry

My suggestion would be that the single largest thing that would make Racket take off is if it could become a replacement for Javascript. The browser is the default GUI for most work these days, and doing real-time interfaces in the browser requires Javascript. If Racket could run inside the

Re: [racket-users] Intro and projects inquiry

Eric Griffis wrote on 10/11/2017 07:44 PM: On Wed, Oct 11, 2017 at 2:58 PM Neil Van Dyke > wrote: * Being there soon with a Web Assembly and HTML5 plus server full-stack story, in case developers respond favorably to that. Web

Re: [racket-users] Intro and projects inquiry

> > Web back-ends are my wheelhouse. It sure would make my professional life > easier... Not gonna lie, this isn't something I'd look forward to banging > out alone. > I've been looking into web stuff for Racket quite a bit, specifically web microservices. Shoot me an email if you're

Re: [racket-users] Intro and projects inquiry

On Wed, Oct 11, 2017 at 2:58 PM Neil Van Dyke wrote: > > * Being there soon with a Web Assembly and HTML5 plus server full-stack > story, in case developers respond favorably to that. > Web back-ends are my wheelhouse. It sure would make my professional life easier... Not

Re: [racket-users] Intro and projects inquiry

Great topic! Providing examples and tutorials around data analysis and visualisation in Racket (and filling gaps and simplifying) gets my vote. Another area that might be interesting is generating data-driven web-sites: e.g. presenting questionnaires and quizzes. I recently did a bit of

Re: [racket-users] Intro and projects inquiry

Welcome, Eric. That "Intro Projects" github wiki page doesn't really distinguish between "here's a very beginner exercise for learning experience", "here's something that might be fun for you to do, and maybe someone else will use it someday", and "doing this would likely advance Racket

Re: [racket-users] Intro and projects inquiry

Thanks for the quick reply. My goal is to make Racket more relevant for general engineering and application development. For example, I asked my scientist brother why he's using Python instead of Racket on his next project. His response: "but would I have to write my own routines for calculating

Re: [racket-users] Intro and projects inquiry

Eric, I don’t mean to inadvertently kill any conversations, but I wanted to point out that there is an existing list of Racket projects on the Racket GitHub wiki: https://github.com/racket/racket/wiki/Intro-Projects It hasn’t seen an update in a while, so some of those may be solved or have