【ウマ娘】新シナリオ『無人島へようこそ』最速攻略！友人凸必須
発展Pt／島トレ／建設ルート／新育成シナリオ公開スペシャル！【ウマ娘プリティーダービー ぱかライブTV チャンミ https://www.yayafa.com/2403198/ #Game #gaming #Gジェネ #LOH #NottinTV #SSR #UA #UB #UC #umamusume #us #アプデ #アプデ情報 #うまむすめ #ウマ娘 #ウマ娘プリティーダービー #オート育成 #ガチャ #キヨ #クロノジェネシス #ゲーム #ゲーム実況 #ゲーム攻略 #ゴールドシチー #サポカ #ジージェネ #シングレ #シンデレラグレイ #タッカーブライン #タマモクロス #チャンミ #のっちん #ぱかライブ #ぱかライブTV #パワー #プラチナ #リセマラ #ローテ #人権 #人権級 #何凸 #凸 #切れ者 #友人 #友人サポカ #因子周回 #完凸 #必須 #攻略 #新シナリオ #最強 #次のシナリオ #無人島 #無人島へようこそ #立ち回り #育成 #育成法
#ssr
0 posts0 participants0 posts today
https://www.tkhunt.com/1962043/ 【ウマ娘】新シナリオ『無人島へようこそ』最速攻略！友人凸必須発展Pt／島トレ／建設ルート／新育成シナリオ公開スペシャル！【ウマ娘プリティーダービー ぱかライブTV チャンミ #game #Gaming #Gジェネ #LoH #NottinTV #SSR #UA #UB #UC #umamusume #US #アプデ #アプデ情報 #うまむすめ #ウマ娘 #ウマ娘プリティーダービー #オート育成 #ガチャ #キヨ #クロノジェネシス #ゲーム実況 #ゲーム攻略 #ゴールドシチー #サポカ #ジージェネ #シングレ #シンデレラグレイ #タッカーブライン #タマモクロス #チャンミ #のっちん #ぱかライブ #ぱかライブTV #パワー #プラチナ #リセマラ #ローテ #人権 #人権級 #何凸 #凸 #切れ者 #友人 #友人サポカ #因子周回 #完凸 #必須 #攻略 #新シナリオ #最強 #次のシナリオ #無人島 #無人島へようこそ #立ち回り #育成 #育成法
Last Thursday I have one engineer talk about ssr & web components at the AmsterdamJS meetup. Click-baity title, but I promise we tried to give the full picture. :)
> Today, we’re excited to launch support for fullstack #Nextjs apps and sites on #Fleek! With this release, developers can now effortlessly deploy apps and experience server-side rendering (#SSR) and static site generation (#SSG) functionality directly within Fleek’s edge-optimized platform, unlocking unparalleled scalability, performance, and control.
https://fleek.xyz/blog/announcements/nextjs-support-release/
fleek.xyzIntroducing Fullstack Next.js Support on Fleek: Build, Deploy, and Scale Dynamic Apps with EaseFullstack Next.js support is live on Fleek. Deploy apps with SSR and SSG on an edge-optimized platform for top performance and control.
The timing is ripe for a #framework to go all-in on #clientside. Between #localFirst tech starting to come together, and the promise of #SSR not coming fully to fruition, there's a path to an alternative architecture.
Continued thread
What at least I *really* need is a unified DX for two types of component: 100% CSR or 100% SSR. None of that isomorphic garbage, but also no (huge) delta between the component models. This should be doable 
#webcomponents #ssr
I'm starting to believe that #SSR for #webcomponents is not really a well-defined concept. Unless the entire App is a react-like pure function, you'd really need to pre-render entire pages with JSDOM, Puppeteer or similar because components could possibly depend on (or modify everything on) any given page.
Check it out; a #webpage served from a #serverless #function that's distributed on #IPFS and executed on someone else's computer that is NOT a big-tech corpo!
https://noisy-answer-late.functions.on-fleek.app/
This is a #fleekFunction running on the #fleekNetwork, a #web3 #blockchain project. The #HTML is a #SSR #webComponent rendered by @enhance_dev
example using package.json for IaC with Hono and Enhance/SSR
https://github.com/brianleroux/arc-example-hono-enhance-ssr/tree/main
GitHubGitHub - brianleroux/arc-example-hono-enhance-ssrContribute to brianleroux/arc-example-hono-enhance-ssr development by creating an account on GitHub.
The entire point of server-side (ssr) rendering is to return fully rendered content. (?)
If you don't want the fully rendered interpreted result and instead want the higher level templating and instructions for the client to interpret that's called client-side rendering (csr).
You can preserve the raw code for additional client render steps in Enhance. But for most elements you won't need to. And yes it can all be shadowdom also if you want to (but again yagni).
Wordpress Plugin for server-side rendering Web Components anyone?
https://github.com/enhance-dev/enhance-wordpress-plugin
@ryanbethel continues to go beast mode porting Enhance to anything that can run WASM.
GitHubGitHub - enhance-dev/enhance-wordpress-plugin: Wordpress plugin to serverside render enhance components in wordpressWordpress plugin to serverside render enhance components in wordpress - enhance-dev/enhance-wordpress-plugin
Extremely clarifying docs regarding how Enhance web components are in fact *real* web components even tho SSR is first class as well as backend runtime agnostic. (Great upgrade to the docs, thx @macdonst !)
enhance.devComponents — EnhanceThe HTML first full stack web framework.
It's weird seeing ppl who are probably pretty smart and definitely experienced web developers acting like an http endpoint returning html is some kind of new idea.
Anyhow here's a cool tree I saw today.
I did what every – exaggerating – #webdev has to do:
Rewriting the own #blog and #website after some years. New website, same URL, all posts should keep working under same URI.
More stuff to come, I just had a few days and a few hours of free time to switch from custom static site renderer (https://andi1984.dev/posts/my-static-site-generator) to #nextjs with #ssr and more dynamic content (planned).
More to come for sure...
andi1984.devAndi1984Frontend dev
Replied in thread
Replied to Brian LeRoux 
CET @brianleroux
– The debate client-side vs server side is almost as old as the web itself. There was a decade where almost everything was rendered on the server because clients didn't have the power to render all that stuff. Then there was the decade where almost everything was rendered on the client because that was "cooler". Now, everyone wants to do #SSR. Truth is, it isn't either or. Both have their pros and cons.
2/2
A perhaps off-base #weirdcarmastodon take I hold is that the early-00s #Chevrolet #SSR 1) looks cool and 2) will some day be sought after.
I just started playing around with #Preact #SSR with #htm and the first thing I did was render the classic:
```
render(html`
<!DOCTYPE html>
<html>
<head>
<title>Preact</title>
<meta charset="utf8">
</head>
<body>
<h2>Hello, World!</h2>
</body>
</html>
`)
```
And this intuitively output:
```
html
<head>
<title>Preact</title>
<meta charset="utf8" >
<body>
<h2>Hello, World!</h2>
</body>
</head>
```
Lolwat?
* `<!DOCTYPE html>` is gone.
* `<html>` turned into `html` and lost its close tag.
* `<body>` got moved inside `<head>`.
Apparently you can't output a doctype at all (https://github.com/preactjs/preact-render-to-string/issues/201) and the `<meta>` tag is not self-closing in #JSX.
I'm willing to accept those constraints, but this is an utter failure of DX IMHO. If my template is wrong, TELL ME! Don't just generate what's effectively garbage for seemingly no reason. There's no obviously logical path from "bad output" to "the mistake in my code". Error messages, please!
GitHubThe output of DOCTYPE is strange. · Issue #201 · preactjs/preact-render-to-string
This is by no means a fully complete/polished project - buuut I have taken my #SPA #TypeScript #CRA and gone FULL #Golang, cached templates, #SSR, and vanilla #JS. There’s only one partially complete #TextAdventure #game (don’t choose the “engineering” arc 
) at the moment, but I’m happy with how things are shaping up. BTW - it’s deployed on Render, so you may exp -2min first page load if they snoozed my server. Oh & @Lowie cheekbones arc is done
otterly.gamesOtterly Ridiculous Games | Play Ridiculous Text Adventure Games OnlinePlay fun and ridiculous text adventure games online right in your browser!