lips

I've created [jQuery Terminal][0] in about 2010 I think it was first library that allow to create CLI applications in Browser. I've started it because I wanted to have SSH like experience on my shared hosting that didn't provide SSH access. I've build application using my Terminal, called [Leash][1]. I don't use it anymore because my current shared hosting have SSH. I've also build [sysend.js][2] (random name with send at the end). It's for sending messages between Open Tabs, It have nice API and it works in all modern browsers and even some older ones like IE11. I didn't know any existing library that did the same, that's why I've created one. Another library of mine is [Tagger][3], because there where no Vanilla JavaScript library like this. I needed it for StackOverflow Q&A site that I've started, but abandoned and it was inspired by S

I'm working on my Scheme based lips interpreter in JavaScript. With great integration with JavaScript, literal regular expression, auto async/await (with option to quote the promise), self documented like ELisp. I'm working on compatibility with R7RS, recently implemented rest of the functions from R5RS. Big part of the standard library is written in Scheme (small LIPS core) and I'm also working right now on Rollup plugin that will allow to created one bundle for all the Scheme code is I no longer need to load them with Ajax. What's missing are continuations and proper tail calls. And syntax-rules macros need to be heavy refactored (I need to add proper expansion time). If you want to take a look make sure to check out 1.0 Beta version, that is completely different than what's suppose to be stable version. Website: https://lips.js.org/ Gi

[ To save readers a search, LIPS is at https://github.com/jcubic/lips ] I'm happy that eslisp has inspired other language ideas. LIPS is cool. The auto-resolving Promise feature is a great idea that's only really possible when you implement the language as an interpreter like you have. Generated code for that would be a mess... I agree about the (. console log) thing. Such a common operation should be easy to type. I only did it this way to avoid adding any more syntax to the language, because I thought I could solve that problem later by making the syntax configurable by users. ...which I haven't really done well yet. Eslisp has a system called _transform macros_, one of which is https://github.com/anko/eslisp-propertify which turns `console.log` atoms into `(. console log)`, making the syntax legal. The transform macro system is

Quite neat indeed, will give it a try. Curious to see how it compares to https://github.com/jcubic/lips and ClojureScript.