Lovins’ later book, Reinventing Fire,48 has a fawning Foreword writtenby the President of Shell Oil Company, which is not surprising since Lovins had adjusted hisgraphs so that fossil fuel phaseout was moved to 2050

It’s great that there’s interest in this stuff. Your articles are inspiring, as is Jillian Hess’s NotesSubstack, team Greene/Holiday/Oppenheimer, and the German scholars who focus on the technology of writing, such as Hektor Haarkötter. But I don’t see this as nostalgia. For me it’s history in service of the present and the future.

I’ve spent years studying how prolific writers, artists, and thinkersof the past managed their creative process. I’ve spent countlesshours researching how human beings can use technology to extendand enhance our natural cognitive abilities. I’ve personally

three steps required to solve the all-importantcorrespondence problem. Step one, according to Shenkar: specify one’s ownproblem and identify an analogous problem that has been solved successfully.Step two: rigorously analyze why the solution is successful. Jobs and hisengineers at Apple’s headquarters in Cupertino, California, immediately got towork deconstructing the marvels they’d seen at the Xerox facility. Soon theywere on to the third and most challenging step: identify how one’s owncircumstances differ, then figure out how to adapt the original solution to thenew setting.

Of course you can start implementing your own thing, but you will waste a lot of precious time reinventing the wheel. Why not take advantage of a validation library that takes care of all this complexity for you?

You can try to build a solution to tackle these issues on your own, but it will cost you time and money... why not use a battle-tested solution to handle all this complexity?

Other frameworks, which use a template syntax built atop HTML — Svelte, Vue, Ractive, Glimmer etc — have historically been fragmented, meaning those tools need to be reinvented many times.

Why not just use that instead of inventing a syntax that's not part of ECMAScript?

Why struggle with custom Syntax DSLs when you can use one so widely supported?

People constantly suggest that I should have just worked with a different library instead of writing another one.

The main rationale for this PR is that, in my hones opinion, Svelte needs a way to support style overrides in an intuitive and close to plain HTML/CSS way. What I regard as intuitive is: Looking at how customizing of styles is being done when applying a typical CSS component framework, and making that possible with Svelte.

Why make another UI component kit when we already got Smelte and SMUI? What's so special about Svelta?

They write their own function because it’s easier and more fun than figuring out how the old function works.

Particularly noteworthy are studies on the struggle over recreational space in Worcester parks (328), the relationship of the automobile to the reorganization of rural American space (176), the changing use of space in charity hospitals (330), and the American depart- ment store (30).