question: I have traefik and some app set up as daemonsets. requests get routed randomly across endpoints. setting internalTrafficPolicy doesn't change anything. topology hints don't get set b/c overload threshold isn't met
I can't wait until we have working 3D scanners. If I were to speculate, though, it seems more likely that we will witness the emergence of 3D models crafted by artificial intelligence using photographic data, prior to the widespread availability of 3D scanners as consumer hardware.
I know #NIX and #NIXOS have lots of fans, but every time I try to use them again I want to drive nails into my forehead. I think I like my immutable with Snap or Flatpak.
Mastodon est magique, j'en suis sûr.
Mon fils de 8 ans est passionné d'astronomie.
Nous lui avons promis un super livre sur ce sujet.
Nous sommes donc à la recherche du meilleur livre possible.
Parmi les astronomes amateurs et professionnel de mastodon, quel livre conseillez vous ?
Le retoot vous décroche la lune. #astronomy#astronomie#astrophotography#astrophysique
Been learning Haskell, and I’m starting to see how inefficient OOP is. For example, taken from “Programming with Haskell” from Graham Hutton with Quick Sort. Something like this in many languages requires way more lines of code. I hear Rust follows same approach to things, so that’s next.
I'm using the spatial data type in SQL Server to get "closest neighbor" results. I really want to remove #SQLServer from the stack if I can though. Anybody try #PostGIS for #PostgreSQL? Opinions? Suggestions?
Unpopular #boomer#developer opinion: #GitHub actions “jobs” should only ever run the same #Make (insert your build system here) tasks or scripts that you run on your own machine. Using actions from the “marketplace” that do anything more than to fetch dependencies means you can’t easily reproduce what happens in those actions. And there is nothing* as repugnant in this field as pushing fake commits to GH in order to debug a failing action.
@anderseknert@parcifal I also like #nix for that because it allows you to replace like 90% of yaml glue, while still reproducing the problematic stuff 100% locally
Something I'm noticing in comments to my recent blog post on #nushell is that a lot of folks have a strict separation between interactive shell and scripting.
When I point out in the post that Nushell is really meant to scale smoothly between the two, some folks say things like "so you're saying it's really a scripting language not a shell"
I want to help folks see they don't have to choose. They can scale ideas all the way up in one language without rewriting.
