The rear derailleur on my cycle wasn't shifting as expected, and so I spent an afternoon following YouTube and adjusting its limit screw and barrel adjuster to no avail.
Finally gave up and took it to a shop, the mechanic took the cable out of the housing, wiped it down, greased and put it back in; the derailleur starts shifting normally.
"Easy to repair" doesn't necessarily mean you or I can repair it easy. It might mean someone, preferably a local, independent business, can repair it easy.
Hey, Frappe Books developer here. Not as of now, but it is something that we will be adding in. There has been a lot of requests for multi user support.
> My most complicated problems were reactive DOM elements based on nested loops and recursive components
Agreed, I've tried solving it by setting an attribute `sb-mark` which allows syncing just the branch of DOM elements that maps to that particular key in the reactive object.
This removes the need for VDOM diffing, but unless I use a `MutationObserver` external updates to marked branches will probably mess it up.
Haven't yet tested it for recursive components, it should work for nested loops.
> and it is simple but sometimes confusing
I understand what you mean, my approach has the aforementioned `sb-mark` attribute/directive which syncs primitives, lists, and objects.
I've started feeling that the convenience of having just one attribute to remember is supplanted by the confusion of its implications not being immediately apparent from context.
> This removes the need for VDOM diffing, but unless I use a `MutationObserver` external updates to marked branches will probably mess it up.
Similar in Reken. It controls all the DOM; DOM updates outside Reken will get stuff out of sync. After a model change, all managed DOM gets directly updated by a generated controller. It does check the DOM first if a textContent or attribute change is necessary. Most DOM state checks are cheap. Another optimization is that all hidden DOM trees get skipped; Great in SPA apps with multiple pages.
The biggest hurdle to using TypeScript is the build step before it can actually be run. If the type annotation TC39 [0] comes to pass this would be largely taken care of; _hype_ waxes. (unfortunately the proposal has been stagnant for more than a year now)
A lot of the new frontend codebases involve a build step before running. For such codebases, TypeScript's build hurdle has already been overcome.
I too tried gym, but now I'm muscular and awkward. Now, before interaction, people don't expect me to be awkward, and it feels as though they are more forgiving of my awkwardness but that could just be my perception.
Going to the gym and losing weight did help a lot with self esteem (and posture) issues though.
After observing my interactions, I found that if I'm unfamiliar with the person, I'll miss out on social cues or there'll be a delay before I perceive them. Also my brain goes into some kind of _fight or flight_ causing slightly impaired speech and memory.
What I do to _fix_ this is watch how others interact with this person and try to mimic them while adjusting for unfamiliarity. Assuming familiarity could be perceived as rude.
For me building familiarity allows me to interact with decreasing awkwardness, so I just try and find the fastest way to do that.
Using rate of speed up is probably a bad metric due to varying densities, but even if one were to account for that and use some kind of smart speed up app that maintains constant information throughput, the issue is with not taking pauses to ruminate.
It's more of an information retention problem rather than an information loss one. IE not committing to long term memory as the author states.
Yeah, I've noticed that with text I'm going to make more pauses thinking about what I just read (especially printed text for some reason). Video is the worst, while audio only in the middle. Maybe because of clunky controls ?
Although the emulations are getting really good. For instance this [0] VSCode plugin isn't even an emulation. It embed neovim into VSC, even loads your init.vim file. Snappy too.
The rear derailleur on my cycle wasn't shifting as expected, and so I spent an afternoon following YouTube and adjusting its limit screw and barrel adjuster to no avail.
Finally gave up and took it to a shop, the mechanic took the cable out of the housing, wiped it down, greased and put it back in; the derailleur starts shifting normally.