search

glittershark / reactable

Fast, flexible, and simple data tables in React
glittershark.github.io/reactable
MIT License
1.51k stars 223 forks source link

Is this repository maintained? #383

Open sassanh opened 6 years ago

sassanh commented 6 years ago

I'm upgrading to React 16 in my development machine and it's seems like it's reactable is incompatible with React 16. Considering the last commit on this repo i'm worried it won't be maintained to support React 16. I wanna discuss this here so that if it's not going to be updated we can decide to migrate to something else before it's late.

rkarroll commented 6 years ago

I was wondering the same thing.

rkarroll commented 6 years ago

fixed-data-table-2 seems to be much more actively maintained and what I'll be using on my project.

sassanh commented 6 years ago

15 months ago after 1 month of starting to work on Frontend, seeing the state of frontend libraries repositories I concluded "Never use a JS library unless it's a big one with lots of stars in repo" because I saw many of them stop being maintained. Today I change that conclusion to "Never use a JS library unless it's ReactJS, babel-*, browserify, or things like that, or you don't expect any update on it". I go with implementing a table for my project as I don't know if fixed-data-table-2 will be maintained 2 months later.

sleaze commented 6 years ago

Agreed, it is frustrating and wastes a lot of peoples time.

sassanh commented 6 years ago

We can't blame the repository owner, he has his own life, but I don't know why it happens only to js repositories, not python repos for example. Maybe repo owners should spend some time and give others some responsibilities so that when they can't spend time, others can fill the gap.

Kadrian commented 6 years ago

Should we create a fork and start maintaining it somewhere else? What's the usual open source procedure in this case? @glittershark Are you open to transferring ownership?

sassanh commented 6 years ago

@Kadrian forking and maintaining elsewhere is usually not an appropriate decision unless repository owner doesn't respond for a long time. Usually the appropriate thing is that repository owner gives permissions to some other individuals who are interested if he doesn't have time to maintain himself. These individuals are usually those who have some accepted PRs.

I hope @glittershark can manage it.

stclairdaniel commented 6 years ago

@glittershark Any word on this?

jackson-sandland commented 6 years ago

Bueller...

mikeLspohn commented 6 years ago

I feel like it's safe to say this isn't being actively maintained at this point...

dandv commented 4 years ago

There's a ton of table components for React. I'm happy to see some of them die - makes the selection process a bit easier.

That selection process would be much easier if those who start new projects, explained WHY they're reinventing the wheel, and how it's different from existing wheels; alas, almost nobody seems to care about that, and they go ahead and open source yet another table (or whatever) component.

el1s7 commented 3 years ago

Well i thought it would be good to make a fork of this and i added some features Feel free to contribute https://github.com/elis-k/reactablex