In Canada we have these refillable prepaid VISA cards https://www.koho.ca/. Not a plug, but it's honestly solved money management for us.
Every week, my wife and I load some amount into the 'joint' card, and a smaller onto the personal cards. The joint card is for necessities, the personal cards are for fun. It's much more convenient than the cash envelopes we were doing before.
Credit cards don't work for us because it's too easy to cheat, and you only have to feel guilty when you square up the tracking. With the prepaid cards, you get a much harsher signal when you're over budget.
I've been using AWS Route53 DNS for my domain for many years, very cheap and easy to automate a DDNS setup if desired (e.g. https://crazymax.dev/ddns-route53/)
> Someone donating large amounts of money to charity just to write it off on their taxes isn’t doing so altruistically
I mean, it's still altruistic because they're going to 'lose wealth' by donating. You're never going to earn back in tax write-offs as much as you spent by donating.
Disclaimer, I like the snap packaging format, and I'm not familiar with the history of launchpad.
Operationally:
- I can trivially host and control my own apt repository, either as a mirror of some upstream repository, or with bespoke packages.
- I can't do the same with snaps.
So launchpad and snap store isn't quite apples-to-apples. It would help of course if a snap store could be statically hosted or re-implemented, but the full API is quite complex.
Hear hear. I imagine for dogfooding, LXD is only packaged in snap, so we can't use apt as the source anymore. After migrating, an upstream push to a 'stable' LXD snap channel introduced a regression that borked our environments, and there was no way to:
1. prevent machines in the fleet from pulling the broken LXD update
2. rollback broken machines to the previously working LXD version on the same channel, since it no longer existed in the Snap Store™.
I've been looking forward for this work to come to something working for some time already, but it's been already 3 years I've eyed on it, is it now coming to something working "soon"?
Debian is a bad choice if you want to package go applications (or rust apps, for that matter). Debian requires that all those little static dependencies be individually packaged. Common container software like lxd, podman, and umoci are not found in Debian.
The following distributions package LXD (that I know of):
* Void Linux
* Alpine Linux
* Arch Linux
* Gentoo
Some of those are more suitable for production installs than others, but if you know what you are doing and manage your deployments well, all of them could work.
Do you happen to know _why_ Debian decided to require that for Go projects? It's so absurdly complicated.
I've been looking into .deb packaging for Caddy but it really feels like they require us to jump through too many hoops to make it happen. I'd much rather just ship a prebuilt binary.
Security. Dynamically linking stuff is always going to be better than statically linking. Do you trust upstream to keep track of security issues and rebuild in the absurd dependency tree that is Golang software? Or the multi-year old effort which is the current Debian security team?
The reason why it's absurdly complicated is solely on the Golang team, not Debian.
I was not aware. Too late to edit now, but that is indeed a great option! Rolling release is a bit ambitious for a hyperlink without nixos like features.
Funny. I have been working on a blogpost detailing the silly things I encountered while packaging LXD properly for Arch Linux. Should probably finish it up one of these days.
Without too much details. But I personally got into LXD while bootstrapping kubeadm clusters with salt. LXD profiles made it very easy to work with compared to alternatives.
It's clearly not production stuff, but it works very well for a quick test bed before production deployments.
Foundational seems like a strong word here - this is a thin wrapper on top of two popular components from ROS (Navigation and MoveIt), and bringup for a specific robot (LoCoBot).
I appreciate the effort here though - ROS feels like it's become harder to use due to stale documentation, and there's value in providing a simple python API that abstracts the underlying bringup.
However looking through the wrapper and its documentation, it doesn't feel like it's making it much simpler by hiding away standard ROS tools.
Yeah, as a robotics + ML researcher at Stanford I can confirm I've looked over this and was not that impressed; our own lab already has a version of this, as do most robotics lab. It's nice that it's open source but it's not that feature-rich.
I really love the ideas/architecture behind Concourse, but there's a few things that disqualified it in favour of Jenkins for a new CI pipeline during prototyping:
Wow I never knew Jenkins could scale its workers like that. We definitely have performance issues with our Concourse cluster running in K8s. It's got it's own set of dedicated nodes but we need to scale the workers better as they're ofter under heavy load throughout the day when the devs are pushing code and a bunch of tests are running in Concourse (and PR checks as well)!
Concourse definitely feels more refined than Jenkins. Like other commenters have said, it's a steep learning curve to grasp how things move between Tasks/Jobs.
Every week, my wife and I load some amount into the 'joint' card, and a smaller onto the personal cards. The joint card is for necessities, the personal cards are for fun. It's much more convenient than the cash envelopes we were doing before.
Credit cards don't work for us because it's too easy to cheat, and you only have to feel guilty when you square up the tracking. With the prepaid cards, you get a much harsher signal when you're over budget.