#introductions Researching new ways to write software that make it easier for newcomers to understand rather than for insiders to maintain. Systems that build easy, reward curiosity. http://akkartik.name/about
#BarbarianProgrammer. Ethos: ship with all deps, gradually streamline their code for own situation, get ideas for improvements, send patches upstream. Implies: can't have too many deps!
@akkartik hey interesting idea! I love that it just lets me read the code without the typical rainbow barf, but gives semantic information about the comments. Which I guess are the best way to document assembly code.
My assembly language hasn't had much syntax highlighting, and I'm playing with a use for all those colors: 4 types of comments!
It took some doing to make them look ok on my 256-color terminal, but also pass the WCAG contrast checker. (They barely do.) Tell me what you think.
@akkartik If you want to play around with a new browser engine, I'm planning to start one soon. I want to show we can have a better web without JS.
Then again I'm looking to fork Servo's layout for it and reuse it's rendering.
Playing around with a whole new browser engine (written in Common Lisp!): https://next.atlas.engineer/quickstart
Algorithms that return “fruit” Show more
I wonder if there’s a method of programming that returns data as “fruit”. The part you want to “eat” is surrounded by inedible skin or thorns.
That is, are they any benefits of removing the constraint of having clean interoperable data.
Is there a way of programming that is less factory design and more garden tending?
@akkartik That's fantastic! Congratulations! What were the syscall changes you needed?
Did you ever try to work through Jack Crenshaw's "Let's build a compiler"? Remember the early point where you add a line of code and "CONGRATULATIONS! You have just written a working compiler!"?
Well, I just ported that one line (and the page of helpers backing it) to my own assembly lang, and it only took me 2 months to do it 😂
In my defense:
a) It's *thoroughly* unit-tested asm, and
b) I had to rethink the design of a couple of OS syscalls to make them testable.
One of my pet rabbitholes over the years has been quantifying the bloat in GNU `cat`, as a microcosm for the bloat in GNU projects in general. Umpteenth iteration: https://news.ycombinator.com/item?id=18436735#18438344
#PortSmash - New side-channel vulnerability on Intel SMT/Hyper-Threading architectures.
What an _amazing_ commit message: https://github.com/git/git/commit/433860f3d0
gender theory, unendorsed idle thought Show more
Childcare is such an onerous duty that some dudes would do just about anything to get out of it. Like forcing an entire gender into child-care-centric servitude by creating an entire political structure (patriarchy) around it, along with the religious/ideological justifications to support it, so women would do it all and they wouldn't have to.
Has most of human history been driven by a conspiracy of dads weaseling out of their share of the childcare?
So, because the existing X terminal emulators are kind of heavyweight, I wrote a new one yesterday and today. It compiles to just under 20 kilobytes, and I can run vi in it, although it needs some work. http://canonical.org/~kragen/sw/dev3/admu_shell.c is the main code, but it also uses admu.c, admu.h, xshmu.c, and xshmu.h. Basically if you want to compile it just git clone the whole directory. It won't work without a 24-bit X server. cc @jason @anthk @brennen @benrob0329 @kelbot @bobstechsite @trashyfins
Follow friends and discover new ones. Publish anything you want: links, pictures, text, video. This server is run by the main developers of the Mastodon project. Everyone is welcome as long as you follow our code of conduct!