There is one alternative to social media sites and publishing platforms that has been around since the early, innocent days of the web. It is an alternative that provides immense freedom and control: The personal website. It’s a place to write, create, and share whatever you like, without the need to ask for anyone’s permission.
So, I dug out my old Boccia that I haven’t worn much since I got my first Apple Watch. It doesn’t have the same fit and finish as my Apple Watch; its band is not as easily swapped. It does not display the weather. It does not tell me when I should get some exercise. But it feels nice.Source: The Apple Watch Turns Four: Some Thoughts — Pixel Envy
I am going to write about the Apple Watch at some point in the future, as I have had a lot of mixed thoughts about it. In the mean time, Nick Heer has really got close to a lot of similar feeling's I've had.
Microsoft moving Edge over to Chromium has been such a big story this year in the web development world and now we have a preview of the upcoming Mac version.
In the very early days when I was first learning about web design, I remember when Internet Explorer 5 on the Mac was released with a big splash. It was ahead of it's Windows cousin in terms of page rendering and offered a theme selection to match your candy colored iMac.
Today, I see this about Edge coming to the Mac and have to wonder who is this for? Other than web developers who are going to test their site while using a Mac, what is the selling point for non-developers?
As someone who has used jQuery for many. years and has recently become a Vue convert, I thought it would be an interesting topic to discuss the migration process of working with one to the other.Source: Making the Move from jQuery to Vue | CSS-Tricks
That being said... I really like working with Vue and for now it is addressing a new set of shortcomings that hoping will be superseded at some point in the future by Web Components and other new-age native features.
Having worked more than a decade now on the web, it is safe to say that the more things change the more they stay the same.
style tag at the top of the page. Every subsequent reload is pulling from that same cache. This greatly helps with page performance as the first visible CSS is loaded immediately.
This works great until you need to push out a new change to a stylesheet. While the cache does have a timeout until the next refresh, there are times when you need to force out an updated stylesheet out to visitors. The first way to do this is to add an additional parameter to the filename, such as
styles.css?v=1. The browser will see this as a new file and be force to make a request to the server for a new version. Making additional changes on that version number will continue to force new versions, however this isn’t exactly sustainable to manually update every time.
How can we automate this in OUCampus? In our main XSL file used for template transforms, usually
template-matches.xsl, I added a template match to catch all stylesheets requested off our own domain and append that version parameter to the filename. Instead of incrementing a number as I mentioned above, it is using the current timestamp as of publish as the versioning number. e.g.