There's a trillion blog posts about everything that is so great with SwiftUI. Now that we all know what is so great about it, I thought I'd write something about what is not so great. This post focuses on macOS but should apply to iOS as well.
Source: What is not so great about SwiftUI.
Budding web developers learning Model-View-Controller frameworks are taught that they should use an Object Relational Mapper (ORM) to interface with their databases. But the “why” is often brushed aside or omitted entirely, leaving a fledgeling programmer with burning questions like ”What are ORMs, anyway?” and “What problems do they solve?”
ORMs are a class of tools that facilitate interactions between a programming language and a relational database management system. They can range in complexity and opinionation from a simple set of abstractions for interactions with relational databases (SQLAlchemy Base) to fully opinionated tools for mapping database rows to language structs (Django ORM, SQLAlchemy ORM). To get a better understanding of how ORMs work, it’s helpful to work through the kind of problems they can solve.
Source: Why should you use an ORM (Object Relational Mapper)?, an article by Karim Marzouq.
In this post I’m going to jot down a few thoughts to a question that has been intriguing me for a while now. “What font-display setting should be used to improve the experience for all users?”. Before I get into that, let’s go over a few of the basics.
Source: A font-display setting for slow connections, an article by Matt Hobbs.