One does not have to go super hard in the paint for a Javascript based website. I am for E2 for a few reasons:

• User acquisition and User Experience - E2 is moving its display logic code to 100% React based. The modern web works this way, and as a "trying to not lose money" business, getting more users in the door is important. It also allows me to more rapidly reformat my site for Page Ranking because most SEO considers mobile media selectors to be table stakes. As perl users are likely to find PM due to a more niche topic, this is less of a concern
• Scalability - Having E2 move towards a full API-driven experience with a javascript client on top of it allows for us to do clever things like serve initial page state for Guest Users from S3 or some other CDN. This is HUGE in terms of cost savings in that Guest Users never have to hit the database. It also means that the servers are doing less of the rendering logic, and are slinging fewer bits on each request. We've squeezed out a ton of additional performance by moving even just the nodelets to React-based processing. The React downloads are appropriately lazy-loaded, meaning about a 1M download the first time you hit E2 on a particular build ID. Assets are managed through an asset pipeline in AWS, which is only necessary because I'm using ARM64-based vms. For bare metal servers, the production deployment can be considerably simplified.
• No really better system in Perl - I've tried things like Mason2, and they are more of a pain than what I really want to deal with. Since I'm using Claude Code to maximize my development velocity, React is well understood by Sonnet, and really meets our business objectives.
• Automated React testing in Jest - It's very easy to tell between Jest and Playwright if something breaks on the website. I've got a lot more to do, but the test coverage has also very much helped velocity, and it allows Claude to drop in and find problems with a major degree of accuracy.

In terms of going down a road like E2, I think there are some quick wins that are a perl-based implementation without doing React pretty quickly if that's of interest. We've stabilized the toolset and approach, and am willing to help this community through it.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.