screenshotbot-oss VS CIEL

Examples (for Common Lisp, so not citing Emacs): reddit v1, Google's ITA Software that powers airfare search engines (Kayak, Orbitz…), Postgres' pgloader (http://pgloader.io/), which was re-written from Python to Common Lisp, Opus Modus for music composition, the Maxima CAS, PTC 3D designer CAD software (used by big brands worldwide), Grammarly, Mirai, the 3D editor that designed Gollum's face, the ScoreCloud app that lets you whistle or play an instrument and get the music score,

but also the ACL2 theorem prover, used in the industry since the 90s, NASA's PVS provers and SPIKE scheduler used for Hubble and JWT, many companies in Quantum Computing, companies like SISCOG, who plans the transportation systems of european metropolis' underground since the 80s, Ravenpack who's into big-data analysis for financial services (they might be hiring), Keepit (https://www.keepit.com/), Pocket Change (Japan, https://www.pocket-change.jp/en/), the new Feetr in trading (https://feetr.io/, you can search HN), Airbus, Alstom, Planisware (https://planisware.com),

or also the open-source screenshotbot (https://screenshotbot.io), the Kandria game (https://kandria.com/),

and the companies in https://github.com/azzamsa/awesome-lisp-companies and on LispWorks and Allegro's Success Stories.

https://github.com/tamurashingo/reddit1.0/

http://opusmodus.com/

https://www.ptc.com/en/products/cad/3d-design

http://www.izware.com/mirai

https://apps.apple.com/us/app/scorecloud-express/id566535238

This LispWorks comment on reddit is very interesting:

---

[cite]

As a Lispworks user, yes it is super pricey, but it does make sense for certain people. Arguably, Lispworks provides features that aren't available in any other programming language, Lisp or not.

* Support for just about every platform I can imagine. Yes it's expensive, but if I want to port to a new platform I can pay Lispworks, and get it over with. It'll mostly work without too much changes. It works on Android, iOS, Windows, Linux, Mac, and some really obscure systems.

* Application delivery with tree shaking. May be there are other languages that do this, but I haven't worked with something like this before in my career. (Maybe proguard for Java, but that's very rudimentary compared to LW's delivery). The tool I work on delivers a binary that people need to download during the CI jobs for every run, so having it be 100MB is way too big. After compression, my LW delivered binaries come to around 9MB.

* You mention support being expensive. Actually, for simple support questions LW does a pretty good job of responding back to you. I've asked tonnes of questions over the years, and have not paid for a separate support contract apart from the yearly maintenance contract. I suspect they like people asking questions, because then they fix those bugs and it becomes even more rock solid.

* The documentation is glorious. And in the off-chance that I need to know something that's not documented, I just mail them and they'll respond usually by the next working day.

* Very stable Java support (although the API could be better), let's me use the entire Java ecosystem of libraries when I need it.

* The platform itself is rock-solid. Now SBCL is fantastic, but when I ran my servers on SBCL, I would have a crash every now and then. With LW, I can have my server running weeks (current uptime is a month) with reloading code multiple times a day, and everything is still super stable.

There's more, but I think the rest is more negotiable. For instance, the FLI is a lot more polished than using CFFI, which makes a huge difference in productivity when writing native code. Or the fact that its remote-debugger facility can be used as a very stable protocol to programmatically control a remote LW process. I don't use the IDE btw, so I'm not even considering that. I don't use CAPI either, but I mean to someday.

2023, Arnold @tdrhq of Screenshotbot (https://github.com/screenshotbot/screenshotbot-oss) on reddit: https://www.reddit.com/r/Common_Lisp/comments/11979q4/common...

[/cite]

You can avoid having to do the step of recording screenshots if you use a tool like Screenshotbot (https://github.com/screenshotbot/screenshotbot-oss) or Vizzy (https://github.com/workday/vizzy)

Oh yeah, github.com/screenshotbot/screenshotbot-oss :)

There are open source tools to achieve this workflow. I've personally built screenshotbot (https://screenshotbot.io / https://github.com/screenshotbot/screenshotbot-oss), I've also built the screenshot testing infrastructure at Facebook. Workday has open-sourced their own tool at https://github.com/workday/vizzy. AirBnb uses another commercial tool called Happo (https://happo.io). Use any of these services with Paparazzi.

There are a few open source tools to do this: there's a tool I built: https://github.com/screenshotbot/screenshotbot-oss similar to the infrastructure at Facebook, and there's another one built at Workday: https://github.com/workday/vizzy. These are screenshot-library agnostic services to notify you on Pull Requests when screenshots change.

Screenshotbot is completely open-source by the way: https://github.com/screenshotbot/screenshotbot-oss

So, I'm in the process of defining something I'm calling an easy-macro. (You can see the code here, but I'm going to extract this into a quicklisp library once I'm happy with it: https://github.com/screenshotbot/screenshotbot-oss/blob/main/src/util/macros.lisp)

I'm the author Screenshotbot (https://github.com/screenshotbot/screenshotbot-oss) , and I think this is exactly what you need. Although the README claims to not support browsers, it does actually support browsers, both in the open source and non open source version. I just need to update the docs.

and for CL: https://github.com/ciel-lang/CIEL/ (pre-alpha) CL with many batteries included (json, csv, http, CLI parser…) so the scripts start fast.

As a CL addict, this isn't unlike Babashka: fast-starting CL scripting with batteries included. https://github.com/ciel-lang/CIEL (alpha) (otherwise the solution is to build a binary)

> lots of interoperability libraries

That's true. For cases when you want to start with a good set of libraries (json, csv, databases, HTTP client, CLI args, language extensions…), I am putting up this collection together: https://github.com/ciel-lang/CIEL/ It can be used as a normal Quicklisp library, or as a core image (it then starts up instantly) or as a binary.

It can run scripts nearly instantly too (so it isn't unlike Babashka). We are ironing out the details, not at v1.0 yet.

> handling a runtime error by just fixing the broken code--in-place, without any restarts [from the blog]

Also (second shameless plug) I should have illustrated this here: https://www.youtube.com/watch?v=jBBS4FeY7XM

We run a long and intensive computation and, bad luck, we get an error in the last step. Instead of re-running everything again from zero, we get the interactive debugger, we go to the erroneous line, we compile the fixed function, we come back to the debugger, we choose a point on the stackframe to resume execution from (the last step), and we see our program pass. Hope this illustrates the feature well!

check out CIEL, one of it's goal is to be a quality terminal repl

I've been doing the protohackers challenges in common lisp to learn, and I ran into a problem that is possibly a bug in the socket library, or much more likely in my misunderstanding it. At any rate the best workaround a found seems pretty ugly, so can anyone advice what would be the cleanest way to solve it, and how we're supposed to deal with sockets? The problem is basically make a tcp server, that forwards all connections to an upstream server, and does a regex find and replace on all the traffic that passes through. Here's my working solution. I haven't learned much how asdf and packages work yet, I am just using CIEL which is SBCL (2.2.9.debian) with a bunch of libraries already loaded, I think if you load usocket, usocket-server, cl-ppcre, and bordeaux-threads it should run. The program is simple, I just forward all traffic from the client to the upstream doing regex replacement on each line, and spawn a thread that handles forwarding all traffic from the upstream to the client with the regex replacement. The issue is that when the client disconnects, my program doesn't disconnect from the upstream, even when I call (close upstream) and (socket-close socket). Before closing the socket or stream, the connection shows as established in ss -tp and as belonging to the sbcl process. After calling close on the socket and stream, the connection still shows as established, just it no longer shows as belonging to the sbcl process, and tcpdump shows that the 4-way termination handshake is not sent. After killing the background thread that is also reading the same socket, the 4-way termination is sent, and the connection is closed. It seems like calling close on the stream or socket should close it? Are sockets or streams not safe to share between threads? Is there a cleaner way to handle closing the upstream connection when the client disconnects rather than calling destroy thread?

I quite agree, so I'm making a meta-library to have useful libraries available out of the box: https://github.com/ciel-lang/CIEL/ It's CL, batteries included. You can use it as a library, as a core CL image (loads up faster), and as a binary to have a REPL, and to run scripts:

    ciel --script myscript.lisp

No, we have to build a binary, which starts up super quickly.

I began to put together a "distribution" of useful CL libraries for everyday tasks: https://github.com/ciel-lang/CIEL/ It comes as:

- a lisp core, which you can use in your editor setup instead of sbcl or ccl, the advantage is that it loads instantly with all these libraries built-in (instead of quickloading all of them when needed)

Hi there. I'd enjoy help on anything web development for openbookstore: https://github.com/OpenBookStore/openbookstore (especially now: setting up i18n) Or, we could work on the terminal REPL experience for the CIEL meta-package: https://github.com/ciel-lang/CIEL/ We could use a better base like cl-repl or better yet, Lish.