4 ms·
GUI-driven development is a perfectly fine way to getting started, which is what this guide does. However, does anyone else get an uneasy feeling about developi
by usui 5y ago
GUI-driven development is a perfectly fine way to getting started, which is what this guide does. However, does anyone else get an uneasy feeling about developing software that revolves too much around using a GUI/heavy IDE? You can argue that Visual Studio Code is bloated, etc., but at the end of the day, I can clone a project on GitHub and easily run a CLI command to compile and try a project, and maybe use Vim if I have to do a quick edit. Any time I see a development guide that depends on screenshots or requires a specific IDE it makes me feel uneasy, even though I know that's not how most newcomers feel.
- brundolf 5y agoI don't really mind it if that IDE works seamlessly without issues, is freely available, and the project data is all in plaintext. I wasn't programming in 2005 but I have reason to think the Xcode experience really was that tight at the time When I lose faith in the IDE and its abstractions, that's when I get really antsy for the ability to opt-out/do everything directly without its help
- wruza 5y agoAll this guide shows is an Interface Builder, basically. Either you use one of these, or walk through a boring process of setting up controls and their properties and their bindings in code. Eventually IB just interferes or breaks your layouts, but at this time you have a good visual idea of its workings. This is a good thing, even if you're a senior newcomer. What they've got wrong is that IB is not a tool, but only a tutorial.