itsgabriel

I generally agree. If you're not doing it for money you don't technically need most of these things. But if you see open source as more than “here's the code” some of them matter. Support will find you, via GitHub issues, emails, or DMs. Analytics is really important because it shows whether the software works for people besides you. Without money you usually do not have playtesters or a UX designer, so you get fewer useful bug reports. Frustrated users rarely take the time to write a detailed issue.

Did you know about this workaround? Afaik it's still active https://peabee.substack.com/p/everyone-knows-what-apps-you-u...

There is a list of software with support here https://clapdb.tech/

as god indented, you mean?

Have you looked at something like Latex or Typst? They come with their own layout engine, so potentially less tedious work like specifying exact positions.

Both Immich and PhotoPrism do have this feature: https://immich.app/docs/administration/system-settings#dupli... https://docs.photoprism.app/user-guide/library/duplicates/

You may also enjoy Surface Stable Dithering: https://youtube.com/watch?v=HPqGaIMVuLs

It's not a failure, it's big techs greatest feature. Try to imagine the likes of Windows, Office, Apple, AWS, Social Media etc. without lock-in, network effect or all the other names for missing interoperability.

How would profitability fail the company? Too expensive products won't be bought means no profit, but if you can get away with the price, you're not failing, are you?

You might have switched up your threads, SO's decline is over here https://news.ycombinator.com/item?id=41376770

I don't think this analogy works, the space laser is instant and does not spread to non-targets. Smoking does reduce the average life span, but not to zero. In the remaining time, healthcare costs are increased on top of anything expensive they'd develop naturally. Smoking also causes serious diseases in non-smokers and kills 1.3 million non-smokers per year. https://www.who.int/news-room/fact-sheets/detail/tobacco

I don't quite get how this reactivity is only possible with a VDom, for example Svelte https://learn.svelte.dev/tutorial/updating-arrays-and-object... also allows you to update the UI on changes to the array.

Contributions to a fork could be done under just the AGPL, without any CLAs (also to the original repo, but those won't be accepted). Then the entire fork is effectively AGPL only. I don't think any original CLAs would apply to the fork, unless the fork owner is the same legal entity/successor as defined in there. Same goes for the original authors, they'd need CLAs from all fork contributors.

Funnily enough the docs are wrong, the GitHub CLI allows changing a forks visibility https://stackoverflow.com/a/78094654/12846952