vitiral

24 ms·

1. 331.▲
   by vitiral 3y ago

   That is damn impressive considering the age of the project. Kudos for getting signoff from all relevant parties!
2. 332.▲
   by vitiral 3y ago

   Great article. One thing for me is that I think we named our variables wrong. We should be specifying the number of bytes, not bits. I use U1, U2, U4, U8, I1, I2, etc Also S for "slot" aka unsigned pointer sized integer (usize_t)
3. 333.▲
   by vitiral 3y ago

   Thanks, I appreciate the thoughts. It's for the civboot.org project, so it has VERY constrained requirements. Basically it is just to build things like a VCS and log collector on. As I outlined in the post I'm only concerned with
4. 334.▲
   by vitiral 3y ago

   To be clear, it would depend on some (equally small) libraries, so it's not like 500 lines of no dependency C or something
5. 335.▲
   by vitiral 3y ago

   Yup, I've seen a lot of those. Cool and inspirational stuff. My favorite so far has been project Oberon. I've not seen how it's assembler works though. What I want is a full stack (assembly included) self-bootsrapping impleme
6. 336.▲
   by vitiral 3y ago

   It would be considered a toy by most yes
7. 337.▲
   by vitiral 3y ago

   Anything that can be shared or tested individually gets moved to a library, no matter how small. I'll have an 'ed' library for things like the gap buffer and undo/redo aware buffer (built on gap) as well as the movement
8. 338.▲
   by vitiral 3y ago

   Normal lines (max 80) but I do prefer having each line do "one full thought", like putting `if then ... end` on a single line (if it fits) I wrote about the database here https://github.com/civboot/civboot&#x2
9. 339.▲
   by vitiral 3y ago

   Thanks :) FYI the real power of / for comments is /token to comment out one token. So useful to add a bit of doc sugar when calling something call(x\sugar) call(x/*sugar*/) Also Thing \(inline comment
10. 340.▲
    by vitiral 3y ago

    One of my goals is to rewrite all software for developing software, with each application at about (or less than) this sweet spot. Database, version control, runtime type system (Lua), proto-like serialization, code refactoring, parsing lib
11. 341.▲
    by vitiral 3y ago

    https://github.com/civboot/civlua/tree/main/metaty
12. 342.▲
    by vitiral 3y ago

    Seems cool, has a lot of the Vibe of Lua but with bit-twiddling types
13. 343.▲
    by vitiral 3y ago

    I made a prototype that works in 3000 lines of C github.com/civboot/fngi It was super fun. I'm going to be going in a different direction (Lua implemented in Lua, with Lua-library assemblers and assembly type system), but it&
14. 344.▲
    by vitiral 3y ago

    And Lua
15. 345.▲
    by vitiral 3y ago

    Lua has done pretty well to avoid this IMO. Notably they added coroutines with basically zero cost to the implementation (essentially just a pointer keeping track of function position on top of the already existing closures). The whole lang
16. 346.▲
    by vitiral 3y ago

    Metatable types are indeed kind of awkward, but it's pretty easy to build a type system on them in a library. Check out metaty where I built a type system, formatter and deep equality checking in like 700 LoC. I'm adding the abili
17. 347.▲
    by vitiral 3y ago

    I had a similar idea and called them "Shifted Search Trees". I can see how they are also a kind of Trie I've written about how they can not only be used for hashes but also for storing sparse indexes. I'm hoping to write
18. 348.▲
    by vitiral 3y ago

    THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYR
19. 349.▲
    by vitiral 3y ago

    I assumed this was about Taylor Swift and her supper power of appealing to all groups of fans. > Instead, Swift embeds a copy of clang, the C and C++ compiler... Ah... interoperability through a non-swappable fork of a behemoth piece of
20. 350.▲
    by vitiral 3y ago

    * the snake eating it's own tail This feedback loop, when you extend LLM to the horizon, is my primary point against this approach. When 90% of the new training data is from content (a worse version of) it previously generated you get
21. 351.▲
    by vitiral 3y ago

    Common for large scale systems. IIUC wire lengths and connectors/joints add impedence
22. 352.▲
    by vitiral 3y ago

    I'm not suggesting changing it, I'm trying to understand how it could possibly have been this way in the first place
23. 353.▲
    by vitiral 3y ago

    The way I see it is that all living systems inevitably grow in complexity until they decay and die. This is their nature. As we are part of the system we can't help feeling trapped when the decay and pain is creeping in, but if we can
24. 354.▲
    by vitiral 3y ago

    I don't think I understand but maybe that's the point. Maybe it seems mysterious because there were other requirements at the time which were themselves already mysterious?
25. 355.▲
    by vitiral 3y ago

    Hey thanks for the article. 100% agree on social media and doing the small stuff. HN is about the only one I use and i try to take month long breaks regularly
26. 356.▲
    by vitiral 3y ago

    I think I'm confused. You make it sound like the "tape reader" hardware/driver isn't talking to the "file reader" part in software . Didn't the file reader tell the tape reader the size of the file, s
27. 357.▲
    by vitiral 3y ago

    I'm arguing that these features make no sense _in the old context_ as well. Why waste 1KiB and namelen-100 bytes per file when space is so precious?
28. 358.▲
    by vitiral 3y ago

    Wouldn't such a feature be better put on the physical media controller/protocol itself?
29. 359.▲
    by vitiral 3y ago

    Thanks for the correction. If space was so important then why waste 1KiB/file? Why waste namelen-100 bytes per file? Why put space into owner/group id?
30. 360.▲
    by vitiral 3y ago

    I don't think any of the alternatives I listed can't be done on an embedded device or a tape drive though. I understand that the format is old and so perhaps many of the arbitrary constraints weren't seen as that bad at the t