Semantic UI VS Skeleton

1. The author links to this file as an example: https://github.com/Semantic-Org/Semantic-UI/blob/49b9cbf47c1... . How would you structure it better than it currently is without using sections?

2. So you have a class that has a bunch of getters and setters. Let's just assume that "generate them automatically" is not an option. You want to make it really easy to see the part of the class which is getters, and the part of the class which is setters, and then skim past that. How do you do it?

3. So you have a file that defines 3 data structures. Each data structure has a definition, a bunch of functions for parsing it, and a bunch of functions for serializing it. The author suggests that you split the file into 3 sections for the types, with subsections each for the definition, parsing, and serializing. How would you do it? Let's say the language is Rust or Typescript.

I'm a big fan of Semantic UI, but I thought it was dead? There's barely been any activity on the repo in over 5 years (https://github.com/Semantic-Org/Semantic-UI/graphs/contribut...).

Semantic UI is a free, open source library that helps you build UIs with confidence. It provides over 3000+ Theming Variables and 50 + UI components and each one of them has been carefully designed to look beautiful and work intuitively. It is designed to be an intuitive, accessible, and flexible starting point for your project. It's packed with features that you can use right out of the box, and it's very easily customizable. To date, it has been downloaded over 6 million times and it has around 50,000 GitHub stars.

The way I see is that it is for the same reason that Qt and GTK include all the widgets and abstractions to create a complete UI.

Another framework that I've used in the past for 2 WebApps projects[1][2] -and I was quite happy with the result- is Semantic-UI (and the fomantic fork)[0]

[0] https://github.com/Semantic-Org/Semantic-UI

Semantic UI - 50K⭐ - Last update: October 2018

Semantic is a UI component framework based around useful principles from natural language.

It uses Skeleton https://github.com/dhg/Skeleton which is a billion years old.

To get styling out of the way, let's download Skeleton CSS, unzip all the CSS files into the src directory, and import all the .css files in the App.css main stylesheet in the project:

Skeleton - 18K⭐ - Last update: December 2014 (Wow! Since 2014!)

Latest stable version: 2.0.4 Github stars: 18.3K Development: without activity for 7 years Long of active development: 1 years Active maintainers: 0 Contributors: 25 Number of commits: 167 License: MIT Used by: 0 Github projects Git repository: https://github.com/dhg/Skeleton

dhg/Skeleton - Skeleton: A Dead Simple, Responsive Boilerplate for Mobile-Friendly Development

So I decided to start with Skeleton. The downside with Skeleton is that the GitHub project is not active anymore. The last release was in December 2014 and there are open PR’s and issues. But besides that it was quiet easy to integrate and customize. Skeleton worked quite well, but the point that the project is not active anymore made me switch to Milligram. Milligram also provides a minimal setup of styles for a fast and clean starting point. So it was easy to adapt my design and switch to Milligram.