Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

The history of the internet universe.

No description
by

Lee Nathan

on 5 December 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of The history of the internet universe.

the history of the internet universe
(not as boring as it sounds - I promise)
the dark ages
click, load, click, load
yawwwwwwn, slow pages
slow development
lots and lots of work
browser wars
impossible to safely develop for multiple browsers
the dot bomb
1999 - the year the tubes went down
the dawn of the interwebs
bullet points
tables
links
images
formatted text
that's pretty much it
first, there was html: for structure
color
spacing
alignment
fonts
other decor
then they added CSS: for style
lets websites be smarter
allowed interactive elements
good for tabs
good for forms
mostly unused
too complex for devs of the day
next, they added JS:
for logic
the stack so far
html
css
just front end tech
high tech futuristic websites from leading corporations
totally hella bitchin rad personal sites
some sites needed more power
to deliver actual services
the stack so far
html / css
thick complex server
old school database
full stack tech
dynamic html
css
still no javascript
server
database
the full stack solution
the database
the server
web 2.0 - 2006 - the renaissance
things get interesting
no more hardware investment
elastic hosting
load balancing
pay only for what you use
used by netflix
Amazon Web Services
eliminates server construction
cuts build time to a third or less
startup weekend's app would have taken at least 2 weeks traditionally
most important was the agile philosophy
Ruby on Rails
allows for server communication from JS
lets you rewrite HTMl without reloading pages
now, click change, not click load
dynamic HTML is now... Web Apps!
prominent examples include:
gmail's all in one page feature
pinterest's infinite scrolling
AJAX
(Asynchronous JS and XML)
the stack so far
html / css
thick heavy JS for AJAX
thin agile servers via frameworks
old school database
design frameworks
twitter bootstrap
zurb foundation
now you can design as fast as making a mockup
next up...
web 2.5 - more awesome shit!
HTML 5
embed video and audio without plugins
GPS!
canvas - like flash but also, no plugins
CSS 3
beautifies the web
rounded corners
animations
gradients
web 3.0 - the future
bring out the flying cars
JS as a server: node.js
thanks google!
The age of Javascript
JS to access data
thanks modern hardware!
JS as a framework
thanks again google!
backbone
ember
angular
love it or hate it, JS has become the one language
unity through frameworks
js, html and css frameworks unify browsers by hiding incompatibilites from developers
separate code for android, iOs and web is no more

mobile is the future
mobile devices have outsold PCs for years
mobile apps still use remote services for data
apps move logic away from the server and into the phone for faster performance
why not move it all?
I'm going mobile
beep beep, mmm, beep beep, yeah
move all code to app
server becomes irrelevant
introducing the BaaS
JS as a mobile app
the stack I chose
html / css (duh)
thin JS / AJAX layer
modern high speed data store
our exact tech stack
still awake?
finally...
Angular JS
our JS framework
the core of our app around which all else revolves
pros
2 way data binding
faster more responsive
popular = community
backed by google
cons
hard to learn
steep learning curve
about to undergo massive changes
hard to learn
Ionic
our front end framework
like bootstrap, but looks more mobile
pros
ties in to angular
looks like a mobile app
uses cordova to access mobile hardware
cons
none so far
maybe smaller community?
but the documentation is execllent
firebase
our data store
it's a BaaS
eliminates the need for a server
pros
ties in to angular
provides 3 way data binding!
backed by google
no maintenance
cons
vendor lock in
scalability limited to their business
pro: our data is ours and can be easily moved
data must be backed up constantly
thanks much!
I wanted to include just the clapping from this video, but prezi wouldn't let me
:(
Full transcript