HNHacker News
TopNewBestAskShowJobs

nobody_nothing

180 karma · joined December 4, 2019

submissionscomments
nobody_nothing··on Show HN: Margin – A lightweight, flexible markup language for structured thought
No, but looking at it now, it's definitely an inspiring model for how to do something like this right.

I'd say the goals of Margin are similar, but more focused on thought that is specifically hierarchical in nature -- whereas ArchieML seems to be more focused on structuring text in key:value pairs (if I'm understanding it correctly).

The hope with Margin is that lots of people already store their notes, to do lists, and random thoughts in a format that might already be (or almost be) valid Margin. It's intentionally non-technical, and its syntax should make sense to those who don't know or care what Margin is.

nobody_nothing··on Show HN: Margin – A lightweight, flexible markup language for structured thought
This is a great question and something I've pondered. I recently learned that mixing tabs and space in certain Python environments, such Google Cloud Functions, simply isn't allowed -- uploading such code will cause an error.

Unfortunately, that might be the cleanest solution for Margin, too: to simply disallow the intermingling of tabs and spaces as hierarchical tokens within a single parent.

In that scenario, you could use tabs in one part of the document and spaces in the other -- as long as all the direct children of one parent item follow the same rules.

nobody_nothing··on Show HN: Margin – A lightweight, flexible markup language for structured thought
My first instinct is no, the order of annotations should not matter to a parser. Or, put more precisely: that would be outside the scope of the spec, and keeping track of annotation order shouldn't be required of a valid parser. (Though, of course, if an application wanted to keep these annotations ordered it should be allowed to do so.)

Though it's a great question, and I could see myself changing course if a good use case were pitched whereby the ordering of annotations mattered specifically in a way that a use-case-specific app couldn't function if those children weren't already ordered for it in the plaintext.

There's also a case to be made that, because annotations are just a special type of child items, and because item order is generally meaningful in Margin, then we might as well keep annotations ordered too for good measure.

nobody_nothing··on Show HN: Margin – A lightweight, flexible markup language for structured thought
Great to hear! As I said to @brigandish below (and will shamelessly repeat): if when building the app you find yourself wanting to contribute to the js parser[1] in any way (or even any non javascript-based parser), it'd be much appreciated. That's my biggest need right now, is actually writing a good parser that'll encourage people to try this out.

[1] https://github.com/gamburg/margin/blob/master/parser/js/Marg...

nobody_nothing··on Show HN: Margin – A lightweight, flexible markup language for structured thought
Agreed! This is my biggest need. If you want to contribute, or know of any open source libraries that might help me build a more robust parser, let me know -- I'm only a casual coder, and this project really stretched my capabilities of recursive thought ::o

The parser in its current form is here: https://github.com/gamburg/margin/blob/master/parser/js/Marg...

nobody_nothing··on Show HN: Margin – A lightweight, flexible markup language for structured thought
This is awesome! Thanks for sending, I actually didn't know about these.

The big difference here would be that Margin isn't an app, but a markup language that's meant to be used as an open & portable storage system for apps. A storage system that is, by design, human readable plain text.

I do love that there's an (albeit niche) interest in apps that let you think/notate in this way.

nobody_nothing··on Show HN: Margin – A lightweight, flexible markup language for structured thought
Great to hear you'd consider using it. If when building the app you find yourself wanting to contribute to the js parser[1] in any way (or even any non javascript-based parser), it'd be much appreciated. That's my biggest need right now, is actually writing a good parser that'll encourage people to try this out.

And fair, re: "you wouldn’t build a web app in markdown". I'm sure it's been done :)

[1] https://github.com/gamburg/margin/blob/master/parser/js/Marg...

nobody_nothing··on Show HN: Margin – A lightweight, flexible markup language for structured thought
Not yet, but it's on the list! https://github.com/gamburg/margin/issues/2

Definitely a necessary feature if people are going to use this to store text. Do let me know if you have any ideas about what kind of syntax might be best for multiline blocks -- keeping in mind it should be both easy to type and easy to read (eg. ideally avoiding '\n' or special newline characters, for example).

nobody_nothing··on Show HN: Margin – A lightweight, flexible markup language for structured thought
Hey Show HN!

I'd love some early feedback on Margin, a markup language for hierarchically structured thought.

Margin came out of my desire to build a lightweight to-do app – though I soon realized what I really wanted was a markup language to capture structured thought. One that was not only human-readable, but also easily machine parsable.

Most importantly, Margin doesn't impose strict hierarchical categories (eg. "Header 1", "Project", "Task"). Instead it allows the user/application to define those categories. The ultimate goal is to democratize your to-do lists, notes, writing, etc. making them portable and platform-independent.

Aside from feedback on the specs & philosophy of Margin, which would be very appreciated, I could use some serious help with the parser (https://margin.love/parser/). I'm only a casual coder, so this problem was a difficult one for me. The parser is both incomplete and buggy, but hopefully it gets across the basics of how Margin is supposed to work.

Thanks!

nobody_nothing··on Ask HN: What are some example of low tech improving your life?
At night, I plug my phone in across the room from my bed, turn it on airplane mode, then power it down.

It's a wonderful moment that marks a healthy "disconnection" from the outside world, allowing me to have some quiet time with myself (or my partner).

Airplane mode ensures sure I'm not flooded with notifications first thing upon turning on my phone in the morning. Even if I need to use an app in the morning, I can take 15 minutes to an hour before I switch off airplane mode, which makes for calmer and more centered mornings.

The only thing you'll need if you want to adopt this change is an old school cheap alarm clock. I've been doing this for probably five years, and haven't looked back.

If you're anxious about missing emergency calls, you can optionally get a landline phone whose number only close friends & family have, and know only to use in case of emergency -- this step is optional, but can be achieved with Google Voice & some hardware for under $100.

← PreviousPage 2 of 2