Our team is working to fix our Next.js project.It's so painful.
Now I'm doubting RSC is a good engineering technology or a good practice.The real world is tradeoffs: RSC really help us improve our develop speed as we have good teamates that has good understanding of fullstack.
1.Support export rendered page to other format,e.g. html,pdf,png,svg
2.The above suggestion is about how to sharing with others.So it's good to procide a way to spread,e.g. every documents made can be viewed from a special url,if you want to make this be a platform.
3.Code blocks hightlighting.Suppose someone want to use teno like juptybook to share their research or other things,code highlight is the key for reading experience.
"What fascinated me about Haskell when I was still a teenager? Who knows. I had been coding with increasing enthusiasm since I was 10 or 11 but I was no wunderkind. I certainly hadn’t attained anything like the skill or, more importantly, taste I had after just a few years in the working world. What I like about it today is that it’s quite natural to program in Haskell by building a declarative model of your domain data, writing pure functions over that data, and interacting with the real world at the program’s boundaries. That’s my favorite way to work, Haskell or not."
I adore these sentences.:)When I read it,it feels like I met myself.
Now I'm doubting RSC is a good engineering technology or a good practice.The real world is tradeoffs: RSC really help us improve our develop speed as we have good teamates that has good understanding of fullstack.
Do hope such things won't happen again.