I want to love this, but the "just install it globally, what could go wrong?" is simply not happening for an AI-written codebase. Open Source was never truly "you can trust it because everyone can vet it", so you had to do your due diligence. Now with AI code bases, that's "it might be open source, but no one actually knows how it works and only other AIs can check if it's safe because no one can read the code". Who's getting the data? No idea. How would you find out? I guess you can wireshark your network? This is not a great feeling.
A GPU's job is to take inputs at some resolution, transform it, and then output it at that resolution. H.264/H.265 (and really, any playback format) needs a fundamentally different workflow: it needs to take as many frames as your framerate is set to, store the first frame as a full frame, and then store N-1 diffs, only describing which pixels changed between each successive frame. Something GPUs are terrible at. You could certainly use the GPU to calculate the full frame diff, but then you still need to send it back to the CPU or dedicated encoding hardware that turns that into an actual concise diff description. At that point, you might as well make the CPU or hardware encoder do the whole job, you're just not saving any appreciable time by sending the data over to the GPU first, just to get it back in a way where you're still going over every pixel afterwards.
But then you go "hang on, doesn't ESM exist?" and you realize that argument 4 isn't even true. You can literally do what this argument says you can't, by creating a blob instead of "writing a temp file" and then importing that using the same dynamic import we've had available since <checks his watch> 2020.
A virtual filesystem makes it possible for the ESM you import to statically import other files in the virtual filesystem, which isn't possible by just dynamically importing a blob. Anything your blob module imports has to be updated to dynamically import its dependencies via blobs.
GFM, because HTML in markdown should not be a parse error, and getting twenty different markdown "specs" to all agree on new syntax for bits they are obviously missing (like details, classed scoping, transclusions, etc) is not happening.
Except under GFM, html is explicitly part of the spec[1], not just "it's not a parse error, but that's because it's just text that doesn't fall in any predefined markdown syntax category", and good luck finding a WYSIWYG markdown editor that gets them right. The number of editors that completely break on <details> alone is disheartening.
labelled "high priority" a month ago. No actual activity by Anthropic despite it being their repo. I'm starting to get the feeling they're not actually very good at this?
Surely this also requires reporting DJI to the authorities for gross negligence? This is not an oopsie, this is deploying a surveillance network without telling anyone.
Every single one relevant to where you live? If you're in the US, the US. "Good fucking luck and lol" and all that, but do it anyway. In the EU? Your country has agencies for this, as does the EU as a whole. Perform your civic duties, they still count in the EU.
Somewhere else? I don't know man, the author sure seems to live in either of those two regions.
You know where to report things if you live on Earth and use the internet.
This is a DJI company? Ouch. [edit] ah it is right in the title of the og article. Wow. Just wow. In China we just use a broom, so maybe it is an oversight (aka no one uses this overprices crap)
"Facebook is just clickbait slop and is making billions" is more the opposite of cooked. They managed to turn garbage into dollars, and people are eating it up for as long as they're allowed to do exploit their market position.
This document makes the mistake of thinking the LLMs (a) have any sort of memory and (b) care. They will violate llm instructions not 2 prompts after being given them because the weights simply generated results.
reply