Alternatives to Phalcon logo

Alternatives to Phalcon

Symfony, Laravel, Django, CodeIgniter, and Lumen are the most popular alternatives and competitors to Phalcon.
218
252
+ 1
352

What is Phalcon and what are its top alternatives?

Phalcon is a web framework implemented as a C extension offering high performance and lower resource consumption.
Phalcon is a tool in the Frameworks (Full Stack) category of a tech stack.
Phalcon is an open source tool with 10.4K GitHub stars and 1.9K GitHub forks. Here’s a link to Phalcon's open source repository on GitHub

Top Alternatives to Phalcon

  • Symfony

    Symfony

    It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP.. ...

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

  • Django

    Django

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

  • CodeIgniter

    CodeIgniter

    CodeIgniter is a proven, agile & open PHP web application framework with a small footprint. It is powering the next generation of web apps. ...

  • Lumen

    Lumen

    Laravel Lumen is a stunningly fast PHP micro-framework for building web applications with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Lumen attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as routing, database abstraction, queueing, and caching. ...

  • Slim

    Slim

    Slim is easy to use for both beginners and professionals. Slim favors cleanliness over terseness and common cases over edge cases. Its interface is simple, intuitive, and extensively documented — both online and in the code itself. ...

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

  • ASP.NET

    ASP.NET

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

Phalcon alternatives & related posts

Symfony logo

Symfony

4.8K
3.6K
1K
A PHP full-stack web framework
4.8K
3.6K
+ 1
1K
PROS OF SYMFONY
  • 168
    Open source
  • 140
    Php
  • 122
    Community
  • 122
    Dependency injection
  • 114
    Professional
  • 74
    Doctrine
  • 66
    Organized
  • 62
    Modular architecture
  • 42
    Smart programming
  • 38
    Solid
  • 14
    Documentation
  • 11
    LTS releases
  • 6
    Robust
  • 6
    Easy to Learn
  • 5
    Bundle
  • 5
    Good practices guideline
  • 5
    Decoupled framework components
  • 4
    Simple
  • 4
    Service container
  • 2
    Powerful
  • 1
    Flexible
CONS OF SYMFONY
  • 9
    Too many dependency
  • 7
    Lot of config files
  • 3
    YMAL
  • 2
    Feature creep
  • 1
    Bloated

related Symfony posts

Benjamin Bernard-Bouissières

I really love Django because it is really fast to create a web application from scratch and it has a lot a facilities like the ORM or the Admin module ! The Python language is really easy to read and powerful, that's why I prefer Django over Symfony.

I use Django at work to make tools for the technicians but I also use it for me to build my personal website which I host on PythonAnywhere, and with a domain name bought on Namecheap.

See more
Samuel Webster
Principal Developer at Colart · | 7 upvotes · 192.2K views

We needed our e-commerce platform (built using WooCommerce) to be able to keep products in sync with our #pim (provided by #akeneo) which is built in Symfony . We hooked into the kernel.event_listener to send RabbitMQ messages to a WordPress API endpoint that triggers the updated product to rebuild with fresh data.

See more
Laravel logo

Laravel

17K
12.9K
3.4K
A PHP Framework For Web Artisans
17K
12.9K
+ 1
3.4K
PROS OF LARAVEL
  • 500
    Clean architecture
  • 359
    Growing community
  • 336
    Composer friendly
  • 312
    Open source
  • 293
    The only framework to consider for php
  • 194
    Mvc
  • 189
    Quickly develop
  • 155
    Dependency injection
  • 142
    Application architecture
  • 129
    Embraces good community packages
  • 57
    Write less, do more
  • 50
    Restful routing
  • 46
    Orm (eloquent)
  • 43
    Artisan scaffolding and migrations
  • 42
    Database migrations & seeds
  • 35
    Awesome
  • 33
    Great documentation
  • 25
    Awsome, Powerfull, Fast and Rapid
  • 25
    Promotes elegant coding
  • 24
    Build Apps faster, easier and better
  • 22
    JSON friendly
  • 21
    Most easy for me
  • 20
    Eloquent ORM
  • 20
    Easy to learn, scalability
  • 19
    Test-Driven
  • 19
    Modern PHP
  • 18
    Blade Template
  • 18
    Beautiful
  • 13
    Security
  • 11
    Clean Documentation
  • 10
    Convention over Configuration
  • 10
    Based on SOLID
  • 10
    Cool
  • 9
    Easy to attach Middleware
  • 9
    Simple
  • 8
    Fast
  • 8
    Easy to use
  • 8
    Laravel + Cassandra = Killer Framework
  • 8
    Simpler
  • 8
    Get going quickly straight out of the box. BYOKDM
  • 8
    Easy Request Validatin
  • 7
    Less dependencies
  • 7
    Simplistic , easy and faster
  • 7
    Its just wow
  • 6
    Friendly API
  • 5
    Its beautiful to code in
  • 5
    Super easy and powerful
  • 5
    Great customer support
  • 4
    Speed
  • 4
    Fast and Clarify framework
  • 4
    The only "cons" is wrong! No static method just Facades
  • 4
    Easy
  • 4
    Active Record
  • 4
    Php7
  • 3
    Laravel Mix
  • 3
    Laragon
  • 3
    Eloquent
  • 3
    Easy views handling and great ORM
  • 3
    Minimum system requirements
  • 3
    Composer
  • 2
    Intuitive usage
  • 2
    Laravel Spark
  • 2
    Laravel Passport
  • 2
    Laravel Nova
  • 2
    Laravel casher
  • 2
    Laravel Horizon and Telescope
  • 2
    Laravel Forge and Envoy
  • 2
    Ease of use
  • 2
    Cashier with Braintree and Stripe
  • 1
    Rapid development
  • 0
    Scout
CONS OF LARAVEL
  • 38
    PHP
  • 26
    Too many dependency
  • 19
    Slower than the other two
  • 15
    A lot of static method calls for convenience
  • 13
    Too many include
  • 10
    Heavy
  • 7
    Bloated
  • 6
    Laravel
  • 5
    Confusing
  • 4
    Does not work well for file uploads in Shared Hosting
  • 3
    Too underrated
  • 2
    Not fast with MongoDB
  • 1
    Difficult to learn
  • 1
    Not using SOLID principles

related Laravel posts

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
CDG

I use Laravel because it's the most advances PHP framework out there, easy to maintain, easy to upgrade and most of all : easy to get a handle on, and to follow every new technology ! PhpStorm is our main software to code, as of simplicity and full range of tools for a modern application.

Google Analytics Analytics of course for a tailored analytics, Bulma as an innovative CSS framework, coupled with our Sass (Scss) pre-processor.

As of more basic stuff, we use HTML5, JavaScript (but with Vue.js too) and Webpack to handle the generation of all this.

To deploy, we set up Buddy to easily send the updates on our nginx / Ubuntu server, where it will connect to our GitHub Git private repository, pull and do all the operations needed with Deployer .

CloudFlare ensure the rapidity of distribution of our content, and Let's Encrypt the https certificate that is more than necessary when we'll want to sell some products with our Stripe api calls.

Asana is here to let us list all the functionalities, possibilities and ideas we want to implement.

See more
Django logo

Django

21.9K
18.6K
3.5K
The Web framework for perfectionists with deadlines
21.9K
18.6K
+ 1
3.5K
PROS OF DJANGO
  • 602
    Rapid development
  • 446
    Open source
  • 387
    Great community
  • 337
    Easy to learn
  • 249
    Mvc
  • 202
    Elegant
  • 201
    Beautiful code
  • 180
    Free
  • 179
    Great packages
  • 167
    Great libraries
  • 55
    Restful
  • 52
    Comes with auth and crud admin panel
  • 51
    Powerful
  • 48
    Great documentation
  • 46
    Great for web
  • 36
    Python
  • 31
    Great orm
  • 27
    Great for api
  • 21
    All included
  • 17
    Web Apps
  • 16
    Fast
  • 14
    Used by top startups
  • 12
    Clean
  • 11
    Easy setup
  • 10
    Sexy
  • 8
    Convention over configuration
  • 5
    ORM
  • 5
    Allows for very rapid development with great libraries
  • 5
    The Django community
  • 3
    Mvt
  • 3
    Its elegant and practical
  • 3
    Great MVC and templating engine
  • 2
    Easy to use
  • 2
    Easy to develop end to end AI Models
  • 2
    Easy Structure , useful inbuilt library
  • 2
    Cross-Platform
  • 2
    Fast prototyping
  • 2
    Full stack
  • 2
    Batteries included
  • 2
    Easy
  • 1
    Great peformance
  • 1
    Many libraries
  • 1
    Zero code burden to change databases
  • 1
    Have not found anything that it can't do
  • 1
    Map
  • 1
    Scaffold
  • 1
    Modular
  • 1
    Very quick to get something up and running
  • 1
    Just the right level of abstraction
  • 1
    Python community
  • 1
    Full-Text Search
  • 1
    King of backend world
CONS OF DJANGO
  • 24
    Underpowered templating
  • 19
    Underpowered ORM
  • 18
    Autoreload restarts whole server
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
  • 7
    Not nodejs
  • 5
    Admin
  • 4
    Configuration hell
  • 3
    Not as clean and nice documentation like Laravel
  • 2
    Bloated admin panel included
  • 2
    Not typed
  • 2
    Python
  • 2
    Overwhelming folder structure
  • 1
    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
CodeIgniter logo

CodeIgniter

3K
1.2K
415
A Fully Baked PHP Framework
3K
1.2K
+ 1
415
PROS OF CODEIGNITER
  • 83
    Mvc
  • 74
    Easy setup
  • 67
    Open source
  • 59
    Well documented
  • 34
    Community support
  • 21
    Easy to learn
  • 17
    Easy
  • 11
    Fast
  • 10
    HMVC
  • 7
    Language Suppert
  • 6
    "Fast","Easy","MVC"
  • 5
    Easy, fast and full functional
  • 4
    I think it is best. we can make all types of project
  • 4
    Powerful
  • 3
    Works on Every PHP Server like shared hostings
  • 3
    Open source, Easy to setup
  • 2
    Super Lightweight, Super Easy to Learn
  • 2
    Customizable
  • 2
    Beginner friendly framework
  • 1
    CLI
CONS OF CODEIGNITER
  • 5
    No ORM
  • 1
    No CLI

related CodeIgniter posts

Saikat Chakrabortty
Shared insights
on
PHPPHPLaravelLaravelCodeIgniterCodeIgniter

I have used PHP to do end to end developments , using Laravel CodeIgniter frameworks.

See more
Narjis Fatima
Web developer at WebSolution Creators · | 2 upvotes · 3.4K views
Shared insights
on
DjangoDjangoCodeIgniterCodeIgniterPythonPython

I have learned Python. I also developed an online Result management system in CodeIgniter for my school but now want to migrate to Django as the system is expanding. Is it a good idea?

See more
Lumen logo

Lumen

348
495
151
The stunningly fast PHP micro-framework by Laravel
348
495
+ 1
151
PROS OF LUMEN
  • 32
    API
  • 25
    Microframework
  • 19
    MVC
  • 16
    PHP
  • 12
    Open source
  • 11
    Eloquent
  • 10
    Restful & fast framework
  • 7
    Illuminate support
  • 7
    Composer
  • 4
    Brother of laravel and fast
  • 4
    Easy to learn
  • 4
    Fast
CONS OF LUMEN
  • 2
    Not fast
  • 1
    Not fast with MongoDB
  • 1
    PHP

related Lumen posts

Tassanai Singprom

This is my stack in Application & Data

JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

My Utilities Tools

Google Analytics Postman Elasticsearch

My Devops Tools

Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

My Business Tools

Slack

See more
Y. Taborda
Shared insights
on
PHPPHPLumenLumenYiiYiiSlimSlim

I'm about to start a new project to build a REST API, and I got to this point: Yii2 Vs Lumen Vs Slim, I used Yii 1.1 a while a go and it was awesome, really easy to work with, as a developer you don't have to worry about almost anything, just setup the framework, get your php extensions, and start coding your app.

But, I was told about performance and someone recomended Lumen or Slim to work with a micro framework and a less bloated framework, what worries me is the lack of advantages that Yii2 offers, ACF and RBAC as a native tool on the framework, gii, the model validations and all the security props already in it.

Is it worth it? Is the performance so great on those frameworks to leave aside the advantages of a framework like Yii2?

How do you suggest to make the test to prove wich one is better?

PHP Lumen Yii Slim

See more
Slim logo

Slim

234
304
134
A PHP micro framework
234
304
+ 1
134
PROS OF SLIM
  • 29
    Microframework
  • 25
    API
  • 21
    Open source
  • 19
    Php
  • 11
    Fast
  • 8
    Restful & fast framework
  • 7
    Easy Setup, Great Documentation
  • 5
    Good document to upgrade from previous version
  • 5
    Clear and straightforward
  • 4
    Modular
CONS OF SLIM
    Be the first to leave a con

    related Slim posts

    Y. Taborda
    Shared insights
    on
    PHPPHPLumenLumenYiiYiiSlimSlim

    I'm about to start a new project to build a REST API, and I got to this point: Yii2 Vs Lumen Vs Slim, I used Yii 1.1 a while a go and it was awesome, really easy to work with, as a developer you don't have to worry about almost anything, just setup the framework, get your php extensions, and start coding your app.

    But, I was told about performance and someone recomended Lumen or Slim to work with a micro framework and a less bloated framework, what worries me is the lack of advantages that Yii2 offers, ACF and RBAC as a native tool on the framework, gii, the model validations and all the security props already in it.

    Is it worth it? Is the performance so great on those frameworks to leave aside the advantages of a framework like Yii2?

    How do you suggest to make the test to prove wich one is better?

    PHP Lumen Yii Slim

    See more
    Node.js logo

    Node.js

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

    related Node.js posts

    Nick Rockwell
    SVP, Engineering at Fastly · | 42 upvotes · 1.4M 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 · | 37 upvotes · 3.5M 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
    ASP.NET logo

    ASP.NET

    18.9K
    4.6K
    6
    An open source web framework for building modern web apps and services with .NET
    18.9K
    4.6K
    + 1
    6
    PROS OF ASP.NET
    • 6
      Great mvc
    CONS OF ASP.NET
      Be the first to leave a con

      related ASP.NET posts

      Greg Neumann
      Indie, Solo, Developer · | 8 upvotes · 714K views

      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

      I found Heroku to be a great option to get ExpressJS up and running with very little hustle. The free tier is great, but I'd recommend to set up a cronjob to visit your site every few minutes so that the server stays awake. Netlify was the option to host the front-end because doing the server side rendering on #Heroku would have taken a little more time than I'd like to. For the moment pre-rendering the app with prerender-spa-plugin is enough to help with #seo. Puppeteer was my choice over other options because it made it easier to scrape websites made on ASP.NET which is what I needed in this case. And Vue.js is my top choice at the moment because it's really beginner friendly and it has a lot of the features I like about Angular 2 and React. vuex is a must in most of the app I build.

      See more