akkartik

61 ms·

901.
by akkartik 6y ago
Then there's the build dependencies of all the libraries. And of the compilers. It's quite possible a complete list would go all the way back to the original Unix or CP/M, passing through multiple architectures along the way.
902.
by akkartik 6y ago
Were your languages very high-level? If so, that kinda rhymes with my experience on past projects. The more expressive the language, the easier it is for programs to create combinatorial explosions that slow everything down if compiled naiv
903.
by akkartik 6y ago
Thank you! https://news.ycombinator.com/item?id=26525349#26529192 Did I miss anything?
904.
by akkartik 6y ago
Here's another interesting one I just noticed: https://github.com/attila-lendvai/maru/blob/maru.10/source/a...
905.
by akkartik 6y ago
Oh your project looks familiar. Though I might have seen it a long time ago. I'll take a closer look. > My reasoning is that as a human reader, the comment is the more readable part, so I'd want to see it first. And for a compu
906.
by akkartik 6y ago
The title seems fine! > Was that latter copying your content from somewhere? It had occurred to me that it might be a Markdown editing service. Maybe somebody tried it out with just the closest Markdown they happened to have on hand? How
907.
by akkartik 6y ago
Great questions! I've actually never considered putting the comment first! I'll have to think about that one. You're right to point out that there are two components to "C compilers written in C make compilers seem compl
908.
by akkartik 6y ago
Yeah, OP is probably not the best place to understand what the purpose of this project is. The list of opcodes is just a list for consulting. It's only about the opcodes, it says nothing about the expected arguments and so on. To und
909.
by akkartik 6y ago
Oh I'd missed that page on the blinkenlights site. Thanks!
910.
by akkartik 6y ago
Thanks for the pointer to terse! I hadn't seen it before. I think of concise as "expressive" or "cryptic". "Minimalist" usually connotes small implementation. Like chibicc or something.
911.
by akkartik 6y ago
List of supported instructions: https://github.com/akkartik/mu/blob/main/subx_opcodes I haven't tried to implement C, but can't immediately think of a reason why not. Forks strongly encouraged;
912.
by akkartik 6y ago
The stuff after / is often just comments. 'syscall' feels more accurate for int 80 than 'interrupt', but the language doesn't encode the name. I only found out about the octal after I started on SubX. I conside
913.
by akkartik 6y ago
Yeah! Most statements translate to a single instruction, and you have to pick registers, so even though performance hasn't been a priority I think it'll tend to be pretty good. It does have some simplifications for safety and clar
914.
by akkartik 6y ago
Not sure what's going on with this website, but I'm happy to see interest in my project: https://github.com/akkartik/mu#readme OP is an old version of the Readme from a year ago. Here's the current page
915.
Remembering G K Chesterton(chroniclesmagazine.org)
5 points by akkartik 6y ago|0 comments
916.
by akkartik 6y ago
Link on the same page: iPhone rescued from ice wall https://www.cbc.ca/news/canada/nova-scotia/group-effort-reco... . Complete with sappy poem. I wonder if there's a whole genre here of feel-good stories
917.
by akkartik 6y ago
Yeah, level 3 will be a HLL. It just doesn't matter too much which one it is, or that it "rules them all". A single reasonably high-level language X is in practice superior to a basket of high-level languages, even if some of
918.
by akkartik 6y ago
Yeah, these are good questions and to be fair your questions are shared by many. My basic worldview is that we need to have 100-1000x more people reading and auditing open source. The original value of open source was in the ability of peop
919.
by akkartik 6y ago
I'm not sure I follow your question, but the idea is that the computer the end user receives has a single opinionated language for programming it. Kinda like Basic for microcomputers. The end user is of course welcome to build their ow
920.
by akkartik 6y ago
I've taken it a step further (or three). I'm building a whole computer on the principle[1] (one possible way of looking at it) of avoiding parsing as far as possible. https://github.com/akkartik/mu Mu takes t
921.
Get a Life(crypto.stanford.edu)
176 points by akkartik 6y ago|21 comments
922.
by akkartik 6y ago
Here are a couple more projects that may or may not seem like Literate Programming, but are motivated squarely by its ethos: to order code for exposition, independent of what the compiler wants. * https://github.com/snaptoke
923.
by akkartik 6y ago
https://github.com/nickpascucci/verso works like this. There's a syntax for creating tags in source files, and exposition for tags lives in a separate file.
924.
by akkartik 6y ago
I have something that feels close to most of the things on your list. But it's diametrically opposite a DSL. Instead it's a _low_ level stack where you can easily drill down to understand how anything works. Programs come out a li
925.
by akkartik 6y ago
I believe that link just renders old data with the current style. We should go look in archive.org or something. I suspect your point still stands, though.
926.
by akkartik 6y ago
"When free software was born, if you wanted to clone, interoperate with, improve, or modify any existing software, all you needed to do was reverse-engineer that software and go to town. "The GPL wasn’t permission to make somethi
927.
by akkartik 6y ago
"Forty years ago, we had cake and asked for icing on top of it. Today, all we have left is the icing, and we’ve forgotten that the cake was ever there. If code isn’t licensed as “free,” you’d best leave it alone."
928.
Cory Doctorow: IP (2020)(locusmag.com)
227 points by akkartik 6y ago|122 comments
929.
by akkartik 6y ago
> How is the current "notion of IP for software" not sustainable? The only reason the "notion of IP for software" is a thing is that our intuitive notions of ownership don't quite work. We can't sell softwar
930.
by akkartik 6y ago
I really like this model and want it to take over the world. It would solve two problems: compensating people for building open-source software, and replacing the notion of IP for software with something more sustainable. More people should

More ›