The latest articles on DEV Community by Federico R. (@benz738). https://dev.to/benz738 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F444139%2F371fb887-78bf-4c76-81da-3f8ef8cd2f35.jpeg https://dev.to/benz738 en Federico R. Tue, 01 Aug 2023 23:23:31 +0000 https://dev.to/benz738/my-two-cents-about-future-tech-trends-3oel https://dev.to/benz738/my-two-cents-about-future-tech-trends-3oel <ol> <li>City buildings enriched by augmented reality content (<a href="https://developer.apple.com/visionos/" rel="noopener noreferrer">Apple visionOS</a> as example)</li> <li>Web browsers "replacing" every day the role, interpreted in the past by the Operating System: <ul> <li>their APIs implement functions way more ahead than the classic web page (e.g. 3D Rendering, MIDI connectivity, Serial port, Bluetooth, Data storage, etc..)</li> <li>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.</li> <li>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.</li> <li>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.</li> </ul> </li> </ol> future trends technology webdev