> The battery lasts for days as well, which you can't really beat.

The Garmin Instinct 2X's (and 3) battery lasts for 40 days in smartwatch mode, not counting the solar charging.

The Instinct is an "outdoor watch" with a monochrome display, but it has most features the Forerunners have.

For the sake of completeness, I would also mention:

- Suunto (20 to 30 days in smartwatch mode for the Verticals, optional solar charging, flashlight on the Vertical 2)

- Coros (2 to 3 weeks depending on the model), no flashlight

- Withings (30 days, looks like a regular watch)

Coros is good for how long they support their watches, and the fact that they don't restrict features in lesser models. Suunto is great for route planning. Polar is renowned for its training metrics (sleep, recovery etc.) but only fetches a week in smartwatch mode.

Also it has a proper builtin flashlight which is surprisingly useful. Amazing watch, especially if you get a comfortable aftermarket strap e.g. from Hemsut.

Dropping in to add that the Venu 4 is an amazing watch as well. Battery says it'll last 14 days. With Pulse Ox enabled at Sleep, it drops to 11, but I'm happy with the tradeoff. Workouts like running for half an hour drop it even more, but comparing it to an Apple Watch, it's no match. It has a flashlight as well and looks like a normal smartwatch instead of rugged. All in all, if you care more about health features rather than watch<->phone connectivity, a Garmin is worth it.

For backlinks, have a look at Andy Matuschak's note-link-janitor: https://github.com/andymatuschak/note-link-janitor/

I wrote my own version of it a few years ago, but have moved on, and currently use LogSeq instead: https://github.com/cdaven/noteexplorer

Yes, it's still called "ASP.NET Core", even though ".NET Core" was renamed ".NET" from version 5 -- not to be confused with ".NET Framework 5", which was renamed ".NET Core 1.0" before launch.

Don't forget ".NET Standard" that could be used from both .NET Core and .NET Framework, until version 2.1.

You can modify the login flow in Keycloak to make it more or less just pass through the credentials/claims, but that's not the default.

Maybe something like this: https://ultimatesecurity.pro/post/first-login-flow/

First, Angular uses classes, and React supports class-based components.

Then, if you have converted lots of Javascript into Typescript, you have probably found several type-related bugs.

On one hand, this makes you (me) trust Typescript more, and feel safer knowing that your types are correct.

Later, you discover that a few of the declared types are wrong! You also still get "this" wrong in callbacks.

You could say that Typescript lets you try to get your types right, but you have to do the heavy lifting yourself.

Yes, I think Zapier is a B2B version of IFTTT.

The principle of sufficient reason states that everything must have a reason or a cause. This is not a principle to lazily toss aside to avoid some more difficult question, it is a foundational idea.

Our understanding of the world (aka science) is largely based on causality, and if things existed without any cause or reason, our understanding of "science" would probably be very different.

(I'm not a physicist, but this is how I understand things.)

I mean... that's a pretty superficial reading of the situation. Where do you stop? If you assume Newtonian time, which extends back to minus infinity... well, what caused time to exist at all?

Also, no one is "lazily tossing it aside". It comes out of the mathematics that describe the observations:

Say you find that all observations you make are perfectly described by dx/dt = 1/x with current time t1. If you follow the trajectories backwards, you find that the trajectory can not be extended back past some initial time t0 at which x(t0) = 0 as the equation becomes singular then. You are now at time t1-t0 from the initial singularity. That is the age of the universe since the big bang. Now the trajectory as it approaches t0 has some unusual properties, it moves infinitely fast, etc... These might lead you to postulate that unknown physics will actually invalidate your law as you approach t0. But there is nothing logically or epistemically _wrong_ with the law you have. The finiteness of time flows out of a causal empirical induction argument. It is not introduced ad hoc to avoid some difficulty, it just is how we find nature to be at the most conservative interpretation of the evidence.

> Where do you stop? If you assume Newtonian time, which extends back to minus infinity... well, what caused time to exist at all?

You stop at the uncaused first cause or the unmoved mover, of course.

In that case, we are not disposing of any principles (as you originally claimed) when we have an uncaused first cause at t = -13.6 Billion years, instead of having at t = - infinity.

For those people unfamiliar with this joke, watch the TV show Seinfeld.

For those people unfamiliar with 'TV shows', they are similar to HBO series, but with less interepisodic narrative.

lmao

There's also the lamp VINDKAST, which in English is "wind throw" or "flurry".

gust of wind

"The ultimate glue and scripting language" is taking it too far, I think.

I have loved Python too, but fell out of love a long time ago. Julia is much better in many ways, _in my opinion_.

Lua is a language that I have no experience of myself, but which is often embedded in things like this, because the interpreter is very small (if I'm not mistaken), which makes it convenient, and therefore in some ways superior to using either Javascript or Python.

Just saying that there are many opinions and ways to think about this.