Thanks for the idea, I’ll try to add a comparison page soon!

The vertical alignement is now fixed, I got lucky with bootstrap ; it looks way nicer, thanks!

Jokes on them, I don’t use this AI bullshit.

« America, fuck yeah » takes a whole new meaning

Also, just to check, do you have a time limit set for the Playground so that people do not over-tax your system?

I double-checked, and it seems my timeout command was incorrect. I set it up again (with additional testing), and it now properly kills the container(s) after 20 seconds.

Thanks for your comment!

That’s a tough question, because it often boils down to preferences. I think a beginner developer or even someone fed up with the complexity of modern languages could be interested in the language, as it is very small but still more than usable. Only 9 keywords, no hidden meaning, everything follows the same rules : open a paren, then the first thing is a function call, the rest are arguments. I think the « lisps have too many parentheses » is a false problem only used by trolls. I won’t say that you have to understand the flow or fall into the matrix to use it and avoid the parens, it’s more about having a consistent coding style so that you don’t have to care about the closing parentheses. Plus with a modern editor, parentheses groups have different colors and are easy to match, you can navigate to the starting / closing paren with a keybind (% in vim, command/ctrl M in jetbrains IDE).

I’m no frontend dev, so I battle a lot with it so it displays how I want ; I tried with flex to center vertically the « getting started » section, will have to try again.

Yes, there is a time, cpu and memory limit to the playground, no worries! I started the playground about a year ago but only just recently managed to compile to wasm, I’ll see in the future if I can swap the docker integration for it.

This smells like bullshit because it’s just based on things users do not see (processes) or do not care about (the style used for your tabs).