If you ever wonder how good the Tiktok-Algos are, open it in a new private Browser and scroll through that. Night and day.
“Java is a boilerplate-driven language for writing instant legacy-code” www.youtube.com/watch
On the other hand, when I do have a concrete idea, I prefer not to use any new tech, but prefer to use something I have experience in, to get it done/out quickly.
I often feel the urge to try out new languages, game-engines, frameworks etc. but the interest almost always wanes after getting a first idea of the thing, because I have no ideas for projects.
Is Meteor still a thing? Note to self: look up.
For full-stack I find it annoying to work on two projects, back- and front-end at the same time. Ofc there is the “classic” server-rendering, but I do feel like the ideal situation is to have one codebase and a permanent connection between browser and server. (The hypothetical use-case here is a side-project with me as only dev)
Asking around some more I came to the conclusion that one should stick to client-only-use with Next.js. I guess something like Elixir/Phoenix with LiveView is the closest thing to my preferred structure/architecture.
Next (hehehe) step will be to make a simple guess-the-number-game in Next.js.
Seems like the “api”-folder is the place for such things. Feels stateless on first look. Let’s see.
I guess the actual question is, whether it’s able to keep a state in sync with the front-end. Maybe I’m thinking too much in the direction of Phoenix and LiveView here.
Starting to look into Next.js and similar approaches. I wonder if it’s possible to do stuff on the (Node-)Server only, like game-logic that the client shouldn’t see. Or server-calls to counter CORS-issues. Or is it just for constructing DOM for that initial render…
Hello, Sailor!