38 lines
2.4 KiB
Org Mode
38 lines
2.4 KiB
Org Mode
|
* 3 new
|
||
|
|
** 1
|
||
|
|
Despite using the same technologies, mobile websites tend to differ from desktop websites.
|
||
|
|
|
||
|
|
The designers need to consider things such as, screen size, processing power available, and data.
|
||
|
|
|
||
|
|
While I've seen plenty of that in regards to screen size, I have seen plenty of data and power waste when browsing mobile sites. The old mobile sites used to be super basic and didn't use much, but lately, I still see things like video pop ups autoloading and following me around the screen.
|
||
|
|
|
||
|
|
** 2
|
||
|
|
Web browsers send information to servers that identify itself so that the web pages can display information more appropriate to the device or specific web browser.
|
||
|
|
** 3
|
||
|
|
Subresource Integrity. I seem to remember reading about the web browsers only trusting JavaScript that came from the same domain. This kinda reminds me of a horror of troubles I ran into when I had to be on Windows (VB). Mark of the web. Hell of an error message to spit at someone when you're just trying to do class work. Anyway, I'm thinking that this subresource integrity concept is a much better version of that.
|
||
|
|
|
||
|
|
If I understand it correctly, subresource integrity allows us to pull JavaScript from other domains that allow it to be treated as if it's from our own domain for security purposes.
|
||
|
|
|
||
|
|
* 2 Interesting
|
||
|
|
** 1
|
||
|
|
Didn't realize that jQuery has been around since 2006. Of course, I was just a stupid teenager when it came out (Wait, did I just date myself? Am I old enough now to think about that?), and probably didn't even realize that JavaScript was much of a thing yet. Then again, it probably wasn't. Everyone finally was done (well...) with java applets and we were charging right in with a steaming pile of flash.
|
||
|
|
** 2
|
||
|
|
Instead of:
|
||
|
|
$(document).ready( () => {});
|
||
|
|
|
||
|
|
We can shorthand it as:
|
||
|
|
$(() => {});
|
||
|
|
|
||
|
|
I'm not sure I care for that. I enjoy concise, and it's certainly nice for minifiying, but readability is gone. Which, probably doesn't matter much, but still. Though, I do like how I feel like I'm using a half-baked lisp with the shorthand method.
|
||
|
|
|
||
|
|
|
||
|
|
* 1 unclear
|
||
|
|
I suppose what's least clear is the responsive/reactive/adaptave ideas. Aren't they mostly just progressions of the same concept? We started out responding to screen sizes with media queries that caused jerkiness while resizing windows and what not, but then we progressed to scaling more smoothly and such. Why do we need all of these things still?
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
NOTE: 12:33 may hold all answers for assignment
|
||
|
|
SRI checking at 1625
|
||
|
|
|
||
|
|
At 45 mins
|