rmrfrmrf

39 ms·

391.
by rmrfrmrf 9y ago
I used to be like this until I went through 2 iPhone 7s in the span of a month (dropped both of them). Now I've accepted my fate as a loser case-using pleb for my phone :(. Props to you for fighting the good fight, though!
392.
by rmrfrmrf 9y ago
I personally don't think it's healthy to operate under the assumption that my belongings will get damaged, lost, or stolen.
393.
by rmrfrmrf 9y ago
I actually thought Tim Cook did a great job this time around. For the first time in a while, I got that "reality distortion field" feeling that I haven't had since Steve Jobs had been the presenter. I think these keynotes go
394.
by rmrfrmrf 9y ago
It looks like they made a point in one of their promo ads that it also works at an angle and with weird lighting/obstructions (the video of the swimmer looking down at her phone that was flat against the edge of the pool).
395.
by rmrfrmrf 9y ago
TouchID always takes a "slightly-perceptible" amount of time to work, so any improvement over that would be fine with me.
396.
by rmrfrmrf 9y ago
I'm simply shocked that Microsoft would go first-to-market with an inferior product.
397.
by rmrfrmrf 9y ago
Kind of a sloppily-written article, tbh. The stats are good, but the shift at the last paragraph to "why we should care" is very weak. And while, yes, I'm sure the White House's policies aren't doing urban revival a
398.
by rmrfrmrf 9y ago
setState has its uses, especially for things like "time from now" displays where the model doesn't change but the display needs to.
399.
by rmrfrmrf 9y ago
By chance, I stumbled upon this same article a few weeks ago while re-learning React and learning Redux. I didn't get much out of the article since gripes 1-5 are all solved by Redux, and 6 is a complaint about Redux having too much bo
400.
by rmrfrmrf 9y ago
The thing is, in real-world scenarios with databases, http, and regexs, golang and node.js have very similar performance with node beating golang in some cases. Furthermore, not everyone is developing cloud-based apps and trying to optimize
401.
by rmrfrmrf 9y ago
I can't help but feel like Google gently encouraged him to promote Go over Node. Or that being told by coworkers (goworkers?) for years-on-end that Go is better than Node has had an effect. Especially considering he talks about green t
402.
by rmrfrmrf 9y ago
I disagree because Rhino and Narwhal were already around. Libuv and the event/callback approach to IO (which is the part that's familiar to front-end devs) are the secret sauce to Node.js.
403.
by rmrfrmrf 9y ago
I'm talking about a userland implementation.
404.
by rmrfrmrf 9y ago
For that matter, anyone who'd like to have "fun" with concurrency and lock management in browser-side JS is free to play around with recurring asynchronous data fetching cached in localStorage when multiple browser tabs are o
405.
by rmrfrmrf 9y ago
What do they say now , out of curiosity?
406.
by rmrfrmrf 9y ago
I edited my comment to clarify (hopefully). What I was thinking was that a theoretical "task pool" would execute callbacks with maximum parallelism.
407.
by rmrfrmrf 9y ago
If you're that concerned about performance, though, aren't doing things like `.asyncJoin()` just going to eat up any potential gains by 1) wrapping the result in a Promise and 2) throwing the Promise back into the event/mic
408.
by rmrfrmrf 9y ago
Depends on what you're doing, but if you just want to take advantage of multiple cores you can already accomplish that with `cluster`.
409.
by rmrfrmrf 9y ago
Forgive the ignorance, but why do we need threads when we already have the event loop? And, as a follow-up, why introduce a new concurrency model that's based on Java instead of, say, creating a concurrent "event pool" where
410.
by rmrfrmrf 9y ago
Looks like a paragraph is repeated in the article.
411.
by rmrfrmrf 9y ago
Yes, which suggests that the "serious problems" mentioned by the grandparent aren't serious (or problems) at all.
412.
by rmrfrmrf 9y ago
The example you've used (invoices) is actually quite instructive for demonstrating the benefits of a "document store." An invoice, historically, was a literal printed piece of paper. Invoices are actually really annoying to i
413.
by rmrfrmrf 9y ago
> the startup overhead of an SQL system is a myth. It's also a myth that devs choose NoSQL over SQL because "SQL is too hard."
414.
by rmrfrmrf 9y ago
This is kind of a ridiculous statement given the massive popularity of NoSQL DBs like Cassandra, Redis, and Lucene. Not to mention what you described seems like a perfectly reasonable architectural evolution. Are we all really expecting to
415.
by rmrfrmrf 9y ago
Meet with this person before the formal meeting if you can. Giving an informal rundown gives time for processing and formulating well-thought-out questions/flags. Provide as much material as you can on the new stack proposal. Make it c
416.
by rmrfrmrf 9y ago
Onyx, AppCleaner, and good-old find(1) all day. Mac directories are well-known enough that you can usually scrub cruft pretty easily.
417.
by rmrfrmrf 9y ago
You could cut this list in half if you just used the free stuff already included in macOS. I still don't get the appeal of iTerm or Alfred.
418.
by rmrfrmrf 9y ago
Hurricane Harvey
419.
by rmrfrmrf 9y ago
That was my same thought. This is one of the few rare times I don't think using the browser history makes sense for an SPA (at least, in its current implementation).
420.
by rmrfrmrf 9y ago
Anyone else just stare at this stuff hoping to understand it someday?

More ›