Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
rubymamis
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
61.
▲
by
rubymamis
10mo ago
Hi there! > The most common performance issues in decently written applications are rendering of invisible items aka overdraw That's indeed what I found as well! Especially, these hidden items consume a lot of unnecessary RAM. What
62.
▲
by
rubymamis
10mo ago
What about Mojo?
63.
▲
by
rubymamis
10mo ago
I already showed in my benchmarks that my block editor is faster than all block editors on the market - even more than those that uses native frameworks. And there are ten of thousand of lines of QML code (and round the same of C++ as well)
64.
▲
by
rubymamis
10mo ago
What exactly - from an end user perspective - do you worry about? Performance? I already showed in my benchmarks that my block editor is faster than all block editors on the market - even more than those that uses native frameworks. And as
65.
▲
by
rubymamis
10mo ago
> The challenge, though, is there isn't really a good comprehensive list of those things the would allow you to compare the framework you use to native. And you can't patch everything if you don't even know where the holes
66.
▲
by
rubymamis
10mo ago
What frameworks do you suggest? I've covered in the blog post apps written in Fultter, web (React), Swift, etc. It's a ton of work building something like that from scratch, so I don't really see myself doing that.
67.
▲
by
rubymamis
10mo ago
> Saying “they’re both c++” is seems kind of misleading and meaningless right? Not really, if you avoid writing Javascript code in your QML components, than most of your executable will end up being compiled C++ code. If you do write Jav
68.
▲
by
rubymamis
10mo ago
QML isn't slower than Qt QWidgets, in the end of the day Qt Quick components are simply C++ objects, you can look at the source code[1]. [1] https://github.com/qt/qtdeclarative
69.
▲
by
rubymamis
10mo ago
(Author here) I think the fact that Qt went with Javascript as the scripting language for QML wasn't a smart decision - especially resulting in poor type safety. That said , they have improved the situation by a lot with required prop
70.
▲
by
rubymamis
10mo ago
(Author here) Wow just noticed my blog post is on the front page! Will try to respond to all comments here soon.
71.
▲
by
rubymamis
10mo ago
I thought about it as well. Might do it at some point.
72.
▲
by
rubymamis
10mo ago
Did someone do a deep dive on why battery life is so awful on Linux? Or is it some Ashai's driver's inefficiencies that causing this?
73.
▲
by
rubymamis
10mo ago
You can always use something like Little Snitch to not allow it to dial home.
74.
▲
by
rubymamis
10mo ago
Please share more info and images, if you can.
75.
▲
by
rubymamis
10mo ago
This looks awesome, looking forward to using it! Qt keeps innovate (although their built-in UI components slack behind).
76.
▲
by
rubymamis
10mo ago
It's still native (in terms of performance and ability to customize the look and feel) and working pretty well, it's just that not enough effort was put into making the built-in components behave and look like those on the platfo
77.
▲
by
rubymamis
10mo ago
Creating Daino Qt - a collection of components that makes Qt apps feel and look native on both Desktops and mobiles (each with its own set of challenges). Developing Qt apps with C++ and QML is a blast - the fast performance of C++ and ease
78.
▲
by
rubymamis
10mo ago
What benchmarks are good these days? I generally just try different models on Cursor, but most of the open weight models aren't available there (Deepseak v3.2, Kimi K2 has some problems with formatting, and many others are missing) so
79.
▲
by
rubymamis
10mo ago
I wish QML was part of CopperSpice.
80.
▲
by
rubymamis
10mo ago
Yes! I'm developing my note-taking app[1] for macOS and now working on a mobile version. [1] https://get-notes.com
81.
▲
by
rubymamis
10mo ago
Hi! That put a smile on my face (: I'm working now on a mobile version with real-time sync, so maybe give it another try when it comes out. Not really, not yet. Once my FOSS app was popular I used to earn a livable amount of money from
82.
▲
by
rubymamis
10mo ago
Yes, my FOSS note-taking app[1] used to be pure Qt Widgets. Recently, I've added the Kanban feature that uses QML (this and the editor settings should be the only parts in QML, if I remember correctly). [1] https://github.co
83.
▲
by
rubymamis
10mo ago
I actually love that separation. QML is a great language for writing beautiful, responsive, modern UI with animations easily. C++ is great for performance and logic. I don't like Javascript but I don't need to write a whole lot of
84.
▲
by
rubymamis
11mo ago
Qt Quick components are just C++ classes[1]. [1] https://github.com/qt/qtdeclarative
85.
▲
by
rubymamis
11mo ago
Indeed, I wrote my note-taking app using Qt with QML: https://get-notes.com
86.
▲
by
rubymamis
11mo ago
I would plug my note-taking app written in Qt C++ and QML: https://get-notes.com .
87.
▲
by
rubymamis
11mo ago
I gave it the task to recreate StackView.qml to be feel more native on iOS and it failed - like all other models... Prompt: Instead of the current StackView, I want you to implement a new StackView that will have a similar api with the diff
88.
▲
by
rubymamis
11mo ago
> Unlike common object-oriented GUI frameworks, Ribir widgets do not need to inherit a base class or hold a base object. It is a pure composition model I'm really not sure how this "composition" is any different to the usu
89.
▲
by
rubymamis
11mo ago
My impression as well!
90.
▲
by
rubymamis
11mo ago
I know it's bloated! I want to prove that so the evidence is clear on how much it affects people's day-to-day use.
More ›