I came across similar anecdotes of build quality and turned my nose. I found myself wishing I could hold a Framework laptop twist it like I was ringing out a wet rag. Surely this is a good test of build quality, I thought to myself. But in a moment of clarity, I realized this and other pseudo signals of build quality that Youtube reviewers and other armchair experts were attempting to use to draw comparison (to a unibody macbook pro) were either irrelevant or pedantic. Why is a unibody the pinnacle of build quality? Shouldn't longevity be?
I checked my Apple elitism at the door and I put my name down for a Framework in September and got it in October. Happy ever since. It's a great little laptop and would highly recommend others.
Something tells me the author would appreciate the minutia of working in functional languages that tend to avoid entire classes of problems like those described and the dogma used to fight it.
The are everywhere. I'm fairly certain that I encounter them more often than SFMTA.
My car was broken into over the weekend and I couldn't help but think about whether a Waymo captured the vandalism... Not like it would help, but like all mass data collection campaigns, the potential implications are strange.
This! I participated in two FIRST robotics competitions as a teenager. I can say, it definitely was a pivotal experienced for me on the path toward a computer engineering degree.
Engineer from Prismatic here. The Android app was written with Java. While we would have loved to build it with Clojure, but support/perf on Android isn't quite there yet (at least for us).
Clicking follow mutates the global app data. Changes to the app data causes the entire application to re-render, and React pushes those changes out to the DOM.
So, to answer your question, we don't propagate events :)
> But letting users write code that appears to work (yet it does not) is not a good property of a language.
I still don't see the point that's trying to be made here. Whether it returns -1, FALSE, or you need a try/catch, the programmer still needs to check. To successfully program in any language with an 'index of' function, a check needs to exist regardless...
Except one minor gotcha: `Fx` then `,` will actually find the next x, since `,` reverses the direction of last character search, and `F` was already going backwards. But I can see how those movement commands are hard to fit into this layout :)
It's nice to see projects like Twitter's Bootstrap[1] being used to help reduce the amount of time it takes to get a site and its information on the web.