Skip to content

Instantly share code, notes, and snippets.

@sogaiu
sogaiu / gist:58a86e29e584d0f24397b19e0be6eb61
Last active January 16, 2026 09:50
veqq naming and import response fragments
i do also happen to think that there are conditions under which english (/ human language) name being changed would be better for reasons i mentioned before, but this is less of an issue from the perspective of api breakage / use in codebases.
i think not changing english names can lead to a kind of confusion that i think it would be nice to avoid (cf. firefox situation) in communication as well as being potentially misleading.
searching for things later can also become more complicated by not changing names because one can end up with more stuff to sift through.
---
to clarify a bit of why i don't want to talk in terms of `import` so much is at least partly because it has complexities that make discussion and thought more cumbersome. listed at [this page](https://janet-lang.org/docs/modules.html) are relative imports, working directory imports, @-prefixed imports, and imports can be customzied a fair bit as well.
@sogaiu
sogaiu / gist:5ffeb2b969fda83836b3b967a25b8921
Created January 16, 2026 01:10
signal installation on debian-based
# NOTE: These instructions only work for 64-bit Debian-based
# Linux distributions such as Ubuntu, Mint etc.
# 1. Install our official public software signing key:
wget -O- https://updates.signal.org/desktop/apt/keys.asc | gpg --dearmor > signal-desktop-keyring.gpg;
cat signal-desktop-keyring.gpg | sudo tee /usr/share/keyrings/signal-desktop-keyring.gpg > /dev/null
# 2. Add our repository to your list of repositories:
wget -O signal-desktop.sources https://updates.signal.org/static/desktop/apt/signal-desktop.sources;
cat signal-desktop.sources | sudo tee /etc/apt/sources.list.d/signal-desktop.sources > /dev/null
* description
create and run certain "tests" that live in comment forms -
"comment-hidden expression tests".
* rationale
* want some meaningful "tests" / "usages" to co-evolve with
development from as early as desired with little activation
effort.
* repository organization
* make the main deliverable `<name>.janet` -- the extension is
important if wanting to be able to use as a library. nicest if
this deliverable sits in the repository root as well.
* for libraries, could still have a `<name>` directory that has the
content `init.janet` and `<name>.janet` for jpm / jeep
installation, but `<name>.janet` can still be used independently
as a single file library? would be nice to have `<name>.janet` at
$ cat sample.janet
(def a 1)
$ janet
Janet 1.40.1-7d672f43 linux/x64/gcc - '(doc)' for help
repl:1:> (import ./sample)
@{_ @{:value <cycle 0>} sample/a @{:private true}}
repl:2:> (import ./sample :export true)
@sogaiu
sogaiu / jeep-vendor-transition.txt
Created December 24, 2025 02:08
jeep vendor transition
deps number of projects
1 22
2 4
3 5
4 1
5 2
6 1
----
todo
(defn diff-path
[left right]
(var i 0)
(var done false)
(def [shorter longer]
(if (<= (length left) (length right))
[left right]
[right left]))
(for j 0 (length shorter)
(when (not= (get left j) (get right j))