- City buildings enriched by augmented reality content (Apple visionOS as example)
- Web browsers "replacing" every day the role, interpreted in the past by the Operating System:
- their APIs implement functions way more ahead than the classic web page (e.g. 3D Rendering, MIDI connectivity, Serial port, Bluetooth, Data storage, etc..)
- the runtime context is enabled by default for online data exchanging, at disposal of every webApp executed by the User. Offline execution is possible but not mandatory.
- their role is the equivalent of what frameworks do in the software development field: provide a valid, stable and ubiquitous set of features, accepted by any programmer who is adopting the framework. This enables a team to jump straight to the core logic of an application and avoid the need of define and mutually approve any architectural/operating concept.
- last but not least: online connectivity ensures that the last version of every application is presented to the final User, excluding the need of periodical updates. This implies transparent rollout/back of features.
How to reduce TTFB
In the past few years in the web dev world, we’ve seen a significant push towards rendering our websites on the server. Doing so is better for SEO and performs better on low-powered devices, but one thing we had to sacrifice is TTFB.
In this article, we’ll see how we can identify what makes our TTFB high so we can fix it.
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (0)