hunterloftis

25 ms·

1. 181.▲
   by hunterloftis 12y ago

   Thanks! As with most software decisions, raycasters involve a tradeoff. They are related to voxels in that they impose constraints on what can be rendered. Voxels render grids in 3 dimensions while raycasters (typically) render them in 2. F
2. 182.▲
   A first-person engine in 265 lines of JS(playfuljs.com)

   528 points by hunterloftis 12y ago|97 comments
3. 183.▲
   Reinventing Code: software development as a creative process(medium.com)

   4 points by hunterloftis 12y ago|0 comments
4. 184.▲
   by hunterloftis 12y ago

   Engaging in unprotected sex with multiple partners while pretending otherwise with each is akin to playing Russian Roulette... with someone else's life. Man or woman, yes, that sort of behavior deserves a beating.
5. 185.▲
   by hunterloftis 12y ago

   > we should strongly prefer female programmers this sort of mentality will encourage (and validate) concerns that female programmers are hired (and retained) because of gender rather than ability.
6. 186.▲
   by hunterloftis 12y ago

   http://en.wikipedia.org/wiki/Russell%27s_teapot
7. 187.▲
   by hunterloftis 12y ago

   Added!
8. 188.▲
   by hunterloftis 12y ago

   I love how you're using a simple but effective dynamic LoD. I'm going to riff on this a bit with a first-person ground-level camera.
9. 189.▲
   by hunterloftis 12y ago

   Wow! Really fantastic. I've already linked to your raycaster; let me know if you build one that dynamically generates the terrain as well.
10. 190.▲
    by hunterloftis 12y ago

    Awesome! Thanks for the link.
11. 191.▲
    by hunterloftis 12y ago

    It can be run lazily in two ways: first, you can lazily add detail (ie, render down to a specific level of detail and postpone the rest); second, you can lazily build grid blocks out to the horizon (eg, for walking around a terrain first-pe
12. 192.▲
    by hunterloftis 12y ago

    Thanks for this! I've been looking for resources on building out lifelike macro-terrain-structures.
13. 193.▲
    by hunterloftis 12y ago

    I like Perlin in situations where its repetitiveness won't negatively impact the simulation, or as an additional layer of pseudo-natural-randomness on top of other algorithms.
14. 194.▲
    Realistic terrain in 130 lines of JavaScript(playfuljs.com)

    339 points by hunterloftis 12y ago|56 comments
15. 195.▲
    by hunterloftis 12y ago

    I disagree. Many of the posts on HN deal with marketing, copy, and focusing on business messaging vs technology as that's the difficult area for many. Viewing the results of a fellow technologist's efforts in this area is very use
16. 196.▲
    by hunterloftis 13y ago

    "relishing in having squirreled away knowledge from your coworkers isn’t productive or healthy." Did we watch the same video? In what way did you interpret the character's behavior as trying to "squirrel away knowledge?&
17. 197.▲
    by hunterloftis 13y ago

    On it!
18. 198.▲
    by hunterloftis 13y ago

    A primary goal of newton is to be accessible, simple, easily read JavaScript with a minimal build step, so I don't plan on moving to something like LLJS. However, I agree that GC friendliness should be a priority. I may implement objec
19. 199.▲
    by hunterloftis 13y ago

    Thanks for the link, I hadn't seen p2.js. Here are a few points for comparison: - p2.js is significantly more complete than newton - p2.js uses a rigid body simulation closer in principle to box2d, while newton uses a particle-and-cons
20. 200.▲
    by hunterloftis 13y ago

    Awesome, thanks. What do you mean though by submitting a single newton.js to github?
21. 201.▲
    by hunterloftis 13y ago

    It is! I'm the author of newton and didn't realize it was going to be published on hacker news. It's fast and simple but lacks some basic features I'm rounding out - plus it needs more examples and a test suite.
22. 202.▲
    The future of web gaming could be canvas; I learned a lot from this project(10k.aneventapart.com)

    3 points by hunterloftis 16y ago|0 comments