If you said anti-prefer, I'd have a better idea of what the word meant.

I know, I know—needing to use JavaScript when writing CSS does feel like defeat, but unless there’s a vwWithoutTheScrollbarPlease unit in CSS, you’re going to need use JavaScript.

Maybe someday, we’ll get a viewport unit that doesn’t factor in the scrollbars, but until then, we can only work around the current one.

it shows history well, along with a good display of alternate history!

This new edition is based on an exhaustive two-year study by the Designer of the records that have come to light since the fall of the Berlin Wall. The game combines highly accurate information on the forces the Warsaw Pact actually had with now de-classified reports from the CIA and the Defense Intelligence Agency regarding what satellite surveillance and HUMINT revealed about their actual plans.

A board game that explores what If the Soviets attacked first in 1941?

Granted it's a toy example using StringIO

Hey, that’s is an imaginary complication of our example - please don’t do this with every condition you have in your app.

It is difficult to come up with content that is not extracted from a real application. Manufacturing scenarios to see if ideas have practical application turned out to be an exhasting and time consuming process.

It makes me happy to see people actually think about things and not just accept a shitty API.

The answer should be: you write a language that compiles to Go’s IR.

Please raise an issue if your use case is not theoretical.

If the react cargo cult didn't have the JSX cowpath paved for them and acclimated to describing their app interface with vanilla javascript, they'd cargo cult around that. It's really about the path of least resistance and familiarity.

It would be cool though to have a framework that does not add any specific limitations

Example with fantasy syntax: