333 karma · joined May 26, 2025
The data seems to suggest it.
Anecdotally, I'm seeing a lot of green accounts posting nonsense. They generally do get flagged or moderated quickly though, so I wouldn't say they have a large effect overall, at least yet.
I tried using a bunch of zoom on my most frequented sites and they mostly worked just fine. At my day job everything is tested to work at 200% zoom as a baseline.
I really don't think we should bend over backwards to cater to accessibility offenders such as LinkedIn.
An example of where I think the paradox would apply might be one where LLMs made software engineers more efficient yet the demand for SWEs would grow.
What I believe also influenced the shift was that at that point in time MS had accumulated a decent amount of developer trust by giving us TypeScript and later on by acquiring GitHub. They appeared to care and have the right vision for open source.
Will that really work? You interacted with the end product, but you don't have the experience and learned lessons that those people had. Are you sure this isn't the LLM reinforcing false confidence? Is the AI providing you with the real thing or a cheap imitation and how can you tell?
As you said, reading this stuff is taxing. What's more, this is a daily occurrence by now. If there's a silver lining, it's that the LLM smells are so obvious at the moment; I can close the tab as soon as I notice one.
This post resonates strongly with me. I strongly believe the default settings _are_ too high, and it takes conscious effort to slow down while bound to the shackles of modern society, but it's so worth it.
That's a weird thing to end on. Surely it's worth more than one sentence if you're serious about it? As it stands, it feels a bit like the fearmongering Big Tech CEOs use to drive up the AI stocks.
If AI is really that powerful and I should care about it, I'd rather hear about it without the scare tactics.
At slow, manageable tempos, you can afford to use motions that don't scale to fast tempos. If you only ever play "what you can manage" with meticulous, tiny BPM increments, you'll never have to take the leap of faith and most likely will hit a wall, never getting past like 120-130 BPM 16ths comfortably. Don't ask how I know this.
What got me past that point was short bursts at BPMs way past my comfort zone and building synchrony _after_ I stumbled upon more efficient motions that scaled. IIRC, this is what Shawn Lane advocated as well.
I recommend checking out Troy Grady's (Cracking The Code) videos on YouTube if you're interested in guitar speed picking. Troy's content has cleared up many myths with an evidence-based approach and helped me get past the invisible wall. He recently uploaded a video pertaining to this very topic[0].
https://cadence.moe/blog/2024-10-05-created-by-a-human-badge...
I just wish I had an addon like this for, well, everything. The browser is such a great platform because you can have this much control over your experience--no such luck with mobile apps.
This PR to Bluesky has more recent discussion about it and offers workarounds:
`<dialog>` only got full compatibility with Firefox about two months ago with Firefox 141. Safari still doesn't support `closedby`.
Given that, I still regard `<dialog>` as experimental, and that'll remain the case as long as the "Baseline Widely available" label comes with an asterisk.
[1]: https://opensource.google/documentation/reference/using/agpl...
LLMs are really valuable for finding information that you aren't able to formulate a proper search query for.
To get the most out of them, ask them to point you to reliable sources instead of explaining directly. Even then, it pays to be very critical of where they're leading you to. To make an LLM the primary window through which you seek new information is extremely precarious epistemologically. Personally, I'd use it as a last resort.
> The package managers we benchmarked weren't built wrong, they were solutions designed for the constraints of their time.
> Buns approach wasn't revolutionary, it was just willing to look at what actually slows things down today.
> Installing packages 25x faster isn't "magic": it's what happens when tools are built for the hardware we actually have.
As I understand it, the main point of semantic web is making the web machine readable, often using languages specifically designed for that task that are not HTML.
Semantic HTML is more concerned with writing standardized HTML that leverages browser capabilities and respects users who use assistive technology to browse the web.
Frankly, I don't see what this framework has to do with either. I was curious about how they implemented the dropdown menus, and they're specially styled <details> elements, which are normally used for accordions. That seems a bit strange to me, because the obvious choice for a dropdown is the <select> element.