[jofer]

Just as an FYI: "leaflet" is the name of a popular web mapping JS library. https://leafletjs.com/

May or may not be relevant for you (and is definitely a very different field/product), but if you're releasing client libraries/SDKs of any sort, it might be good to be aware of. There's a large ecosystem of plugin libraries named "leaflet-foo" or "foo-leaflet" etc in addition to the "main" one. If you start releasing any libraries to work with your app (even if they're not JS), you'll likely want to be aware of and work around naming collisions for library names.

Either way, looks nifty!! I love the approach and we need more people willing to do something like this that competes with google docs / etc, but does so by targeting a specific use case / niche / etc and not by trying to do everything.

[jpereira]

Leaflet looks like an amazing library. We only came across it and the naming collision after we got started, and so far haven't had too much confusion, but definitely a good idea to be aware when we do an SDK. Would love to make the confusion worse by including a map block in leaflet.pub via leafletjs someday though!

[ks2048]

My first thought was maybe the overleaf.com people had branched-out from LaTeX documents.

[6stringmerc]

Have you noticed the rampant appropriation of common words of late in HN references to products? Engine. Leaflet. Bayleaf. On and on I’ve forgotten how many I’ve seen but it’s ridiculous to think that in time, they’ll all be trademarked in the US. In short, I find it an issue with no remedy at present, yet to say it’s all well and good would be a sign of ignorance.

[ricardonunez]

My first thought was a new product from the LeafLetJS people, cool.

[4ndrewl]

My first thought too.