Re:If it is worth keeping, save it in Markdown
by ytjohn on Wednesday February 26, 2025 @08:51AM
(#43183584)
I think they're mixing the GH web ui with the syntax. You can paste an image right into the editor and it does a really good job of inserting it right where you need to. It is really good UX that I miss when editing markdown locally. Obsidian also does a decent job, but not quite as smooth.
Re:If it is worth keeping, save it in Markdown
by everybodyknows on Wednesday February 26, 2025 @01:17PM
(#43186382)
Sounds like powerful lock-in for Github. How could such a project ever decamp to Gitlab or Codeberg?
Re:If it is worth keeping, save it in Markdown
by ytjohn on Wednesday February 26, 2025 @05:54PM
(#43189230)
So I also do use gitlab quite a bit, but not as much recently. I went to compare. Gitlab actually does have a similiar ux experience, though I'd give the Github one just a bit of an edge. It looks like the key difference is that github converts a pasted image to an html image tag, while gitlab uses markdown with the width/height brackets that the end.
Honestly, I think using an html image tag is the right way to go. I type in markdown all the time, and I have no problem making links. But markdown image syntax I have to double check each time or let the editor figure it out. HTML image tags, I find easier to remember and read than a markdown one. (But maybe that's because I learned HTML before markdown).
> GitHub-flavored Markdown is so popular because you can really easy inline them.
I'm not sure what you mean. GitHub-flavored Markdown has pretty much exactly the same image syntax as every other Markdown flavor.