The JSON types are string, number, boolean, null, object and array. So how could the suggested code possibly work? Do you want JSON.parse to do arbitrary code execution like Python's pickle?
You definitely need discipline to use C++ in embedded. There are exactly 2 features that come to mind, which makes it worth it for me: 1) replacing complex macros or duplicated code with simple templates, and 2) RAII for critical sections or other kinds of locks.
Consteval is great for generating lookup tables without external code generators. You can use floating point freely, cast the result to integers, and then not link any soft float code into the final binary.
I'm generally fully in agreement that AI writing is bad.
But this is one of the few cases where it might be acceptable.
Author is not a native speaker; in an announcement that a known project is being forked for maintenance the occasional odd phrasing and possible errors in grammar could sound unprofessional.
I wonder if in such cases a better use of AI would be to try to write it yourself and just ask a LLM to revise instead? Maybe with some directive to "just point out errors in syntax and grammar, and factual mistakes. No suggestions on style"?
They explain why in their AI policy. It's an ethical stance. Of course they wouldn't notice if there aren't clear signs of LLM-ness, but that's not the main reason why they forbid it.
Thanks for the clarification. Not that I agree with their stance (the exact same could have been said at the start of the industrial revolution) but I respect it nonetheless.
> the exact same could have been said at the start of the industrial revolution
The pollution caused by said revolution is currently putting humanity at a serious risk of world war and maybe even extinction so... maybe they had a point? I'm not taking a strong stance either way here, but worth thinking about the downsides from the industrial revolution, too.
The main reason open source projects exist at all is because of people who started them with quite often fringe ideological leanings. Just look at the GNU project.
And fringe economical leanings, too. Just look at the GNU project: the firmware in printers is still of subpar quality, and GNU didn't really help to change that... and why on Earth would it, anyway?
There's still a line between values I disagree with and values that directly attack me as a person. The former is how many of us feel about some of our dependencies and most proprietary software we use, so it's clearly fine to some degree.
I remember when people were crying about how much power a google search uses. This is the same thing all over again and it is as pointless now as it was back then.
> Google says it dropped the energy cost of AI queries by 33x in one year. The company claims that a text query now burns the equivalent of 9 seconds of TV.
No, it's entirely justified when quality of code matters. They don't want a thousand gallons of unreviewable slop. They want a reasonable amount of code that can be sensibility reviewed.
There are ways to achieve that without a blanket ban, if you read their AI policy it seems more "ethically" motivated. They certainly address this first, with many more words and 7 references.
They do go on to address code quality but it is more of an after thought with 0 references, less words and appears lower down the page.
PostmarketOS doesn't exist in a vacuum. It’s the final stage of a device's life cycle. If the initial sales of new devices decline, the pool of available hardware for enthusiasts to tinker with in five years will be significantly smaller.
Yes. In five years, once the PMOS devs manage to get a 2025 device in working state, they might have less devices to play around with, so there could be an indirect effect on the project.
What I struggle to believe - what I don't believe - is that there any sort of connection between the report about likely declining sales and PMOS' announcement.
Right now, their wiki page on device support [0] lists zero actual devices as "fully supported":
> These are the most supported devices, maintained by at least 2 people and have the functions you expect from the device running its normal OS, such as calling on a phone, working audio, and a functional UI.
> Besides QEMU devices, this is currently empty. The ports we had here earlier weren't as reliable as we would have liked. We plan to add new devices here with a higher standard.
The most recent smartphone in the Community section of that page is the Fairphone 4, released half a decade ago, in 2021. Pixel devices can trivially be bootloader unlocked, but that doesn't make the work that goes into supporting them much easier: the latest device in Testing is the 6a/6 Pro, from 2022, and its device page lists all the features but the most basic (touchscreen, flash, internal storage) as "Untested".
This is incredibly simple. If a project doesn't want machine generated code, don't force machine generated code into the project. This isn't anything here that warrants multiple paragraphs of freakout.
Agreed. I would have chosen differently, but I appreciate the policy is unambiguous and explained succinctly with references.
Some people enjoy the outcome, others enjoy the process.
I find the criticism interesting. It's like one restaurant saying they'll use only electric stoves for the climate, then chefs all over the world calling them stupid naive for it.
It's like ethical arguments rationalizing local behavior are automatically interpreted as a global attack that has to be rejected.
You say "uncompromising stance" with "justification", I say stubborn prejudice. They simply state the same weak, nonsensical complaints that apply to many other technologies that they undoubtedly don't have issues with and are happy with the use of.
reply