Email or username:

Password:

Forgot your password?
Top-level
Artyom Bologov (t?he(y|m)?)

@neauoire I’ve been confusing I guess 😅

What I mean by similarity of goals is that we both are looking for something reliable and portable to base our software off. In this sense, HTML (and the surrounding technology, however wary I am of JavaScript) is a perfect portability layer for me.

Regarding the interactive/hypertext blogs though, I am indeed in search of a good format for my posts. I’m settled on HTML for now, but that might change.

See also aartaka.me/hypertext

4 comments
Kartik Agaram

@aartaka I got around to checking out your defense of html, and it doesn't really make sense to me. Why will the minor differences in markdown implementations matter more than relying on Google to render html in the long term? Why is the browser less likely to die than Obsidian?

@neauoire

Devine Lu Linvega

@akkartik @aartaka I think Obsidian is a web app isn't? If I had to guess, the browser would have to die for Obsidian to die, but the death of Obsidian wouldn't affect the browser at all, making it more robust?

DELETED

@neauoire @akkartik @aartaka obsidian isn’t, and browsers historically have needed to maintain backwards compatibility; so an html document has more longevity so long as you stick only to features that are at least 10 or so years old and don’t use a framework

DELETED

@neauoire @akkartik @aartaka that said, Markdown dialect incompatibilities are a worse problem than different versions of browsers. and there’s the perhaps minor point that markdown has a much more direct dependency on html and the precise ways it renders in a browser than most people realise, even setting aside that the standard requires that a markdown dialect literally support all of html inline

Go Up