CSE 135 Lecture 3: L3 1/11/19Premium
1 pages45 viewsWinter 2019
DepartmentComputer Science and Engineering
Course CodeCSE 135
This preview shows half of the first page. to view the full 1 pages of the document.
As commonly implemented responsive design favors developer ease OVER actual user
- Accessible, but NOT optimal
- Coding responsive design for ALL possible devices is a LOT of work!
A possible solution? Code splitting
- Only load the webpage, not the entire code!
- WHY don’t we actually do that?
- To the user, does time count or bytes? Time
- If you split the code, that might issue MORE requests
The Medium of Development
Babel - converts modern versions of JS (ES6+) to older JS (ES5)
Want to still support the folks who use older versions (in general)
User-Agent: in other words, the browser that you’re using
GitHub - ONLY supports newer versions of JS
- All native components (not even React!)
- They came to the realization that supporting older versions was “wasted” engineering
Say if wanted form validation, and we put it in:
- The client’s browser
- Vulnerable to things like XSS! (or can turn off JS)
- The server
- It’s going to be WAY slower to get the form validated when you could just have
Browser does a LOT of stuff (could even argue it is your OS!)
- Has MANY subsystems
URLs and Friends
Using https protocol, go to this website at port 8080, and look into some directory to grab some
file where something is set to something
- File systems may be “case sensitive”!
- Depends on the PL being used, HOW it’s being written, etc
You're Reading a Preview
Unlock to view full version
Loved by over 2.2 million students
Over 90% improved by at least one letter grade.