I don't care one bit if the content is interesting, useful, and accurate.
The issue with AI slop isn't with how it's written. It's the fact that it's wrong, and that the author hasn't bothered to check it. If I read a post and find that it's nonsense I can guarantee that I won't be trusting that blog again. At some point there'll become a point where my belief in the accuracy of blogs in general is undermined to the point where I shift to only bothering with bloggers I already trust. That is when blogging dies, because new bloggers will find it impossible to find an audience (assuming people think as I do, which is a big assumption to be fair.)
AI has the power to completely undo all trust people have in content that's published online, and do even more damage than advertising, reviews, and spam have already done. Guarding against that is probably worthwhile.
Even if it's right there's also the factor of: why did you use a machine to make your writing longer just to waste my time? If the output is just as good as the input, but the input is shorter, why not show me the input.
I have a simpler way of doing this. I just don't use websites that are enshittified. Trying to fix a broken site is a tedious game of cat and mouse as the devs break your fixes. Just find an alternative.
It probably isn't really using that much but it will have reserved that much. V8 reserves memory in chunks of 256MB using virtualalloc with MEM_RESERVE on Windows (I think). It has to do that for each isolated process where an isolate is a tab, webview, worker, etc. A page that's built up from 4 isolated processes will reserve 1GB of RAM. That's only virtual alloc though, so other OS processes can take the memory if they really need it.
There is essentially no way to tell if a JS app is using a lot of memory just by looking at what the process has reserved. There's loads of things that end up in that space - cached pages, cached compiled code, cached bitmaps of rendered pages, etc.
The task monitor tells you what Chrome or Chromium (e.g. Electron) is doing, not what the web app is doing.
There is a good argument to suggest Chromium is hogging more than it should. That's not really WhatsApp's fault though.
I mean, you could argue that you're at fault when you're choosing a platform that literally eats your RAM. They're not at fault that the platform is shit. But they could have chosen another platform. Or, even better, just use the existing, most of the time perfectly working app, and optimize it.
They had no resources to build the new features for every single platform that they offer native clients for?
I could not imagine any other app for which this would be more hypocritical. Give me the iOS WhatsApp IPA from 2016, or even earlier, and the Windows Chromium Wrapper from 2018, and I will tell you neither me nor probably 98% percent of users will notice any difference in feature, let alone design.
I have no doubt this could be a useful tool given the nice looking UX, but everything it does is already in Devtools.
If you open Devtools, then click "Sources", there are two options in the left panel 'Page' and 'Workspace'. Change to workspace and add the folder where your project lives. Now you can edit the code for your React (or anything else) project in Devtools and it'll save to your filesystem. You can make this a part of the project if you want to - https://chromium.googlesource.com/devtools/devtools-frontend...
Gemini is integrated into the Sources panel, so I just opened a JSX file and asked what classes I'd use in Tailwind to replace my CSS and it told me the right answer. It didn't update the code though. That 'Apply Edits' feature in jsxtool would be useful for a non-dev user.
Jesus, since when Fortnite and BF6 became gaming benchmark nowadays?
In order to 'win' a console generation there needs to be support for the games people want to play. Capitalism is a literal popularity contest, and any console that doesn't have Fortnite, COD, FIFA, etc won't win, regardless of what you or I might think of the games.
The reason why Steam can't win a console generation is simply because Microsoft, Sony, and Nintendo have enough sway over publishers (especially ones they own) than they stop popular games being available on a rival platform. They market it as 'exclusives' but really it's just anti-consumer.
That might work, but the second order effect would probably be companies trying to do the work of time synchronisation themselves in case it happened again. That would lead to fragmentation and incompatibility.
Most of the time when someone says they are in the “North East of the UK” it’s not some Scotsman up in Shetland it is an English person who is currently in the North East of England.
The North East of England is in the middle part of the UK mainland.
"Most of the time when someone says they are in the “North East of the UK” it’s not some Scotsman up in Shetland it is an English person who is currently in the North East of England."
So .. they don't see scotland as part of the UK anyway? Why was it such an issue then that they wanted to leave? (And why were there bloody wars fought about it in the first place?)
So Scotland didn’t want to leave. And Scotland didn’t unite with England until after the Scottish King took over he English throne hundreds of years after the time of William Wallace
You might be confusing the U.K. with the USA where a pet of the country there wanted to leave and were refused and that did lead to war, and that happened far more recently than 700 years ago.
Someone with a tiny little...um...axe to grind and not enough sense to take it someplace where people care. You can tell when they have to go back to Culloden to try and drag something up to wave around.
reply