From 11/7/2021, 3:08:45 AM till now, @kamrani has achieved 43 Karma Points with the contribution count of 46.
Recent @kamrani Activity
Hi, appreciate your support.
The goal is to make it really easy to go from idea to URL. So the CLI boosts your speed in kick starting the project and you should be able to deploy it on cloud with a single command.
There will be a platform, that gives you PaaS experience on AWS/Azure/GCP so it speeds up the end to end process.
Thanks.
Definitely. I've taken an iterative approach to supporting languages/frameworks and adding features. Python will be the next language to support.
I start with a minimal/basic support and in later iterations I keep adding features.
Thanks for your support
Show HN: A CLI to kick-start any language
13 points • 6 comments
Zapier Alternative for Free
16 points • 1 comments
I just want to make sure people can use it for free if they want but I don't want to give the right to sell.
Then I think it's not what I want.
Fair points. It's not a library and it's actually going to be provided as a SaaS product and as you mentioned I think it's best not to share the critical parts of code. At least that's what I'm doing.
Not always really. Code commit/build/deploy still are some of the worst products in AWS and they're far behind Gitlab which is OSS.
Btw, I'm not really concerned about Amazon particularly, it's a general question about someone taking advantage of few years of work without putting in any effort.
I think I have to use something exactly like the license Sentry is using then. It's just one license and it should be fine I guess if it had protected them.
Also, I'm not concerned about Amazon exactly but it can be any other entity with enough resources to offer my product to their existing user base and definitely with massive marketing budget, etc.
Thanks, sounds like what I need. Not sure if with AGPL still I have to use a dual license approach.
Also it's very true about what happened to elastic search or was about to happen to Sentry.
Thanks it's a good read.
That's exactly what I'm trying to do.
My concern is that a large enterprise like Amazon jumps in and in a few months I see exactly the scenario you describe.
I'll add a contributor agreement right away and it seems a dual license is the way.
I think the last one then.
I want to be able to sell it (exclusively), and anyone should be able to use the open-source version for free if they want (there is a SaaS offering for whoever wants it).
Ask HN: What license should I choose for my software?
11 points • 23 comments
Open source, simpler, and more flexible alternative to Zappier
3 points • 0 comments
Ask HN: Who takes the decision about buying a SaaS product in small companies?
1 points • 2 comments
Well, maybe for early adopters? I think I've got something wrong...
And do you think if approach users they'd think we're not ready?
Ask HN: Is it called a launch if you still haven't enabled payment?
2 points • 5 comments
site design / logo © 2022 Box Piper