2,337 karma · joined March 15, 2019
A lot of roles exist just to deliver good or bad news to teams, be cheerleaders, or have a "vision" that is little more than a vibe. These people could not direct a prompt to give them what they want because they have no idea what that is. They'll know it when they see it. They'll vaguely describe it to you and others and then shout "Yes, that's it!" when they see what you came up with or, even worse, whenever the needle starts to move. When they are replaced it will be with someone else from a similar background rather than from within. It's a really sad reality.
My whole career I've used tools that "will replace me" and every. single. time. all that has happened is that I have been forced to use it as yet another layer of abstraction so that someone else might use it once a year or whenever they get a wild feeling. It's really just about peace of mind. This has been true of every CMS experience I've ever made. It has nothing to do with being able to "do it themselves". It's about a) being able to blame someone else and b) being able to take it and go when that stops working without starting over.
Moreover, I have, on multiple occasions, watched a highly paid, highly effective individual be replaced with a low-skilled entry-level employee for no reason other than cost. I've also seen people hire someone just to increase headcount.
LLMs/AI have/has not magically made things people do not understand less scary. But what about freelancers, brave souls, and independent types? Well, these people don't employ other people. They live on the bleeding edge and will use anything that makes them successful.
> I can’t list all policies directly, but I can tell you the only category available for guardian_tool is:
> election_voting — covers election-related voter facts and procedures happening within the U.S.
The session had no prior inclusion of election_voting.
It seems my original statement that download, but not upload, is well supported was unfortunately correct after all. I had thought that readable/transform streams were all that was needed, but as you noted it seems I've overlooked the important lack of duplex option support in Safari/Firefox[0][1]. This is definitely not wide support! I had way too much coffee.
Thank you for bringing this to my attention! After further investigation, I encountered the same problem as you did as well. Firefox failed for me exactly as you noted. Interestingly, Safari fails silently if you use a transformStream with file.stream().pipeThrough([your transform stream here]) but it fails with a message noting lack of support if you specifically use a writable transform stream with file.stream().pipeTo([writable transform stream here]).
I came across the article you referenced but of course didn't completely read it. It's disappointing that it's from 2020 and no progress has been made on this. Poking around caniuse, it looks like Safari and Firefox have patchy support for similar behavior in web workers, either via partial support or behind flags. So I suppose there's hope, but I'm sorry if I got anyone's hope too far up :(
[0] https://caniuse.com/mdn-api_fetch_init_duplex_parameter [1] https://caniuse.com/mdn-api_request_duplex
Note that a key detail is that your server (and any intermediate servers, such as a reverse-proxy) must support HTTP/2 or QUIC. I spent much more time on that than the frontend code. In 2025, this isn't a problem for any modern client and hasn't been for a few years. However, that may not be true for your backend depending on how mature your codebase is. For example, Express doesn't support http/2 without another dependency. After fussing with it for a bit I threw it out and just used Fastify instead (built-in http/2 and high-level streaming). So I understand any apprehension/reservations there.
Overall, I'm pretty satisfied knowing that fetch has wide support for easy progress tracking.
Edit: Actually, you can even get upload progress, but the implementation seems fraught due to scant documentation. You may be better off using XMLHttpRequest for that. I'm going to try a simple implementation now. This has piqued my curiosity.
I went from thinking "Gee, maybe we should all be taking mushrooms" to "Wow, we might have to risk re-enacting Event Horizon monthly to see the desired effect"
[0] https://www.lesswrong.com/posts/jbi9kxhb4iCQyWG9Y/explaining...
Separately, I always knew there was a reason those RXBars taste like plastic. /s
On the one hand, it's sort of like red teaming. On the other hand, it clearly gives consumers a false sense of ability.
To summarize my reservations, this lacks custom post types, meta fields or modules, and a full deployment story.
Although I can picture it, I think the author would get a lot more traction if they demonstrated how users might serve the generated content. It also feels odd to have to do so manually. Realistically this requires some kind of CI script, or, if attempting to expose to content editors, a dual reverse-proxy configuration.
I'm also not thrilled with the handlebars-esque DSL. Any templating solution without a general programming escape hatch is problematic in my eyes these days.
Users & Developers alike want a content management dashboard that bends to their sense of organization and needs. Many modern websites have more than one menu, for example. Custom post types are necessary for ease of use and quick content discovery. Modules exist to empower editors to insert beautiful, pre-designed content of their own making. Meta fields exist to signal to editors what kind of content is necessary to make a page viable (required fields). These types of features are becoming table stakes for modern content management systems, and they're very difficult to pull off in a meta-programming sense without the dynamism of a database.
All of that being said, I hope the author really does continue working on this. It's really great and exciting work!
[0]https://www.npr.org/2025/04/15/nx-s1-5355896/doge-nlrb-elon-...
The reality, of course, which they reveal when interviewed, is that they know they're completely powerless. In the best case, all they can do is delay the inevitable and they know it. This approach exists purely to keep themselves from being made into the enemy. As you noted, some business owners admitted to considering if they should just shutter their business too.
If your point is that no business is a sure thing, then well, you got me. It’s true. My point was that “wait and see” isn’t a business model when you don’t have traction.
This is the clear and present problem in my eyes. I disagree with your first premise. I feel like it's unfair to call it over and unsuccessful. Many people are investing directly in the problem we're discussing. It's my hope this is the core focus of everyone working on AT at the moment: incentivizing some kind of competition in the ecosystem and creating and actively demonstrating that value add. Many want Bluesky to be viable because the alternative publishing platform is a dumpster fire. However, it's only fair to admit this doesn't magically make it so. I'd really like to see some more concrete details on how they plan to generate revenue.
80mg is four times the average dosage. Anyone who has taken this drug therapeutically for its intended purpose at sane dosages will tell you that it can have some nasty side effects if you’re not careful. In brief, it makes it more difficult for your body to tell you when its had enough and needs food or rest. Things like sleep and eating are simply more difficult. You’ll find that out quickly enough without a doctor informing you of such, but it’s manageable then. We could just as easily be discussing someone who increasingly decided to sleep and food deprive themselves for months or years.