• 0 Posts
  • 9 Comments
Joined 3 years ago
cake
Cake day: June 14th, 2023

help-circle
  • Designed for newspaper printing, so it’s exceedingly narrow, and it’s also intended for ink which will ‘bleed’ a bit, so the fine details are too fine for high quality prints.

    If you’re arranging text into two-inch wide columns and then printing with a high-speed roller, then it might be a good choice.

    But since that’s niche and very unlikely, it’s probably a bad choice. It’s also a terrible on-screen font, and since the cost of rendering a web page isn’t meaningfully affected by the size of the glyphs, then there’s no justification for choosing it for web purposes.


  • I’m in this photo and I don’t like it.

    More specifically, my programming background is in industrial automation and I’d like to add some more ‘robust and flexible’ algorithms to CoolerControl so I can control my system fans / temperature better, but it’s written in a mix of TypeScript and Rust.

    I’ve spent 20 years programming hard real-time z80 assembly and know quite a few higher-level languages. (Although I prefer the lower-level ones.) Not those ones, however, so it’s not just a couple of hours work to raise a PR against that project. Going to need to crack some books.


  • Well, yeah. The real advantage is only having a single file to transfer, makes eg. SFTP a lot less annoying at the command line.

    Lossless compression works by storing redundant information more efficiently. If you’ve got 50 GB in a directory, it’s going to be mostly pictures and videos, because that would be an incredible amount of text or source code. Those are already stored with lossy compression, so there’s just not much more you can squeeze out.

    I suppose you might have 50 GB of logs, especially if you’ve a logserver for your network? But most modern logging stores in a binary format, since it’s quicker to search and manipulate, and doesn’t use up such a crazy amount of disk space.







  • I feel that Python is a bit of a ‘Microsoft Word’ of languages. Your own scripts are obviously completely fine, using a sensible and pragmatic selection of the language features in a robust fashion, but everyone else’s are absurd collections of hacks that fall to pieces at the first modification.

    To an extent, ‘other people’s C++ / Bash scripts’ have the same problem. I’m usually okay with ‘other people’s Java’, which to me is one of the big selling points of the language - the slight wordiness and lack of ‘really stupid shit’ makes collaboration easier.

    Now, a Python script that’s more than about two pages long? That makes me question its utility. The ‘duck typing’ everywhere makes any code that you can’t ‘keep in your head’ very difficult to reason about.