"we" didn't pass them --- i don't think changing the severity of law enforcement alone can achieve what i wish for in society, but the existence of many laws (and severity of their punishment) i disagree with and thus do not want enforced
janet has replaced sh, python, awk, etc. for me, for system scripts over a certain length! it has a very fast startup time (on my system, 1.4ms via hyperfine vs. 1ms for dash) for scripts (not compiled executables), and its sh-dsl module allows typing shell commands very elegantly, like ($ cmda w x | cmdb y z). the ability to load an image to debug is a big help, too. i've started using it very recently but it's probably one of my favorite languages now, and the only other lisp i've used is mit scheme for sicp.
This is a great comparison and I've been wondering about it for a while.
Between babashka, janet(i discovered it just now), fennel, guile.
Which one would be a better scripting language?
Please tell me you experience, and if you are interested, we can work on a small article and benchmark about this.
It's platform-dependent isn't it? Otherwise, the practical differences between Lisp dialects are negligible. For me writing either in Janet or Fennel or Clojure feels almost like writing in the same language.
Babashka has replaced bash-scripting for me. I don't hate Bash, but why would I ever choose to use a language that has no true REPL, if I don't have to? bb is pretty much Clojure, which is the greatest choice if you're dealing with data - any data. Clojure is incredibly data-driven, which wins me over Janet. I also reach out to nbb whenever I need to deal with Node. e.g. scraping scripts driven by Playwright.
Janet is great when you need tiny runtime or you're dealing with subprocess-heavy scripts - Janet feels closer to actual shell syntax; or when you have to embed it to C/C++ program.
Fennel is indispensable for any Lua - mpv, Hammerspoon, AwesomeWM and Neovim configs, etc.
> Clojure is incredibly data-driven, which wins me over Janet.
I'm curious what differences you see? I've been all in on Janet, but barely used Clojure. What more data driven aspects does Clojure have .... offer? My mental model/assumption's always been that Janet's Clojure without JVM and (sadly) not so pure. I don't use any of Janet's C interop facilities. I'd love to know what I'm missing
afaik, Janet's immutable structs/tuples are flat copies - no structural sharing. Clojure uses HAMTs. So it's truly immutable by default - you'd transform data without intermediate allocations.
In Clojure, the standard library already knows about your data - it has the tools to group, index, validate, serialize, and transform maps/vectors/sets without you reinventing them. In Janet, you have the building blocks but it feels like you're assembling the furniture yourself.
The trade-off is that babashka adds ~200ms to cold start and can be pretty memory hungry, but god, Clojure is so nice to deal with data. For small scripts it may not matter. For processing log files or CSVs with millions of rows, it does.
this is good to know :) my use for janet hasn't involved much processing of external data but i'll keep bb in mind when the use case arises. thank you for the information!
True. But for things that they all can do, normal scripting (replacing bash/powershell, etc.), creating CLI and TUI apps, I would like to do a comparison of them.
1. which one is more pleasant to write
2. which one has the better echo system and tooling
3. performance benchmarks
4. portability
AI is already in a bunch of creative workflows. Just look at modern Photoshop. Selecting and hitting delete has AI infill for the background replacement.
Creates can these video gen AI in various ways. There are some youtube channels of people using these in creative workflows that are really impressive, from mocap replacement, character insertion, background replacement, changing camera angle in post, animating/inserting characters from character boards, animated between stills generated in traditional methods, etc. It's not just "prompt and generate". It can be, because it's easy, but it also doesn't have to be. It's a tool.
I do wonder how studios are working around consistent human faces, it's a problem on almost every discussion forum I have read for AI videos and not something that seems to be solved yet.
Do you have any examples of those creative workflows that have made it into Hollywood for example?
i do photo restoration as part of my research (bizarre place to be for a math undergrad), so i do think AI is a lifesaver for very small adjustments that would be tedious or subpar otherwise. i just disagree that its creative output is of value (which isn't the case you made, anyway).
Is there a description of this project on any other site? They clearly can't post it's bot bait on the git repo, and maybe not on the leaderboards site because it's linked from the repo.
But there must be some announcement about the project somewhere? I'd like to get that to pass it around.
The disclosure about being a honeypot is in the CONTRIBUTING.md:
Warning
Heads up: This is a research project — bounties listed here are symbolic and part of an academic study on open-source contribution patterns. PRs are reviewed for research purposes only and will not be merged into production. If you're looking for paid bounty work, this is not the right repo.
Which makes it slightly surprising those bots with system prompts to find "high value bug bounty targets" or similar aren't deterred by that when they pull the repo.
I guess a sort of task blindness where once they've gone as far as to git clone they've already switched gears from searching Github for qualifying bounties into a find bug->fix bug->open slop PR mindset to close the loop and end the turn? By that point an incidental warning they ingest in passing while looking for the Solana contract vulnerability they already committed to working on in a comment might not even register as relevant to the current task at hand.
Yeah but if I want to pass it to friends I need a link describing the project. I could write a summary myself but they may ignore it or find it too hard to verify.
the original kakoune is just cli; the binary has a json ui client option to allow communication with the kakoune server, with the intent of any gui or alternative client being separated from the kak binary/repo. that being said, this seems entirely ai-generated :( i had planned to write a kakoune frontend that supported rtl text (arabic in particular) + unicode, prop fonts, etc., and might look to how some things were done here, but i'd be blown away if this didn't have a great number of rough edges w.r.t. line wrap, unicode, rtl, etc. ...
just got my stickers from there yesterday! :-) i wish my less cs-oriented friends could see how cool i think the sdf is, lol; and, that some kind of "small-web" system, complete with the self-expression the sdf offers via web-hosting, a radio station(!), etc., was accessible to more people (not at the fault of anyone; just that there's a lot to the internet that most people will never see). :>
reply