I've been building a Markdown variant called Zd that's focused on extensibility and simplicity. I'm curious what you would change about Markdown if you were designing it from scratch, what challenges you face as a user, or what you wish were easier to do when incorporating Markdown into your own projects.
Any conversation
pรฉldรกul Telegram, Facebook, stb., de ilyen รผgynรถkรถkkel bรกrki talรกlkozhat naponta, egybลl felismerhetลk, meg is kell ลket szรฉpen jelรถlni, รฉs egyre bรฉnรกbbak a szรถvegรผk is, ahogy megfigyeltem, gondolom, attรณl fรผgg, ahogy promtoljรกk, vagy instruรกljรกk ลket, ha a gazdรกjuk kifogy az รถtletekbลl, a projekt hamar elfรกrad, a bot csak unalmas h#lyesรฉgekre kรฉpes egy idล utรกn
for example, Telegram, Facebook, etc., but anyone can encounter such agents every day, they are immediately recognizable, they need to be nicely labeled, and their text is getting lamer and lamer, as I have observed, I think it depends on how they are promoted or instructed, if their owner runs out of ideas, the project quickly gets tired, the bot is only capable of boring nonsense after a while
code quality is about coupling.
coupling is not a technical property of the code bytes.
code acquires its meaning in contact with the cultural environment, and coupling is about meaning.
two constants with no semantic relationship are nonetheless coupled in pragmatics if they refer to the same domain concept.
if your goal is to minimise the time integral of future work, you must understand your domain: it decides which lines will need changing.
to carve up a codebase is to carve up the world.

