There's ~four of us trying to reproduce this right now, using Astro and Remix, and cannot at all.
An important note: React-based frameworks tend to use camelCase attributes vs. hyphen-case (which is the output) in components: including the icon library being used here. Something during the build process is not converting them to hyphen-case.
* This is all deployed via the Pages Build system; no local builds at all.
* Someone else on the team has an Astro example stood up with the specific unplugin-icons library: https://astro-svg.pages.dev/ - cannot reproduce the invalid SVG attributes.
We're going to continue investigating but don't see this as widespread and don't yet have any other reports. That there is a _difference_ between the direct deploy vs. using Pages Builds is a problem, though. We've also asked the Astro folks to understand if there's something up here as well.
Based on the article, it's happening before anything gets served, it's specifically happening during the Astro build phase, but only on the Cloudflare build machines. So by the time it comes to serve the assets, stuff is already broken.
My guess would be that there is some specific bit of information set during the build that triggers this incorrect build in Astro, and this information is set only by the Cloudflare build process. But here the people from Cloudflare are struggling to reproduce that effect, so it looks very specific to this person's setup.
> The fact that D1 still doesn't support replication is an indication to me that it has been deprioritized, likely with other newer and less used products, while the infrastructure updates are dealt with.
D1 is definitely not deprioritized. We're heads down on replication, and it's important for us to get it right. Takes time!
> What a nightmare! Now your application code spills into your database and our initial goal of simplifying application development is nothing but a long-forgotten dream. All of that for what? To save a few milliseconds to display a web page.
I think "a few milliseconds" vastly understates this: if you want to run your application closer to users, even just across the US, each query is (at least) 70ms just to get over the network and back again.
"Application code spills into your database" was a bad thing when you wrote one language (say, Java, or PHP) and another language (PSQL/TSQL/etc) for your "stored procedures", but that's not what most modern databases are advocating for.
Instead, and not unlike something like React Server Components (RSC), you can choose whether to run code close to the user or closer to the DB (for transactions) in the same language as your application, because it's still part of your application code. This is the model that Durable Objects[1], our coordinated storage service, uses.
Disclaimer: I work on D1 & Durable Objects at Cloudflare, so I'm likely to be called biased here, but it's not like we haven't a) thought about this deeply and b) actually use D1 and Durable Objects to build distributed systems at Cloudflare.
> due to the writers literally having disdain for the actual source material and we're just using the how's setting as a backdrop to push their own entirely disconnected stories.
Is this concretely true, or just disinformation to put blame on writers vs. producers?
I’m not saying it’s not plausible either way, but this is a common cop out.
It's all entertainment industry gossip, but one of the writers for the Witcher show said the same thing:
> "I've been on shows — namely 'Witcher' — where some of the writers were not or actively disliked the books and games (even actively mocking the source material). It's a recipe for disaster and bad morale," wrote DeMayo.
Also, this characterinzaction of the Witcher series writing is 100% correct - especially in last season. Going by the comments writer made publicly, she did not even understood events or relationships between characters in books. It is as if she understood adolescents, but had real issue comprehend adults or write about them.
> It is as if she understood adolescents, but had real issue comprehend adults or write about them.
This seems like a very common problem in modern American entertainment. I think it's because they're hiring writers who are too young with too little life experience. Characters who should be mature adults seem like immature teenagers. Maybe the writers know how to write mature characters but think this is what audiences want... but I tend to think the writers are nepo hire hacks.
I think part of it is generating and stretching out drama to create more content. If situations were handled like sensible adults then much of the show wouldn't happen.
I don't think this is true. First, this is specifically not true about Witcher or Game of Thrones. Plenty of drama even if they all acted sensible.
Second, being fully grown adult does not have to imply perfection. Fully grown adults make bad insensible decisions all the time. They however do that differently then teenagers, for different more complex reasons.
And this is something that is super visible in Witcher. Original characters don't make sensible decisions all the time ... but they have adult psychology. Even when they are bad to each other, they still don't act like middle schoolers. They act like adults with issues. And show writing just completely stripped them off the adulthood.
That sound similar to the bad writing technique of "character X did action Y because the plot needed Y to happen somehow", which cheapens character X and makes them seem less like a real person and more like a puppet for the authors.
One of my big concerns is that people will see the lack of communication as normal acceptable behavior and emulate it, the show will either not address it or will explicitly excuse it. They’ll see the negative outcomes as incidental and faults from the other characters.
> I think it's because they're hiring writers who are too young with too little life experience.
That’s what you get when you hire writers willing to work in mini-rooms (and not go to production): inexperienced folks still sponging off their parents.
This is an unfair comment. First, people do have to get started somewhere and early career is rarely as glamorous as late career. It’s highly possible that the only jobs in that industry for new entrants are in mini-rooms. So the choice becomes not working in one’s chosen industry at all or starting out in mini rooms — I say starting out because you’re talking about inexperienced folks. So that part of the comment isn’t really fair.
The other part of the comment that isn’t fair is the “sponging” part. Generally this implies loafing or laziness, someone taking their parents resources and being lazy with them. But we’re talking about working people who are new to their career and putting in the sweat and willing to work in mini-rooms. I don’t think using parental resources is sponging when someone is early career and trying to work hard to get ahead.
I read labster's comment as a criticism of the industry, rather than the writers.
If the pay is so bad that the job's only available to kids with rich parents, whence comes the breadth of experience needed to portray the world as it really is?
And by offering such bad pay, hasn't the industry brought this on themselves?
Those things are exactly the problem. You don’t actually gain experience without going to production, and you don’t have steady enough income to support yourself. They can work hard but never actually get ahead.
Imagine a world where all junior developers are contractors hired for a month or two. They work with more experienced senior devs to write a program together. But junior devs contracts end before the code is ever compiled or run, so they never learn anything about bugfixing or adjusting to client changes or performance with real world data. This is what working hard to get ahead looks like in Hollywood today.
They don't pay enough so people who's moral code whould have them support themselves can't participate and instead you get people who are OK with mommy and daddy paying for everything, often well into their 30's, and it shows.
If this is someone’s “moral code” then it goes against basically all of human history’s actions with the elders helping out the children until they get on their feet, and then the children supporting their parents when the parents age. Not everyone has the privilege to align with this system, but certainly aligning instead with a contrived moral code comes across more as sour grapes than any principled stand against receiving some help from one’s elders.
Majority of human history have kids being expected to contribute meaningfully much much sooner then we do know. And them being seriously mistreated if they don't. And them being expected to actively help elders by the time they are 30.
The older I get, the more I realize those supposedly "mature adults" do the exact same shit that immature teenagers do. They might be better at hiding it, but they still do it.
That is because you are interpreting "mature" and "immature" as terms for approval or disapproval. I am not arguing that mature adult characters should do all the supposedly rational correct decisions. I am arguing that their behavior is NOT the same as behavior of a teenager nor the behavior of 22 years old. The difference is not just in hiding something. It a lot of stuff like that for teenagers 2 months ago is long time ago while for mature adults it is yesterday. It is that mature adults form friendships differently then kids.
And good writing sees the difference. Take Breaking Bad - neither Walt nor Jessie make good decisions. But Walt is clearly mature man and Jesse is young and immature(and matures during the show). That is good writing involving mature adult, Walt, despite him making one bad and emotional decision after another. Same thing Game of Thrones in initial series - involves well written mature adults doing horrible things.
Then take writing in the Netflix Witcher (and everything that was said about it) or last Game of Thrones series. Long term friendship between mature imperfect adults is something the writer did not even understood. Complicated respectable mature women (who still have difficult personality) is changed into clingy teenager with crush. And judging from interviews, the writer just does not understand these aspects of humanity or of writing.
> They might be better at hiding it, but they still do it.
An important note: React-based frameworks tend to use camelCase attributes vs. hyphen-case (which is the output) in components: including the icon library being used here. Something during the build process is not converting them to hyphen-case.
* I've pasted a decently complex SVG exported from Figma into a Remix component verbatim (hyphen-attributes) and it renders fine: https://9b14a265.test-broken-svgs-remix.pages.dev/ (scroll down)
* I've rewritten those attributes to camelCase: and again, renders fine - https://1af766a8.test-broken-svgs-remix.pages.dev/
* This is all deployed via the Pages Build system; no local builds at all.
* Someone else on the team has an Astro example stood up with the specific unplugin-icons library: https://astro-svg.pages.dev/ - cannot reproduce the invalid SVG attributes.
We're going to continue investigating but don't see this as widespread and don't yet have any other reports. That there is a _difference_ between the direct deploy vs. using Pages Builds is a problem, though. We've also asked the Astro folks to understand if there's something up here as well.
(If not clear: I work at Cloudflare)