Chat Logs

  1. * dreamreal joined #primate
  2. blueWB dreamreal.
  3. dreamrealrestarted weechat for an update :D
  4. dreamrealhow was your weekend
  5. bluegood, mostly repopack work
  6. dreamrealI was living in asciidoc, rust, and yardwork
  7. bluefor your blog?
  8. bluealso, rust ewww
  9. dreamrealno, for work
  10. blueoh
  11. dreamrealMy blog already supports asciidoc as input, I just don't use it as much, because the asciidoc wikisyntax support is wonkier than the markdown parser. Plus, obsidian uses markdown, so I have a much richer toolset support system for markdown than for asciidoc. Better mousetraps are awesome - but they have to be on the market to make any difference.
  12. dreamrealWork has some extra requirements for *any* document format, so we'd actually chosen myst (markdown for sphinx) but that's a 600MB artifact to support in sphinx; asciidoctor's a good bit smaller, and we have physical transport requiremnts to consider.
  13. dreamreal(that 600MB is actually *good* - what we use weasyprint to convert html to pdf. Actually generating the PDF would have been better but would have meant a 2.1G deliverable, and noooo.)
  14. blueI see. 600MB for converting markdown to html?
  15. dreamrealerrr... if you want to put it that way, sure
  16. dreamrealsphinx is a documentation system, it uses markdown and yaml as input and creates HTML, so sure
  17. bluerepopack on master [$โœ˜!?] via ๐ŸฅŸ v1.3.14 du -sh node_modules/marked/
  18. blue460K node_modules/marked/
  19. bluejust puttig it out there, no judgment >_>
  20. dreamrealwhat is that?
  21. bluemarked?
  22. blueit's an npm package to convert markdown to html
  23. bluenot sure why someone would need 600mb to convert markdown to html
  24. * dreamreal sighs
  25. dreamrealbecause that's not all that it's doing
  26. blueso the rest of what it's doing is 600mb - 460kb?
  27. bluethat's still, uh, a lot
  28. dreamrealno, that's the docker image
  29. blueoh
  30. bluewell, what's it do other than markdown to html?
  31. dreamrealit's a documentation system: organization, validation, etc., so the image has to be a docker image + OS + python + our stuff
  32. dreamrealplus we have to include stuff to convert to PDF as well
  33. bluemhm
  34. dreamrealthe "right way to do that" is to use sphinx + latex, but that's the 2.1G image
  35. blueholy heck
  36. dreamreallatex is not small
  37. blue2.1G is a dumpster fire
  38. * dreamreal shrugs. latex is a cannon and our problem is more ... tiny
  39. dreamrealIt's actually impressive that Word covers most of what you'd need latex for
  40. blueshooting sparrows with cannons, I see
  41. dreamrealthat's why we went with weasyprint: far fewer features but we're not represnting complex maths, for example
  42. bluemhm
  43. * jreicher joined #primate
  44. jreicherblue: why does the 2.1G surprise you?
  45. bluejreicher: because that's a buttload of bytes
  46. jreicherYes it is, but it sounds like you were expecting less? Why?
  47. bluebecause I expect my software to be lean, not to consume gigabytes of space
  48. bluefor something to be 2.1G and justify, it means to do more than 'organisation, validation, etc.'
  49. bluejustify it*
  50. jreicherIt's not just software.
  51. jreicherIn fact the majority of those bytes isn't software, I think.
  52. blueWell, yeah; Containerfile are ridiculous large, too, and that's unacceptable too
  53. jreicherNot that either.
  54. blueSo what then?
  55. jreicherFonts