20,850 karma · joined June 1, 2018
.WebGL-0x15bc15784800] GL_INVALID_OPERATION: glRenderbufferStorageMultisample: Texture total allocation size is too large.
play/:1 [.WebGL-0x15bc15784800] GL_INVALID_FRAMEBUFFER_OPERATION: glClear: Framebuffer is incomplete: Attachment has zero size.
play/:1 [.WebGL-0x15bc15784800] GL_INVALID_FRAMEBUFFER_OPERATION: glDrawArraysInstanced: Framebuffer is incomplete: Attachment has zero size.
228[.WebGL-0x15bc15784800] GL_INVALID_FRAMEBUFFER_OPERATION: glDrawElementsInstanced: Framebuffer is incomplete: Attachment has zero size.
11[.WebGL-0x15bc15784800] GL_INVALID_FRAMEBUFFER_OPERATION: glDrawElements: Framebuffer is incomplete: Attachment has zero size.
10[.WebGL-0x15bc15784800] GL_INVALID_FRAMEBUFFER_OPERATION: glDrawArrays: Framebuffer is incomplete: Attachment has zero size.
play/:1 [.WebGL-0x15bc15784800] GL_INVALID_FRAMEBUFFER_OPERATION: glDrawArraysInstanced: Framebuffer is incomplete: Attachment has zero size.
play/:1 [.WebGL-0x15bc15784800] GL_INVALID_FRAMEBUFFER_OPERATION: glBlitFramebuffer: Framebuffer is incomplete: Attachment has zero size.
play/:1 [.WebGL-0x15bc15784800] GL_INVALID_FRAMEBUFFER_OPERATION: glClear: Framebuffer is incomplete: Attachment has zero size.
play/:1 [.WebGL-0x15bc15784800] GL_INVALID_FRAMEBUFFER_OPERATION: glDrawArraysInstanced: Framebuffer is incomplete: Attachment has zero size.
play/:1 WebGL: too many errors, no more errors will be reported to the console for this context.Mostly confused for what exactly this thing that made the front page for me is about!
It's easy to be outraged about everything, it's hard for everyone to do everything right 100% of the time for use cases most have never even heard of.
(I don't work at Apple).
I've been maintaining my patcheset to it for 5 years as one dude who's $dayjob is not coding. It just got a lot easier with LLMs recently as well. And of course companies have been carrying larger much larger changesets than I have been for many years.
Hell, even Firefox has multiple forks which deviated to keep old engines/UIs/features for many years and it has a tiny market share/little to no 3rd party company backed spins in comparison.
But it seems like you don't have much interest in all of this, just repeating that an upstream source is involved therefore you believe there can be no differences worth noting or discussing. Your loss, not the title's.
Not that it's exactly a shock they don't care about XSLT either (how many do these does) but carrying a patch set for different functionality against upstream is something individual users on HN (including myself) do when they like, let alone entire companies shipping browser products.
I doubt the author really expected/intended any other result to be reasonable, it's just an excuse to create fake shock for social media "humor"/"makes you think" type sharing one would expect of an X post.
There was a REALLY annoying period where I'd give it full control of a VM and a dedicated project folder and it'd continually refuse to delete anything I asked it to or just silently archive it, even though everything was already in a git repo. It seems to have gotten somewhat better about that now, but I still include "create cleanup scripts to delete unnecessary project content" in the default steps before doing the final merge on a change.
> For functionality and compatibility reasons, Microsoft Edge adopts nearly all of the Chromium project's changes to the web platform. However, Microsoft retains full control of the Microsoft Edge browser and may defer or reject changes.
Removed features don't always follow the same timelines either (and not just because of a lag in syncing to upstream Chromium).
LPG, no - the pressures are much lower (but also still pumped in and significantly reactive).
The moral of my personal story in this context is probably somewhere near the intersection of "not all cancers are the same", "you can always find an anecdote which suggests something", and "luck is a factor in life".
If I were to go through it again I'd still probably get a second opinion and go to a better place even if it was a straightforward type though because why not if it's covered the same in the end.
That's completely orthogonal to whether you can still find tasks which require more accuracy or not (except for the sole case someone claims it's 100%).
Maybe the next time I spend some tokens on it I'll ask for it to convert the implementation to a "proper" runtime rip where the user can provide the source ROM and it extracts those assets live.
Last weekend I had it decompile the "Kitten Cannon" Flash game and then ran (what I believe was) an exhaustive check of the 36 trillion reachable launch+power+rng combinations to see what the longest run was (I got a little over 11k feet, successfully replayed in the Flash version).
It's so cool to see modifications/enhancements to nostalgic things appear for next to no effort as much as I want rather than be limited by the time I have for it.
I've been at a company that went through Chapter 11 and still work with (at the new place) a few folks hired during that time.
The thing to note here isn't supposed to be that 1.5 TB/s is record breaking/astounding though, even the consumer 5090 GPU has higher bandwidth than that, it's just capacity@bandwidth is what defines the usefulness of an AI accelerator and this is good on both sides instead of just one. I.e. there are a lot of "cheap" low-capacity@high-bandwidth devices and a lot of "cheap" high-capacity@low-bandwidth devices. What makes this accelerator interesting is not that it has 480 GB of LPDDR5X, it's that it has 480 GB of LPDDR5X at a speed worth having that much for, which has normally been the realm of the likes of Nvidia/AMD and their AI/DC options.