Just because data can be rendered to DOM on the client doesn't mean it always should be.
I'll try to render HTML wherever the data is stored. Meaning, if the data lives in a hosted database I'll render on the server. If data is only stored on the client, I'll render there.
Its less about bundle size in my opinion and more about reduced complexity and data security.
That said, I've never been a fan of RSC and don't see it solving the "reduced complexity" goal.
There is no additional data security if you are sending a rendered version of it to client instead of raw version.
Data that will be rendered on the client generally should be sent to the client in my opinion because you can easily determine if bugs are a rendering problem or a data problem without sifting through server logs.
There absolutely is. I can fetch a full user record from the database and use it to render on the server, not ideal but still secure. Send the full user record to the client and that data is now more at risk.
QA is still alive and well in many companies, including manual QA. I'm sure there's a wide range these days based on industry and scale, but you simply don't ship certain products without humans manually testing it against specs, especially if its a highly regulated industry.
I also wouldn't be so sure that programming is the hardest of the three roles for someone to learn. Each role requires a different skill set, and plenty of people will naturally be better at or more drawn to only one of those.
There's a whole ball of wax here that boils down to whether a society would rather be individualistic or collectivist.
Its a chicken and egg problem as well, the way we regulate and manage health care and health insurance (at least in the US) allows for costs to pretty easily bleed out to the rest of society. That implies that we must then be collectivist in other policies, though that is counter to many of the original goals of our country and the question is whether we changed those goals or inadvertantly built a system that requires changing gials after the fact.
We have a similar problem with immigration laws. Our immigration laws today are completely counter to what they once were, and counter to what is still written on the Statue of Liberty. We have immigration laws now that are necessary because of the welfare programs we implemented, even if we wanted to live up to the older ideals we couldn't without abandoning those welfare programs entirely.
It was marketing that was installed on the statute of liberty in 1903, when the U.S. was already fully developed. It doesn’t reflect the original intent at all.
It was written in 1883, as part of fundraising for the pedestal. It might not reflect precisely the "original intent" of the statue, but it's very much in line with all of the other context.
The statute of liberty was from a french admirer of the constitution and abolitionist. It was conceived at a time when Napoleon III had declared himself emperor. The connection to immigration was a completely unrelated glomming-on.
Death of the author. People sailed under the statue to get to Ellis island, it's not a difficult connection to make. The location was known when the poem was presented in 1883, 2 years before the statue arrived in the US and the author volunteered for one of the numerous aid organizations helping jewish immigrants.
The fact that people used it after the fact for marketing an unrelated issue doesn’t have anything to do with the original intent of the statue. There was a lot of ret-conning American history in the late 19th to early 20th century as a result of mass immigration.
Things can come to mean something different from what their funders intend.
It happens all the time, especially with art, language and especially public monuments.
The Statue of Liberty’s connection to Ellis island is undeniable. The national museum of immigration is part of the same monument and run by the same staff.
It’s not ret-conning to say that the Statue of Liberty is indelibly linked - physically and symbolically - to mass migration of working and lower class people. It was the busiest port of entry for more than 60 years, and more than 20 million people entered there. There are uncountable contemporaneous accounts of immigrants viewing their passing the statue as a marker of the end of the voyage, and the beginning of their life in America.
One French guy funded it for one reason. 20 million others saw it as a symbol for something different in their lives.
The full title of the statue is “La Liberté éclairant le monde”—it’s impossible not to see it as a symbol of the ideals of the Enlightenment spreading across the world. That’s the common philosophical ground of both American and French Revolutions, and from there the source of the friendship that the statue represents.
At least some minimal notion of hospitality with respect to migration is part of that Enlightenment. (Kant’s Perpetual Peace is emphatic about this; Derrida annotates the relevant section with fresh eyes in Hospitality vol. 1, the first lecture and ff.)
That said, I also agree with you that symbols are not fully formed at birth and it is not the case that what they represent never changes at all in the course of their history.
> There's a whole ball of wax here that boils down to whether a society would rather be individualistic or collectivist.
Yeah, but the US seems to me to be one of the worst places for individual responsibility. Everyone expects their environment to be perfect safe, and they can behave with a large degree of personal negligence, and if anything goes wrong they want to sue anyone they can think of. And then corporations take defensive actions against that, and you wind up with "do not take Flumitrol if you are allergic to Flumitrol" kinds of warnings everywhere. It is "individualistic" in the most narrowly narcissistic sense, which I don't think is what the founders envisioned either.
The way I see it is that enabling individualism, perhaps through strongly collective rules is very different than individualistically segmenting all sorts of experiences and protections. The latter of which, as you have noted, may not result in individualism on any sort of practical level - especially if it just lets large corporations mow down all sorts of people segmented to an individual level of power.
> whether a society would rather be individualistic or collectivist
Like many of these sorts of choices, its false to think of it as binary because its about choosing a place on the continuum between them.
On the methanal risk issue, one possible compromise would to have places which can run free checks on booze for methanal. Not too different from the practice in France where you can bring in mushrooms you've collected to the pharmacist who can tell you which ones are delicious and which are death incarnate. But of course this would have to be a publicly funded service which america seems to loathe ("I'd rather go blind than have a single tax dollar go to free booze testing!")
> But of course this would have to be a publicly funded service which america seems to loathe
This hasn't been my experience in the US over the last couple decades. Both parties like to complain about the other side, but they both spend money we don't have and are happy to fund new government programs as long as its their party's program.
This is a bit oxymoronic. People are a bit too happy to pick and choose what they like and otherwise pretend they're an island to themselves, but it doesn't take a communist to see the contradiction.
You're assuming its a binary rather than a spectrum though. I wouldn't expect to find anyone who is entirely individualistic or entirely collectivist.
Plenty of people would agree they're willing to pay taxes and give governments the authority to build and maintain public roads, for example. That doesn't mean they would also then be okay with government taking over industry.
Pacifism at such a large scale is a self-defesting strategy though. If its well understood that a country will never respond, eventually someone will take them over or wipe them out.
I've never understood the post-WWII goal of permanent peace. Its a great vision to have, but unless its completely infeasible.
Unless we've managed to find ourselves alive at the point in all of history where humanity forever abandoned war all together, there will be another war at some point.
That doesn't mean it needs to happen today or that fighting to sustain peace isn't an admirable, and necessary, action to take. It does mean one still needs to consider the next war though, in case its forces upon us despite wanting peace.
I've had the same challenge when an argument is raised that nukes haven't been used since 1945 so they may never be used. It is quite a feat for sure, but in my opinion the only way a nuke is never again used in conflict is if we invent an even worse weapon and someone eventually uses that instead.
>I've never understood the post-WWII goal of permanent peace. Its a great vision to have, but unless its completely infeasible.
There is no post-WWII goal of permanent peace. It’s a side effect of the invention of nuclear weapons, which made wars amongst powerful countries a lose-lose scenario for everyone.
I'll try to render HTML wherever the data is stored. Meaning, if the data lives in a hosted database I'll render on the server. If data is only stored on the client, I'll render there.
Its less about bundle size in my opinion and more about reduced complexity and data security.
That said, I've never been a fan of RSC and don't see it solving the "reduced complexity" goal.
reply