Lubbock Coding Academy Blog #16

matt coston
2 min readApr 4, 2019

--

  1. Describe one thing you learned in class today. Answer: I learned that I still do not like front end development as much as I do backend development.
  2. Why is it generally a good idea to position CSS <link>s between <head></head> and JS <script>s just before </body>? Do you know any exceptions? Answer: Link tags will go toward styles as the page loads so since it is higher up it will load the correct layout and colors. Script tags near the body is for the opposite reason. JS can be slow to load on phones or slower connections. If you put it near the bottom the page will load first so at least the user has something to look at while the rest of the functionality loads. Exceptions occur with defer and async script tags.
  3. Consider HTML5 as an open web platform. What are the building blocks of HTML5? Answer: Semantics: allowing you to describe more precisely what your content is.
  • Connectivity: allowing you to communicate with the server in new and innovative ways.
  • Offline and storage: allowing webpages to store data on the client-side locally and operate offline more efficiently.
  • Multimedia: making video and audio first-class citizens in the Open Web.
  • 2D/3D graphics and effects: allowing a much more diverse range of presentation options.
  • Performance and integration: providing greater speed optimization and better usage of computer hardware.
  • Device access: allowing for the usage of various input and output devices.
  • Styling: letting authors write more sophisticated themes.

4. Explain some of the pros and cons for CSS animations versus JavaScript animations. Answer: Use CSS animations for simpler “one-shot” transitions, like toggling UI element states. Use JavaScript animations when you want to have advanced effects like bouncing, stop, pause, rewind, or slow down. If you choose to animate with JavaScript, use the Web Animations API or a modern framework that you’re comfortable with.

5. Can you describe the difference between progressive enhancement and graceful degradation? Answer: Progressive enhancement makes a website better looking for more up to date browsers while graceful degradation does the opposite. It slowly takes away features or styling that may slow down the older browser.

--

--

matt coston
matt coston

Written by matt coston

0 Followers

Hey there! I'm an IT manager by day, and I dabble in all things web development by night.

No responses yet