Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I worked a lot with AG Grid in my previous job.

Cons:

  Buggy around save and restore with complex scenarios like row grouping, 
  aggregations and server side row model. 
 
  Massive size of library, easily the biggest dependency in bundle. You need to 
  do some work in bundler to optimize into own immutable chunk. 
 
  Complex upgrade process. They release a new major version every year and if 
  you use a lot of features and have custom theme, this can be painful.
  
  Mismatch with react. Ag Grid core is imperative. You will spend a lot of time 
  fiddling with columnApi and gridApi if your use case is complex enough.
Good:

  Probably most advanced and feature complete grid implementation.  

  Framework-agnostic and well maintained. Given feature scope, it works surprisingly 
  well. 
The problem with things like AG Grid is that designers and product people will try to invent weird things on top of it. I think as long you do not customize too much and use default features, you will be good.


Thanks for the feedback! We've actually addressed most of the Cons you've listed in recent releases:

We added a Grid State API in v31 to make saving & restoring state easier, which includes things like Row Grouping: https://www.ag-grid.com/react-data-grid/grid-state/

Our latest release reduced our bundle size by 20-40% (depending on what features you're using) and we're planning on reducing this further over the next few releases: https://www.ag-grid.com/react-data-grid/modules/

We now offer LTS versions of AG Grid and AG Charts so that you can upgrade at your own pace: https://blog.ag-grid.com/introducing-long-term-support-for-a...

These changes were all based on feedback just like this, so thanks for taking the time out to share your experience




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: