rwieruch / why-frameworks-matter Goto Github PK

Why vanilla JavaScript isn't used for large applications

Home Page: https://www.robinwieruch.de/why-frameworks-matter

HTML 20.84% JavaScript 45.09% TypeScript 33.70% CSS 0.37%

javascript vanilla-javascript es6 es6-javascript react angular vue jquery

why-frameworks-matter's Introduction

Why Frameworks Matter

The repository features different libraries and frameworks which solve the same problem: searching stories from Hacker News and show the results in a list in a browser. It should show how the same thing can be achieved with different solutions. But most important, it should show why large applications are not built with vanilla JavaScript anymore. Read more about it: Why Frameworks Matter.

Features

Vanilla JavaScript
jQuery
ES6 JavaScript
React
React (with hooks)
Vue
AngularJS 1.x
Angular 2+
NextJs

Looking for contributions:

Ember
Preact
Others

Getting Started

globally install a http server once: npm install http-server -g
move into one of the given folders
serve application: http-server
visit the URL shown in the command line

why-frameworks-matter's People

Contributors

Stargazers

Watchers

Forkers

manjunatha-d xgenvn knurddongle junste marveldeviser antonkuleshov fabiradi todun femmor maksung228 uxshahil casdidier matthewhohavas ryansworld84 zangbianxuegu lukaszherman-stx lucasherman

why-frameworks-matter's Issues

Improve Angular x Example

We have a Angular X project already in this repository, but I feel it uses too much CLI magic. Isn't it possible to have a minimal example with index.js and index.html similar to the other examples? I have no clue about Angular X, because I have only used 1.x in the earlier days. Would appreciate any help on this!

Add Ember Example

Add Angular X Example

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.