Live data from Hacker News

Ask HN: What tech stack would you use to build an open-source Google Keep clone?

news.ycombinator.com

111–120 of 128 posts

Re: Ask HN: What tech stack would you use to build an open-source Google Keep clone?

#111
post #90
post #79

Earlier quoted context omitted.

For me it shows the [Reddit logo] and [Safari logo], since I'm on IOs. So it seems like it pulls the standard browser...

> standard browser Why would Chromium be the standard browser for Android? I have never had that installed on my phone. Edit: Yes I know Google develops the Chrome products. Down-voting my post without discussion is pretty useless, no?

Maybe the reddit popup just pick a ‚standardish‘ browser depending on the OS. I only have Safari on my phone...

Re: Ask HN: What tech stack would you use to build an open-source Google Keep clone?

#112
post #81

Earlier quoted context omitted.

A bit OT, but honest question: would it bother you if it was almost-open-source, that is, if license forbid leechers (other cloud providers selling competitive offering)? I am thinking of releasing a product under Apache + Common Clause, Zero License, Business Source License or similar, maybe with GPL timebomb. Basically, feel free to use, improve and share, but don't sell or offer it as a service to 3rd parties. I w…

No the OP, but as someone who is happy to pay for hosting, with free software, I would not be happy at all with your suggestion. In fact the original topic is really the reason I would not be happy. The original poster is asking how to build a new service since their service provider has become unresponsive. This is really the last straw. Ideally, as a consumer, you want to be able to potentially move to a new provid…

Thank you (and siblings) for an answer! I especially appreciate the reasons given.

You are of course correct - requesting a commercial license for any potential competitor will limit users' options with respect to the provider they choose. It does however grant them the option to self-host. While not that convenient, it still provides some incentive for me to try better, and is a backup plan for users if I become unresponsive. Better for users (and safer for me) than Open Core I think?

That said, the decision is not final yet, and I'm also not satisfied with any license I checked (closest is Common Clause, but what happens with snippets of code, reused in other, maybe foss projects?). Thank you!

Re: Ask HN: What tech stack would you use to build an open-source Google Keep clone?

#113
post #38

Earlier quoted context omitted.

If you're goal is to get the app done and published rather than learning a new tech then go with your default stack. I've never worked with Rails but it seems like a totally valid choice for the product. You can always bolt on a more modern frontend later if you need it.

Thanks. It's Rails' frontend performance stigma that made me hesitate. I suppose bolting a better FE is an option, but I won't know it until I benchmark it.

As others have pointed out the SPA route can introduce a huge amount of complexity. If you're a Rails dev one option worth exploring might be Phoenix + the upcoming LiveView feature.

Re: Ask HN: What tech stack would you use to build an open-source Google Keep clone?

#115

Earlier quoted context omitted.

No the OP, but as someone who is happy to pay for hosting, with free software, I would not be happy at all with your suggestion. In fact the original topic is really the reason I would not be happy. The original poster is asking how to build a new service since their service provider has become unresponsive. This is really the last straw. Ideally, as a consumer, you want to be able to potentially move to a new provid…

Thank you (and siblings) for an answer! I especially appreciate the reasons given. You are of course correct - requesting a commercial license for any potential competitor will limit users' options with respect to the provider they choose. It does however grant them the option to self-host. While not that convenient, it still provides some incentive for me to try better, and is a backup plan for users if I become unr…

Just to be clear (without being annoying I hope), there will be a class of users (myself included) who won't touch it. I would consider it a proprietary license. It isn't a kind of open source compromise. Having said that, there are a lot of considerably worse proprietary licenses. Good luck on your endeavours!

Re: Ask HN: What tech stack would you use to build an open-source Google Keep clone?

#116
post #76
post #69

Earlier quoted context omitted.

> I've been building an open source notes app recently and I picked Rust + ReasonML and React in the front end. Could you share a link to the repo? I'd love to take a look :)

Sure! It's https://github.com/pascalw/pragma/ and there's a demo running at https://pragma-demo.pascalw.me/ . I've actually just taken a short break from the project. It turns out building a good offline + sync note taking app is more complicated than I imagined it would be :-) Given that I'm just working on it in my spare time every now and then it frustrates me a little sometimes that I'm not making as much progres…

For those interested, password is: demo

Re: Ask HN: What tech stack would you use to build an open-source Google Keep clone?

#117
I had the same issues.

After reading GTD, I ended up switching to the Things 3 app. I think I paid a one time $10 or $20 but it has been worth it in my opinion.

The one app I have not found yet, is one that can help me organize all the knowledge I discover online. I end up using favorite on HN and had a bunch of links in Google bookmarks. Still, its hard to find the stuff once it gets in there.

Re: Ask HN: What tech stack would you use to build an open-source Google Keep clone?

#120

Earlier quoted context omitted.

Thank you (and siblings) for an answer! I especially appreciate the reasons given. You are of course correct - requesting a commercial license for any potential competitor will limit users' options with respect to the provider they choose. It does however grant them the option to self-host. While not that convenient, it still provides some incentive for me to try better, and is a backup plan for users if I become unr…

Just to be clear (without being annoying I hope), there will be a class of users (myself included) who won't touch it. I would consider it a proprietary license. It isn't a kind of open source compromise. Having said that, there are a lot of considerably worse proprietary licenses. Good luck on your endeavours!

[deleted]
Post reply on HN