Before that, i only started them and lost motivation after ~2 weeks. The projects a wanted to do were cyclic though, so i often came back to restart things i had left unfinished.
It took me time to change that, but the main thing i did was starting with extremely limited projects, that i knew i could finish in 2 weeks. I did very basic things at the beginning, like hosting a pure html website (but it was by first website i hosted, with nginx and certbot). Sometimes i would get back to it and improve something, like styling, text, SEO,...
I say "finished" because the bottleneck is finding users, not the code. So i still work on these projects, but not at the same speed.
Not that I know every French people
Antilisp is a Lisp designed for code generation in non-lisp languages. The interpreter is written in RPython, and the language is designed for easy adoption by non-lispers. The project is still young, but the language can be played with if you don't mind missing some important features like modules and pattern matching.I have not published the source code yet, because I am not completely sure...
The language is heavily inspired by Python for the dev UX, and the interpreter is written in RPython (what Pypy uses). Rewriting to RPython was tedious, but the 80x speedup was worth it.
There are only so many language implementers, and many opportunities to innovate in language design become obvious when it's your turn to decide what to implement.
For example, I made macros and axioms first-class citizens of the language as special cases of the function type, because using an interpreter allowed me to decide how things should be ewaluated at runtime. I accidentally found a trivial way to bootstrap (quote) in my language. I also found a way to make a much more general reader macro system by simply writing a modular value reader that can be extended by adding new elements to a list of parsers. This make non-lisp syntaxes like JSON much easier to implement than with the CL reader macro system where reader macros are bound to some special parameters.
Note for context: In my case, the Lisp interpreter is under 3KLoC, and most of the abstractions are bootstrapped from macros and reflection primitives, or primitive that are shadowed by higher level builtins.
Location: Paris, France
Remote: Open to Remote/Office/Hybrid
Willing to relocate: Yes
Technologies: Python, Django, Flask, FastAPI, PostgreSQL, Linux, Docker, Asterisk,...
Résumé/CV: https://antilisp.com/static/resume.pdf
Email: [email protected]