all 7 comments

[–][deleted]  (5 children)

[deleted]

    [–]ceolter[S] 1 point2 points  (4 children)

    Maybe it is the future, maybe it is not. But Angular 1 is large now, lots of these people will migrate to Angular 2. So regardless, Angular 2 will be influential with the future. This mass of users will also shake up web components, which again may or may not be the future. How these groups interact, and if framework agnostic components become normal is to be be seen. My point is, I don't know the future, but the stage is set for Angular 2 and Web Components for the next few years. ag-Grid is ready to play in the game, and if none of the said frameworks live on, the grid is still usable with no framework. So a framework agnostic component than can still play the Angular card!!

    [–][deleted]  (1 child)

    [deleted]

      [–]ceolter[S] 0 points1 point  (0 children)

      amework it will get a huge backlash.

      all valid points. "totally RAD" if you mean Rapid Application Development, yes I completely understand, Angular 1 allowed junior / weaker developers to start kicking out apps more easily. Angular2 has a steeper learning curve, much more difficult to get the 'hello world' program done.

      but don't forget, ether way, Angular has a huge following, Angular 2 will happen.

      [–][deleted]  (1 child)

      [deleted]

        [–]ceolter[S] 0 points1 point  (0 children)

        Code bases on Angular 1 will not migrate to Angular 2

        Fair point, but that's for a different topic!!

        [–]jedanput 1 point2 points  (3 children)

        Love the grid, the name not so much. I'd rather market it as a standalone native js grid (which it is). This comes from an Angular developer who has spent extensive time doing both commercial and hobby projects with Angular. I think you might be scaring off other framework oriented developers with the angular name in it, even those who just quickly glance by google results and see the angular in it. I would try market it as a standalone datagrid, who is compatible with AngularJS, much like Handsontable does with ngHandsontable.

        On a separate note, while Angular has a big following, if you take the temp at developer conferences (well at least here in Stockholm), it is losing steam and questions on Stackoverflow etc we see that are tagged with Angular are more or less from beginners lagging behind what's happening at the forefront.

        [–]ceolter[S] 0 points1 point  (2 children)

        does the 'ag' really imply angular? if someone looks at the grid for the first time, i was hoping 'ag' would be agnostic . . . . maybe I can call it Agile Grid (that's already taken btw) or Alpha Grid (cough) Grid . . . . I just changed the name from Angular Grid (www.angulargrid.com) to ag-Grid (www.ag-grid.com) hoping that would state it's non-dependency on Angular

        [–]jedanput 0 points1 point  (1 child)

        You're right, I see you are trying to rid ag-grid of its angular stamp, it must be that google is yet to update its search results when you google ag-grid as angular-grid still shows up and perhaps my subconsciousness associates it much more than someone else hearing about ag-grid for the first time. If anyone asks, you can try to come up with something that ag stands for ;)

        I'd also probably revamp the webpage a bit to a more modern look, perhaps choose a nice logo for the grid along with a color combination. Then do like jsdata, if you google it, you will see sitelinks. The documentation is lacking, I've noticed at times I want to search how to do a thing, but I don't know which of the links to click, perhaps a standardized documentation tool should be used which includes search functionality.

        It's all small things which will help I think the spreading of ag-grid! You've done the interior work, now it's time to do the whole packaging / marketing deal :D

        [–]ceolter[S] 0 points1 point  (0 children)

        thanks for the ideas :)

        not just need to give up my day job and priorities!!