cuttle VS LIPS

I got started in web development by building a full stack web app to play my favorite card game, Cuttle, pvp. Now that I'm working in the industry, I've open sourced the project and I continuously improve it with the help of other contributors. Here's the live deployment and here's the code.

The app is live at https://cuttle.cards and actively in (modest) use. We are continuously improving it, and you can practice essentially any part of the full stack by contributing. Here’s the code. The app is a Vue3 SPA with a nodejs backend (using sailsjs), and a postgres database, and we use cypress for the bulk of our automated testing.

Everyone is welcome! The best way to get started is to join us on discord where you can chat with me and the other devs about setting up and picking your first issue. Otherwise feel free to grab any of the issues on our github!

For one thing, you're welcome to join our discord where you can chat with me and other contributors (players too). I'd be happy to help you find a first issue to contribute. Regardless, feel free to check out our issue list to see if there are any you'd like to take a crack at.

For what it’s worth, I’ve open sourced my project (here’s the code) so if anyone would like to practice full stack web development skills by working on the oldest known combat card game, come check it out! We have five tournaments every year and open play sessions twice a week so your contributions will be used by real people in a live environment

Here’s the code

Cuttle is my favorite card game and I learned web development by creating cuttle.cards: an open source, fullstack pvp web app where people can play Cuttle online, for free! The app uses a postgresql database, a nodejs backend and a vue3 front-end. Here's the code.

I use websockets in my card game project: cuttle.cards as the way of updating all the players when someone makes a move. Here’s the code.

It’s a full stack web app with a Vue frontend and a nodejs backend built with the sailsjs framework. Here’s the code. The project is open source and under continuous development to improve the player experience.

We don’t have the full team structure that you’d see in a professional setting, but we have 5 core engineers including myself who work consistently on the project and a number of other contributors at various levels of experience. Here’s the repo. If any of that interests you, hit me up!

Sweet, I'll have to give that a go :)

Another option in browser land is lips[0], which exclusively targets a js backend.

[0] https://lips.js.org

For Scheme implementations there are LIPS and biwascheme. I haven't done more than play around with them, so I can't really give an informed opinion about pros and cons or favorites.

Your example revealed a bug in my Scheme interpreter. This is an example that fails to match:

In my interpreter, LIPS Scheme, vector literal syntax is created using a syntax extension, a token that is mapped to a function or a macro. So you can use things like this:

I'm not sure about other Scheme interpreters but in my interpreter LIPS Scheme, there is (env) function that returns a list of symbols. You can also access environment objects e.g. (current-environment) return object that is used internally. And you can even access the scope chain because the env object has __parent__ property that returns the parent scope.

Few of my Open Source projects: * jQuery terminal * LIPS Scheme * Gaiman * Sysend * Wayne

(define promise (--> '>(fetch "https://lips.js.org/") (then (lambda (res) (res.text))) (then (lambda (text) (. (text.match #/\s*([^>]+?)\s*<\/h1>/) 1)))))

ngl when I first saw the headline my first thought was, “Wait, bring CAR into JavaScript? Make it a Lisp? But hasn't it already been done?”

Languages like Biwa Scheme and LIPS Scheme are good for running Scheme in the browser. But I would prefer compiling Scheme code to JavaScript in the server, then serving the compiled JavaScript image to the browser.