Maybe, but I would argue that some of these features are genuinely useful and important. Take translation, for example. It's not great to have to send off a page that potentially contains identifying content to Google, but it is the easiest way to handle the matter. Firefox uses local AI to perform a decent translation relatively quickly, and I'd like them to work on improving that capability.
Agreed on all counts. Right now there's not even a keyboard shortcut implemented (fiddly context menu only), and the translations are sometimes dodgy too, but I still use it. It's such peace of mind to know that the translation is happening entirely locally.
"JPEG XL" is a little bit of a misnomer as it's not just "JPEG with more bits". It supports lossless encoding of existing content at a smaller file size than PNG and allows you to transcode existing JPEGs recoverably for a 20% space savings, the lossy encoding doesn't look nearly as ugly and artifacted as JPEG, it supports wide gamut and HDR, and delivers images progressively so you get a decent preview with as little as 15% of the image loaded with no additional client-side effort (from https://jpegxl.info/).
It is at least a very good transcoding target for the web, but it genuinely replaces many other formats in a way where the original source file can more or less be regenerated.
Honestly, I don't like how webp and now jpegxl support both a lossless and lossy mode.
Let's say you want to store images lossless. This means you won't tolerate loss of data. Which means you don't want to risk it by using a codec that will compress the image lossy if you forget to enable a setting.
With PNG there is no way to accidentally make it lossy, which feels a lot safer for cases you want lossless compression.
You can use too few bits of color depth to get lossyness in PNG. More generally, I can't find myself very sympathetic to "I don't want a format that can do X and Y, because I might accidentally select X when I want Y in my software". You might accidentally choose JPG when you want PNG too. Or accidentally resample the image. Or delete your files.
If you want a robust lossless workflow, PNG isn't the answer. Automating the fiddly parts and validating that the automation does what you want is the answer.
PNG can and is often used in a lossy way. Reducing the number of colors so PNG8 can be used instead of PNG24/PNG32 is the most common way to do that. Tools like pngquant exist, and for example Photoshop when exporting to PNG also has an option to reduce the colors, to flatten the image (remove alpha), or to change the colorspace.
16-bit PNG files can easily accidentally be reduced to 8-bit, which is of course a lossy operation. Animated PNG files can easily get converted into a still image (keeping only the first frame). CMYK images will have to be converted to RGB when saving them as PNG, which is also a lossy operation. It can happen that an image gets created as or converted to JPEG and then gets saved as PNG - which of course is a bad and lossy workflow, but it does happen.
So I don't agree that with PNG there is no way to accidentally make it lossy.
In any case: lossless or lossy is not a property of a format, but of a workflow. For keeping track of provenance information and workflow history, I would recommend looking into JPEG Trust / C2PA, which is a way to embed as metadata what happened to an image since it was captured/generated. Relying on the choice of image format for this is fragile and doesn't allow expressing the nuances, since reality is more complicated than just a binary "lossless or lossy".
> Specifically for JPEG files, the default cjxl behavior is to apply lossless
recompression and the default djxl behavior is to reconstruct the original
JPEG file (when the extension of the output file is .jpg).
You're right, however, that you do need to be careful and use the reference codec package for this, as tools like ImageMagick create loss during the decoding of the JPEG into pixels (https://github.com/ImageMagick/ImageMagick/discussions/6046) and ImageMagick sets quality to 92 by default. But perhaps that's something we can change.
> 8.10. the legal defense of financial and violent crimes, including those related to money laundering, murder, robbery, assault, battery, sex crimes or crimes against minors;
And as per the article,
> On Sunday night, Emmons’ fundraiser stated that “funds will go to help pay for any legal services this officer needs.” That language was removed after WIRED’s inquiry and replaced by Monday morning with the phrase, “Funds will go to help him.”
The rules aren't so specific as to say whether or not they have to have been formally charged, just that GoFundMe has historically only taken action once there are formal charges. And that's interesting in this scenario, because
> Local prosecutors claimed that without access to the FBI’s case file, it may be impossible for the state to assess whether charges are warranted
No matter what decision they make, it will appear political.
OP is not looking to get people fired for using particular words. OP doesn't appear to be fighting any sort of political battle. OP is telling people to be nice, and that's as much his right as it is yours to use the wrong words.
And I don't think elections or "the culture" should have anything to do with it. If that's how we made every decision, life would only improve for whoever exists in the overall majority. What if we each chose to have some integrity and do the right thing, even when there's nothing measuring it? It wouldn't kill us, I don't think.
That's only true of people who overreact or use offense as an excuse to let off some righteous anger. Most people don't react that way, even if that is what you'll most often see surfaced on social media because it's the most exciting and engaging sort of reaction. Most people will just tell you it's not a good thing to say and let you quietly reflect on it, or just exit the conversation.
tbh politely saying it bothers you is totally fine. That's not my argument.
All I'm saying is that making it your personal mission to make sure nobody uses the words in any context has lead us to where we are now, where we have a big backlash and young people are using gay and retarded more than they ever would have if we maybe just chilled out a little bit with the language policing.
We have taken this magic word mindset so far that we created a broad set of words that were so taboo you could get fired for using them in ANY context, even if you are talking about the word itself (like the case with the Papa Johns guy). And we had institutions like Stanford coming up with inane things like the "Elimination of Harmful Language Initiative" where they wanted to police words like "crazy" and "dumb".
Instead of making a fuss, have you considered taking another look at the video page? It includes a summary that helps show why those technical facts are actually relevant in the context of German society, and hints at how those things came to happen. I would normally not bother with a comment, but this time I'm genuinely curious as to how someone might have missed scrolling down to see the summary.
(edit: the fussy bit, where the poster complains about downvotes, has been edited out. I'm leaving my comment the way it is.)
> I'm genuinely curious as to how someone might have missed scrolling down to see the summary.
Pretty simple. On my laptop the video fits 100% in the browser tab and there is no indication that there is more content under it. There is no text except the video title in the portion that I see when the page loads. And the link is marked [video] on HN.
It's not nice, and in fact really quite rude, to complain about people trying to make something more accessible. You don't have to be nice and help, but complaining about it is definitely not nice.
I do agree this is where AI shines. If you need a quick rehash of something that's been done a zillion times before or a quick integration between two known good components, AI's great.
But the skills you describe are still skills, reading and researching and doing your own fact finding are still important to practice and be good at. Those things only get more important in situations off the beaten path, where AI doesn't always give you trustworthy answers or do trustworthy work.
I'm still going to nurture some of these skills. If I'm trying to learn, I'll stick to using AI only when I'm truly stuck or no longer having fun.
reply