That polyfill is 46 Megabytes in size. This would suck so much to have this suddenly in the build.
Readit Newsahofmann commented on Should we remove XSLT from the web platform? github.com/whatwg/html/is... · Posted by u/edent
> The file is a mere 512 bytes, and unpacks to a 26kb file, which again unpacks to 3Mb.
My brain hurts when thinking about that. How could 512 bytes be enough to store ~3 million bytes? I know that compression is basically about finding patterns and this sequences should be very compressible.
ahofmann commented on Multimodal WFH setup: flight SIM, EE lab, and music studio in 60sqft/5.5M² sdo.group/study... · Posted by u/brunohaid
The contrast between all that fancy equipment and the actual work surface being a cheap-as-can-be fibreboard (that will get nasty quickly and suck up all liquids) with a more or less unfinished edge that will probably feel uncomfortable is a bit too much of the designerly touch for me...
Man, I got carpal tunnel syndrome just from looking at the edge of that fibreboard. I couldn't work at that "desk" for 20 minutes.
ahofmann commented on Linear sent me down a local-first rabbit hole bytemash.net/posts/i-went... · Posted by u/jcusch
Unless you are running some really complicated globally distributed backend your roundtrip will always be higher than 80ms for all users outside your immediate geographical area. And the techniques to "fix" this usually only mitigate the problem in read-scenarios.
The techniques Linear uses are not so much about backend performance and can be applicable for any client-server setup really. Not a JS/web specific problem.
My take is, that a performant backend gets you so much runway, that you can reduce a lot of complexity in the frontend. And yes, sometimes that means to have globally distributed databases.
But the industry is going the other way. Building frontends that try to hide slow backends and while doing that handling so much state (and visual fluff), that they get fatter and slower every day.
ahofmann commented on Linear sent me down a local-first rabbit hole bytemash.net/posts/i-went... · Posted by u/jcusch
A web request to a data center even with a very fast backend server will struggle to beat 8ms (120hz display) or even 16ms (60hz display), the budget for next frame painting a navigation. You need to have the data local to the device and ideally already in memory to hit 8ms navigation.
This is not the point, or other numbers matter more, then yours.
In 2005 we wrote entire games for browsers without any frontend framework (jQuery wasn't invented yet) and managed to generate responses in under 80 ms in PHP. Most users had their first bytes in 200 ms and it felt instant to them, because browsers are incredibly fast, when treated right.
So the Internet was indeed much faster then, as opposed to now. Just look at GitHub. They used to be fast. Now they rewrite their frontend in react and it feels sluggish and slow.
Why doesn't PHP remove the horrid $ symbol for variables and the -> symbol for calling methods? I think those alone would do a lot more for its perception and adoption than adding the pipe operator.
I honestly don't understand this. The syntax is one of the most boring parts of a programming language. It is solved by the IDE (and now LLMs). I don't care about syntax, I care about what I can build. Since the beginning of time people argue about things like tabs vs. spaces, or the dollar sign and I honestly don't understand why that is. It just doesn't matter.
Just to be clear: consistency does very much matter. The mental load of reading totally different styles of code is awful and a waste of energy.
ahofmann commented on Offline.kids – Screen-free activities for kids offline.kids/... · Posted by u/ascorbic
ahofmann commented on Offline.kids – Screen-free activities for kids offline.kids/... · Posted by u/ascorbic
ahofmann commented on Hiding secret codes in light protects against fake videos news.cornell.edu/stories/... · Posted by u/CharlesW
I think you might have misunderstood some core use cases.
One significant problem currently is long form discussions which are taken wildly out of context for the sake of propaganda, cancelling or otherwise damaging the reputation of those involved. The point isn't that a given video isn't edited originally, but that the original source video can be compared to another (whether the original was edited or not is neither here nor there).
I'm not saying this solution is the answer, but attempts to be able to prove videos were unedited from their original release is a pretty reasonable goal.
I also don't follow where the idea that viewers need to be forensic experts arises from? My understanding is that a video can be verified as authentic, at least in the sense of the way the original author intended. I didn't read that users would be responsible for this, but rather that it can be done when required.
This is particularly useful in cases like the one I highlighted above; where a video may be re-cut to make an argument the person (or people) in question never made (and which might be used to smear said persons–a common occurrence in the world of long form podcasting as an example).
While I don't know if the paper is "stupid", or not, I think nobody in the last two decades has ever seen an uncut interview. So I don't see how this light would help or proof anything.
> [This patch] fills holes in executable sections with 0xd4 (ARM) or 0xef (MIPS). These trap instructions were suggested by Theo de Raadt.
into commit messages, but not in the code. What's the cost? What's the downside to having a 2 to 3 line comment above a constant in a C file? Why pretend like all this is super obvious when clearly it isn't?
There seems to be some unwritten cultural rule, particularly in FOSS land, that you're supposed to write code as if you're an all-knowing oracle, as if everything is obvious, and so comments are for losers (as are descriptive variable names). I simply can't understand how and why that developed.