3 ms·
It is embarrassing, but I only know how to write HTML like it’s 1999. The last new thing I learned was an iframe, the kids tell me CSS something I should learn.
by justjonathan 7y ago
It is embarrassing, but I only know how to write HTML like it’s 1999. The last new thing I learned was an iframe, the kids tell me CSS something I should learn...
- isostatic 7y agonah, newfangled stuff, cross browser compatability issues, not worth it - it won't catch on
- im3w1l 7y agoKeeping up is an endless treadmill. If your primary work is in some other domain, say backend infra or some non-coding profession that writes a line every blue moon, the investment may not pay off. If you are a front-end dev it's of course a no-brainer to keep up.
- krapp 7y agoI legitimately remember the day I first saw an iframed site and how cool I thought it was. God I'm old.
- rolltiide 7y agoiframes have had a wild ride in acceptance 1999 - Cool and Clever 2005 - Horrible 2010 - Horrible but sometimes necessary 2015 - Awesome
- majewsky 7y ago> 2015 - Awesome Huh, what happened?
- EdwardDiego 7y agoWe started injecting everyone else's JS everywhere.
- d_k_f 7y agoLimitations imposed upon embedded scripts from foreign domains by technologies like CORS and the like, combined with modern styling abilities. You can place another service's elements on a page that look like they're actually part of the page layout while the JS running them can freely communicate with the service's backend without having to bother with cross domain problems. Think of all the support/chat widgets you see on modern-day pages, they're all iframes. And obviously: tracking all the things!