Alternatives to RichFaces logo

Alternatives to RichFaces

PrimeFaces, AngularJS, jQuery, JSF, and Node.js are the most popular alternatives and competitors to RichFaces.
5
6
+ 1
0

What is RichFaces and what are its top alternatives?

It is an advanced UI component framework for easily integrating Ajax capabilities into business applications using JSF.
RichFaces is a tool in the Frameworks (Full Stack) category of a tech stack.
RichFaces is an open source tool with 62 GitHub stars and 100 GitHub forks. Here’s a link to RichFaces's open source repository on GitHub

Top Alternatives to RichFaces

  • PrimeFaces
    PrimeFaces

    It is a popular open source framework for JavaServer Faces featuring over 100 components, touch optimized mobilekit, client side validation, theme engine and more. ...

  • 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. ...

  • jQuery
    jQuery

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

  • JSF
    JSF

    It is used for building component-based user interfaces for web applications and was formalized as a standard through the Java Community ...

  • Node.js
    Node.js

    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...

  • Django
    Django

    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...

  • ASP.NET
    ASP.NET

    .NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications. ...

  • Laravel
    Laravel

    It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching. ...

RichFaces alternatives & related posts

PrimeFaces logo

PrimeFaces

88
142
3
An open-source user interface component library
88
142
+ 1
3
PROS OF PRIMEFACES
  • 1
    JEE Integration
  • 1
    Support Contract available
  • 1
    Nice Components
CONS OF PRIMEFACES
  • 1
    Some components have to be bought
  • 1
    JSF

related PrimeFaces posts

I need to modernize a Java web application that runs on JSF. I am used to building websites, so Bootstrap kinda feels like "home." But when it comes to applications, I feel Bootstrap is not the right way to go. Can someone explain to me what PrimeFaces is capable of in comparison with BS?

See more
AngularJS logo

AngularJS

49.2K
35.9K
5.2K
Superheroic JavaScript MVW Framework
49.2K
35.9K
+ 1
5.2K
PROS OF ANGULARJS
  • 887
    Quick to develop
  • 587
    Great mvc
  • 572
    Powerful
  • 521
    Restful
  • 503
    Backed by google
  • 349
    Two-way data binding
  • 343
    Javascript
  • 328
    Open source
  • 305
    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
    Angular 2.0
  • 14
    Javascript mvw framework
  • 13
    Great extensions
  • 13
    Efficient
  • 10
    Easy to prototype with
  • 8
    High performance
  • 8
    Coffeescript
  • 7
    Mvc
  • 7
    Two-way binding
  • 7
    Lots of community modules
  • 6
    Easy to e2e
  • 6
    Clean and keeps code readable
  • 5
    Easy for small applications
  • 5
    One of the best frameworks
  • 4
    Fast development
  • 4
    Works great with jquery
  • 3
    I do not touch DOM
  • 2
    Be a developer, not a plumber.
  • 2
    Declarative programming
  • 2
    Dart
  • 2
    Community
  • 2
    The two-way Data Binding is awesome
  • 2
    Hierarchical Data Structure
  • 2
    Typescript
  • 1
    Botionescu@gmail.com
  • 1
    The powerful of binding, routing and controlling routes
  • 1
    Fkin awesome
  • 1
    Opinionated in the right areas
  • 1
    Supports api , easy development
  • 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
    Acoperișul
  • 1
    Consistency with backend architecture if using Nest
  • 0
    Httpș//Acoperișul 0757604335
  • 0
    Angular js
  • 0
    Oautho loc
  • 0
    Shvzjn
  • 0
    Acoperișul 0757604335
  • 0
    Js
  • 0
    Bot Ionescu
  • 0
    Google.com
CONS OF ANGULARJS
  • 10
    Complex
  • 3
    Dependency injection
  • 2
    Learning Curve
  • 2
    Event Listener Overload
  • 1
    Hard to learn

related AngularJS posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.5M 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 · | 22 upvotes · 1.1M 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
jQuery logo

jQuery

174.6K
54.7K
6.5K
The Write Less, Do More, JavaScript Library.
174.6K
54.7K
+ 1
6.5K
PROS OF JQUERY
  • 1.3K
    Cross-browser
  • 957
    Dom manipulation
  • 806
    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
    Used everywhere
  • 2
    Just awesome
  • 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
  • 5
    Sometimes inconsistent API
  • 5
    Large size
  • 5
    Encourages DOM as primary data source
  • 2
    Live events is overly complex feature

related jQuery posts

Kir Shatrov
Engineering Lead at Shopify · | 21 upvotes · 669.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 · 2.8M 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
JSF logo

JSF

118
187
4
It is used for building component-based web interfaces
118
187
+ 1
4
PROS OF JSF
  • 2
    Rich and comprehensive Request Life-cycle
  • 1
    Very Mature UI framework
  • 1
    Server Side component
CONS OF JSF
    Be the first to leave a con

    related JSF posts

    Hello guys! I would ask for your advice. Our situation is like that there will be a project to revamp workflows and introduce new services like mobile apps, machine learning, and some online services that would use cloud storage. We use JSF, JavaScript, Ajax, Spring, Oracle 12c running on Linux (VM) and providing online services to internal users and the public. But, we are not technically savvy enough to evaluate what tools should be introduced. Personally, I am evaluating whether to take this opportunity to change our practice/PM approach from Prince to Scrum/Agile (It seemed that DevOps is popular) ... Since we adopt ISO 27001 and ISO 20000, security is a crucial factor that we consider. Would you please help to recommend a list of tools and explain the reasons why you recommend them? Thanks in advance~!

    See more

    I need to modernize a Java web application that runs on JSF. I am used to building websites, so Bootstrap kinda feels like "home." But when it comes to applications, I feel Bootstrap is not the right way to go. Can someone explain to me what PrimeFaces is capable of in comparison with BS?

    See more
    Node.js logo

    Node.js

    141.6K
    118.7K
    8.5K
    A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
    141.6K
    118.7K
    + 1
    8.5K
    PROS OF NODE.JS
    • 1.4K
      Npm
    • 1.3K
      Javascript
    • 1.1K
      Great libraries
    • 1K
      High-performance
    • 799
      Open source
    • 485
      Great for apis
    • 475
      Asynchronous
    • 420
      Great community
    • 390
      Great for realtime apps
    • 295
      Great for command line utilities
    • 81
      Websockets
    • 81
      Node Modules
    • 68
      Uber Simple
    • 59
      Great modularity
    • 57
      Allows us to reuse code in the frontend
    • 42
      Easy to start
    • 35
      Great for Data Streaming
    • 32
      Realtime
    • 28
      Awesome
    • 25
      Non blocking IO
    • 18
      Can be used as a proxy
    • 17
      High performance, open source, scalable
    • 16
      Non-blocking and modular
    • 15
      Easy and Fun
    • 14
      Easy and powerful
    • 13
      Future of BackEnd
    • 13
      Same lang as AngularJS
    • 12
      Fullstack
    • 11
      Fast
    • 10
      Scalability
    • 10
      Cross platform
    • 9
      Simple
    • 8
      Mean Stack
    • 7
      Great for webapps
    • 7
      Easy concurrency
    • 6
      Typescript
    • 6
      Fast, simple code and async
    • 6
      Friendly
    • 6
      React
    • 5
      Easy to use and fast and goes well with JSONdb's
    • 5
      Fast development
    • 5
      Control everything
    • 5
      Great speed
    • 5
      Scalable
    • 5
      Its amazingly fast and scalable
    • 4
      It's fast
    • 4
      Isomorphic coolness
    • 4
      Easy to use
    • 3
      Blazing fast
    • 3
      Easy to learn
    • 3
      Easy
    • 3
      Javascript2
    • 3
      Great community
    • 3
      Not Python
    • 3
      Sooper easy for the Backend connectivity
    • 3
      TypeScript Support
    • 3
      Scales, fast, simple, great community, npm, express
    • 3
      One language, end-to-end
    • 3
      Less boilerplate code
    • 3
      Performant and fast prototyping
    • 2
      Lovely
    • 2
      Npm i ape-updating
    • 2
      Event Driven
    CONS OF NODE.JS
    • 46
      Bound to a single CPU
    • 42
      New framework every day
    • 37
      Lots of terrible examples on the internet
    • 29
      Asynchronous programming is the worst
    • 23
      Callback
    • 18
      Javascript
    • 11
      Dependency based on GitHub
    • 10
      Dependency hell
    • 10
      Low computational power
    • 7
      Can block whole server easily
    • 7
      Very very Slow
    • 6
      Callback functions may not fire on expected sequence
    • 3
      Unneeded over complication
    • 3
      Unstable
    • 3
      Breaking updates
    • 1
      Bad transitive dependency management
    • 1
      Can't read server session
    • 1
      No standard approach

    related Node.js posts

    Nick Rockwell
    SVP, Engineering at Fastly · | 44 upvotes · 1.9M views

    When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

    So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

    React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

    Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

    See more
    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 40 upvotes · 4.8M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    Django logo

    Django

    29.6K
    26.5K
    3.9K
    The Web framework for perfectionists with deadlines
    29.6K
    26.5K
    + 1
    3.9K
    PROS OF DJANGO
    • 641
      Rapid development
    • 473
      Open source
    • 406
      Great community
    • 357
      Easy to learn
    • 266
      Mvc
    • 217
      Beautiful code
    • 212
      Elegant
    • 196
      Free
    • 194
      Great packages
    • 182
      Great libraries
    • 71
      Restful
    • 67
      Powerful
    • 67
      Comes with auth and crud admin panel
    • 64
      Great documentation
    • 61
      Great for web
    • 48
      Python
    • 38
      Great orm
    • 36
      Great for api
    • 27
      All included
    • 22
      Web Apps
    • 22
      Fast
    • 19
      Used by top startups
    • 17
      Clean
    • 16
      Easy setup
    • 16
      Sexy
    • 13
      Convention over configuration
    • 12
      ORM
    • 9
      Allows for very rapid development with great libraries
    • 9
      The Django community
    • 7
      Great MVC and templating engine
    • 7
      King of backend world
    • 7
      Its elegant and practical
    • 6
      Mvt
    • 6
      Full stack
    • 6
      Fast prototyping
    • 6
      Have not found anything that it can't do
    • 6
      Cross-Platform
    • 5
      Batteries included
    • 5
      Very quick to get something up and running
    • 5
      Easy Structure , useful inbuilt library
    • 5
      Easy to develop end to end AI Models
    • 4
      Python community
    • 4
      Great peformance
    • 4
      Easy
    • 4
      Easy to use
    • 4
      Modular
    • 4
      Many libraries
    • 3
      Full-Text Search
    • 3
      Map
    • 3
      Zero code burden to change databases
    • 3
      Scaffold
    • 3
      Just the right level of abstraction
    • 2
      Easy to change database manager
    • 1
      Node js
    • 0
      Asdasd
    • 0
      Rails
    • 0
      Aaaa
    • 0
      Fastapi
    CONS OF DJANGO
    • 25
      Underpowered templating
    • 21
      Autoreload restarts whole server
    • 20
      Underpowered ORM
    • 15
      URL dispatcher ignores HTTP method
    • 10
      Internal subcomponents coupling
    • 7
      Not nodejs
    • 7
      Configuration hell
    • 7
      Admin
    • 5
      Not as clean and nice documentation like Laravel
    • 3
      Bloated admin panel included
    • 3
      Not typed
    • 3
      Python
    • 2
      Overwhelming folder structure
    • 2
      InEffective Multithreading

    related Django posts

    Dmitry Mukhin

    Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

    Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

    For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

    However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

    All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

    See more

    Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

    See more
    ASP.NET logo

    ASP.NET

    23K
    8.1K
    18
    An open source web framework for building modern web apps and services with .NET
    23K
    8.1K
    + 1
    18
    PROS OF ASP.NET
    • 13
      Great mvc
    • 5
      Easy to learn
    CONS OF ASP.NET
    • 1
      Not highly flexible for advance Developers
    • 1
      Entity framework is very slow

    related ASP.NET posts

    Greg Neumann

    Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.

    This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!

    But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?

    I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.

    Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...

    See more

    Hi. We are planning to develop web, desktop, and mobile app for procurement, logistics, and contracts. Procure to Pay and Source to pay, spend management, supplier management, catalog management. ( similar to SAP Ariba, gap.com, coupa.com, ivalua.com vroozi.com, procurify.com

    We got stuck when deciding which technology stack is good for the future. We look forward to your kind guidance that will help us.

    We want to integrate with multiple databases with seamless bidirectional integration. What APIs and middleware available are best to achieve this? SAP HANA, Oracle, MySQL, MongoDB...

    ASP.NET / Node.js / Laravel. ......?

    Please guide us

    See more
    Laravel logo

    Laravel

    22.3K
    18.2K
    3.6K
    A PHP Framework For Web Artisans
    22.3K
    18.2K
    + 1
    3.6K
    PROS OF LARAVEL
    • 526
      Clean architecture
    • 379
      Growing community
    • 354
      Composer friendly
    • 328
      Open source
    • 307
      The only framework to consider for php
    • 208
      Mvc
    • 203
      Quickly develop
    • 161
      Dependency injection
    • 150
      Application architecture
    • 138
      Embraces good community packages
    • 67
      Write less, do more
    • 62
      Orm (eloquent)
    • 60
      Restful routing
    • 51
      Database migrations & seeds
    • 50
      Artisan scaffolding and migrations
    • 36
      Great documentation
    • 36
      Awesome
    • 27
      Awsome, Powerfull, Fast and Rapid
    • 25
      Build Apps faster, easier and better
    • 25
      Promotes elegant coding
    • 22
      Eloquent ORM
    • 22
      Modern PHP
    • 22
      JSON friendly
    • 22
      Easy to learn, scalability
    • 21
      Most easy for me
    • 20
      Beautiful
    • 20
      Test-Driven
    • 20
      Blade Template
    • 14
      Security
    • 13
      Based on SOLID
    • 12
      Clean Documentation
    • 12
      Cool
    • 11
      Simple
    • 11
      Convention over Configuration
    • 11
      Easy to attach Middleware
    • 10
      Easy Request Validatin
    • 9
      Fast
    • 9
      Simpler
    • 9
      Easy to use
    • 8
      Laravel + Cassandra = Killer Framework
    • 8
      Its just wow
    • 8
      Friendly API
    • 8
      Get going quickly straight out of the box. BYOKDM
    • 7
      Simplistic , easy and faster
    • 7
      Super easy and powerful
    • 7
      Less dependencies
    • 6
      Great customer support
    • 6
      Its beautiful to code in
    • 5
      The only "cons" is wrong! No static method just Facades
    • 5
      Fast and Clarify framework
    • 5
      Active Record
    • 5
      Php7
    • 5
      Speed
    • 5
      Easy
    • 4
      Composer
    • 4
      Laravel Mix
    • 4
      Minimum system requirements
    • 4
      Easy views handling and great ORM
    • 4
      Eloquent
    • 4
      Laragon
    • 3
      Laravel Spark
    • 3
      Ease of use
    • 3
      Cashier with Braintree and Stripe
    • 3
      Laravel Forge and Envoy
    • 3
      Laravel Horizon and Telescope
    • 3
      Laravel Nova
    • 3
      Laravel casher
    • 3
      Laravel Passport
    • 3
      Intuitive usage
    • 2
      Heart touch
    • 2
      Rapid development
    • 2
      Laravel love live long
    • 2
      Like heart beat
    • 2
      Touch heart artisan
    • 2
      Scout
    • 1
      Deployment
    CONS OF LARAVEL
    • 44
      PHP
    • 30
      Too many dependency
    • 21
      Slower than the other two
    • 17
      A lot of static method calls for convenience
    • 14
      Too many include
    • 11
      Heavy
    • 7
      Bloated
    • 6
      Laravel
    • 5
      Confusing
    • 5
      Too underrated
    • 4
      Does not work well for file uploads in Shared Hosting
    • 2
      Not fast with MongoDB
    • 1
      Difficult to learn
    • 1
      Not using SOLID principles

    related Laravel posts

    I need to build a web application plus android and IOS apps for an enterprise, like an e-commerce portal. It will have intensive use of MySQL to display thousands (40-50k) of live product information in an interactive table (searchable, filterable), live delivery tracking. It has to be secure, as it will handle information on customers, sales, inventory. Here is the technology stack: Backend: Laravel 7 Frondend: Vue.js, React or AngularJS?

    Need help deciding technology stack. Thanks.

    See more
    Antonio Sanchez

    Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.

    Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.

    By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.

    Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.

    There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.

    We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.

    As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com

    See more