Even though macros can do this, it's not intuitive to expect this kind of JSX soup in rust. It's difficult to reason about than a function call. Something like flutter where widgets are ordinary function calls is far better.

Plus the macros add to the compile time tax.

This is another exhibit that rust is full of web programmers from React JS world (the above is exactly like JSX), all about aesthetics than practicality and predictability these days, pulling what should be a system language into incompatible directions.

Long live zig for trying engineering directions rust couldn't. But we need a rust killer with memory safety which gatekeeps web programmers and slop peddlers.

In any case railers are screwed (or railed, if I may). Either use the upstream which DHH is going to slopify and slowly kill, or use these forks by left-fascists who might happily sabotage you for perceived wrongthink in future.

Social media, dating apps, even andrew tate was doing well till some point.

It does appear most JS features can be translated to C++, even if at some overhead. Did you encounter any which wasn't straightforward?

Jokes aside, have you watched 2001 - a space Odyssey?

In 5-10 years, the people who have paid attention to these will be needed to bail us out of the mess that the rest of the slop-addled monke brains have created.

Adding numbers like this is not common in real world code. Now let's say instead of adding x, you have too look up X in a cache with an additional "type" param and update a metric of cache hits (or misses). You have to define a free function to keep your fold readable and understandable. In for loop it's much easier to understand.