oh
mu
oh | mu | |
---|---|---|
6 | 29 | |
1,344 | 1,344 | |
- | - | |
4.3 | 4.3 | |
8 months ago | 5 months ago | |
Go | Assembly | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
oh
- Understanding the Power of Lisp (2020)
- Bass – Lisp dialect for scripting the infrastructure beneath your project
-
CommandConsole: A shell written in C
I think an extensible shell like oh shell would be something I would prefer. Though it should not need closures on heap to extend (which is ridolous slow on arithmetic) and generate the data types at compilation time.
-
Bash functions are better than I thought
> Is there a reason we aren’t using a shell with a proper programming language for scripting?
Mostly because the people who want to introduce a "programming language" into the shell don't prioritize being a shell.
Check out the "Oh" shell for contrast. This is what a programming language looks like when you force it to conform to being a shell first priority.
https://github.com/michaelmacinnis/oh
https://www.youtube.com/watch?v=v1m-WEZz46U
This is "Scheme-like" but has FEXPRs so things can be redefined and evaluation can be controlled.
-
Show HN: SectorLISP Now Fits in One Sector
I love chatting about Kernel :D Here's my most recent post: https://lobste.rs/s/d0hogq/problem_with_macros#c_nozcrm
Thanks for showing me Oh! It really has f-exprs?! I didn't immediately see it in https://github.com/michaelmacinnis/oh/blob/main/doc/manual.m...
- Oh, a New Unix Shell
mu
-
Damn Small Linux 2024
Depending on how minimal a distribution you want, a few years ago I had a way to take a single ELF binary created by my computing stack built up from machine code (https://github.com/akkartik/mu) and package it up with just a linux kernel and syslinux (whatever _that_ is) to create a bootable disk image I could then ship to a cloud server (https://akkartik.name/post/iso-on-linode, though I don't use Linode anymore these days) and run on a VPS to create a truly minimal webserver. If this seems at all relevant I'd be happy to answer questions or help out.
- Ask HN: Good Books on Philosophy of Engineering
-
x86-64 Assembly Language Programming with Ubuntu by Ed Jorgensen
This was the thinking behind my https://github.com/akkartik/mu
- Show HN: FocusedEdit – a classic Macintosh to web browser shared text editor
-
Plain Text. With Lines
Yes thank you, I was indeed alluding to https://github.com/akkartik/mu. Perhaps a more precise term would be "software stack".
-
Inferno: A small operating system for building crossplatform distributed systems
I built a computer with its own languages, and I consider it to be _less_ cognitive load when everything is in 1/2/3 languages. I don't have to worry that the next program I want to read the sources will require "Go, Rust, C++, JS/TS, Python, Java, etc."
There are other metrics to consider besides your notions of cognitive load and productivity. Inferno predates most of the languages on your list. My computer (https://github.com/akkartik/mu) uses custom languages because I was able to design them to minimize total LoC, and to ensure the dependency graph has no cycles (unlike all of the conventional software stack, at least until https://www.gnu.org/software/mes connects up all the dots).
- Llisp: Lisp in Lisp
-
10 Years Against Division of Labor in Software
"Separation of concerns is a hard-won insight."
Absolutely. I'm arguing for separating just concerns, without entangling them with considerations of people.
It's certainly reasonable to consider my projects toy. I consider them research:
* https://github.com/akkartik/mu
* https://github.com/akkartik/teliva
"The idea that projects should take source copies instead of library dependencies is just kind of nuts..."
The idea that projects should take copies seems about symmetric to me with taking pointers. Call by value vs call by reference. We just haven't had 50 years of tooling to support copies. Where would we be by now if we had devoted equal resources to both branches?
"...at least for large libraries."
How are these large libraries going for ya? Log4j wasn't exactly a shining example of the human race at its best. We're trying to run before we can walk.
-
My self-hosting infrastructure, fully automated
I still believe :) I'm looking not for an economic argument but for a strategic one. I think[1] a self-hosted setup with minimal dependencies can be more resilient than a conventional one, whether with a vendor or self-hosted.
https://sandstorm.io got a lot right. I wish they'd paid more attention to upgrade burdens.
[1] https://github.com/akkartik/mu
-
My 486 Server
I'm very interested in the network stack, having explored it for a while for https://github.com/akkartik/mu before giving up. What sort of network card do you support?
What are some alternatives?
elvish - Powerful scripting language & Versatile interactive shell
cosmopolitan - build-once run-anywhere c library
sicp - HTML5/EPUB3 version of SICP
mtpng - A parallelized PNG encoder in Rust
cl-unix-cybernetics - UNIX system administration in Common Lisp
collapseos - Bootstrap post-collapse technology
nsd - NGS Scripts Dumpster
mirage - MirageOS is a library operating system that constructs unikernels
hasura-ci-cd-action
librope - UTF-8 rope library for C
PPSS - Parallel Processing Shell Script
teliva - Fork of Lua 5.1 to encourage end-user programming