Some First Thoughts on Next 13

I was stoked when I started hearing about Next 13 a couple of months ago. I had some time on my hands, so I thought I’d do <a href="https://github.com/AmyBlankenship/next-contacts-example" rel="noopener ugc nofollow" target="_blank">an example project</a> to kick the tires. The big thing that had me so excited was the new streamed HTML capability. I’d <a href="https://dev.to/tigt/the-weirdly-obscure-art-of-streamed-html-4gc2" rel="noopener ugc nofollow" target="_blank">read about it a few months ago</a>, and it was exciting to see it come <a href="https://nextjs.org/blog/next-13#streaming" rel="noopener ugc nofollow" target="_blank">to Next JS and React</a>. I really wanted to like Next 13. <h1>Pre Release Software</h1> When I started my career, nearly all software aimed at developers was paid. Beta programs were closed, mostly limited to prominent members of the community. On the one hand, this meant that very few developers had much of a grasp of the new features when the new version was released. On the other hand, the small pool of beta testers meant that the team developing the new version could help testers get unblocked to fully exercise it. The way testers got to be prominent members of the community was through spending considerable time helping others learn the software, so time invested in teaching them to use the new version was well spent. Closed betas prevented uncomplimentary reviews while the software was under development. Not only was it super clear the new version was not releasable yet, but also beta testers wanted to make sure they would be invited next time. <a href="https://betterprogramming.pub/some-first-thoughts-on-next-13-922a6a6c5200">Click Here</a>