rmrfrmrf

30 ms·

271.
by rmrfrmrf 9y ago
Isn't this kind of thing part of the reason why you log to stdout instead of handling disk writes in your app?
272.
by rmrfrmrf 9y ago
Hadn't heard of Dinghy before. Thanks!
273.
by rmrfrmrf 9y ago
NXDOMAIN hijacking is enough for me to switch, and most ISPs are doing it nowadays.
274.
by rmrfrmrf 9y ago
Clever. I like it.
275.
by rmrfrmrf 9y ago
> any competent IDE can do it for you. My biggest gripe with Java by far is the implied IDE requirement.
276.
by rmrfrmrf 9y ago
yawn
277.
by rmrfrmrf 9y ago
This isn't secret and isn't news. Who keeps posting this garbage?
278.
by rmrfrmrf 9y ago
Tor's US government roots have been public knowledge since its inception. Why is this suddenly trying to be a scandal?
279.
by rmrfrmrf 9y ago
60fps on Safari/iPhone 7 Plus
280.
by rmrfrmrf 9y ago
I've never seen a PeopleSoft implementation go well. It's always underbaked and overpriced.
281.
by rmrfrmrf 9y ago
Sounds like a great side-channel attack vector for law enforcement.
282.
by rmrfrmrf 9y ago
I worked out the math a while ago and it will take over 10 years for a home-built NAS to be more cost-effective than iCloud, and that's only if there are no hardware or disk failures, and doesn't include the additional hassle of b
283.
by rmrfrmrf 9y ago
Spoiler: no type systems guarantee anything. At least JS doesn't have the audacity to make false promises about bug prevention.
284.
by rmrfrmrf 9y ago
As someone who loves JS, your post sort of made me more comfortable with WASM as a competitor. JS is currently under seige by competing factions of OOP and FP that are constantly at odds with one another. Perhaps if these two groups had the
285.
by rmrfrmrf 9y ago
I felt the same, and also thought that the article didn't really do enough to explain why "write better reward functions" isn't enough, especially because in gaming, if anyone set the same goals these researchers did, hu
286.
by rmrfrmrf 9y ago
A monad is most simply described as the quantum superposition of the state of being (or not being) a burrito.
287.
by rmrfrmrf 9y ago
Would you call a car mechanic elitist for talking about carburetors and alternators?
288.
by rmrfrmrf 9y ago
Another fun fact: the guy who mocked devs asking for monadic Promises later "championed" and subsequently withdrew the TC39 proposal for Promise cancelation, presumably after realizing that it's impossible to shoehorn into th
289.
by rmrfrmrf 9y ago
If you're working with Promises as glorified event handlers, then yes, it suits that use case well. The problems that arise later, though, have to do with composability, cancelation, and scheduling.
290.
by rmrfrmrf 9y ago
You can have your referentially-transparent cake and eat it too, but the main problem is that no one has developed a decent library that marries FantasyLand-compliant wrappers with Promise interop. There are about 8 million Task/IO mon
291.
by rmrfrmrf 9y ago
I just got there myself after thinking async/await would be all I needed. There's still a lot that can be done with generators, so I don't see them falling out of favor completely yet.
292.
by rmrfrmrf 9y ago
This isn't correct for native Promises. Native Promises flatten themselves out at the end of each tick and will do any synchronous work possible before either the Promise settles or there's something that needs to get thrown to th
293.
by rmrfrmrf 9y ago
This was a problem before native Promises, but not so much anymore. Throwing on unhandledRejection has been the default in Node.js >= 7 and browsers now have DOM Levels 1 and 3 events for unhandledrejection.
294.
by rmrfrmrf 9y ago
`throw` can throw anything. By convention, it throws Error objects.
295.
by rmrfrmrf 9y ago
Out of curiosity, why does the syscall rate scale descend from left to right?
296.
by rmrfrmrf 9y ago
"Science" doesn't say either of those things are safe. Studies (often paid for by the companies trying to sell the technique) say that the core concepts and techniques are safe. The problem is that side-effects are left out o
297.
by rmrfrmrf 9y ago
That happens on Reddit already, so no surprise it would happen here sooner or later.
298.
by rmrfrmrf 9y ago
Not nearly as abusive as const obj = { foo: 1, bar: 2 }; const propToDelete = "foo"; { [propToDelete]: _, ...newObj } = obj; newObj; // { bar: 2 } but will probably be more performan
299.
by rmrfrmrf 9y ago
YAGNI
300.
by rmrfrmrf 9y ago
According to the article, this is more about google's competitors strangling them (by being so intrusive that customers consider full ad blockers to be necessary).

More ›