They forked almost 15 years ago. Of course they share some code, but not a lot. And even still… so? Or course it helps diversify when blink has nearly 80% market share.

Kagi’s search results, in my experience, have been worth every penny.

When Orion started, the Servo project was kind of dead. It wasn’t until a year later at FOSDEM, that they announced the refresh that started development up again. A great choice now, but at the time, and still today, WebKit is also a decent choice, as long as one doesn’t mind that most of its development and optimization targets the Apple ecosystem.

I have tinkered with Orion. It has a lot of promise, but it is still a bit buggy. I’m all Firefox since before it was Firefox, but I respect your assessment. I’m also looking forward to Ladybird, even though it also has its fair share of controversy.

Recent Firefox has been really good to me. Vertical tabs and new design are excellent; though I don’t seem to be with the crowd in that.

One small feedback that is meant less as a correction and more in case people are curious. Chromium isn’t an engine, it is an open source browser. The Gecko / WebKit equivalent here is Blink.

I don’t know exactly what you’re after since project management is such a broad topic, but I can just say how I do this.

I keep 2 obsidian vaults: 1 personal and 1 professional. Among hundreds of other notes and topics I keep a project note per project (some personal some professional), keyed by project directory. Each keeps a running history of what is happening with each project. Then my daily journal links to the projects I’m working on with short notes about what is happening.

This is an aside, but obsidian.nvim is a superb way to interact with these notes.

If you’re looking for kanban and such, that’s a completely different approach, but I find after decades of sucking at keeping track, this has finally fit nicely with how I approach projects.

I actually think this is just further manifestation of the massive scam that is health insurance.

Waste of tokens for the agent to make changes that the human then changes to comply with contrib guidelines. Potentially a smaller number used to read in some guidelines and get closer to correct in the first place.

Like formatters and git ignore configuration, some agent instructions are personal and those should not be commited. But some are worth sharing. Having formatter config in a repo is not uncommon. And in this case the file is only a link to the readme, so the agent reads the contrib guidelines.

Which makes sense, if you want some standards across contributions. Setting aside that agent assisted contribution itself is questionable, as long as it is happening, a universal agents file is probably helpful.

Inkscape is one of the go-to best-in-class FOSS applications.

Fascinating how uttering the term “AI” can cause so many downvotes even when the system is just a harness that runs self hosted and can use completely openweight, even self trained models. Or maybe many on Lemmy just hate pewdiepie.