yoklov

61 ms·

541.
by yoklov 12y ago
Please. I've struggled with ADHD for most of my life, and while it probably does have an effect on both my work and my code, this is not the effect. Don't make broad generalizations based on the pop culture definition of mental il
542.
by yoklov 12y ago
No. There are 4-5 common approaches. - Macros, as you see. - Writing a generic implementation that takes a void* (or suitable "any" type). This has many, many drawbacks... no type safety, poor performance, frequently requires allo
543.
by yoklov 12y ago
Honestly for well designed modern-ish renderers this sort of thing tends not to be as big of a deal as it might sound. In general most of the additional steps are things people already do. e.g. you shouldn't be deleting textures that a
544.
by yoklov 12y ago
> when's the last time an indie game directly programmed against DirectX or OpenGL (barring webGL)? I don't work in indie, but my understanding is that this is still pretty common, especially for games with any budget at all.
545.
by yoklov 12y ago
They seem to mention this at the end of the slides.
546.
by yoklov 12y ago
Very cool. Sadly, the link to the interactive demo seems to be broken.
547.
by yoklov 12y ago
> How is making a returning a new dynamic array worse than doing a O(n^2) implementation Avoiding unnecessary allocations can easily mean the difference between missing a frame and not. Keep in mind that we frequently have to deal with b
548.
by yoklov 12y ago
ISPC is cool, what it helps out with (writing the SIMD kernel) has never really been the bottleneck in my experience. The data still has to be arranged optimally for the hardware in order for SIMD code to have any benefit (and at this point
549.
by yoklov 12y ago
Thanks for this link. A lot of these things were things I've grown to believe from working in game development (and listening to programmers better than myself), but I never had seen it written out as competently and thoroughly as this
550.
by yoklov 12y ago
Aside from logging (and games don't typically do a lot of logging), everything you mention is covered, and argued against, in the article.
551.
by yoklov 12y ago
Unfortunately, a lot of bugs can be caused when a function that was only ever intended to be used from a single place gets called from another place, when it seems to do the needed work.
552.
by yoklov 12y ago
I'm not sure I've ever interviewed anybody who can't program at all , but a large number of people I interview are shockingly bad. My go-to question to detect this is to remove the odd numbers from a dynamic array of integer
553.
by yoklov 12y ago
Uh, can we... not? Not sure how people think this will end up being anything but awful for the human race (Paperclip maximizer[0] and all that). On the bright side, I think 10-20 years is hilariously over-optimistic, given that it's a
554.
by yoklov 12y ago
Actually I'm pretty sure the feature overlap of this and GitGutter is nil. GitGutter shows you the diff in the sidebar, whereas this is a general git usage tool (closer to SublimeGit), that has per-line staging (e.g. run git add on onl
555.
by yoklov 12y ago
I bought SublimeGit a while ago, and have been reasonably happy with it, but this looks much better (and has many of the features I would have wanted from sublime git). How stable/well tested is it?
556.
by yoklov 12y ago
Worse than average for the game industry? I'm making less than 60k over here :( (But honestly I'd rather do something I enjoy and make less than something I don't even if it pays more)
557.
by yoklov 12y ago
> All three "just worked" with absolutely no surprises Jeez. That's pretty incredible. As someone who absolutely hates dealing with build configuration it's almost tempting enough to take a closer look at go, despite
558.
by yoklov 12y ago
Long compile times are bad user experience, and language design influences this. Performance is also extremely important for language ux, and there are certainly constructs that will prevent your language from ever being efficient. Someone
559.
by yoklov 12y ago
That's true, but more people thinking about a problem makes breakthroughs more likely.
560.
Google, Our Patron Saint of the Closed Web(sealedabstract.com)
297 points by yoklov 12y ago|94 comments
561.
by yoklov 12y ago
Navmeshs are pretty common these days. My perspective is that they're much more common for high end games than any other technique (nodes, grids, ...), but that might just be because we use them at work.
562.
by yoklov 12y ago
C++ std::shared_ptr does the same thing as ARC (reference counting based on scope/lifetime). Rust probably has something similar in it's standard library. FWIW I wouldn't use reference counting in game development if I could
563.
by yoklov 12y ago
Speaking as someone in the game industry, Valve certainly has it's problems, but they aren't platform problems. PC is stronger this generation than it was last generation, I'm not sure about the numbers but I suspect that it
564.
by yoklov 12y ago
Most people take it to mean "Don't optimize if you don't need to", but he actually means it as "Don't optimize until you know which parts are slow". The missing context is where he talks about (or implies,
565.
by yoklov 12y ago
> Disadvantages: None. Well, I'm convinced.
566.
by yoklov 12y ago
Sort of. The big difference is that forth is still reasonably widely used. Much more so than factor, not that they target the same domain.
567.
by yoklov 12y ago
Are you experienced with the language? I can't parse it either, but I don't know if "readability for a beginner" is a metric I care a whole lot about in a programming language.
568.
by yoklov 12y ago
To add to the (at this point rather large list), Haxe[0] allows this, although it prefers that you don't use the string-based method (which IIRC the docs, outside of the API reference, don't really mention, but does exist), but in
569.
by yoklov 12y ago
IIRC Braid made a couple million. I think less than 10 though. Minecraft, OTOH, made Notch over a billion dollars. So it depends on your definition of truly rich .
570.
by yoklov 12y ago
This is too clever to the point of being painful. (Not to mention, it has a performance penalty for no real benefit.) I think I'd just give up and go home if I ever saw this in code I had to maintain. EDIT: Actually, looking more close

More ›