Posts Tagged with 'webdev'
After my post the other day, I found myself reflecting on just how far CSS itself has come in the last 25 years.
This makes me think about the die-hards who are against the Web as an application platform. They always say the Web was intended as a document platform and therefore shouldn't be used for applications. But Fielding modeled the REST architecture on the Web, and he and others working on the initial tech considered it to be a large, distributed application. So by that line of thinking, the Web as an application platform is nothing new. These separate web apps are just sub-features of the World Wide Web application.
In this blogpost I argue the case for consigning the term "REST API" to history. In its place we should adopt the terms "HTTP API" and "hypermedia API", which better differentiate two distinctive design conventions for the programmatic interfaces of web services.
Fielding's thesis was a kind of retrospective on the design decisions that led to the World Wide Web — a distributed hypermedia-driven information retrieval system — becoming the runaway success it was.
I've read about Fielding's REST dissertation (never actually read the dissertation itself), but this is an interesting way to think about it. I've tried to explain the ideas behind REST to colleagues before, but I don't think I've ever been successful. Describing it with the Web as an example of the architecture makes it much more tangible.
April is upon us, and we have a most timely release for you — Firefox 88. In this release you will find a bunch of nice CSS additions.
An in-depth look at the technical stack behind this very blog! We'll see how I use Next's API routes to implement my hit and like counters, how I use MDX to add interaction and customization, and how I organize my codebase, among others.
Update, April 9, 2021 : We've launched Am I FLoCed, a new site that will tell you whether your Chrome browser has been turned into a guinea pig for Federated Learning of Cohorts or FLoC, Google’s latest targeted advertising experiment. The third-party cookie is dying, and Google is trying to create...
You can remove your website from Google's FLoC rollout by altering HTTP response headers.
Support for QUIC and HTTP/3 is now enabled by default in Firefox Nightly and Firefox Beta. HTTP/3 will be available by the end of May.