patsplat

9 ms·

31.
by patsplat 7y ago
In linear single player games lowering the cost of failure is a powerful way to encourage aggressive play. Games like Super Meatboy don't even make the player wait after death, encouraging the player to keep trying immediately. In mul
32.
by patsplat 7y ago
What a fantastic tool! A long time ago used unison to keep file uploads on 2x primary web servers[1] in sync. It worked like a charm. With IIS on Windows!
33.
by patsplat 7y ago
Agreed. I generally delete everything but the bold sentences.
34.
by patsplat 7y ago
Investing time upfront is only productive if one has ready access to a broad and relevant corpus of data.
35.
by patsplat 7y ago
So many problems solved by formmail.pl
36.
by patsplat 7y ago
OP does a poor job explaining what CGI scripts were. From the RFC linked in the OP: https://tools.ietf.org/html/rfc3875#page-23 CGI defined an interface between a web server and an executable that would provide a respo
37.
by patsplat 7y ago
Reading this on an Android phone... Some might argue it's an abuse of open source but it is Linux nonetheless.
38.
by patsplat 7y ago
From the article: > A ship towed the U-shaped barrier from San Francisco to the patch in September to trap the plastic. But during the four months at sea, the boom broke apart under constant waves and wind and the boom was not retaining
39.
by patsplat 7y ago
It's a bit unclear. So does OS/2 run on the turnstiles? Also my mom loved OS/2 Mahjong so it had a long life in my house growing up.
40.
by patsplat 7y ago
The result of this architectural pattern: https://vimeo.com/166807261
41.
by patsplat 7y ago
Learned as a junior: results matter Learned as a senior: stories matter
42.
by patsplat 7y ago
If your workload is summing 32 million float32s use foreach. Otherwise pay for readability with CPU.
43.
by patsplat 7y ago
It's the appropriate first choice. If things are slow, instrument and investigate. Only bother fiddling with Array.length if profiling with production workloads exposes that as the bottleneck. More likely the problem will be elsewher
44.
by patsplat 7y ago
Persistence is still slow, but is no longer a major bottleneck. SSDs are faster, but io and network is still slow. What has changed it is much easier for the client to be continually in touch with the server so that by the time the next &q
45.
by patsplat 7y ago
Use Linq and forget about array length. It's an interesting analysis and all, but why bother when the language has such an elegant collections API.
46.
by patsplat 7y ago
Double buffering is a standard rendering technique. It might be pure overhead but it won't look that way.
47.
by patsplat 7y ago
Thanks for the links, though I stand by my snark
48.
by patsplat 8y ago
Lol https://developers.google.com/protocol-buffers/
49.
by patsplat 8y ago
Not just Scala https://github.com/yellowblood/hocon-js
50.
by patsplat 8y ago
It's never to early to teach consent
51.
by patsplat 8y ago
Figuring drawing is a great first step to loosen up, relax, and practice seeing and abstraction. There's probably a class nearby. Photography, especially digital, is a great way to explore composition and narrative. And a key bit of a
52.
Ask HN: Design patterns for REST API integration?
1 points by patsplat 8y ago|0 comments
53.
by patsplat 8y ago
The loading graphic may be more to prevent a Flash of Unstyled Content (FOUC) than to mask loading times: https://en.m.wikipedia.org/wiki/Flash_of_unstyled_content Single page apps have quite a bit of control over rend
54.
by patsplat 8y ago
Found these links helpful: https://en.m.wikipedia.org/wiki/Satisfiability_modulo_theori... https://github.com/Z3Prover/z3/wiki/Slides Appears to be useful for static analysis and verific
55.
by patsplat 8y ago
Not sure why this was down voted. Squash’n’Merge on Pull Request keeps master history clean while tolerating sheninagins on feature branches. If important things are lost then perhaps the PR was too large.
56.
by patsplat 8y ago
This seems to be more a benchmark for ClosureScript rather than "the web"
57.
by patsplat 8y ago
the analogy to "distributed CGI" is on point
58.
by patsplat 8y ago
that sounds like an interesting architecture and problem set but don't see how 'serverless' would help
59.
by patsplat 8y ago
Please, share the use cases where serverless is the optimal choice. Because I've tried it. For problems like thumbnail generation which is literally the canonical example [1]. And even in that case, found myself switching the workloa
60.
by patsplat 8y ago
Serverless applications suffer from a few under reported drawbacks: - Local development is complex. Does one provision a full cloud environment per developer? Emulate a cloud environment locally? These are solvable but it's a grind o

More ›