The part that takes time in UI isn’t wiring up components, it’s the small changes like something is a pixel to the right or that gap is two pixels wide. Changing those in a C++ project means recompiling and that adds up to significant overhead over a day of polishing the UI. If C++ was able to get builds out in less than a second, this wouldn’t be an issue. People value performance in their own tools more than the tools of their customer.
In modern Qt you don't write UI in C++ anymore - you do that in QML. It is far simpler to create amazing pixel perfect UIs with drooling-inducing animations in QML. I wrote a blog post that talks a bit about this[1].
In wxWidgets you use sizers, so you don't work on pixel-level alignments. I can understand if you're using an ancient framework like MFC, but even then I seem to recall there was a sizer equivalent system (or it is easy enough to write a class to do so, moving components).
I think it is a daft thing to move to shipping a colossal web framework and entire browser simply because of 1px UI alignments (which have been a solved problem for decades in C++ anyway).
After all expertise is mechanized, we’ll be in their loop instead of them being in ours.
Think of this like going to a doctor with a simple question. It probably won’t be simple to them. At the end though, we usually do whatever they tell us. Because they are the experts, not us.
These AI agents have been such a burden to open source projects that maintainers are beginning to not take patches from anyone. That follows from what you’re saying here because it’s the editing/review part that’s human-centric. Same with the approval gates mentioned here.
Another parallel here is that AI agents will probably end up being poor customers in the sense of repeat business and long-term relationships. Like how some shops won’t advertise on some platforms because the clicks aren’t worth as much, on average, maybe we’ll start to see something similar for agents.
Yes, in the worst case they will be super fast to churn. That's unless they just forget to unsubscribe and you end up with a charge back because the principal has no idea he ever even signed up for your product.
I think we very often confuse engineers with scientists in this field. Think of the old joke: “anyone can build a bridge, it takes an Engineer to build one that barely stands”. Business value and the goal of engineering is to make a bridge that is fast to build, cheap to make, and stays standing exactly as long as it needs to. This is very different from the goals of science which are to test the absolute limits of known performance.
What I read from GP is that they’re looking for engineering innovation, not new science. I don’t see it as contradictory at all.
It can take some people a few years to get over OOP, in the same way that some kids still believe in Santa a bit longer. Keep at it though and you’ll make it there eventually too.
Some systems pulling the average up and some pulling down but the average of them is net up. I wonder though if it would have been better or worse for us if the net change ended up negative (dropping temps every year) instead. Probably worse, right?
I see it as the most important home maintenance tool. Saves hundreds per year on little things that break. Like a wall patch, small o-ring for a toy, drawer slide mount, basement light mount, etc. I will say though that the learning curve is a bit rough if you don’t have CAD experience.
I was a huge fan of the high-framerate Hobbit films. It made the huge battles much easier to follow and I felt like I picked up a lot more of the details. Such a shame it never had a retail release.
Never mind the battles and action scenes, just any scenes with normal movement of the camera.
There is a lot of panning in the initial scenes of The Hobbit (opening scene is the fall of Erebor). I watched that movie initially with the new higher frequency, and everything was soooo smooth. When I rewatched it, every single time I have to experience the terrible, terrible choppy, hard-to-see-anything lower frequency transformations and I cry. This is the 12st century, and the movies can't even pan across some landscape smoothly?
In that first viewing I saw everything in those caves, it was so easy. Oh how I miss that.
It's really infuriating that after decades of dealing with the implications of NTSC video systems not supporting 24 FPS the Blu Ray designers chose not to support 48 FPS even though 60 FPS is supported.
reply