I work at Qt and I would say the focus is not at all on the open source Qt. It’s actually kind of a burden for us since it can eat some commercial sales. I think many of us at Qt often wish it wasn’t free
It was in preparation of this exact scenario that the free qt agreement was put in place. KDE developers were pretty miffed at the drama around this at the time (basing a free environment on a toolkit that could go full proprietary at any time, leading to GNOME), but I'm pretty sure most are happy about it now. What an awful waste it would have been if Qt had ended up proprietary after all.
It’s pretty obvious why they didn’t, they’re GC by default. That’s already enough to put people off, even if it’s “not a problem” in reality, people will just avoid it for systems programming if they hear that, they will assume all the good features need the GC
Nim is stack allocated by default, and you annotate types explicitly with `ref` to use the GC. Even then, the compiler elides reference counting using borrow checks, you can choose different GC options, and the GC isn't stop the world like most. You don't need to touch reference counting if you don't want to, and Nim fits embedded dev pretty well for that reason.
A theoretically perfect next token prediction machine is just an LLM with a temperature of 0, which performs worse than one with a non-zero temperature (i.e. imperfection)
The "prediction" has nothing to do with predicting the future, it just means choosing the most likely next token for existing human text
No that would be a pretty terrible next token predictor. It would perfectly match the training data, but the training data is just a sample of what we are really trying to predict: human language, knowledge, and thinking, which is inherently probabilistic. Perfectly matching the training data is a pretty good sign that you've overfit.
The point of fantasy or even surrealism is to contrast with the parts of the work that are chosen to be realistic. When random parts of the work are broken in meaningless ways it becomes slop
It's one of the reasons Microslop have been pushing Windows for ARM, only for them to discover that ARM doesn't actually solve this problem. It's less likely to cause problems just because there are less Windows ARM devices out there, with less variety and thus more consistency, but the underlying problem of drivers and other BS being able to block sleep and Windows not being able to handle it is unsolved. Heck, sleep working just fine on x86 Macbooks should have told them that.
Even worse is the fact that support for S3 sleep is going away, so if that did work for you, you'll be pushed over to using S0 sleep, which also doesn't actually solve this problem to any significant degree.
Going by the article, Asus clearly don't. Given the stories floating around about the others, I doubt they have it too, except maybe Lenovo on Thinkpads and the like, although they too aren't immune from problems that really should be caught in QC.
reply