screenshotbot-oss VS schema

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.

Plumatic schema (https://github.com/plumatic/schema) , or friends I might be wrong, but I think schema might make more sense to you coming from the F# world (might be wrong)

This one? I didn't. I hear good things about it, and it's reached a point of maturity, being widely used in production.

Uhhh spec has existed for a long time and before that, schema Nowadays we also have the excellent malli. If his codebase is full of functions where the shape of the data isn’t obvious, isn’t documented and isn’t specified in a specific/schema, that’s on him and his bad coding practices and really no different from passing data in other dynamic languages. A class by itself (without additional effort) only gives you field names.

I don't understand this reputation either. There are very large systems built on other Lisps. For example, Emacs has a massive amount of Elisp. Elisp is much more primitive than Clojure, and traditionally libraries don't use e.g. data schemas [1] as runtime contracts for data.

Obviously, once a system built on top of a dynamic language grows beyond certain threshold, you need to be very disciplined as there are no static types to ensure some degree of correctness.

[1] https://github.com/plumatic/schema

Try to learn a schema library early, like Malli or Prismatic Schema. Do not mistook them as "static-typing" things - it's more for data validation and coercion than "security that things will get the right typing information". The idea to learn them early is how you'll shape future code: validating all "output data" first, them using that data inside your program without "defensive programming" like checking every time if a specific value on a map is nil, etc

In Clojure, declarative data specifications for validation and generation are also very mainstream. Schema was first out the door, Clojure Spec is the most popular library, while malli is gaining popularity fast at the moment.