sergej
2019-8-9 12:09:18

The home page link to Racket 7.4 in the News section is broken: leads to https://blog.racket-lang.org/2019/05/racket-v7-4.html, should probably lead to https://blog.racket-lang.org/2019/08/racket-v7-4.html instead


nma.arvydas.silanskas
2019-8-9 13:10:18

is there somewhere a comparison of racket with other feature-packed schemes like chicken?


nma.arvydas.silanskas
2019-8-9 13:11:40

the ones I find are very shallow and short


spdegabrielle
2019-8-9 13:18:05

I don’t know of any - the closest I can think of is the ‘racket features’ page on Wikipedia - but that isn’t contrasting :racket-flat: Racket with other schemes.


spdegabrielle
2019-8-9 13:35:16

There isn’t really enough there for a blog. The hard work is done by raco pkg new. I just loaded the results into a repo and marked it as a template adding a few github specific features along the way. I’m not sure a template repository is a right approach - maybe extending raco pkg new to support git/github/gitlab is a better path. (and adding a gui in DrRacket )


jarcane
2019-8-9 13:40:38

depends on the features you mean?


jarcane
2019-8-9 13:40:42

There’s a hyperpolyglot list


jarcane
2019-8-9 13:41:13

ahh, never mind that doesn’t have any other Schemes


nma.arvydas.silanskas
2019-8-9 13:50:09

well the big ones like pattern matching, generics, contracts / static typing, ffi


jarcane
2019-8-9 14:07:11

where is the documentation for building a custom printer?


jarcane
2019-8-9 14:07:33

Or extending the built-in one


jarcane
2019-8-9 14:08:16

Heresy objects are implemented as lambdas, and this is a problem with respect to printing.


jarcane
2019-8-9 14:08:47

I want them to be able to print some more readable representation


ryanc
2019-8-9 14:11:54

@jarcane you probably need to represent your objects using a struct type that has the struct-type properties prop:custom-write (to customize printing) and prop:procedure (to make them act like procedures).


jarcane
2019-8-9 14:18:27

oooh, yes, this could work maybe


jarcane
2019-8-9 14:18:44

Without too much retrofitting even. Maybe.


steveh2009
2019-8-9 14:57:28

I share your sentiments and concerns. I’m an okd programmer but decided to pick up Racket when I was looking for a Lisp for my personal projects (in real-time trading). Given the possible future, it’s probably in my best interest to port my work as I go to Clojure and sbcl. Just my opinion, but since Racket was borne from academia, I think the key researchers there feel they need to maintain a fertile ground from which to produce papers, masters/PhD research, etc. Walmart is running Clojure for backend online order handling so I think that pretty much dismisses the s-exp argument as a deterrent to growing popularity. Like you, I will go with the flow until that flow doesn’t suit my needs. Thanks for you thoughtful replies on the subject!


badkins
2019-8-9 15:09:24

@steveh2009 I wouldn’t jump ship just yet. My hope is that #lang racket will become the stable, industrial strength branch :slightly_smiling_face: It’s a mature language by now, and the fact that it will be able to utilize modules written in the new language (and vice versa) means that the library situation, which is already great, will get even better for both languages. I expect we’ll get some clarification of the roadmap in coming weeks.


asumu
2019-8-9 20:57:42

Is this statement from the build README true for the 7.4 release too? > Chez Scheme is included in a Racket source distribution and configure detects that source, so no separate download or Git checkout is needed in that case. I couldn’t find it but maybe I didn’t look hard enough


samth
2019-8-9 20:58:11

That’s a mistake in the packaging for the RacketCS source distribution


samth
2019-8-9 20:58:27

Also noticed earlier today by @jbclements (cc @mflatt)


asumu
2019-8-9 20:58:48

Oh ok, I will wait on that getting resolved for a Racket CS PPA then


rljacobson
2019-8-10 03:02:07

Is Racket CS the recommended Racket distribution?


sorawee
2019-8-10 04:33:51

From the release note:

> Racket CS is “beta” quality for the v7.4 release. It works well enough to be worth trying, but there are likely too many lingering problems for a project to switch to Racket CS for production use at this time. We encourage you to kick the tires of the new CS releases, and to help push this project forward by reporting any problems that you find.