🐢 Open source JavaScript e-learning for cyber nomads ✨ 🍉
🍜 This repo hosting is a landing page for our e-learning app for JS nomads 🌴
Page: https://wizardamigos.com App: https://app.wizardamigos.com (130 learning videos for beginners)
- from (lesson 1): ...what's a browser? ...how to make an email?
- over (< lesson 105): ...how does javascript work?
- to (> lesson 105): how to build and deploy your first web & iPhone apps More: https://github.com/wizardamigos/app/blob/master/skillTree.md Ask in the support channel how & where to start learning :-)
https://meetup.com/wizardamigos We have two regular meetups (one in berlin and one in taipei) ...but we have occasional meetups in slovenia and thailand
We all try to work on becoming self employed and collaborate as partners and all this remote and with a lifestyle of traveling.
The only thing that a backend is supposed to do (if clients cant do it without) is to connect clients to each other, so that they can communicate and exchange data. Our idea is, that apps connect p2p without servers... like as if desktop apps would connect directly to each other... In rare cases where this needs servers to make it work we will build them, but usually it works without.
- Frontend is the new FullStack.
- A traditional backend can be built into the client like https://github.com/mafintosh/browser-server
- not every app needs servers
- when app need servers, they might be existing ones (e.g. facebook, twitter, github, google drive, ...)
- sometimes you need generic ones, like databases or real time connection across different users (e.g. firebase, pusher, pubnub)
- sometimes you have clients that already have backends (e.g. written in PHP, Java, Ruby, Python, ....) that you can connect to via API
- Our way of thinking about apps is:
- you build an
index.htmlwhich is like a traditional desktop app - you start it by opning the
index.htmlin your browser - once the
index.htmlapp started, it might connect to one or more "backend servers" via API and send or receive data
- you build an