kartoffelmos

I could imagine a way to use this to run a forge locally, no running web server needed -- just working with files on my file system.

Animals don't synthesise B12, bacteria does. Animals cumulate it from eating food grown in soil. Industrial farming often require B12 to be added to animal feed as a supplement as they don't graze (as much).

Give this a second thought: humans don't synthesise B12 either.

Considering the capital burn rate here, I suspect that waiting years between iterations will be a hard pill to swallow for investors.

> Who cares about the licencing.

Well, for one, the author of the Rust based utils cared enough to change it (or rather to not re-adopt GPL, but IMO that's the same ting). Why shouldn't we care about the licencing?

We try to have a clean-as-you-go policy. Try to improve bits and bobs while maintaining the code base as a whole. While (IMO) a one-liner here and there is fine, it can quickly spiral out of control.

I usually keep an improvements commit at the start of my branch which I `--amend` to while picking away at the task. If the commit gets too big I submit it separately, to be reviewed in isolation.

It was after discovering/learning `git bisect`, I started really understanding the value of using Git "properly". Being able to pinpoint in which commit an error was introduced is really invaluable.

I `git cherry-pick` all the time when I graft a PR. Sometimes I drift and start doing something unrelated to a task, and I often want to push it as a separate thing. Cherry picking it into another branch is most often how I achieve this. This does mean that I have to be structured in how I construct commits while I work though. Drafting, crafting, fixing and maintaining releases is however probably the most common use case for cherry-picking. Some commits needs to be cherry-picked for other release lanes.

`git worktree` is a feature I've often heard being raved about. I've not yet been able to use it for myself, in out code bases, but I imagine it being very nice if you have it work for you.

Aside: suggestion to add `git switch` and `git restore` to your repertoire. I'm guessing you use `git checkout` for these commands, but switching branches and resetting the staging area are two _very_ different tasks and making these two different commands is a wise decision. Lessens the likelihood for errors, at least for me.

PS2 backwards compatible with PS1, early models of PS3 was compatible with PS2.

This was achieved by simply cramming the older hardware into the newer. Quite a common strategy, really – I believe Sega did this too with Mega Drive being able to play Master System games (using a physical adapter).

Nintendo did the same for achieving backwards compatibility for Game Boy games on Game Boy Advance. Wii-GC compatibility was however achieved by the consoles using the same (but buffed) chipset. Gonna be interesting to see how they achieve backwards compatibility this time around.

Problem with docx is that there's no real way to _just_ view a file. I don't really want to spin up an entire word processor just to read the meeting minutes. I honestly much prefer a PDF to docx.

Sony Interactive Entertainment (which I believe is the "Sony" he's referring to) too is an American company.

This is making me imagine what a vCard powered profile service could look like… I'm not seeing anything here that vCard doesn't already support.

How will this address methane leakage, which is a substantial source of athmospheric greenhouse gas emissions? Converting Co2 to methane is not carbon neutral if/when leaked...

Do you have a source for this?

Except in this case "good" will fail to deliver emails to perfectly valid email addresses.

I considered paying for Monica because to get this feature. Glad I didn't, I suppose. No word from the authors that this is being addressed, and I can't seem to find any mention of CardDAV in the UI...