Moderators should fix the title and add "in 2018" to the end, as it's on the chart itself. Omitting "in 2018" part changes message completely and is misleading.
It would be misleading if sales peaked in 2018, then fell, and have subsequently surpassed the 2018 peak. That's not what happened though. And reporting "sales have peaked" 6 years after the peak is reasonable - doing so 2 years after the peak would be premature.
I still support adding it to the title, because it's even more impressive.
The timeframe is even more important due to the macro environment of the past six years - one might have credibly suggested 2019 was a fluke and that 2020-2021 was obviously a major outlier on many fronts, but the trend keeps going into the latest years they have data for, which combined with the increase in EV sales makes 2018 as Peak Internal Combustion pretty much irrefutable from the vantage point of early 2025.
How is it misleading? It would be impossible for someone to credibly claim something peaked in 2024, for example. So it must be some time in the past (and 2018 is not very long ago).
It just reads as present tense. Your point is valid. However, there are going to be how many eye balls that don’t read past the headline and don’t think deeply on it, but now have the impressions that they are currently at a peak
Installed and tried it for a sample Flutter app. So far looks too good to be true :) Super easy to start and tinker with. And surprisingly fast. Learning how to write real world tests with Flutter apps probably will have some learning curve, but that's expected.
Would be amazing to use it with Flutter desktop (macos at least) to avoid running iOS simulators.
I’ve been using Maestro for two very large Flutter apps and it’s been so ahead of every other option is not even funny.
No long compilation times, no half baked testing dev experience, supports iOS and Android, no pumpAndSettle BS, No Flutter hacks, multiple cloud providers (cloud.mobile.dev, moropo), you can interact with native elements, so you can work with push notifications, system dialogs, system settings, email clients, web views, browsers, and a very simple test definition files that every capable QA engineer can maintain with very little supervision from developers (no need for dart expertise for writing tests).
haha happy to hear that :) (I created Patrol) ((and then worked on Maestro at mobile.dev briefly))
I too think that for the vast majority of use cases, Maestro is the best solution. Fast and easy to write and run.
Also it's cool that it's open-source and has very strong community. I'd be skeptical to have all my tests stored in some SaaS that I can't even run locally (as some other solutions do)
Maestro being open source, being able to run it locally AND having two providers where we can just sign up and start running our tests was an important factor going with them.
We ended up going with Moropo as their pricing matched our needs better. Even if in the future we had issues with them, we could just go to a different provider is a big plus.
As someone who has used EdgeDB religiously for years now and still has projects with EdgeQL code generators (that use old syntax), one of my earlier requests was, "Please don't break things". Don't change the syntax of EdgeQL in a backward incompatible way, don't rename commands in the command line, etc. It's really not a big issue to remember some not-so-perfect term. Requiring thousands of people to unlearn/relearn new terms, commands, and names, and rewrite scripts and documents - is an issue. Didn't expect to see the whole name EdgeDB being replaced with another, ungoogleable name.
The argument of "some developers don't look past name and think that it's an edge-computing database" is superficial at best. I can get how it can be annoying, personally, but unless it was backed up with data showing that it hurts adoption, I wouldn't take it as a serious problem worth forcing thousands of users to switch to a new name/commands.
Following this logic, these developers could also ask "MySQL? Huh, you must be running it only on your own servers" or "Gel? Huh, is it some toy database for kids?".
I wish more people realized the enormous cognitive costs and debt created by such renamings. :/
Sorry, divan, for causing pain. This wasn't an easy decision. FWIW we're still strict about backwards compat and all you stuff should continue working.
Nice! Excited about HTML export. I used LaTeX for autogenerating some semi-legal documents in both PDF and HTML, so all editing happens on Github and Github Actions do the rest for publishing PDFs and updating site. Started using Typst for some of these, but HTML export was a missing piece to completely switch to it.
Is it by design, or it just how it worked with that particular person?
reply