woo
prechelt-phone-number-enco
Our great sponsors
| woo | prechelt-phone-number-enco | |
|---|---|---|
| 15 | 3 | |
| 1,252 | - | |
| - | - | |
| 5.6 | - | |
| 4 months ago | - | |
| Common Lisp | ||
| MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
woo
- Learn Lisp the Hard Way
- Algorithms and data structures implemented in many programming languages
- Woo: A fast non-blocking HTTP server on top of libev
- Lisp can be Hard Real Time [pdf]
-
Help starting woo server
Can I ask you this though? Again, all I have in my file is what's under the "Start a server" section of the woo readme.
-
Does the Haskell client for Selenium still work?
For example, let's look at this project: https://github.com/fukamachi/woo
-
Struggling as a junior web developer
One of the nice things about Common Lisp is that it also has the fastest web server: https://github.com/fukamachi/woo
-
V Language Review (2022)
Here you have a web server written in Chez Scheme: https://github.com/guenchi/Igropyr So you see that Lisp is very suitable for web applications. Another project that proves that Lisp is excellent for web servers is Woo: https://github.com/fukamachi/woo
-
Is Woo still "beta quality" or prod ready?
I remember a long time ago when I checked out woo https://github.com/fukamachi/woo it still had the same warning "This software is still BETA quality." Is that really still the case? As of now, I'm seeing the last update was only 4 days ago, so it looks like it's been worked on relatively actively this whole time.
prechelt-phone-number-enco
-
Optimising Common Lisp to try and beat Java and Rust on phone encoding 2/2
> it’s using Unicode-aware string stuff
Rust uses UTF-8 internally for Strings, so it's very efficient to parse a file into a String, then using slices to go through it... this is probably the best you can get as parsing ASCII input as UTF-8 is very efficient (the 0-bit is always zero in ASCII, the unicode decoder only needs to check that's the case for every byte, so it's not some kind of complicated computation it's doing to decode)...
If you use bytes for everything, you will make the whole code much harder to follow and it still won't run faster.
Check for yourself: https://github.com/renatoathaydes/prechelt-phone-number-enco...
-
Learning Common Lisp to beat Java and Rust on a phone encoding problem
This is a pretty introductory CL article, mostly a commentary on Norvig's solution to the problem. Still, I learned about the #. readmacro from it. The conclusion: "[The Lisp implementation] was the fastest implementation for all input sizes except the largest one, where it performed just slightly worse than my best Java implementation." GH repo at https://github.com/renatoathaydes/prechelt-phone-number-enco.... Sounds like he was mostly measuring the performance of the SBCL bignum implementation.
-
How to write slow Rust code
source: https://github.com/renatoathaydes/prechelt-phone-number-enco...
What are some alternatives?
wookie - Asynchronous HTTP server in common lisp
prechelt-phone-number-encoding - Comparison between Java and Common Lisp solutions to a phone-encoding problem described by Prechelt
cl-tbnl-gserver-tmgr - Hunchentoot Gserver based taskmanager
prechelt-phone-number-encoding - Comparison between Java and Common Lisp solutions to a phone-encoding problem described by Prechelt
cl-cookbook - The Common Lisp Cookbook
jelm - Extreme Learning Machine in J
cl-async - Asynchronous IO library for Common Lisp.
snabl - a simple Go scripting language
bordeaux-threads - Portable shared-state concurrency for Common Lisp