-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call for Funding | Future for Production Usage #3159
Comments
I'm not a company, I'm a freelancer, and I can't spare $2,000, but $100-200 is within my means. I'm in. |
The latest RC sent yesterday should fix the issues with wasm builds. I'm on vacation from work, I'm going to dedicate myself to GetX for the next 2-3 weeks to launch version 5. I believe that any version after 5 will be much easier to maintain, the codebase is old (I wrote GetX 5 years ago) and I'm updating everything. Furthermore, the change to Navigator 2 was not something that changed part of the project, it simply caused it to be rewritten from scratch. GetX is currently used by 181,299 people, which is an astonishingly large number, but I'm sure that even though it's desirable, it would be practically impossible to earn income from it, and I'm fine with that. I work to support myself; this is where I have fun when I have the time. But rest assured, I will never abandon it, I have an immense debt to Flutter and the community. I'm sorry for the delay, I would like to provide more time for him, and I will organize myself for that. |
Thank you so much for your honesty and dedication. Your work with GetX has helped build careers for thousands of developers, and we'll continue to keep you in our thoughts and prayers. GetX is truly one of the best things that has happened to the Flutter ecosystem. We’re all hopeful to see many new changes, tutorials, and updates in the near future. A suggestion for @jonataslaw: Please consider accepting financial contributions as a well-deserved reward. If you still feel you don’t need it, perhaps you could use it to hire someone to update the documentation and create comprehensive Flutter GetX courses, especially with GetX 5. This would tremendously benefit the community and amplify its impact tenfold. |
It's nice to have that commitment, but so far too many people are using getx Please consider accepting a financial contribution as a deserved reward. If you still don't feel like you need it, maybe you can use it to hire someone to update documentation and create a comprehensive Flutter GetX course, especially GetX 5. This will greatly benefit the community and increase its impact tenfold |
Thank you so much for your kind words and consideration! I truly appreciate the suggestion of accepting financial contributions and understand the importance of ensuring that GetX remains a valuable tool for the Flutter community. It’s gratifying to know that the work I’ve done with GetX has helped so many developers and companies around the world. My commitment to GetX has always been and will always be rooted in my passion for Flutter and my desire to contribute to something greater. While I don't depend on the project financially, I’m completely open to the idea that contributions could be used to further strengthen the community. With this support, I could dedicate more time to the library, delivering bug fixes and new features more quickly. The idea of hiring someone to help or improve the documentation also seems very reasonable to me. My focus right now is to ensure that version 5 is released as quickly as possible and that it is stable and easy to maintain. I'm dedicating all my free time to this, and any additional support, whether financial or in terms of collaboration, will certainly be welcomed and used in the best possible way to benefit the community. Once again, thank you so much for the support and encouragement. I’m excited about the future possibilities and remain committed to continuing to improve GetX for everyone. |
@markbreuss Kindly Contribute and also @jonataslaw Tell us how to send the amount. |
Kindly Donate Here: https://ko-fi.com/jonataslaw |
What are the possibilities for supporting GetX from Russia and Belarus? Or other places where there is no visa/mastercard/paypal |
Wasm support is there! I'm doing an experiment with nested routes that will simplify the entire codebase. There's just one small detail to make it ready. I'm sorry for the delay, I promise I'm doing everything I can with the time I have left. |
Well, I would like to know, but I haven’t found anything yet. I have residency in both Europe and Brazil, and when the BRICS meeting takes place and Brazil and Russia have a new alternative payment system, I think this will become simpler. |
What is the forecast to release @jonataslaw ? In this year or in 2025? |
@markbreuss Have you contributed?? |
We as a company would be happy to contribute, like I said. However we can, as you will understand, not contribute into the blind. Obviously the open source "coffee buying" approach has had issues in this specific case. I would thus argue for a more "traditional " approach, like any software agency or freelancer handles coding projects. So @jonataslaw if we want to get this going, send me a quote at [email protected] which includes the delivery of a first stable version of getx5 published on pub.dev with a reasonable deadline and a committment of certain development hours. Or at least something along those lines. You get the signed offer back, and after delivery the payment will be wired. |
Any news? |
@markbreuss is you haven't arranged it yet with the dormant dev of the GetX, you may have better chances with @Aniketkhote, who maintains GetX's fork - https://pub.dev/packages/refreshed. |
I think if we all start chipping it would be much better instead of asking him |
I read the article and thought you were a pioneer, but after reading this comment, it turns out you're just being sly. |
You’re turning the gesture of offering coffee to open-source contributors into something twisted. Instead of giving them the recognition they deserve for their hard work, which they never asked for in the first place, are you aiming to close the deal? Your actions are completely contradictory to the message of your article. It’s really disappointing. I use GetX and love the library, and when I saw the title, I thought you were a good person. But by the time I scrolled to the end of the article and read your comment, it was such a letdown |
Hi there,
I completely agree with @jonana0999's sentiments. It's disheartening to see
how the narrative has shifted from appreciation to entitlement.
Open-source maintainers like @jonataslaw dedicate their time and skills to
create tools that benefit countless developers and companies. While
financial contributions are always welcome, they should be given freely as
a gesture of support, not with the expectation of turning the maintainer
into a contracted freelancer.
If GetX has been valuable to these companies, the right way to show
appreciation is through donations or contributions without strings
attached.
Best,
Faheem
…On Tue, Jan 14, 2025 at 10:36 PM jonana0999 ***@***.***> wrote:
We as a company would be happy to contribute, like I said.
However we can, as you will understand, not contribute into the blind. I
need an offer and a contract that outlines the work that will be done and a
deadline.
Obviously the open source "coffee buying" approach has had issues in this
specific case. I would thus argue for a more "traditional " approach, like
any software agency or freelancer handles coding projects.
So @jonataslaw <https://github.com/jonataslaw> if we want to get this
going, send me a quote at ***@***.*** which includes the delivery
of a first stable version of getx5 published on pub.dev with a reasonable
deadline and a committment of certain development hours. Or at least
something along those lines.
You get the signed offer back, and after delivery the payment will be
wired.
You’re turning the gesture of offering coffee to open-source contributors
into something twisted. Instead of giving them the recognition they deserve
for their hard work, which they never asked for in the first place, are you
aiming to close the deal? Your actions are completely contradictory to the
message of your article. It’s really disappointing. I use GetX and love the
library, and when I saw the title, I thought you were a good person. But by
the time I scrolled to the end of the article and read your comment, it was
such a letdown
—
Reply to this email directly, view it on GitHub
<#3159 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIRXJSB3ZUUQEG245LIANGD2KVDIPAVCNFSM6AAAAABMIA74B6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJQGY3DKOBZHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
What a waste of money, just switch to BLOC or Riverpod and do guys, yourself, a favor. |
I suggest people try out the latest release candidate instead and share any issues here which will help gather confidence that it is working well. |
I cant, GetX is so much better and easier to work with. I wish @jonataslaw update the version 5 to new stable. |
agree, but jonas should make it aavailable and replace the version 4 before
that so more than a millions devs start noticing
…On Sun, Jan 19, 2025 at 7:04 AM deepss1 ***@***.***> wrote:
I suggest people try out the latest release candidate instead and share
any issues here which will help gather confidence that it is working well.
—
Reply to this email directly, view it on GitHub
<#3159 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIRXJSA4EF3NTBNXS54BYDL2LMBZPAVCNFSM6AAAAABMIA74B6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBQGQ3TONZTGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
We are a startup which has built their App with Getx. https://www.markone.at/
We want to upgrade to the latest Flutter Version and especially start using WASM Support.
As is now it looks like it becomes a buisiness risk to continue with Getx as the upgradability is not certain.
Changing out our whole State Management would proboably take us months and 10s of thousands of dollars in develompent costs.
Given the popularity of the package I would assume that there are thousands of companies in the same situation.
I know that open source work can be hard and often be unrewarding.
My proposal is that companies that are in the same situation, pool together ressources to fund a development contract with a maintaner to get out the 5.0 version to future proof it for the next versions.
if only 50 companies would join this with 2000 USD we could set up a development contract of around 100K which I imagine would suffice for some time.
We are willing to make the first move by providing 4000 USD which is still an order of magnitude cheaper than ripping out our state management.
What are the toughts of other people using Getx in a serious production environment?
@jonataslaw would you be open to something like this?
Is funding even the bottleneck?
Thanks for your work so far and all the best,
Mark Breuß
The text was updated successfully, but these errors were encountered: