hi all, Earlier i selected angular as the front end technology for my project, but with the suggestions i got from the community i have done a comparison with three main libraries Angular 5 , React and Vue.js. comparison follows.
Angular is one of the top ranked front end frameworks, since its a complete framework it forces the developer to learn its specific technologies like Typescript. Because of these preselected libraries and usual practices angular learning curve is higher than the other two. though the main selling point and headache being Typescript of being OOP is also sometimes questionable. On my personal experience using this.property caused me errors and made me to pass the object to the function to get rid of the issue. main drawback of angular is bigger learning curve and lack of flexibility compared to other two. Also provides advantages in two way data binding, template reuse better documentation and routing. React succeeding angular in faster rendering with virtual DOM, community adaptation is on top , Simplicity, smaller learning curve, easy syntax and almost all areas. Biggest selling point of react is its bigger eco system than angular and vue. Material UI libraries are more stable and mature with react than the other two. React has a lot of tools according to most developers who have used both angular and react. Another unique feature available with react is its mobile support. Same code can be used in more platforms. It lacks some notable features too. Data flows one way in react, no OOP since its using JS and JSX makes code complex. Though these drawbacks are accepted as features in some scenarios But wider range of people accept it as issues. Developers are facing issues in reusing the components. Vue.js is like the combination of pros from both as most people quoted it has learned from other libraries(React and angular). Vue is faster than react in most small scale scenarios. But its very simple and makes it easy to learn than any other framework out there. It provides better options where react been better compared to angular while fixing the issues react had. while template support is better which makes code re usability a pro for vue. it doesn't use enforce us to use JSX though it supports. It has two way data binding too. number of lines to do the same thing with these libraries resulted lesser with vue. But its adoption rate is low though its constantly gaining popularity. It has a Chinese background, people believe it wont be having a proper documentation, but documentation is better than react even if its not as good as angular. But it's flexible as much as react do. Few user stories suggest vue is better than react even in complex scenarios though most blogs suggest react as the first option because of its bigger eco system. Vue has a future, obviously it's going to be better and people gonna adapt it more Since our task is not that much complex, we don't have very complicated UI design but this web interface have to be supported by so many new people my selection would be vue.js. Hoping it's very simple code syntax and faster learning helps any new supporter to understand and commit to the project to improve the web application in future. My choice was react by the time i started reading for this comparison. But end up with Vue. But i'm waiting for you comments too to finalize the decision. Thank you [1] https://medium.com/@TechMagic/reactjs-vs-angular5-vs-vue-js-what-to-choose-in-2018-b91e028fa91d [2] http://cuelogic.com/blog/angular-vs-react-vs-vue-a-2018-comparison/ [3] https://vuejs.org/v2/guide/comparison.html [4] https://expertise.jetruby.com/react-vs-vue-js-which-front-end-framework-to-choose-in-2018-2a62a1fe76f9 [5] https://medium.com/reverdev/why-we-moved-from-angular-2-to-vue-js-and-why-we-didnt-choose-react-ef807d9f4163 On Tue, Jun 12, 2018 at 10:48 AM, Chris Mattmann <mattm...@apache.org> wrote: > Thanks a lot Ahmed! > > > > > > > > From: Ahmed Ifhaam <ahmedifha...@gmail.com> > Reply-To: "dev@drat.apache.org" <dev@drat.apache.org> > Date: Monday, June 11, 2018 at 1:04 PM > To: "dev@drat.apache.org" <dev@drat.apache.org> > Subject: Re: [GSOC 2018] DRAT UI redesign (was Re: Current Status and > Plans (was Re: Joining on board)) > > > > hi all, > > > > As i mentioned in my previous mail, I'm working on the issue of improving > > drat UI. Currently completed part of my task that is removing shell scripts > > and implementing rest API calls from Java API calls. Now I'm working on GUI > > design which is part of my second task of combining both Proteus and viz > > UIs. i have updated the wiki page for Proteus UI [1]. > > There i have updated it with three sections, > > > > 1. Proteus UI > > > > Here you can find the current UI for proteus > > > > 2. Viz UI > > > > Screen captures of Viz ui showing the features of it. > > > > 3. Currently proposed UI design Combining both viz and proteus > > > > Here you can find the design mock ups for proposed GUI (Proteus) > > > > I'm eagerly waiting for your feedbacks, suggestions and corrections. Let us > > make this better .. > > > > > > Thank you > > > > [1] https://github.com/apache/drat/wiki/Proteus---A-GUI-for-DRAT > > > > On Sun, Jun 3, 2018 at 6:08 PM, Ahmed Ifhaam <ahmedifha...@gmail.com> > wrote: > > > > Hi all, > > > > I was working on replacing drat functions with java API calls, as of now i > > have replaced all functions (CRAWL,INDEX,MAP,REDUCE). > > with this pull request[1] i complete that task and simultaneously working > > on a new design for DRAT proteus web interface as well. > > It would be very helpful if you guys can leave me some feedbacks, > > suggestions and any idea for new web interface too. > > I'm glad for the support i got so far. > > > > > > > > > > [1] https://github.com/apache/drat/pull/131 > > > > > > Thank you > > > > On Wed, May 23, 2018 at 9:48 AM, Chris Mattmann <mattm...@apache.org> > > wrote: > > > > Thanks Amhed I appreciate it! > > > > > > > > Cheers, > > > > Chris > > > > > > > > > > > > > > > > From: Ahmed Ifhaam <ahmedifha...@gmail.com> > > Reply-To: "dev@drat.apache.org" <dev@drat.apache.org> > > Date: Tuesday, May 22, 2018 at 12:23 PM > > To: "dev@drat.apache.org" <dev@drat.apache.org> > > Subject: Re: [GSOC 2018] DRAT UI redesign (was Re: Current Status and > > Plans (was Re: Joining on board)) > > > > > > > > Thanks a lot Chris, I will give my 200% to finish them, Sure i'll make my > > > > dead line for all api's > > > > > > > > On Tue, May 22, 2018 at 10:58 PM, Chris Mattmann <mattm...@apache.org> > > > > wrote: > > > > > > > > Thank you Ahmed, > > > > > > > > > > > > > > > > This is great. So, just to let you know I merged the specific PR you are > > > > talking about > > > > after several rounds of feedback. Others feel free to inspect here: > > > > > > > > > > > > > > > > #129 https://github.com/apache/drat/pull/129 > > > > > > > > > > > > > > > > So what this means is that one portion of the API, which previously relied > > > > on > > > > the equivalent of a Exec/Shell Call to the ./bin/drat index script is > > > > replaced by > > > > direct Java APIs. This is the first step of the proposal – to make a > > > > better UI we > > > > need API calls for DRAT that are not based on System calls and instead are > > > > using > > > > the OODT and DRAT REST APIs. > > > > > > > > > > > > > > > > Regarding the sendEvent function I think that the best way to describe it > > > > is > > > > to read this paper, and watch this lecture from ApacheCon NA 2013: > > > > > > > > > > > > > > > > First: > > > > > > > > https://www.researchgate.net/profile/Paul_Ramirez3/ > > > > publication/232619682_A_Reusable_Process_Control_System_ > > Framework_for_the_ > > > > Orbiting_Carbon_Observatory_and_NPP_Sounder_PEATE_missions/links/ > > > > 0c960528a4d0967196000000.pdf > > > > > > > > > > > > > > > > Then: > > > > > > > > https://www.slideshare.net/chrismattmann/wengines- > > > > workflows-and-2-years-of-advanced-data-processing-in-apache-oodt > > > > > > > > > > > > > > > > I think that will help a lot to understand it. You may also want to read: > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/OODT/Catalog+and+Archive > > > > > > > > > > > > > > > > And specifically the right hand column under Workflow / CAS-PGE / Resource > > > > Manager > > > > > > > > > > > > > > > > Also FWIW, I think based on the size of your contribution for the > > > > replacing the index function, > > > > and the quickness you worked on that, I would expect that the _entire_ set > > > > of remaining APIs > > > > e.g., crawl, map, and reduce, are completed by next week. I am committed > > > > to helping you > > > > get there, so please keep asking questions. I think to stay on schedule we > > > > need to finish the > > > > full set of APIs by next week so you can get started with the actual > > > > beginnings of the API development. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Chris > > > > > > > > > > > > > > > > > > > > > > > > From: Ahmed Ifhaam <ahmedifha...@gmail.com> > > > > Reply-To: "dev@drat.apache.org" <dev@drat.apache.org> > > > > Date: Tuesday, May 22, 2018 at 7:54 AM > > > > To: "dev@drat.apache.org" <dev@drat.apache.org> > > > > Subject: Re: Current Status and Plans (was Re: Joining on board) > > > > > > > > > > > > > > > > hi all > > > > > > > > cureently i have completed the task of moving indexing function from > > > > > > > > process wrapper to java calls. > > > > > > > > but other > > > > > > > > funcyions like crawling,mapping needs some more deeper understanding where > > > > > > > > i need more time so ill be completing one more api replacement from one > > > > > > > > week as of today. > > > > > > > > > > > > > > > > from you all i need some support to understand what is the workflow whats > > > > > > > > the sendingevent function does and some docs which describes it better. > > > > > > > > > > > > > > > > thank you > > > > > > > > > > > > > > > > On 22 May 2018 12:06 a.m., "Chris Mattmann" <mattm...@apache.org> wrote: > > > > > > > > > > > > > > > > Dear Ahmed, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Can you please update the community on your plans for what you are working > > > > > > > > on what is done and what you expect to complete in the next week or two? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Chris > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > From: Ahmed Ifhaam <ahmedifha...@gmail.com> > > > > > > > > Reply-To: "dev@drat.apache.org" <dev@drat.apache.org> > > > > > > > > Date: Sunday, May 13, 2018 at 12:30 PM > > > > > > > > To: "dev@drat.apache.org" <dev@drat.apache.org> > > > > > > > > Subject: Joining on board > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > hi all, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > As part of GSOC_2018 i'll be working on DRAT. I'm very pleased to work on > > > > > > > > > > > > > > > > this and expect your support and advice as well. I'ts great to joining you > > > > > > > > > > > > > > > > all. Thank you > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > *Ahmed Ifhaam * > > > > > > > > > > > > > > > > University of Kelaniya | MIT '19 > > > > > > > > > > > > > > > > Tel :- 0662244937 | Mob :- 0776699609 > > > > > > > > > > > > > > > > ahmedifha...@gmail.com <e-mail-ahmedifha...@gmail.com> > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > *Ahmed Ifhaam * > > > > University of Kelaniya | MIT '19 > > > > Tel :- 0662244937 | Mob :- 0776699609 > > > > ahmedifha...@gmail.com <e-mail-ahmedifha...@gmail.com> > > > > > > > > > > > > > > -- > > *Ahmed Ifhaam * > > University of Kelaniya | MIT '19 > > Tel :- 0662244937 | Mob :- 0776699609 > > ahmedifha...@gmail.com <e-mail-ahmedifha...@gmail.com> > > > > > > > > > > -- > > *Ahmed Ifhaam * > > University of Kelaniya | MIT '19 > > Tel :- 0662244937 | Mob :- 0776699609 > > ahmedifha...@gmail.com <e-mail-ahmedifha...@gmail.com> > > > > -- *Ahmed Ifhaam * University of Kelaniya | MIT '19 Tel :- 0662244937 | Mob :- 0776699609 ahmedifha...@gmail.com <e-mail-ahmedifha...@gmail.com>
