Homework would still be assigned as a learning tool, but has no impact on your grade.
2,986 karma · joined October 23, 2009
Homework would still be assigned as a learning tool, but has no impact on your grade.
Once started, the engine would run with no electrical system at all! Even the fuel shutoff operated on vacuum.
By far my favorite hack :)
The OM617 (as used in many 1980’s Mercedes sedans) fuel shutoff operated on vacuum, and once started, the engine would run with no electrical system at all.
You misunderstood my post, and I don't appreciate the tone of your reply.
It seems like vertical scaling has fallen out of fashion lately, and I’m curious if this might be the new high-water mark for “everything in one giant DB”.
I don’t mean to be rude, but that’s how an iOS intern would implement it.
Keeping UI rendering under 16ms is the gold standard for native apps. That leaves only deserialization as the other target which the mobile developer can optimize. However, the typical solution there involves convincing the backend to ship a different format (i.e. switching from JSON to binary PList or to SQLite DB file).
I'm kind of surprised no one seems to have explored this idea before (happy to be shown examples proving otherwise!)
The typical retort I hear is “but it’s just this one feature, how hard is it to learn just one feature?” But you’re only considering your favorite feature. To the casual code reader, it isn’t just that one feature, it’s everyone else’s favorite obscure feature as well.
Using cat makes your code readable to a wider audience. Using cat has real upside with no downside. Forcing your readers to learn more shell syntax has real downside with no practical upside.
Ok, so where does the toast go if you've already scrolled or otherwise navigated to a different area of the UI? These optimistic updated could take multiple seconds to succeed, and maybe as much as 30 seconds to fail.