Re:Exact – a new cross platform UI framework by the Expo team
by whilenot-dev on Tuesday November 10, 2026 @11:00AM
(#50442213)
EMCAScripts statements are enough, no need to redefine them in JSX.
<div class="container">
My list
{
list.map((item) => {
let content = null;
if (item.loading) {
content = <p>Loading...</p>;
} else if (item.error) {
content = <p>Error loading item</p>;
} else {
content = <p>{item.description}</p>;
}
return (
<>
<h2>{item.name}</h2>
{content}
</>
);
})
}
</div>
VS <div class="container">
My list
@for(item in list) {
<h2>{item.name}</h2>
@if(item.loading){
<p>Loading...</p>
} @else if (item.error) {
<p>Error loading item</p>
} @else {
<p>{item.description}</p>
}
}
</div>
I still don't see any limitation.
Re:Exact – a new cross platform UI framework by the Expo team
by halflife on Tuesday November 10, 2026 @01:20PM
(#50444100)
In my suggestion I demonstrated a theoretical approach to how I think JSX shouldve been done.
JSX eventually is not a templating engine, it’s just sugar over createComponent/createElement functions, and thats its downside, we are creating html components that need templates to render.
Your'e missing the point arguing about semantics of components or JSX elements, the point is that if you want to avoid control flow via expressions, you must destruct you template (however simple it may be) into tiny template fragments that makes it harder to understand the complete rendered picture.
Imaging if JSX could look like this:
This is much easier than the suggested JSX approach: