kevingadd

It's not a huge conspiracy, but it is worthwhile to consider what the incentives are for people from each browser vendor. In practice all the vendors probably have big backlogs of work they are struggling to keep up with. The backlogs are accumulating in part because of the breakneck pace at which new APIs and features are added to the web platform, and in part because of the unending torrent of new security vulnerabilities being discovered in existing parts of the platform. Anything that reduces the backlog is thus really appealing, and money doesn't have to change hands.

Arguably, we could lighten the load on all three teams (especially the under-resourced Firefox and Safari teams) by slowing the pace of new APIs and platform features. This would also ease development of browsers by new teams, like Servo or Ladybird. But this seems to be an unpopular stance because people really (for good reason) want the web platform to have every pet feature they're an advocate for. Most people don't have the perspective necessary to see why a slower pace may be necessary.

Yes. That is exactly how web standards work historically. If something will break 0.1% of the web it isn't done unless there are really really strong reasons to do it anyway. I personally watched lots of things get bounced due to their impact on a very small % of all websites.

This is part of why web standards processes need to be very conservative about what's added to the web, and part of why a small vocal contingent of web people are angry that Google keeps adding all sorts of weird stuff to the platform. Useful weird stuff, but regardless.

Former Mozilla and Google (Chrome team specifically) dev here. The way I see what you're saying is: Representatives from Chrome/Blink, Safari/Webkit, and Firefox/Gecko are all supportive of removing XSLT from the web platform, regardless of whether it's still being used. It's okay because someone from Mozilla brought it up.

Out of those three projects, two are notoriously under-resourced, and one is notorious for constantly ramming through new features at a pace the other two projects can't or won't keep up with.

Why wouldn't the overworked/underresourced Safari and Firefox people want an excuse to have less work to do?

This appeal to authority doesn't hold water for me because the important question is not 'do people with specific priorities think this is a good idea' but instead 'will this idea negatively impact the web platform and its billions of users'. Out of those billions of users it's quite possible a sizable number of them rely on XSLT, and in my reading around this issue I haven't seen concrete data supporting that nobody uses XSLT. If nobody really used it there wouldn't be a need for that polyfill.

Fundamentally the question that should be asked here is: Billions of people use the web every day, which means they're relying on technologies like HTML, CSS, XML, XSLT, etc. Are we okay with breaking something that 0.1% of users rely on? If we are, okay, but who's going to tell that 0.1% of a billion people that they don't matter?

The argument I've seen made is that Google doesn't have the resources (somehow) to maintain XSLT support. One of the googlers argued that new emerging web APIs are more popular, and thus more deserving of resources. So what we've created is a zero-sum game where any new feature added to the platform requires the removal of an existing feature. Where does that game end? Will we eventually remove ARIA and/or screen reader support because it's not used by enough people?

I think all three browser vendors have a duty to their users to support them to the best of their ability, and Google has the financial and human resources to support users of XSLT and is choosing not to.

They want to punt a half-baked polyfill over the wall and remove support from the browser so they don't have to do any maintenance work, making it someone else's problem.

At the time I ran across lots of real websites using it. I successfully used it myself at least once too. Off the top of my head, Blizzard was using it to format WoW player profiles for display in the browser.

If we really want to increase turnout, we can just make voting mandatory like other countries have.

Requiring ID is a problem given that a lot of people don't have easy access (or access at all) to legal ID, for various reasons, some as simple as cost. Having a license costs money on an ongoing basis and you need to have access to documents to prove your identity like a birth certificate, and some citizens don't have those through no fault of their own, like losing everything in a fire or even the relevant records agency itself burning down. Thankfully there are often fee waivers for hardship but there are certainly corner cases where saying 'if you want to vote you need ID' is basically a poll tax, something we rightfully banned in the US a long time ago.

I checked the original tweet to try and understand this better and what appears to have happened is that Otter kept recording after he left and the VCs stayed on the call chatting (for hours, according to the tweet). This violates the assumption baked into the recording agent (all participants of the call have a right to a transcript of the whole call) by repurposing a scheduled meeting into a party line/just chatting sort of situation.

You could fix this by training people not to use booked meetings this way but I'm not sure how realistic that is to do. I think it might be that services like Otter need to be adjusted to take into account that not every part of a meeting is of equal sensitivity.

i.e. my HOA's monthly meetings have a private period for the board only and a public period for all residents. If Otter were used in this configuration, it would broadcast the exact details of those private discussions to the whole building, which might include board members discussing details that shouldn't be shared with everyone.

One potential virtuous cycle here is that accessibility trees used by tools like screen readers are also a nice potential way for a model to consume information about what's on screen and how it can be interacted with. So it creates an additional incentive for improving the accessibility of new and existing software, because doing that lights up integration with future models.

Quoting the start of the paper:

> While MCGs and LCGs have some known defects, they can be used in combination with other pseudorandom number generators (PRNGs) or passed through some output function that might lessen such defects. Due to their speed and simplicity, as well as a substantial accrued body of mathematical analysis, they have been for a long time the PRNGs of choice in programming languages.

EDIT: And going further, they call out Marsaglia's work in particular, it seems.

> Since the 1980s, parents have grown more and more afraid that unsupervised time will expose their kids to physical or emotional harm. In another recent Harris Poll, we asked parents what they thought would happen if two 10-year-olds played in a local park without adults around. Sixty percent thought the children would likely get injured. Half thought they would likely get abducted.

> These intuitions don’t even begin to resemble reality. According to Warwick Cairns, the author of How to Live Dangerously, kidnapping in the United States is so rare that a child would have to be outside unsupervised for, on average, 750,000 years before being snatched by a stranger.

I wonder how we ended up in a situation where people think Stranger Danger is this bad. Is it just from TV and the internet inflating the danger to drive views/clicks?

In many areas crime has been trending down but people seem to think things are more dangerous than ever, in general. It baffles me.

Just to be clear you're literally repeating a conspiracy theory. The thing you described effectively does not happen. We can talk about whether it should be allowed to happen, but at present it doesn't. Policies followed by most medical professionals simply don't allow it.

Where I live in Seattle we fund keeping the streets in good condition. I see city staff roaming around during the day from time to time wearing hi-vis, doing stuff like picking up trash or removing graffiti.

If trash is lying around only getting picked up by generous citizens in their spare time, what that implies is that the city/county have chosen not to invest in maintaining the streets, and the citizens have elected to throw trash everywhere. I don't think we should take either of those conditions as a given. Better things are possible.

I see white on dark purple at a perfectly legible size using a regular font. Did an extension you have installed block loading of an image or style sheet?

Had to buy an IPv4 address for a VPS the other day in order to clone some git repositories. Couldn't believe it. Costing their customers money when they should be able to support v6 by now.

Can't you already do this by creating a tree of invisible DOM elements with the right ARIA attributes?

> In a judgment that spanned 2000 pages, Australian Federal Court Justice Jonathan Beach, ruled that Apple had a substantial degree of market power. The Judge said both Apple and Google had breached Section 46 of Australia’s Competition Act. The companies had abused their market power to stifle the competition. But, it wasn't all in favor of Epic Games. Beach rejected the claim that Apple and Google had breached consumer law, he also said that the companies had not engaged in unconscionable conduct.

2000 pages! I can see why the case took something like 5 years.

It sounds like a mixed ruling so Epic didn't get everything they wanted here, but if they're able to launch the Epic Games Store on iOS in Australia that's a pretty big win by itself.

Typically when a human has a disorder or limitation they adapt to it by developing coping strategies or making use of tools and environmental changes to compensate. Maybe they expect a true reasoning model to be able to do the same thing?

Almost every mention I've seen of gpt-oss was a complaint that the training on synthetic datasets produced a model that's mostly good at benchmarks. Are benchmarks the great results you're referring to or are there a lot of satisfied users out there that just don't post here on HN? Genuinely curious.

I can see how performing well on benchmarks at the expense of everything else counts as great results if that's the point of the model.

Replies seem to be arguing that this wasn't a 51% attack and was something else. I don't know crypto well enough to verify their claims, though.

The country's money is his money. For example: That plane that got 'gifted' to him is getting expensive retrofits on the taxpayer's dime, and he gets to keep the plane after he leaves office.

https://www.nytimes.com/2025/07/27/us/politics/air-force-one...

Part of the complexity here is the temporary object allocation and the need to read properties out of it as you iterate. This is one of the things I tried to push back on but the spec people were in a hard spot, since JS doesn't have native multiple return values. I think in ideal circumstances the allocation can be optimized out by doing store-to-load forwarding on the properties, but in cases like the post here since inlining can't happen, no such luck. :(

Depending on where you work they might not let you publish a paper about it. Certainly was the case at one game studio I worked for, very secretive.

If you're using a portable library that needs to render graphics on mac, it's probably using OpenGL to do it unless it has a platform-specific backend.

This article feels like it generalizes quite a lot about a very, very large population. I'm always wary of pieces that try to put the vast majority of people from a given territory into some broad buckets in order to draw conclusions about them. There are a grand total of two citations in the whole thing unless I missed some, and they're not supporting most of the generalities.

> Much of East Asian culture is rooted in the teachings of Confucius.

Really?

Interesting topic at the very least. Any time there's a big population disparity in selective groups it's usually worth investigating how that disparity came to be to see if we can learn something from it and potentially equalize it (if it exists for a bad reason).

It usually happens by accident. For example, let's say you have a class Person with two data members named firstName and lastName. We're already in trouble, but let's make it worse: It has a getter named fullName which returns $`{this.firstName} {this.lastName}`.

That getter looks inoffensive and will, depending on your requirements, work just fine. But it has side effects because the string interpolation allocates and could trigger a garbage collection.

Note that if you're using modern JS 'class' blocks a 'get x ()' will be ignored by JSON.stringify, so if you're aiming to reproduce this you have to use old-school Object.defineProperty instead.

Calling a property getter can have side effects, so if you serialize an object with a getter you have to be very cautious to make sure nothing weird happens underneath you during serialization.

People have exploited this sort of side effect to get bug bounties before via type confusion attacks, iirc.

I agree that it is probably occurring at multiple points in the pipeline. We recently observed one attempt at fixing this earlier in the pipeline (affirmative action at universities) being struck down, though - perhaps for good reason. So it seems like it's not allowed to fix it at the university level, and it's not FAANG's job to fix it in their hiring pipeline, so whose job is it to fix it? Elementary school teachers?

My instinct is that it has to be addressed broadly across all stages of the pipeline for there to be any results.

I would expect you can only transmit so fast in morse code given the need for the dots and dashes to be clearly distinguished from each other and identifiable by the recipient.

Of course, if you know both ends are computers you can just transmit in some other encoding at a much higher rate.

The fundamental question is whether you think the population distribution of a company with thousands (or tens of thousands) of employees should look similar to the population distribution of the countries it's based in.

If the distribution doesn't look similar, why not? Is there a good excuse for being predominantly male, or predominantly white, or predominantly asian, or predominantly indian? What does that good excuse look like? I see people complain about these things all the time.

There's an assumption here that discrimination in the workplace only exists because of DEI which is a weird leap to make IMO. You could argue that DEI made the situation worse and that gets us somewhere but it's not clear to me whether that's your position.