1 hour ago · 11 min read2203 words · Tech · hide · 0 comments

Native toolkits are not terribly ergonomic, and are a lot more painful to use compared with web dev in many ways. Building a UI with them is an imperative exercise where you construct widgets one call at a time, pack them into containers, and wire each event to its handler by hand. What's worse is that the structure of the interface often ends up living outside your language altogether forcing you to use tools like GtkBuilder XML or Xcode storyboards, where none of your usual tools for composing and refactoring code can reach. Layout is governed by box packing rules and constraint systems that are easy to describe but hard to predict. And a common task such as turning a list of items into a list of widgets that stay in sync with the data results in a ton of boilerplate that you have to repeat over and over.The pain of working with native toolkits gave rise to things like Electron which simply package a browser engine as a frontend for the application. While that technically works,…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.