Websites built with JavaScript frameworks need SSR because of SEO. Applications don't, so most are SPAs, because they can be. The fully decoupled SPA is a special architecture. Complexity isn't just lessened, a lot of it vanishes. Poof, bye bye headaches. If you can use it, you do, and most web applications can, so they do.
I had a bedbug problem in a place I rented. The landlord used heat, and it seemed to work. I also just used common sense and got a mattress liner and used Permethrin around the perimeter of my room, and it cleared up.
People who grew up in the Web 2.0 era are obsessed with trends and influence. Posit A#1 of these people is: The more people who think something, the truer it is. Therefore, you must be in the biggest group of people possible in order for your groupthink be true. A small group that tries to disagree with a big group is wrong. Therefore, their ideas will die, and there is no point in being a member of such a group. You might as well just think for yourself, which, as they all know, is insane.
Practical CRUD app architectures still exist like always. You just wouldn't know it anymore from social media. The engineers who understand it got exhausted of explaining the obvious over and over again. Just let the beguiled play with their insane contraptions. It's of no concern.
At about the 20 minute mark, they show the Foucault testing of the mirror, and actually put a camera at the test focus, so you can see a Foucaugram of the mirror. It's of poor quality, but still. You see the donut. To anyone who was into amateur telescope making, ground their own mirror, used the Foucault test, and was as interested in mirror metrology tests as I used to be, this is absolutely fascinating.
I can't believe how much of a nuisance JavaScript monoglots make themselves. My God, go learn a server-side language, please. I will teach you if you stop this.
If you take the credo of don't reinvent the wheel to a fanatical extreme, your best practice devolves into a ritualistic appeasing of the wheel gods to bestow wheels upon you.
If you polled all the engineers that work on actually designing and building browsers, I bet they would all say "Of course Wasm containers sounds way better than JavaScript containers. What are you, a pathetic frontend noob? Oh, wait, even they don't use JavaScript anymore. They all use a superset of it that's slighly less stupid. JavaScript containers, sheesh. Go be quiet in the corner."
Have you noticed how much content in social media has become either hating those who deserve it, or hyper sentimentality? It’s like manic lizard brain theater.
Shh! Us Angular devs are working in obscurity on purpose. Have you seen the misinformation and library bloat that comes with popularity? Nothing to see here, go back to your React, kids.
There's a whole new kind of fishing lure called a swimbait, of which there is a sub-type that's just a jointed fish shape. You cast it out, and reel it in, and it waves like a flag, looking exactly like a swimming fish. The only thing powering it is hydrodynamics.
I think the misunderstanding is, beyond special cases like a payment processing, why would you be calling third party services from your service? When I think of calling a 3rd party HTTP API, I am thinking of public APIs, like say a widget that shows the weather in a users area.
Yes, I think the normal way to integrate an app with an HTTP API is via the browser.
Calling an external API from a backend that integrates directly with an client app has been rare for me. Payment processing is all that comes to mind, and that was usually through an imported API package. I've made data scraping tools, but they were unique projects, not part of an app backend. I am a senior full-stack webdev.
Intercommunicating backend services isn't new, but having an HTTP API call another one from the backend is a case that used to be more normally accomplished by calling both APIs from the frontend. The slow ooze of browser-oriented thinking onto the backend took time. Existing backend engineers, who thought it a harebrained scheme, had to eventually wear down, and give up.
If you like Deno because of TypeScript, you're gunna love this: Imagine the jump from JavaScript to TypeScript, only taken to a whole new level! It's free, open source, cross-platform, really fast, has an enormous ecosystem, and is great for games and native apps! It's called C#.NET.
The entire point of an API is decoupling. A decoupled API makes double sense for a SPA. It's the client-server architecture on a silver platter.
This idea got muddled when people started making websites as SPAs, which necessitated SSR for SEO and first-page load. Now you blurred the lines between client and server, otherwise known as isomorphism, which is a good sounding word for a bad idea.
Oh, Proceedings of SPIE. I wasted more time in college rifling through those glorious yellow tomes in the solace of the engineering library than I did getting drunk.