Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
yoklov
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
56 ms
·
511.
▲
by
yoklov
12y ago
Strange, I wasn't working that long ago, but most of what I've heard from people who have is that not having a degree was very common. This might be a game industry vs rest of software engr thing though.
512.
▲
by
yoklov
12y ago
Right, my point is that I typically don't really want to tie memory lifetime to object lifetime either. So the whole of RAII is not a great fit, outside of a couple edge cases.
513.
▲
by
yoklov
12y ago
Well, you can avoid using desctructors, but then you can't use the majority of the STL, so what's the point? (This is basically what I do anyway)
514.
▲
by
yoklov
12y ago
Haha, even if that were something I was interested in at all, I'm honestly not sure what you could do to fix it at this point. I think that ship has sailed. Most of the issues are library issues (and are far deeper than my complaints a
515.
▲
by
yoklov
12y ago
Is this true? That's a great piece of trivia if so.
516.
▲
by
yoklov
12y ago
Definitely, the programmers need to stay away from integration methods that introduce energy. Jeez, I thought everybody figured this out by now.
517.
▲
by
yoklov
12y ago
The allocator support in C++11 and, from what I've seen, the proposed allocator support in C++1y/z/whatever still leaves a massive amount to be desired. Polymorphic allocators solve what's basically a non-problem for gam
518.
▲
by
yoklov
12y ago
errno is supposed to thread local, so it should be thread safe.
519.
▲
by
yoklov
12y ago
Off topic, but does anybody know if there's a way to turn off ASLR e.g. while debugging (honestly, i'd be interested if you can do this on any platform)? I'm pretty confident the answer is no, but it can really be a pain some
520.
▲
by
yoklov
12y ago
Worth noting that the style of C++ most common (in my experience) in game development is pretty far from what is considered "modern C++11 best practices", and the modern C++11 style tends to be frowned upon. Thats not ubiquitous,
521.
▲
by
yoklov
12y ago
C++ in a lot of places. And systems programming is a much smaller niche now than it used to be.
522.
▲
by
yoklov
12y ago
Out of the box mobile browser support is a big one.
523.
▲
by
yoklov
12y ago
These days sqrt and rsqrt are so cheap that they aren't a worthwhile optimization target. You're much better off optimizing cache usage.
524.
▲
by
yoklov
12y ago
C++, you mean. There are no classes in C.
525.
▲
Personal Security for Programmers with Security Through Obscurity [video]
(youtube.com)
2 points
by
yoklov
12y ago
|
0 comments
526.
▲
by
yoklov
12y ago
I disagree. It's worth working things out from first principals as a method of practice, because when you have to do something completely novel, you won't be totally lost (If you never have to do this in your work, then I guess it
527.
▲
by
yoklov
12y ago
I've worked with a lot of these (I work in game development, where this sort of thing is fairly popular), and IMO they're not worth the significant runtime cost and software complexity required to integrate them. In my experienc
528.
▲
by
yoklov
12y ago
> it's Intel-specific Most platforms offer intrinsics. > it's a maintenance risk unless everyone in the shop knows how to write and maintain SSE code. This is understandable, but not the case where I work. If you need to be
529.
▲
by
yoklov
12y ago
Again, inline ASM is pretty rare these days (when we do use it, it isn't for SIMD). Intrinsics are much more common. The big issue (aside from convincing MSVC to implement it ;) with your suggestion is that, unlike TCO, vectorization i
530.
▲
by
yoklov
12y ago
The reason to use intrinsics and inline assembly (actually, the latter is pretty rare these days, intrinsics being much more common) isn't only about beating the compiler. When you're relying on the compiler to vectorize, you run
531.
▲
by
yoklov
12y ago
I'm going to disagree with most of the comments here which say that you can't become faster, as I have become notably faster over the past couple of years (perhaps 1.5-2x faster!!). Basically, it was a fairly major coding style ch
532.
▲
by
yoklov
12y ago
GitLab has been ridiculously easy to manage for us. Really my only complaint is that it's slow as all hell, and gives up too early on a lot of pages because of this. Still, compared to the Perforce server crashing every other week (a s
533.
▲
by
yoklov
12y ago
The Jeff and Casey show is probably my favorite: http://mollyrocket.com/jacs/index.html . It's hosted by the owner/founder of Rad Game Tools and one of their (now ex-) programmers (who has recently had minor f
534.
▲
by
yoklov
12y ago
Architecture astronaut isn't a term for starting projects and not finishing them. It's a term for people who overengineer or overdesign their system. Overengineering can lead to not finishing a project, but in the case of someone
535.
▲
by
yoklov
12y ago
What ryanthejuggler said is true (and mainly why even impressive ones aren't worth much), but mainly because game jam projects are usually unimpressive and made of gluing a bunch of things together. Totally ignore is probably stronger
536.
▲
by
yoklov
12y ago
Well, the biggest why of exceptions is that we want to be able to compile with exceptions turned off. And there are lots of reasons why not to use virtual functions or function pointers, but aside from 'it kills performance if used too
537.
▲
by
yoklov
12y ago
The first is probably the right approach, as the second comes off as unnecessarily condescending to me.
538.
▲
by
yoklov
12y ago
I've been criticized as being too harsh in code review before, and I'll try this. I'm not sure how to apply it in all cases though. Frequently the issues I see are coding standard violations... use of exceptions, bad use of v
539.
▲
by
yoklov
12y ago
FWIW, In the games industry it's fairly common practice to totally ignore anything a potential programmer made in a game jam (unless they carried it on afterwards). Feels somewhat equivalent, even though it's probably for differen
540.
▲
by
yoklov
12y ago
This is used in some dynamic language runtimes as a way to represent a compact (64bit) tagged union. It's known as nan-boxing, and a couple years ago most of the JS vms did it (in fairly different ways) but I'm not sure they still
More ›