Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

LeanQt – GUI is here, Widgets are near

github.com

Post reply on HN
Print view View original

1–10 of 55 posts

Re: LeanQt – GUI is here, Widgets are near

#3

Post by recuter » 

  With the new gui, image and thirdparty modules, the uncompressed size of the source tree has grown to ~43 MB (10 MB zip compressed), with close to 3000 C/C++ files and more than 700 kSLOC.

  LeanQt is designed to build only the modules you actually need.

  ..The resulting source tree has less than 800 files and requires only ~11 MB (2.6 MB zip compressed), and perfectly works as a substitute of the full source tree in this guide; see the attached LeanQt_core_only.zip file.
Good. Not Alan Key 10kSLOC for the entire universe good. But certainly a step in the right direction.

I have searched high and low for something better, here is one rabbit hole: https://www.areweguiyet.com

Many people are trying, but frustratingly, even in 2022 you could do a lot worse than QT.

If you really want to get depressed read about the internals of Servo (rip) and how they tried to render text.

No wonder something that calls itself lean is still somehow hundreds of thousands of lines.

Re: LeanQt – GUI is here, Widgets are near

#5

Post by bachmeier »

Nice to see. I remember a while back trying to compile an open source app built with Qt. I gave up on it when I got to the part where I had to sacrifice a young male goat. Referring in particular to this: "Unfortunately, there has been a certain proliferation over the years where Qt has been bloated with all sorts of features with questionable value. The standard binary installation of Qt swallows several gigabytes and requires a login to a commercial company server, which discourages many people."

Re: LeanQt – GUI is here, Widgets are near

#7

Post by opencl »

dotancohen wrote: post #6

An interesting idea. I would love to see Python bindings, right now seems to be Cpp only.

It's just normal Qt with a bunch of features removed. Modifying one of the existing Python Qt bindings to build against this should be relatively straightforward.

Re: LeanQt – GUI is here, Widgets are near

#8

Post by jcelerier »

recuter wrote: post #3

With the new gui, image and thirdparty modules, the uncompressed size of the source tree has grown to ~43 MB (10 MB zip compressed), with close to 3000 C/C++ files and more than 700 kSLOC. LeanQt is designed to build only the modules you actually need. ..The resulting source tree has less than 800 files and requires only ~11 MB (2.6 MB zip compressed), and perfectly works as a substitute of the full source tree in th…

> Not Alan Key 10kSLOC for the entire universe good.

if this was enough that's what we'd use though, no ?

While I like this project, I don't use half of the features it mentions in the supported features, and I use half of the features with no support planned so it's not an option for me ; i'd wager anyone not making todo apps has different set of requirements which leads to something like Qt which comes with everything. Simple example: no scripting support means pretty much that it's unuseable for any technical app e.g. in CAD/CAM or similar. No SQL means that it's unuseable for any kind of enterprisey CRUD client app.

Re: LeanQt – GUI is here, Widgets are near

#9

Post by Waterluvian »

Are there tools to evaluate (imperfectly) the percent of a binary that actually gets used?

Like, run an application, run the watcher tool, then “walk the application” as best as possible and get an output: “35% of the binary was never read.” ?

What’s on my mind is evaluating the actual result of tools and methods for not including unnecessary things. I struggle with this in web land. Tree shaking and such does a wonderful job but I honestly don’t know how much of my bundle is still superfluous.

Re: LeanQt – GUI is here, Widgets are near

#10

Post by bkallus »

Waterluvian wrote: post #9

Are there tools to evaluate (imperfectly) the percent of a binary that actually gets used? Like, run an application, run the watcher tool, then “walk the application” as best as possible and get an output: “35% of the binary was never read.” ? What’s on my mind is evaluating the actual result of tools and methods for not including unnecessary things. I struggle with this in web land. Tree shaking and such does a wond…

I don't know, but one could implement this without too much difficulty as a wrapper around afl-showmap.
Post reply on HN