Yeah but see, we're talking about a functionality that is inherently visual. Ergonomics has nothing to do with esthetics, and it's such a dumb excuse to hand wave aside interface issues as of they are just about "making things look pretty"
> I think in many cases the authors value functionality much more then esthetics.
In many cases the repository isn't meant to be more than for source code too, not everyone use their git repository as also the marketing page, that'd go somewhere else.
With that said, grapheneos.org doesn't seem to have any screenshots either, which I also don't understand and think is a bummer. Even though the point of the differences with GrapheneOS might not be mainly visual, just showing what it looks like seem like a no-brainer.
It doesn't happen overnight, but the adversarial behaviour of the current administration and the tariffs really changed the perspective about America on many Europeans.
The discussion about building European alternatives had never been so mainstream. If and once they emerge, I think the shift will happen. But let's see
I started to consider it a show show way earlier than 18 months ago. Jira is so terrible to use that it is hard to phantom how they are able to be paid for their product
Jira is how it is because almost any product that grows to be that flexible will develop the same problems.
They failed to rearchitect it to something suitable for the inherent flexibility though, so it remains a disaster area, but one that is uniquely able to fit the whims of any manager that can then mandate it for everyone else.
Maybe the workflows, etc., are inherent complexity, so that any similarly-flexible product will have the same problems.
But the awful client-server architecture, where anything you do takes several seconds of waiting for the client to send who-knows-what to the server and get data back, even selecting something from a dropdown... that is absolutely just Jira. A competing product would be able to deliver much, MUCH snappier UX. Jira is just the crappiest, slowest UI that I have ever had the displeasure of being forced to work with.
The point is that there aren't many complex tasks were fable delivers a significant value increase over cheaper models.
Single prompting a very complex tasks is rare even on frontier models, because it can be done successfully only for specific situations (e.g. you have a very strong verification step the model can iterate on).
Most of my everyday usage is for smaller takes, were you don't really get the benefit of the most expensive models, and my guess is that is the case for the most users
> do we think we're discovering that Chrome had more big holes than we thought or are we raising the security bar by fixing smaller holes?
To me the most probable explanation is that they automated a way to find (and fix) existing vulnerabilities in a way that was not possible before.
Some holes were probably very small, some were probably almost impossible to actually exploit, I don't doubt it. But still, I find it very hard to not consider this a strong security improvement overall (unless they made those numbers up)
Of course it is just tokens, but the result is the same.
If, in the amount of data they ingested, there was a clear pattern of responding in an hasty and carefree way to frenetic questions, LLMs will try more hasty and carefree solutions to a frenetic prompt.
You can decide whether you can say that they "feel" the urgency or not, but the outcome is very much the same
> That's not an advantage for the user at all, is it
Of course it is an advantage. I tend to access most of my apps and services from both the PC and the smartphone, having data shared across the two is a deal breaker for the very vast majority of them.
If in 10 years the ratio moves from 70/6 to 50/26, the situation will be vastly different.
The options are not black and white
reply