Ah yes, i got an account suspended on play console due to inactivity. The new help system has been "improved" in the sense that it is directly inside play console, so of course i can't appeal or request to reinstate or transfer the app ids to a new account, because THE CURRENT ACCOUNT IS CLOSED AND I AM ALWAYS REDIRECTED TO A PAGE THAT TELLS THAT THE ACCOUNT IS CLOSED.
So i tried appealing using another console account. After about a week i got the usual automated response stating that my previous report was auto-translated into english (i wrote it in fucking english of course) and some generic babble about what happened.
To which i replied that i have no problem opening a new account using the old email, but i'd want to know beforehand if i'd keep, or how to retain, the package IDs so it's not going to be a fucking painful mess to tell customers to reinstall.
And of course i got the same autogenerated email, with a couple new lines summarizing the first part.
I feel for the author, it is literally impossible to talk to a human there.
renault already put out some of these cars a few years ago, with this system you could get up to 1000km with a full gas tank! Just what my much cheaper diesel always could do!
On a different corner of the open source ecosystem, PrusaSlicer, also a wxWidget project, just announced the first of its v3 releases with a full GUI rewrite, and what a blast from the past it was to have a X11, non-scaled, wrong font & dpi. It's really unfortunate that they didn't take the opportunity to switch to Qt
Most people that have never maintained >=Qt5 projects assume free wxWidgets native cross platform OS interface support is less hassle.
Refactoring the application core means their team should have forked the project to audacity-qt rather than inject long term Qt library and license dependency issues into the original package.
Qt on occasion has proven to cause problems with license term changes, GL library bugs on Linux window managers no one ever fixes, and a chain of legacy build issues.
Microsoft people tend to design around entertainment eye candy rather than functional long-term reliability. A interface use-case context pop-up isn't a design choice, but rather just chaotic depending on who is using the seat.
The Audacity 3 interface certainly needed a lot of work, but nuking it for v4 re-write is simply packaging a different program as the original.
Hopefully the remake works out. The odds are not in their favor though... =3
My understanding is that the Qt 6 build system is vastly easier to work with.
Also, Audacity is not the first major FOSS project to successfully migrate from wxWidgets to Qt: Dolphin, the GameCube/Wii emulator, made a similar migration several years ago[0][1][2][3].
The Audacity team imported their existing Qt interface code from a previous project. Depending on the design, the code smell could have a lot of vestigial parts unrelated to the new project.
I have always seen FOSS as the last stop for public domain software. It is supposed to become the stable road future kids walk down to become professionals. The Qt framework is often antithetical to that goal in my opinion. =3
Rule #3: popularity is not an indication of utility.
I don't know, it took me a while to get used to but i actually prefer Qt6+CMake over Qt5. Porting the first application was kind of a nightmare due to how many things i had to change.. though they were code smells to begin with, now everything run smoothly.
imagine picking some Vue framework over Qt when talking about "the stable road future kids walk down to become professionals". There's software written today in Qt that traces back all the way to the mid 90s and are still top-of-the-line for their business.
The project I'm working on has been based on Qt since Qt 4 era, has been through people vouching for JavaFx, Angular, JUCE, React, Electron, and a dozen other frameworks over Qt, and had entire competitors based on web tech come and wither. How many Vue software will still be written in Vue 20 years from now ?
Structurally, Qt is sometimes worse given the compatibility issues. There are desktops where Qt5/Qt6 software runs fine if you can get it to compile, but the GL interface has been broken on many platforms for over a decade.
If folks don't plan on maintaining things after a release cycle it no longer matters how one ports disposable code. On mobile the App life cycles are short. Quasar does exactly what Qt has been doing for years, but just abstracts the compilation pipeline for each MacOS/Win11/Android/iOS/Linux platform. For simple stuff it works fine, and generates solutions in under an hour.
>How many Vue software will still be written in Vue 20 years from now ?
Probably all of them in their bloated glory, as the build artifacts do not rely on a single unstable external fragile framework library heavily coupled to the operating system releases.
Personally I prefer wxWidgets for desktop, but it is not appropriate for every project. =3
> There are desktops where Qt5/Qt6 software runs fine if you can get it to compile, but the GL interface has been broken on many platforms for over a decade.
do you have example / bugreports of this ? for my app I run tests across a wide range of laptops, platforms and distros, across nvidia / intel / amd / llvmpipe / ... and it all works fine. hell, with the help of Claude I managed to port back the current dev branch of Qt6 back to Windows XP, with working OpenGL.
The thing that bothers me is why the fuck are they still scraping git.kernel.org or any other site that has already been scraped a million times before. Who would pay for that data?
Then again there is the conspiracy theory about cloudflare sponsoring the scrapers
i snatched a lenovo yoga slim aura with a core 5 226 for 650 euro. Its build quality is on par if not better than the colleague's macbook, it's pretty good for working, runs fedora natively, battery last at least 12 hours unless i'm playing games.
On the battery life front, both Intel and AMD have caught up. Apple greatly inflates their battery numbers; to get 18 hours, you need the lowest spec model and you need to basically not use it. Chromium or Firefox open? Bluetooth active? Yeah, you’re looking at 12 hours, not 20.
12 is still good, but intel as of lunar lake (2 generations ago!) matched that. Now, the performance is still behind, particularly single core. But the efficiency is there, and these are standard x86 chips.
The efficiency doesn’t come from ARM, it comes from the process node and chip design. Apple uses the latest process nodes with an SOC design. When intel does the same, as they have done, they match the efficiency easily on x86.
The real gain is the SOC. When you shove the ram and chipset into the CPU you save massive battery.
> On the battery life front, both Intel and AMD have caught up.
Intel and AMD's cpus don't have batteries ;)
Their chips are approximately as efficient as Apple's chips from ~2 years ago, but that's not their fault, it's Apple getting the entire allocation of new chips for about 1.5 years.
> to get 18 hours, you need the lowest spec model and you need to basically not use it. Chromium or Firefox open? Bluetooth active? Yeah, you’re looking at 12 hours, not 20.
I work on compilers, often maxing out all the CPU cores, and have stopped carrying the power adapter altogether. I plug it in maybe once in three days.
> The efficiency doesn’t come from ARM, it comes from the process node and chip design. Apple uses the latest process nodes with an SOC design. When intel does the same, as they have done, they match the efficiency easily on x86. The real gain is the SOC. When you shove the ram and chipset into the CPU you save massive battery.
Yes, I agree. IDGAF about whether the battery lasts longer because of ARM or magic pixie dust.
Yes, I meant that Intel and AMD laptops have caught up to battery life, due to the chips.
I have both an M1 Pro MacBook Pro and an Asus lunar lake laptop. The M1 battery life is… good. But again not what Apple claims, if you actually use the computer. The lunar lake laptop has better battery life.
The base M1 is probably much better, but I still think these lofty 20 hour battery life claims from Apple are, well, lofty. It might be true if you playback local media with hardware acceleration and run in airplane mode. But as soon as you’re using all the antennas, the battery life goes down a lot. Bluetooth especially drains battery life.
correct! it's better on lenovos. All metal, trackpad has a proper click, keyboard doesn't shit itself. Screen is not retina, but then again i don't need that ridiculous resolution as the OS i'm using doesn't employ a toy UI with bubbles and rounded everything. Before this i had macbooks for 15 years, colleagues have this generation's macbooks at work, i like this one a lot more.
I'm a bit opponent of Apple's walled garden, but the build quality of this laptop is quite far away from a MacBook... Except the display, this OLED WXHQwhatever is stunning.
Source: I bought the same (with core i7, so it's performant, etc.).
So i tried appealing using another console account. After about a week i got the usual automated response stating that my previous report was auto-translated into english (i wrote it in fucking english of course) and some generic babble about what happened.
To which i replied that i have no problem opening a new account using the old email, but i'd want to know beforehand if i'd keep, or how to retain, the package IDs so it's not going to be a fucking painful mess to tell customers to reinstall.
And of course i got the same autogenerated email, with a couple new lines summarizing the first part.
I feel for the author, it is literally impossible to talk to a human there.
reply