I got a Garmin watch after being frustrated with the tech company watches lasting only hours on a charge. I charge this watch once a week and it does everything I realistically want from a smart watch:
- shows notifications
- tracks workouts
- silent alarm clock
- home assistant shortcuts
I'm a big fan of Garmin watches, it's really impressive what they've built. They're responsive, they have the smart features I want without the bloat I don't want, the battery lasts forever (if I don't use GPS at all it lasts something ridiculous like three weeks, with GPS it's still around a week). And they're so good I don't feel any urge to upgrade to a newer model even though the one I currently have came out in 2019. I bought it "renewed" 2.5 years ago at a significant discount and I could see myself happily using it for at least another 4-5 years.
Garmin watches are great! I wish the lighter/smaller models also had solar charger, but last time I checked only the bigger "ultra-durable" ones had it, but they're not that comfortable to wear.
I work on an open source server project that is deployed in many different contexts and with many different clients and front ends. GraphQL has allowed us to not feel bad about adding extra properties and object to the response, because if a particular client doesn’t want them, they don’t request them and don’t get them. It has allowed us to be much more flexible with adding features that only few people will use.
I want to be able to sync Orion with Firefox. I use non Apple operating systems on some computers, and I would love to have Orion sync with Firefox on them.
I have tried jj several times but I feel like it slows me down significantly because I can’t grok the workflow. I like to do a bunch of changes then quickly select them in my editor and commit them, breaking them up into different commits to keep them organized. With jj’s lack of editor integration, I don’t know how to do this with the cli alone so I end up with bigger messier commits.
Or if you don't care to set a commit message just yet: jj split -i
Or if you want to defer making sure each commit has the right content until later, just use jj new, and then later use jj squash and jj split to make the commits have sensible changes, and jj desc to set the descriptions.
The compatibility with git is the whole reason it's so popular (just run `jj git init --colocate` in your git repo).
You can use it without forcing your collaborators to switch from git and you can use it will a git forges as well.
I don't think you need `--colocate` any more, and maybe you don't even need `git`? I tried `jj init` in a git repo the other day and it did create a colocated jj repo, as far as I could see.
I am involved with the OpenTripPlanner project, which is a Java trip planning application that also uses the RAPTOR algorithm! It’s used in cities all over the world, with the biggest deployment being ENTUR’s in Norway, which covers the entire country. I believe all trip planning apps in Norway use this deployment.
It supports many features and has a very active developer community.
OTP is such a wonderful project! It's my go-to example of open source in government and it's so much more than a trip planning engine. For the country-wide transit app I'm working on (ok, it's a small country, but still), we use it as the database as well. We convert everything into GTFS(-RT), throw it into OTP, then have a fairly thin API layer that queries it via GraphQL and returns JSON for our app [0].
I also have to say the code is far more elegant and readable than what I expected from a 15 year old Java project. I had to fix a bug once and I figured it would take me at least a few hours to get my bearings in a codebase that size, but I managed to wrap my head around the core routing logic and fix the bug in an hour or so. The A* implementation for non-transit routing is such a good example of "enterprise code" done right.
I have location shared with a dozen or so of my friends. It has many times been useful to find out that we happen to be near each other and end up hanging out.
