Readit NewsWithout threads, there is no breach of thread-etiquette.
When "channels" are so awkward, nobody uses them. Then there is no constant deluge of middle-age folks creating a Facebook out of work, needing to be reminded that the photos channel is for business-photos, not pictures of their kids.
When emoji support is limited, nobody has to police people pushing the boundaries of what emojis are appropriate.
The software is baffling. But I like it that way.
There are definitely still breaches of etiquette though, e.g. people frequently tagging a whole channel when they have a support question, even though it contains hundreds of people.
Because it is just not suitable for growing crops that humans can realistically consume. If you can figure out a way to change this at scale, it'll be a discovery on par with Haber's process w.r.t. impact on human civilization.
I think we can eventually get there, as evidenced by billionaires and real estate companies buying up bad farmland over the last decade or so.
Feeding the world is technically easy, there is more than enough space for growing crops. The only reason that it's not done is the desire to eat meat and the lack of any real will to do it.
It might be interesting for wild fish, but I'm not sure if there are accurate numbers for the wild populations remaining.
Commercial decks, where the deck maintainer is paid for his efforts, make a lot of sense.
And I suppose if they are making money out of the ecosystem, it also only makes sense that commercial deck makers make a contribution to the technology that makes it possible. I suppose I would prefer that be a contribution rather than ownership and custody, but I suppose Anki's license terms (it is AGPL3+ - I think without a CLA) prevents them closing it.
So cautiously optimistic
In fact, I've been using Jujutsu for ~2 years as a drop-in and nobody complained (outside of the 8 small PRs chained together). Git is great as a backend, but Jujutsu shines as a frontend.
I will try to give Jujutsu a go based on your recommendation!
Butter the toast, eat the toast, shit the toast... God, life's relentless.
C# actually has fairly good null-checking now. Older projects would have to migrate some code to take advantage of it, but new projects are pretty much using it by default.
I'm not sure what the situation is with Unity though - aren't they usually a few versions behind the latest?
https://docs.mermaidchart.com/blog/posts/7-er-diagram-exampl...
There are some disadvantages however:
1. The foreign key relationships aren't completely clear
2. The diagram became difficult to navigate in vscode as our schema grew in size