Alternatives to winjs logo

Alternatives to winjs

AngularJS, Electron, Knockout, jQuery, and React are the most popular alternatives and competitors to winjs.
13
40
+ 1
1

What is winjs and what are its top alternatives?

WinJS is a set of JavaScript toolkits that allow developers to build applications using HTML/JS/CSS technology forged with the following principles in mind: 1. Provide developers with a distinctive set of UI controls with high polish and performance with fundamental support for touch, mouse, keyboard and accessibility. 2. Provide developers with a cohesive set of components and utilities to build the scaffolding and infrastructure of their applications'
winjs is a tool in the Javascript UI Libraries category of a tech stack.
winjs is an open source tool with 4.1K GitHub stars and 497 GitHub forks. Here’s a link to winjs's open source repository on GitHub

Top Alternatives to winjs

  • AngularJS
    AngularJS

    AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding. ...

  • Electron
    Electron

    With Electron, creating a desktop application for your company or idea is easy. Initially developed for GitHub's Atom editor, Electron has since been used to create applications by companies like Microsoft, Facebook, Slack, and Docker. The Electron framework lets you write cross-platform desktop applications using JavaScript, HTML and CSS. It is based on io.js and Chromium and is used in the Atom editor. ...

  • Knockout
    Knockout

    It is a JavaScript library that helps you to create rich, responsive display and editor user interfaces with a clean underlying data model. Any time you have sections of UI that update dynamically (e.g., changing depending on the user’s actions or when an external data source changes), it can help you implement it more simply and maintainably. ...

  • jQuery
    jQuery

    jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML. ...

  • React
    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

  • Vue.js
    Vue.js

    It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API. ...

  • jQuery UI
    jQuery UI

    Whether you're building highly interactive web applications or you just need to add a date picker to a form control, jQuery UI is the perfect choice. ...

  • Select2
    Select2

    It gives you a customizable select box with support for searching, tagging, remote data sets, infinite scrolling, and many other highly used options. It comes with support for RTL environments, searching with diacritics and over 40 languages built-in. ...

winjs alternatives & related posts

AngularJS logo

AngularJS

56.4K
39.7K
5.2K
Superheroic JavaScript MVW Framework
56.4K
39.7K
+ 1
5.2K
PROS OF ANGULARJS
  • 889
    Quick to develop
  • 588
    Great mvc
  • 572
    Powerful
  • 521
    Restful
  • 503
    Backed by google
  • 349
    Two-way data binding
  • 343
    Javascript
  • 328
    Open source
  • 306
    Dependency injection
  • 197
    Readable
  • 75
    Fast
  • 64
    Directives
  • 63
    Great community
  • 56
    Free
  • 38
    Extend html vocabulary
  • 29
    Components
  • 26
    Easy to test
  • 24
    Easy to learn
  • 23
    Easy to templates
  • 23
    Great documentation
  • 21
    Easy to start
  • 18
    Awesome
  • 17
    Light weight
  • 14
    Javascript mvw framework
  • 14
    Angular 2.0
  • 13
    Great extensions
  • 13
    Efficient
  • 10
    Easy to prototype with
  • 8
    Coffeescript
  • 8
    High performance
  • 7
    Mvc
  • 7
    Two-way binding
  • 7
    Lots of community modules
  • 6
    Clean and keeps code readable
  • 6
    Easy to e2e
  • 5
    One of the best frameworks
  • 5
    Easy for small applications
  • 4
    Fast development
  • 4
    Works great with jquery
  • 3
    I do not touch DOM
  • 2
    The two-way Data Binding is awesome
  • 2
    Typescript
  • 2
    Dart
  • 2
    Community
  • 2
    Hierarchical Data Structure
  • 2
    Be a developer, not a plumber.
  • 2
    Declarative programming
  • 1
    Common Place
  • 1
    Great
  • 1
    Very very useful and fast framework for development
  • 1
    Amazing community support
  • 1
    Readable code
  • 1
    Linear learning curve
  • 1
    Scopes
  • 1
    Programming fun again
  • 1
    The powerful of binding, routing and controlling routes
  • 1
    Consistency with backend architecture if using Nest
  • 1
    Fkin awesome
  • 1
    Opinionated in the right areas
  • 1
    Supports api , easy development
CONS OF ANGULARJS
  • 10
    Complex
  • 3
    Dependency injection
  • 2
    Event Listener Overload
  • 2
    Learning Curve
  • 1
    Hard to learn

related AngularJS posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 26 upvotes · 3.3M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API’s resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 23 upvotes · 1.8M views

Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

  • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
  • Vue Styleguidist as our style guide and pool of developed Vue.js components
  • Vuetify as Material Component Framework (for fast app development)
  • TypeScript as programming language
  • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
  • ESLint, TSLint and Prettier for coding style and code analyzes
  • Jest as testing framework
  • Google Fonts and Font Awesome for typography and icon toolkit
  • NativeScript-Vue for mobile development

The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

  • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
  • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
  • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
  • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
  • Large scaling. Vue.js can help to develop pretty large reusable templates.
  • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
See more
Electron logo

Electron

9.7K
8.9K
140
Build cross platform desktop apps with JavaScript, HTML, and CSS
9.7K
8.9K
+ 1
140
PROS OF ELECTRON
  • 66
    Easy to make rich cross platform desktop applications
  • 51
    Open source
  • 13
    Great looking apps such as Slack and Visual Studio Code
  • 7
    Because it's cross platform
  • 3
    Use Node.js in the Main Process
CONS OF ELECTRON
  • 18
    Uses a lot of memory
  • 8
    User experience never as good as a native app
  • 4
    No proper documentation
  • 4
    Does not native
  • 1
    Each app needs to install a new chromium + nodejs
  • 1
    Wrong reference for dom inspection

related Electron posts

The Slack desktop app was originally written us the MacGap framework, which used Apple’s WebView to host web content inside of a native app frame. As this approach continued to present product limitations, Slack decided to migrate the desktop app to Electron. Electron is a platform that combines the rendering engine from Chromium and the Node.js runtime and module system. The desktop app is written as a modern ES6 + async/await React application.

For the desktop app, Slack takes a hybrid approach, wherein some of the assets ship as part of the app, but most of their assets and code are loaded remotely.

See more

Slack's new desktop application was launched for macOS. It was built using Electron for a faster, frameless look with a host of background improvements for a superior Slack experience. Instead of adopting a complete-in-box approach taken by other apps, Slack prefers a hybrid approach where some of the assets are loaded as part of the app, while others are made available remotely. Slack's original desktop app was written using the MacGap v1 framework using WebView to host web content within the native app frame. But it was difficult to upgrade with new features only available to Apple's WKWebView and moving to this view called for a total application rewrite.

Electron brings together Chromium's rendering engine with the Node.js runtime and module system. The new desktop app is now based on an ES6 + async/await React application is currently being moved gradually to TypeScript. Electron functions on Chromium's multi-process model, with each Slack team signed into a separate process and memory space. It also helps prevent remote content to directly access desktop features using a feature called WebView Element which creates a fresh Chromium renderer process and assigns rendering of content for its hosting renderer. Additional security can be ensured by preventing Node.js modules from leaking into the API surface and watching out for APIs with file paths. Communication between processes on Electron is carried out via electron-remote, a pared-down, zippy version of Electron's remote module, which makes implementing the web apps UI much easier.

See more
Knockout logo

Knockout

219
195
6
Create rich, responsive UIs with JavaScript
219
195
+ 1
6
PROS OF KNOCKOUT
  • 3
    Data centered application
  • 2
    Great for validations
  • 1
    Open source
CONS OF KNOCKOUT
    Be the first to leave a con

    related Knockout posts

    jQuery logo

    jQuery

    180.1K
    60.6K
    6.6K
    The Write Less, Do More, JavaScript Library.
    180.1K
    60.6K
    + 1
    6.6K
    PROS OF JQUERY
    • 1.3K
      Cross-browser
    • 957
      Dom manipulation
    • 808
      Power
    • 660
      Open source
    • 610
      Plugins
    • 458
      Easy
    • 395
      Popular
    • 350
      Feature-rich
    • 281
      Html5
    • 227
      Light weight
    • 92
      Simple
    • 84
      Great community
    • 79
      CSS3 Compliant
    • 69
      Mobile friendly
    • 67
      Fast
    • 43
      Intuitive
    • 42
      Swiss Army knife for webdev
    • 35
      Huge Community
    • 11
      Easy to learn
    • 4
      Clean code
    • 3
      Because of Ajax request :)
    • 2
      Just awesome
    • 2
      Used everywhere
    • 2
      Powerful
    • 2
      Nice
    • 1
      Widely Used
    • 1
      Improves productivity
    • 1
      Open Source, Simple, Easy Setup
    • 1
      It Just Works
    • 1
      Industry acceptance
    • 1
      Allows great manipulation of HTML and CSS
    • 1
      Javascript
    • 1
      Easy Setup
    CONS OF JQUERY
    • 6
      Large size
    • 5
      Sometimes inconsistent API
    • 5
      Encourages DOM as primary data source
    • 2
      Live events is overly complex feature

    related jQuery posts

    Kir Shatrov
    Engineering Lead at Shopify · | 22 upvotes · 880.6K views

    The client-side stack of Shopify Admin has been a long journey. It started with HTML templates, jQuery and Prototype. We moved to Batman.js, our in-house Single-Page-Application framework (SPA), in 2013. Then, we re-evaluated our approach and moved back to statically rendered HTML and vanilla JavaScript. As the front-end ecosystem matured, we felt that it was time to rethink our approach again. Last year, we started working on moving Shopify Admin to React and TypeScript.

    Many things have changed since the days of jQuery and Batman. JavaScript execution is much faster. We can easily render our apps on the server to do less work on the client, and the resources and tooling for developers are substantially better with React than we ever had with Batman.

    #FrameworksFullStack #Languages

    See more
    Ganesa Vijayakumar
    Full Stack Coder | Technical Lead · | 19 upvotes · 3.3M views

    I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

    I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

    As per my work experience and knowledge, I have chosen the followings stacks to this mission.

    UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

    Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

    Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

    Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

    Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

    Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

    Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

    Happy Coding! Suggestions are welcome! :)

    Thanks, Ganesa

    See more
    React logo

    React

    143.8K
    121.4K
    4K
    A JavaScript library for building user interfaces
    143.8K
    121.4K
    + 1
    4K
    PROS OF REACT
    • 801
      Components
    • 663
      Virtual dom
    • 572
      Performance
    • 500
      Simplicity
    • 442
      Composable
    • 183
      Data flow
    • 165
      Declarative
    • 126
      Isn't an mvc framework
    • 116
      Reactive updates
    • 113
      Explicit app state
    • 44
      JSX
    • 27
      Learn once, write everywhere
    • 20
      Uni-directional data flow
    • 20
      Easy to Use
    • 16
      Works great with Flux Architecture
    • 11
      Great perfomance
    • 9
      Built by Facebook
    • 9
      Javascript
    • 7
      TypeScript support
    • 6
      Speed
    • 5
      Hooks
    • 5
      Excellent Documentation
    • 5
      Props
    • 5
      Functional
    • 5
      Easy as Lego
    • 5
      Closer to standard JavaScript and HTML than others
    • 5
      Cross-platform
    • 5
      Server Side Rendering
    • 5
      Feels like the 90s
    • 5
      Easy to start
    • 5
      Awesome
    • 5
      Scalable
    • 4
      Strong Community
    • 4
      Server side views
    • 4
      Fancy third party tools
    • 4
      Scales super well
    • 4
      Start simple
    • 4
      Super easy
    • 3
      Simple, easy to reason about and makes you productive
    • 3
      Fast evolving
    • 3
      SSR
    • 3
      Great migration pathway for older systems
    • 3
      Rich ecosystem
    • 3
      Simple
    • 3
      Has functional components
    • 3
      Allows creating single page applications
    • 3
      Has arrow functions
    • 3
      Very gentle learning curve
    • 3
      Sdfsdfsdf
    • 3
      Beautiful and Neat Component Management
    • 3
      Just the View of MVC
    • 2
      Split your UI into components with one true state
    • 2
      Fragments
    • 2
      Sharable
    • 2
      Every decision architecture wise makes sense
    • 2
      Permissively-licensed
    • 1
      Image upload
    • 1
      HTML-like
    • 1
      Recharts
    CONS OF REACT
    • 38
      Requires discipline to keep architecture organized
    • 27
      No predefined way to structure your app
    • 26
      Need to be familiar with lots of third party packages
    • 10
      JSX
    • 8
      Not enterprise friendly
    • 6
      One-way binding only
    • 3
      State consistency with backend neglected
    • 3
      Bad Documentation
    • 2
      Paradigms change too fast
    • 2
      Error boundary is needed

    related React posts

    Vaibhav Taunk
    Team Lead at Technovert · | 31 upvotes · 2.3M views

    I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

    See more
    Adebayo Akinlaja
    Engineering Manager at Andela · | 29 upvotes · 1.6M views

    I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

    A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

    In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

    If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

    See more
    Vue.js logo

    Vue.js

    47.5K
    39K
    1.5K
    A progressive framework for building user interfaces
    47.5K
    39K
    + 1
    1.5K
    PROS OF VUE.JS
    • 292
      Simple and easy to start with
    • 225
      Good documentation
    • 193
      Components
    • 129
      Simple the best
    • 99
      Simplified AngularJS
    • 90
      Reactive
    • 74
      Intuitive APIs
    • 54
      Javascript
    • 49
      Changed my front end coding life
    • 46
      Configuration is smooth
    • 35
      Easy to learn
    • 34
      So much fun to use
    • 24
      Progressive
    • 21
      Virtual dom
    • 16
      Faster than bulldogs on hot tarmac
    • 11
      It's magic
    • 11
      Component is template, javascript and style in one
    • 9
      Best of Both Worlds
    • 9
      Light Weight
    • 9
      Perfomance
    • 8
      Elegant design
    • 8
      Without misleading licenses
    • 8
      Application structure
    • 7
      Intuitive and easy to use
    • 6
      Good command line interface
    • 5
      Easy to integrate to HTML by inline-templates
    • 5
      Logicless templates
    • 5
      Like Angular only quicker to get started with
    • 5
      Small learning curve
    • 4
      Single file components
    • 3
      Customer Render ending eg to HTML
    • 3
      High performance
    • 2
      Component based
    • 2
      Vuex
    • 2
      Bridge from Web Development to JS Development
    • 2
      Concise error messages
    • 2
      Supports several template languages
    • 2
      One-way data flow
    • 2
      Intuitive
    • 2
      Lots of documentation
    • 1
      GUI
    CONS OF VUE.JS
    • 9
      Less Common Place
    • 5
      YXMLvsHTML Markup
    • 3
      Don't support fragments
    • 3
      Only support programatically multiple root nodes

    related Vue.js posts

    Johnny Bell
    Shared insights
    on
    Vue.jsVue.jsReactReact

    I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.

    It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.

    See more
    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 26 upvotes · 3.3M views

    Our whole Node.js backend stack consists of the following tools:

    • Lerna as a tool for multi package and multi repository management
    • npm as package manager
    • NestJS as Node.js framework
    • TypeScript as programming language
    • ExpressJS as web server
    • Swagger UI for visualizing and interacting with the API’s resources
    • Postman as a tool for API development
    • TypeORM as object relational mapping layer
    • JSON Web Token for access token management

    The main reason we have chosen Node.js over PHP is related to the following artifacts:

    • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
    • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
    • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
    • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
    See more
    jQuery UI logo

    jQuery UI

    38.8K
    11.9K
    897
    Curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library
    38.8K
    11.9K
    + 1
    897
    PROS OF JQUERY UI
    • 214
      Ui components
    • 155
      Cross-browser
    • 121
      Easy
    • 100
      It's jquery
    • 81
      Open source
    • 57
      Widgets
    • 48
      Plugins
    • 46
      Popular
    • 39
      Datepicker
    • 23
      Great community
    • 7
      DOM Manipulation
    • 6
      Themes
    • 0
      Some good ui components
    CONS OF JQUERY UI
    • 1
      Does not contain charts or graphs

    related jQuery UI posts

    Ganesa Vijayakumar
    Full Stack Coder | Technical Lead · | 19 upvotes · 3.3M views

    I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

    I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

    As per my work experience and knowledge, I have chosen the followings stacks to this mission.

    UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

    Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

    Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

    Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

    Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

    Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

    Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

    Happy Coding! Suggestions are welcome! :)

    Thanks, Ganesa

    See more
    Khauth György
    CTO at SalesAutopilot Kft. · | 12 upvotes · 503.8K views

    I'm the CTO of a marketing automation SaaS. Because of the continuously increasing load we moved to the AWSCloud. We are using more and more features of AWS: Amazon CloudWatch, Amazon SNS, Amazon CloudFront, Amazon Route 53 and so on.

    Our main Database is MySQL but for the hundreds of GB document data we use MongoDB more and more. We started to use Redis for cache and other time sensitive operations.

    On the front-end we use jQuery UI + Smarty but now we refactor our app to use Vue.js with Vuetify. Because our app is relatively complex we need to use vuex as well.

    On the development side we use GitHub as our main repo, Docker for local and server environment and Jenkins and AWS CodePipeline for Continuous Integration.

    See more
    Select2 logo

    Select2

    2.9K
    67
    0
    The jQuery replacement for select boxes
    2.9K
    67
    + 1
    0
    PROS OF SELECT2
      Be the first to leave a pro
      CONS OF SELECT2
        Be the first to leave a con

        related Select2 posts