Re:Release Announcement for Racket 6.10
by shakna on Monday July 31, 2017 @10:23PM
(#14897455)
I have in the past, as a web server.
It used Racket's inbuilt Threads, http constructors, and the only external package, db-lib, to talk to Postgres.
Supported about ~12,000 long-lasting connections/min for the first 48hrs, without dropping or being overly slow.
Lack of some libraries weren't really an issue, because:
* Typed, Lazy and normal Racket can all talk to each other easily.
* Re-inventing the wheel is ridiculously easy and quick in Racket.
* Re-writing something from SLIB [0], is a five minute thing, if you need to make any changes.
* Racket has a decent FFI, and wrapping C is simple. (There is also progress for talking to Java)
Add to that, for most people Python is easy. And when they get used to parentheses, most of my team were surprised to find Racket is a lot like Python, which meant fast iteration, with better performance than Python, but less opinion.
It used Racket's inbuilt Threads, http constructors, and the only external package, db-lib, to talk to Postgres.
Supported about ~12,000 long-lasting connections/min for the first 48hrs, without dropping or being overly slow.
Lack of some libraries weren't really an issue, because:
* Typed, Lazy and normal Racket can all talk to each other easily.
* Re-inventing the wheel is ridiculously easy and quick in Racket.
* Re-writing something from SLIB [0], is a five minute thing, if you need to make any changes.
* Racket has a decent FFI, and wrapping C is simple. (There is also progress for talking to Java)
Add to that, for most people Python is easy. And when they get used to parentheses, most of my team were surprised to find Racket is a lot like Python, which meant fast iteration, with better performance than Python, but less opinion.
[0] http://people.csail.mit.edu/jaffer/SLIB