waldir

Oh, indeed I can't see any reply other than this one :(

Thanks for the link — that's pretty comprehensive!

Got it, thanks for the context!

Do you have a comparison page, or a list of the annoyances you fixed from PicoCSS, accessible anywhere?

Were you aware of git-bug when you created gitsocial? If so, which patterns did you reuse and which ones did you decide to diverge from? Or would you say the two projects embody fundamentally different visions?

> It's the difference between instructions for a user and instructions for a developer

Sounds like a job for a CONTRIBUTING.md :)

I get why people may not like the comparison you're making, but that aside, I agree that the article insists uncomfortably often that the freedom only comes if "the work" gets done (in various phrasings). As if to ensure that nobody gets the impression that a pleasant work experience is something anyone deserves rather than a generous gift by such a magnanimous employer.

So... was your project one of the 20 accepted ones? I got the email but my project (tldr-pages) wasn't selected.

Doesn't that suggest that tooling wasn't the issue after all?

That's why I prefer outliners. They still provide the sense of an infinitely nestable hierarchy, allow focusing on arbitrary levels of it as a temporary "root" document", and allow collapsing entire trees that are irrelevant for the current work I'm doing. But crucially, if they implement live cloning of subtrees (in Workflowy, for example, these are called "mirrors"), they can also allow a more flexible graph structure as opposed to a strictly hierarchical tree.

Of course, that misses the graphical/spatial aspect of other tools, but as josephg points out, these sometimes backfire without a natural, design-encouraged way to organize the content, and a stable frame reference. I for one don't miss the ability to organize my content spatially, even though I do that when working with physical paper. I think that's because of the limitations of the medium — i.e. I spread paper sheets out on a surface, and spread content within those sheets, because it's the only way to group content in a stable manner. The nesting system performs the same function for me in outliners.

Interesting. Can you share an example of this working?

It's really great to be able to just click a link and start playing with Julia without installing anything! While there are other platforms offering a similar experience, I'm glad Repl.it added Julia to its tool belt.

Just a quick note for the inattentive like me: you have to click the "Run" button before executing the `@enter foo(20)` command.