Chat Logs

  1. * phaleth joined #primate
  2. bluehi phaleth
  3. phalethhi blue
  4. phaleththis is cool https://docs.opnsense.org/development/api/core/interfaces.html
  5. nevetInterfaces โ€” OPNsense documentation
  6. bluewhat is that
  7. blueit's an API for managing your comp?
  8. phalethAPI to manage VLANs
  9. phalethREST
  10. bluenice
  11. phalethpeople are building all the things we need https://github.com/AthennaMind/opnsense-exporter
  12. blueholy guacamole
  13. bluebut'd need to use freebsd
  14. bluetime for superarch
  15. phalethheh, yeah
  16. phalethfreebsd is the goal anyway
  17. blueman I friggin' despise those modern people with their 'main' branches
  18. * blue spits
  19. blueone more reason not to use github
  20. blueI think once RP is up, I'll move primate as well
  21. blueI don't really inherently care for GH stars, and I despise GH enough to want to completely move away from it
  22. bluethe only reason to stay is that if you get over 1k stars, you get clanker freetime with claude, and I've cancelled my claude subscription anyway, clankers produce only nonsense
  23. phalethpeople do main branches outside of github as well
  24. blueyes, unfortunately, this cancer has spread everywhere
  25. phalethheh
  26. phalethit's nice that contabo allows to install freebsd, even if outdated, I think I still got the freebsd upgrade steps somewhere, cause opnsense is installable on top of freebsd using some bootstrap script, so there will not be a need to pay contabo for custom image storage
  27. bluecoolsies
  28. blueso one mistake I think zig did (beyond moving to codeberg), was that they left the old issues open on GH
  29. blueshould have migrated them
  30. phalethyeah, prolly, they are busy jumping from one place to another
  31. phalethit's complicated to migrate from github, for example gitea is still trapped there
  32. phalethbut at least that makes gitea discoverable
  33. bluethe only thing it requires is guts, otherwise you'll never break GH's awful monopoly
  34. bluebut zig have chosen the worst of all worlds. they could have selfhosted, AND they should have migrated all the issues and set the repo on GH to archived/readonly
  35. blueI'd say a gitea selfhost could have been the right path for zig
  36. bluebut now you have a situation where there are over 3k open issues on GH, and every bug needs to be checked twice
  37. bluetypical andrew
  38. bluepeople often forget there's a difference between a good engineer and a good maintainer, andrew is a great engineer and a terrible maintainer
  39. phaleththere is a non-profit behind codeberg that cares about the hosting and zig devs can't even be bothered about setting up nginx properly on their Hetner VPS
  40. blueyes, but would *you* trust an ideological german non-profit? I wouldn't
  41. phalethI think it's better for them to stay zig compiler focused
  42. phalethwell, they can always move again later, at least now they are not too bothered
  43. bluetrue
  44. phalethgitea is still cool, straightforward to setup, but when you have nobody doing devops and only compiler people then you need some help
  45. phaleththe cool thing about non-profits is that the expenses are tax deducible, doesn't matter if it's german
  46. phalethbut for sure germans are crazy about software
  47. bluemy problem with codeberg is mostly that they are ideological, and I don't like ideological people in software
  48. blueyou could say RMS is ideological too but I don't mean software ideology, I mean political ideology
  49. bluesoftware should just be software. we should all use master, drop the cocs nonsense, and focus on creating the best product
  50. blueI've added a `migrate` option to store creation in primate
  51. bluebecause more than one store can facade a table, it could become impossible to run migrations
  52. blueso you'd need to set `migration: false` on the store you want to exclude
  53. blueor migrate: false, rather
  54. phalethif they manage to get some projects of off github then that's fine, lot of people prolly self-host git remote solutions nowadays
  55. blueyes
  56. phalethnice
  57. bluesomeone warned me migrations is a can of worms but it's such a big can
  58. blueit's a small can of worms
  59. blueit's not such a big can*
  60. blueso far the complexity isn't very great
  61. phalethyeah, but still it would be great if you could implement them only for postgres and possibly also mariadb if there are similarities
  62. blueI'm writing the cli part now. I already finished implementing the primitives for postgres, mysql, sqlite and mongo
  63. bluethe drivers have two primitives, 'introspect' and 'alter'
  64. bluethat's all you need
  65. phalethah, ok
  66. bluewell technically you also need the table create primitive if there'a store file but no table, but it already existed
  67. blueI don't get eslint sometimes
  68. blue`if (!store.migrate) continue;`
  69. blue1. Unexpected any value in conditional. An explicit comparison or type conversion is required. [@typescript-eslint/strict-boolean-expressions]
  70. bluethat's so weird. `migrate` is already a boolean, inverted booleans aren't 'any'
  71. phalethmaybe it expects three exclamation marks !!!
  72. blueI don't really mind writing `store.migrate === false`, but it's not more strict of an expression than !store.migrate
  73. bluelol
  74. blueI think something's broken here
  75. blue"Forbids usage of non-boolean types in expressions where a boolean is expected. boolean and never types are always allowed"
  76. blueoh yeah, itwas some weird artefact. I reloaded the file and the error is gone
  77. phalethheh, cache
  78. phalethsilly webdevs
  79. bluepenultimate boss of software, caching, final boss, complexity
  80. phalethI wish zig succeeds with the zig run watch thing and that it's very fast and flawless
  81. bluewhat's that, reload on changes?
  82. blueor rather, recompile
  83. phalethrecompile, yes