While it's not possible to define a <script type="importmap"> within a module, it is possible to define it in a synchronous <script> tag, as long as it's before any module starts executing.
Example (works in Chrome / Edge / WebKit / Safari / Firefox)
<!DOCTYPE html>
<html lang="en">
<head>
| <!-- | |
| When an input element gets focused, iOS Safari tries to put it in the center by scrolling (and zooming.) | |
| Zooming can be easily disabled using a meta tag, but the scrolling hasn't been quite easy. | |
| The main quirk (I think) is that iOS Safari changes viewport when scrolling; i.e., toolbars shrink. | |
| Since the viewport _should_ change, it thinks the input _will_ move, so it _should_ scroll, always. | |
| Even times when it doesn't need to scroll—the input is fixed, all we need is the keyboard— | |
| the window always scrolls _up and down_ resulting in some janky animation. | |
| However, iOS Safari doesn't scroll when the input **has opacity of 0 or is completely clipped.** |
| // https://medium.com/@bdc/web-components-the-react-way-8ed5b6f4f942 | |
| const store = (() => { | |
| let state; | |
| return todos => { | |
| if (todos) { | |
| state = todos; | |
| render("todo-list"); | |
| } | |
| return state; | |
| }; |
04/26/2103. From a lecture by Professor John Ousterhout at Stanford, class CS142.
This is my most touchy-feely thought for the weekend. Here’s the basic idea: It’s really hard to build relationships that last for a long time. If you haven’t discovered this, you will discover this sooner or later. And it's hard both for personal relationships and for business relationships. And to me, it's pretty amazing that two people can stay married for 25 years without killing each other.
[Laughter]
> But honestly, most professional relationships don't last anywhere near that long. The best bands always seem to break up after 2 or 3 years. And business partnerships fall apart, and there's all these problems in these relationships that just don't last. So, why is that? Well, in my view, it’s relationships don't fail because there some single catastrophic event to destroy them, although often there is a single catastrophic event around the the end of the relation
A lot of people mentioned other immutable JS libraries after reading my post. I thought it would be good to make a list of available ones.
There are two types of immutable libraries: simple helpers for copying JavaScript objects, and actual persistent data structure implementations. My post generally analyzed the tradeoffs between both kinds of libraries and everything applies to the below libraries in either category.
Libraries are sorted by github popularity.
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
