This is just not true. My landing page doesn't have much if anything in common with Handy's and that was never the goal. I stated explicitly that I forked Handy for a reason, it's not a secret and I'm not ashamed of it.
Of course, most of what my app does now is very similar to Handy, but isn't it normal when you fork something? Discrepancies grow over time, not overnight. I've already implemented many things differently, and am working on features that will probably never be in Handy anyway. I have different goals and ideas.
Some people only see evil in starting from an open source project and building something proprietary. But isn't the whole point of the MIT license to have full freedom? I love open source and I actually intend to contribute back to Handy.
People who request features from open source projects might never get what they want or need if it doesn't align with the maintainers vision or if they don't have the bandwidth. Most of the time, open source software comes without any guarantees, without any support, ... Which is perfectly fine since it all comes for free. What I'm doing is building a commercial product, with actual support, and long-term commitment to my customers.
I'm a solopreneur, working hard on the side, trying to build a sustainable business. And working on a project like this for a long time without any revenue is not sustainable unless you have enough runway. I did that a few years back and don't intend to make the same mistake again (https://www.dsebastien.net/2021-01-04-20-months-in-2k-hours-...).
As an example, I'm very focused on Knowledge Management & Obsidian. Integrating first-class support in Knowii Voice AI for interacting with Obsidian is one of the short-term goals I have in mind. It's not something that would make sense to add to Handy, it's too niche. But it does make sense for my app and my customers because many of them are also into knowledge management and have been following me for a long while.
Anyways. I'll build my project, find people who want to support my work, and do my best to deliver what they want and need. Sorry if it goes against the common ideas that forking an open source project to build something proprietary is wrong, that forks should be open source and that they should be vastly different from day one or be free.
Of course, most of what my app does now is very similar to Handy, but isn't it normal when you fork something? Discrepancies grow over time, not overnight. I've already implemented many things differently, and am working on features that will probably never be in Handy anyway. I have different goals and ideas.
Some people only see evil in starting from an open source project and building something proprietary. But isn't the whole point of the MIT license to have full freedom? I love open source and I actually intend to contribute back to Handy.
People who request features from open source projects might never get what they want or need if it doesn't align with the maintainers vision or if they don't have the bandwidth. Most of the time, open source software comes without any guarantees, without any support, ... Which is perfectly fine since it all comes for free. What I'm doing is building a commercial product, with actual support, and long-term commitment to my customers.
I'm a solopreneur, working hard on the side, trying to build a sustainable business. And working on a project like this for a long time without any revenue is not sustainable unless you have enough runway. I did that a few years back and don't intend to make the same mistake again (https://www.dsebastien.net/2021-01-04-20-months-in-2k-hours-...).
As an example, I'm very focused on Knowledge Management & Obsidian. Integrating first-class support in Knowii Voice AI for interacting with Obsidian is one of the short-term goals I have in mind. It's not something that would make sense to add to Handy, it's too niche. But it does make sense for my app and my customers because many of them are also into knowledge management and have been following me for a long while.
Anyways. I'll build my project, find people who want to support my work, and do my best to deliver what they want and need. Sorry if it goes against the common ideas that forking an open source project to build something proprietary is wrong, that forks should be open source and that they should be vastly different from day one or be free.