• 1 Post
  • 259 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2023

help-circle









  • There are several issues with native development without a browser layer.

    First of all, native UI toolkits are very different and making a robust cross platform app is pretty much impossible. So, the traditional approach is to use one toolkit, which will be native to one platform, and then let your other users deal with it. For example, GTK apps on Windows and Mac look and feel like shit.

    Another approach is to use a custom cross platform toolkit, which doesn’t use anything native at all. If enough work and thought is put in such application, it can be a very pleasant experience. But often it’s shit for all users.

    The second issue is that it can be quite hard to manage fluid window sizes and to build a proper responsive UI with native toolkits. Some are better at it, some are worse. Native toolkits also tend to punish developers for deep nesting of components making UI development even more painful.

    HTML + CSS solves all that. It’s responsive by design, everyone is used to web apps already, nesting is not a problem at all, etc.











  • Some parts of London. I used to live in a building next to three sets of railways: the tube, regular intercity and express/higher speed intercity. That’s a bit too much railway outside the window. And that’s not even the worst location, in the New Cross area some residential buildings are sandwiched between railways on all four sides.

    Don’t get me wrong, I love trains in London, so many trains means I don’t need a car, but London has the oldest railway infrastructure in the world and the way they were built in the 19th century makes some areas a total disaster today.

    On the other hand, riding a DLR train through a skyscraper is bloody epic!