471 karma · joined March 3, 2020
I think being offline is a lesser headache than a large bill, especially for those who are inclined to a free tier to begin with.
When I was new to their corresponding GUI frameworks, the dot + property notation was appealing because it looked clean. However, as I got more experienced I'm no longer seeing the advantage of saving two parentheses characters at the expense of potentially hiding function calls where anything can happen.
I'm not sure why D joined the club given it doesn't have a corresponding de facto GUI framework, and its users even discourage it.
Haven't used it though, since I already had programming experience and just ended up using SFML in C++ or Monogame in C#.
[0] https://blog.research.google/2014/10/hdr-low-light-and-high-...
[1] https://handmade.network/forums/articles/t/7330-implementing....
[2] https://github.com/nothings/stb/blob/master/stb_truetype.h
But first, it helps to have sample files to see recurring structures. Ideally, you also have access to software that generates these files. This allows you to deal with simpler files containing less information to reason about, make small changes within the program and compare the corresponding change(s) in the file.
It gets GUI layouts done fast, but I also think it has some drawbacks. Manually drawing controls, i.e. sizing & positioning, eventually becomes a tedious chore once you have a lot of them or if you anticipate frequent updates in the UI. One trick I always end up using is just using some simple math to do the layout as the form resizes. In C# + Winforms, I'd go further by bypassing the visual designer as much as I can and just manually spawn the widgets just like any other object. Other UI frameworks also assist in layouts or just don't make this a problem to begin with. For example WxWidgets, Qt and, if I'm right Ultimate++, have sizer/container controls that do the layout logic.
From what I hear, it is also trying to solve the multi-language problem.