Dlib VS sciter

dlib

The apparent gender estimates from photos are using dlib, and I really ought to get what I'm doing cleaned up in such a way that other people can use it easily.

I really like dlib's code https://github.com/davisking/dlib

Additionally, C++ may be used for extremely high levels of optimization even for cloud-based ML. Dlib and Kaldi are C++ libraries used as dependencies in Python codebases for computer vision and audio processing, for example. So if your application requires you to customize any functions similar to those libraries, then you'll need C++ knowhow.

If you know C++, you don't need anything else. Go and learn APIs for C++ libraries. If you're into DSP, why not study Dlib?.

The data is mostly in this spreadsheet. The apparently facial gender estimates are made with Dlib. The mental health assessments are from Beck's Depression Inventory and the Snaith-Hamilton Pleasure Scale. The graph is made with gnuplot.

The plugin uses dlib library with a very fast HOG detector for both face recognition and detector following the relative examples.

The dlib facial recognition model thinks that I am now a distance of about 0.3 from where I started, which is far enough to start getting many false positive matches, but still within the design intent that different pictures of the same individual will be within 0.6 of each other.

Dlib's face recognition module thinks that I am about 0.25 units away from where I started; its design intent is that distinct individuals will be 0.6 or more apart, although in practice other people start showing up around 0.3.

> wondering if css and svg could be used as abstraction over graphics and UI libraries

There's another project called Sciter that uses CSS to target native graphics libraries: https://sciter.com

> I wonder how hard it was to implement css. I've heard it can be pretty complex.

It was hard, but the biggest barrier is the obscurity of the knowledge.

Text layout is the hardest, because working with glyphs and iterating them in reverse for RTL is brain-breaking. And line wrapping gets really complicated. It's also the most obscure because nobody has written down everything you need to know in one place. After I finished block layout early on, I had to stop for a couple of years (only working a few hours a week though) and learn all of the ins, outs, dos, and don'ts around shaping and itemizing text. A lot of that I learned by reading Pango's [1] source code, and a lot I pieced together from Google searches.

But other than that, the W3C specifications cover almost everything. The CSS2 standard [2] is one of the most beautiful things I've ever read. It's internally consistent, concise, and obviously the result of years of deliberation, trial and error. (CSS3 is great, but CSS2 is the bedrock for everything).

[1] https://gitlab.gnome.org/GNOME/pango/

otherwise, if we have only retained mode as in browsers, we will need to modify the DOM heavily and create temporary elements for handles.

[1] https://sciter.com

I've still never used it but I've long been curious about Sciter:

https://sciter.com

These bullet points are exactly what I did in Sciter (https://sciter.com)

- Windowing

-- Tabs

-- Menus

-- Painting

-- Animation

-- Text

-The compositor

-Handling input

-- Pointer input

-- Keyboard input

- Accessibility

- Internationalization and localization

- Cross-platform APIs

- The web view

- Native look and feel

On top of that DOM and CSS implementations to achieve declarative UI. And JS as a languuage behind UI - declarative in some sense way of defining UI behavior.

I'm not sure if it can support all the libraries but yes it can be used to make desktop apps. Theres also Sciter.

https://sciter.com/