In what world should the editor double check third-party quotes in an article submitted by a journalist? Do you think the Washington Post phones the White House every time an article quotes the president (ok, bad example, pretend I asked this question about a serious paper in a healthy democracy)?
There's also such a thing as journalistic confidentiality -- the editor may not even know the identity of the quoted source. That doesn't apply to this specific case but your claim was generic, and I think there's a serious misapprehension here if you think it's the editor's job to verify citations in journalists' writings.
/e/OS and Murena are the same company. Initially, they used the name /e/ everywhere, but a single letter is not searchable on the web, so they rebranded to Murena. Everything is now called Murena except the OS itself.
> as we are reaching more and more people and progressively catching interested from a mainstream audience, we have to introduce a new, strong brand, easier to use, easier to refer to and easier to share with people.
> Google pulls the plug ? cool, you're stuck on Android 17
And you're stuck on the current hardware generation. Pretty much the only reason why Android sucks less than other mobile OSes is that hardware vendors have a pressing reason to make it work. The further the Google Android kernel diverges from its last-open version, the harder it will become to backport drivers -- and that's assuming that hardware vendors even bother to comply with the GPL when Google decides not to.
It can, and has in the past, diverged from the baseline Linux kernel, but not from “the last open Android kernel” as it must remain open source per GPL.
Oh how the public opinion has been moved already. Rewriting your argument to echo the sentiment from a generation ago:
> The laws need to be updated. Having police officers monitor public streets was fine because they wouldn't actually recall anything unless there was an incident. Now it's possible to go back and review specific footage and identify everyone on those camera's -- we need new privacy laws to reflect this capability.
C doesn't have exceptions, do you mean signals? If not, I don't see how that is that any different from having to handle I/O errors from write() and/or open() calls.
It's very different since at random points of your program your signal handler is caleld asynchronously, and you can only do a very limited signal-safe things there, and the flow of control in your i/o, logic etc code has no idea it's happening.
Well at least in this case the timing won't be arbitrary. Execution will have blocked waiting on the read and you will (AFAIK) receive the signal promptly in this case. Since the code in question was doing IO that you knew could fail handling the situation can be as simple as setting a flag from within the signal handler.
I'm unclear what would happen in the event you had configured the mask to force SIGBUS to a different thread. Presumably undefined behavior.
> If multiple standard signals are pending for a process, the order in which the signals are delivered is unspecified.
That could create the mother of all edgecases if a different signal handler assumed the variable you just failed to read into was in a valid state. More fun footguns I guess.
> Since the code in question was doing IO that you knew could fail handling the situation can be as simple as setting a flag from within the signal handler.
If you are using mmap like malloc (as the article does) you don't necessarily know that you are "reading" from disk. You may have passed the disk-backed pointers to other code. The fact that malloc and mmap return the same type of values is what makes mmap in C so powerful AND so prone to issues.
Yes, and for writing (the example is read-write) it's of course yet another kettle of fish. The error might never get reported at all. Or you might get a SIGBUS (at least with sparse files).
Signals are extremely bad to work with. Would rather do error handling in javascript. It feels like trying to write low level primitives in rust or trying to learn c++. There are so many edge cases that I start questioning what am I doing with my life
China has been competing with India for decades for the most-polluted cities crown, and only slightly ranks below the US and Russia in CO2 emissions per capita. It's also the only large country where its emissions have been growing over the last decade. Where does the idea come from that China somehow puts less pressure on the environment? Less than what, exactly?
By slightly ranks below you mean ~50-60% per capital.
>China somehow puts less pressure on the environment
PRC renewables at staggering scale.
Last year PRC brrrted out enough solar panels whose lifetime output is equivalent to MORE than annual global consumption of oil. AKA world uses about >40billion barrels of oil per year, PRC's annual solar production will sink about 40billion barrels of oil of emissions in their life times. That's fucking obscene amount of carbon sink, and frankly at full productionm annual PRC solar + wind can on paper displace 100% of oil, 100% of lng, and good % of coal (again annual utilization) once storage figured out.
This BTW functionally makes PRC emission negative, by massive margin, arguably the only country who is.
It's only retarded emission accounting rules that says PRC should be penalized for manufacturing renewables, but buyers credited AND fossil producers like US not penalized for extraction, which US has only increased.
Also, unlike US and Russia, China has green transition as an official policy. There are additional savings from total electrification. (I think they also care more about longterm and being closer to the equator and the sea, they better understand the consequences of global warming.)
Naming a fantasy creature after a common gemstone should make it non-trademarkable anyway, but I'd love to see Nintendo tie up the US government in court for years.
No. You seem to be implicitly arguing that that unsigned apps are inherently less trustworthy than PlayStore apps. That's a claim that needs to be proven first. And based on the huge amount of documented data exfiltration performed by Google-approved apps, I'm going to say that claim is false.
I'm arguing that a curation process that includes security review is likely to produce a more secure set of software. Admittedly it might be completely ineffective, but I think that's an unreasonable assumption. So some review is more secure than no review. Now I'm not saying "better", you could argue it's a false sense of security, but it's still more security.
> I'm arguing that a curation process that includes security review is likely to produce a more secure set of software
I actually totally agree! There is no external entity users can rely on to make sure apps they download are legitimate. I read the thread from root to this comment and I don't see it mentioned, so I'm not sure if you know this and are just arguing something else but...
There is actually nothing about testing or verifying apps themselves in the announcement made by Google. It's just about enforcing developer verification in some Google service and "registering the apps".
EDIT: I checked your profile, and I now see that you actually work at Google, on Android... Is there something I misunderstood about these announcements?
> you could argue it's a false sense of security, but it's still more security
Well here I don't agree, I would much rather be aware of the dangers than think I'm safe when I'm actually not.
In what world should the editor double check third-party quotes in an article submitted by a journalist? Do you think the Washington Post phones the White House every time an article quotes the president (ok, bad example, pretend I asked this question about a serious paper in a healthy democracy)?
There's also such a thing as journalistic confidentiality -- the editor may not even know the identity of the quoted source. That doesn't apply to this specific case but your claim was generic, and I think there's a serious misapprehension here if you think it's the editor's job to verify citations in journalists' writings.
reply