Live data from Hacker News

Show HN: Bike – macOS Native Outliner

hogbaysoftware.com

11–20 of 243 posts

Re: Show HN: Bike – macOS Native Outliner

#15

If this supported multi-user synchronous editing Google-docs style I'd be thrilled.

Sorry that's not likely. I'm a single developer, not ready to run a server. More likely (though still have many more basic features on roadmap) is automatic merging support when a Bike file is stored on something like Dropbox. In fact that would be a pretty great service (for someone else to develop). "Dropbox", but for strutted data (xml, json, whatever) that knows how to merge trees and make use if unique ids. Mayb…

I think you could encode a “shelf” last-write-wins CRDT into your HTML using data attributes without exploding your file size. You would need to add a data-version attribute, and if you want to support hand-editing or editing by programs that don’t understand the CRDT, a CRC32 or other parity as data-parity so your loader can tell when a user might have edited a row without updating data-version.

Shelf is really simple - the JS implementation is tiny (https://github.com/dglittle/shelf) and a walkthrough of the algorithm here is a quick read: https://bartoszsypytkowski.com/shelf-crdt/amp/

It wouldn’t handle character level sync - but would let you merge documents at a rows/items/blocks level.

Re: Show HN: Bike – macOS Native Outliner

#17

Workflowy and Logseq already provide these features. Am I missing something?

They both provide many great features, but Bike provides some unique features too. I think they are pretty well listed on Bike's home page (features), but I'll add some notes here:

1. "Fluid" (smoothly animated) editing. You could argue it's not important, but this is something new and unique to Bike. Bike is a "tool for thought". I think how the app feels is an important aspect.

2. macOS native app, of course this is a plus and minus. But if you are on a Mac Bike will generally us a lot less resources then those apps and integrate better with the rest of the system.

3. Local files in open formats. Logseq has this of Course, but I think there's something pretty nice about having your outline just be simple HTML. Easy to parse, easy to work with, should be able to view and make sense of as long as web's around.

4. Faster. Bike is designed to work on somewhat big outlines. Moby Dick has been my test file. It opens instantly. I've just pasted that into Logseq and my computer is working hard a few minutes later. Not sure how workflowy does because it puts me over quotas.

Bike has a pretty unique foundation compared to other outliner apps. It's also missing a lot of higher level features that I plan to build out over time.

Re: Show HN: Bike – macOS Native Outliner

#18

Workflowy and Logseq already provide these features. Am I missing something?

As the post title says, it's a macOS native app, focusing on fluidity.

Mac native I get. But what is "fluidity"? The other two are just as "fluid".

Re: Show HN: Bike – macOS Native Outliner

#19
post #13

Are there any limits to the unlicensed mode? Is it a shareware or more in line with Sublime Text style?

There are some editor preferences that need a license and AppleScript support requires a license. Going forward I expect most new features will also require a license. For example I hope to add rich text support next and that will require a license. (same license will unlock all new features)
Post reply on HN