The UIs are text only, so they are textual. Modern TUIs may support mouse events. That this tool can export to several TUI frameworks is evidence that these UIs are indeed TUIs, even if not the most traditional.
Another to add to the list:
Allow flexible naming. For example, drilling the two sum problem requires the user name the hashmap prev_map, but I feel memorizing this sort of stuff detracts from the lesson.
And a banner ad may display on a laptop in your home, what's your point? Location or device type matters not. This ad doesn't interrupt the user or demand any attention.
Ads really aren't that bad. Targeted ads may even help you discover products you'll enjoy.
The ad in the article is pretty obviously an ad to anyone that can read the words, "New Series. Start Watching".
Ads like these that randomly display during idle is hardly what I consider invasive.
Hopefully OP's sister gets her mental health under control, but I wouldn't immediately raise pitch forks to ban an entire industry vital to the economy and business-consumer communication.
Pedantics aside, not much reasoning against quality. Perhaps I've lucked out, but I've worked in many sectors and do not at all agree with sentiment here about DOD software quality. There is significant formal investment/research in DOD to improve operations, including taking the best of practices in commercial. In my experience, the worst of software is written by teams with little experience improvising under Agile and taking on tech debt with no time/resources to get things done the right way.
> Well, this is just standard Aerospace grade software
Can't be further from the truth. DOD software is given huge budgets where it's not surprising to see 3 separate teams performing QA for one software milestone. It's one of the few sectors that still plan software upfront waterfall style and implement strict procedures for traceability, change management, etc. Who else is using formal methods or safety critical stacks like ADA/Spark?