Removing the GetX package from Options

[filiph]

It looks like the package author makes some pretty wild claims* on social media. Removing the links, at least until we can verify that these claims are true.

*) The claims are about the package's official support from Google and/or usage by Google Product Managers — neither of which I'm aware of. I'd also like to verify the claims about performance (currently, they are backed only by a benchmark written by the author).

[sfshaza2]

Thanks for that, @filiph

[OrlandoEduardo101]

Big day!

[BlackLeg15]

Make Flutter great again

[pauloantonelli]

finally! ¬¬.

[geronimoxd]

take out this shit! #bigday

[MaxweelFreitas]

Flutter really don't need of a toxic ambient. Let's cut it by root if is true!

[fabiojansenbr]

@filiph do you have any proof of this "wild claims"?

[fabioselau077]

I hope it's just a mistake and the package is added to the documentation again.
The package is one of the most used in the world by the Flutter community and removing the documentation will be a great loss for new users.

[pauloantonelli]

I hope it's just a mistake and the package is added to the documentation again.
The package is one of the most used in the world by the Flutter community and removing the documentation will be a great loss for new users.

I don't see it that way! I see that it is a way for new people to start correctly, with tools that follow good opensource practices.

[fabioselau077]

I hope it's just a mistake and the package is added to the documentation again.
The package is one of the most used in the world by the Flutter community and removing the documentation will be a great loss for new users.

I don't see it that way! I see that it is a way for new people to start correctly, with tools that follow good opensource practices.

From what I saw the people involved here in the post are from a community that always discussed with the author of the package.
Do you think doing this will contribute to the Flutter and open-source community in general?
Doing everything to harm a package designer who contributes much more to Flutter than you all do just by personal discussions doesn't help anything in the community, it just hurts.
I'm not saying that if he did something bad he shouldn't be punished but contributing to it just because he doesn't like the creator is a bad thing.

[mkiisoft]

@fabiojansenbr yes, we have the proof.

[mkiisoft]

Doing everything to harm a package designer who contributes much more to Flutter than you all do just by personal discussions doesn't help anything in the community, it just hurts.

Please, use a respectful language. This is a healthy community and we don't want toxicity.

[fabiojansenbr]

@fabiojansenbr yes, we have the proof.

Where? Im Just trying to understand.

[gabrielscr]

@mkiisoft show us, i wanna see

[fabioselau077]

Doing everything to harm a package designer who contributes much more to Flutter than you all do just by personal discussions doesn't help anything in the community, it just hurts.

Please, use a respectful language. This is a healthy community and we don't want toxicity.

Doing everything to harm the author of a package just because you don't like it is not toxic, right?

[pauloantonelli]

I hope it's just a mistake and the package is added to the documentation again.
The package is one of the most used in the world by the Flutter community and removing the documentation will be a great loss for new users.

I don't see it that way! I see that it is a way for new people to start correctly, with tools that follow good opensource practices.

From what I saw the people involved here in the post are from a community that always discussed with the author of the package.
Do you think doing this will contribute to the Flutter and open-source community in general?
Doing everything to harm a package designer who contributes much more to Flutter than you all do just by personal discussions doesn't help anything in the community, it just hurts.
I'm not saying that if he did something bad he shouldn't be punished but contributing to it just because he doesn't like the creator is a bad thing.

I think the issue is not community or package x or y, but the flutter is an environment with good practices from opensource, which always guarantee us software, tools ... reliable and also scalable.

[mkiisoft]

We should call a mod here and close comments as the responses are not going anywhere. Thanks everyone for this effort.

[jehhxuxu]

@fabiojansenbr yes, we have the proof.

Where? Im Just trying to understand.

we need to explain? or the package?
https://github.com/jonataslaw/getx/blob/afebab9c7e826a6e994b41017c38f3bb70264178/CHANGELOG.md

[rene-kt]

brazilian guys celebrating that a brazilian package was officially removed, smh. Is that the way yall support the community? I mean, theres a plenty of ways to correct this issue, removing the package is a huge step towards back to the community. doesnt make sense: delete a WHOLE package just because of some BS that the creator has said

[OrlandoEduardo101]

brazilian guys celebrating that a brazilian package was officially removed, smh. Is that the way yall support the community? I mean, theres a plenty of ways to correct this issue, removing the package is a huge step towards back to the community. doesnt make sense: delete a WHOLE package just because of some BS that the creator has said

man, did you read? it was only removed from the official flutter documentation.

[rkpontes]

Removing the Google package will favor a select group that people who are unable to compete honestly and use inefficient arguments. I support Getx as it opens doors for new and experienced developers.

[jonataslaw]

Well, I'm seeing this now and:
I never said that Google officially supported the package (not least because it doesn't make sense, it is a package, not part of the SDK).
As for the performance issue, there are benchmarks in the repositories, but there is freedom to check.
I hope this is all a misunderstanding, I have always had the greatest respect for the flutter and dart team.
This will cause a revolution in the community, and this is bad.

[mkiisoft]

Everyone here: The package was not removed out of existence, only is not showing as Flutter supported/approved one in the site, that's all. Please, let's close comments for this PR.

[fabioselau077]

brazilian guys celebrating that a brazilian package was officially removed, smh. Is that the way yall support the community? I mean, theres a plenty of ways to correct this issue, removing the package is a huge step towards back to the community. doesnt make sense: delete a WHOLE package just because of some BS that the creator has said

I just hovered over their profile and I noticed that they are from a group that has had discussions with the author of the package for years.
I just want to warn you that harming a fantastic plugin just by having a fight with the author is not good.
You are Brazilians, instead of helping a Brazilian who helps the community you are undoing just for the sake of ego.

@edit: I know you guys are going to give my comment a "deslike", but I don't care, I know I'm on the right side of the story and I'm not participating in a closed group that is attacking the package just because I don't like the author.

[rene-kt]

brazilian guys celebrating that a brazilian package was officially removed, smh. Is that the way yall support the community? I mean, theres a plenty of ways to correct this issue, removing the package is a huge step towards back to the community. doesnt make sense: delete a WHOLE package just because of some BS that the creator has said

man, did you read? it was only removed from the official flutter documentation.

yeah, indeed, i get it wrong, sorry, thx anyway

[jehhxuxu]

Removing the Google package will favor a select group that people who are unable to compete honestly and use inefficient arguments. I support Getx as it opens doors for new and experienced developers.

select group? this is an efficient argument? this is true?

[Hixie]

Folks, please recall our code of conduct, which is that we must all "Be kind. Be courteous. Be welcoming.".

It's not enough just to be polite. You have to be actively friendly and welcoming. Many of the comments here are unnecessarily antagonistic, aggressive, or generally less than entirely friendly.

[sfshaza2]

Thanks for locking, @Hixie! I was just coming to do that.