| Funny. I liked the TypeScript being added and then removed in the TODO. I've been working with the web since before JS and CSS existed, back in the cgi-bin days, and have somehow ended up still working with it to this day. I used most of the pre-SPA frameworks, when everything was what is now being referred to as "SSR". Then I was dragged (somewhat kicking, screaming, and muttering about 'kids these days') into the world of SPAs, except I ended up on the Angular side and have not really been on the React side. I will say that I have been following along with this Next.js stuff and the other changes going on over in the React ecosystem, and I am left utterly confused while at the same time having an uneasy feeling about the whole thing. It's not necessarily because we've seen all this before, it's more about "why now?", and then wondering about how badly this is going to be abused, because if it can be, it will be. I get it, people need SEO, FCP times need some help ... and ... well that's about what I came up with off the top of my head. Have you ever seen a SQL statement that JOINs 20 tables in your a component, that uses a magic string to indicate that it is not your ordinary component? You will. Naturally, almost anything can be used in ways it should not be. But when you are combining the dominant SPA framework, blurring the lines between the front and back ends, and employing a large amount of fairly complex magic behind the scenes to make it happen, I get the sense that bad things may be afoot. I for the moment am content working with a different framework, it's been smooth sailing for a complex enterprise system. I'll see how the rest of this unfolds from afar. |
I implore people to try liveview though, doing everything (pretty much) on the server is incredible. So powerful and no headaches about leakage or security of APIs or whatever - all data is in BEAM/elixir process state unless you render it into a template or explicitly send it to the client in an event.