(no title)
priime0 | 2 years ago
It's very much possible to use Racket without interacting with macros and language-building features.
> Racket / typed Racket should focus on more production/libraries for regular programmer
Libraries are dependent on the community, which unfortunately is comprised of mostly academic folk at the moment.
> DrRacket always felt and looked alien to me. I can't really judge the feature set, but having vscode as the defacto IDE i think would be it more welcoming
I do agree -- if I remember correctly, DrRacket was primarily built as a pedagogic IDE, not one meant for more professional use. VSCode, however, does have the "Magic Racket" extension.
> This one is will definitively be controversial but introduce a "curly brace"/C style syntax for Racket.
Not necessarily C-style syntax, but you could take a look at Rhombus. It's meant to have a more approachable syntax compared to S-expressions.
soulbadguy|2 years ago
I would say that macros are integral part of Racket, maybe event the best part.
But point is not about what is possible, it's really about what is the default/obvious part. It wasn't a comment on racket the language, but more about the environement around the language.
> Libraries are dependent on the community, which unfortunately is comprised of mostly academic folk at the moment.
I am not sure what point you are making here. Julia has a very very strong academic community, but the library ecosystem seems more production ready and actionable.
> Not necessarily C-style syntax, but you could take a look at Rhombus. It's meant to have a more approachable syntax compared to S-expressions.
Rhombus seems to be more than just alternate syntax. And how is the progress on this thing ?
I think to make racket more mainstream would need more than things that are "possible", or available etc... It probably need a cohesive story and experience around those, and that story to be at the for front on how Racket present itself : vs code extension as the main IDE, alt syntax + better libraries.