Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jblow
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
58 ms
·
541.
▲
by
jblow
12y ago
If you want a further analogy, it's like public transit. Which is a better commute: You take Bus A, which then drops you off at the stop for Bus B, at which you have to wait a varying and indeterminate amount of time, because the sched
542.
▲
by
jblow
12y ago
I could type up a thorough explanation, but it would take about an hour, and I have a lot to do. It is actually not a bad idea to do such a write-up, but I don't think the appropriate venue for it is an ephemeral post on Hacker News ..
543.
▲
by
jblow
12y ago
As someone who has actually done a good amount of soft-real-time audio programming, I can tell that you probably haven't. Everything you are saying about CPU speeds is made-up nonsense. Look into how these things are done on systems wh
544.
▲
by
jblow
12y ago
But ... why is there a period size? Isn't that a broken design that can only introduce latency? What is wrong with "however much audio data is ready when the application asks, send it"?
545.
▲
by
jblow
12y ago
If you actually read the words in the article you will see that that test was the absolute best case they could find.
546.
▲
by
jblow
12y ago
This does not read to me like good advice from an experienced programmer.
547.
▲
by
jblow
12y ago
Nope. Nope nope. This is the same argument that early OO people used to justify the idea that you should use getter/setters everywhere rather than directly accessing your variables. You never know if the implementations of those ideas
548.
▲
by
jblow
12y ago
Yeah. I only heard about "dependency injection" a few months ago, and my reaction was that my brain just didn't get it, because, like, why are you making a huge deal about such a simple thing? If we made this much of a big de
549.
▲
by
jblow
12y ago
Before posting a question like this, please bother to look into the logistics involving the company (for example, their actual plans for scaling). They are a new car company. They do not yet have the capacity to manufacture at high scale, b
550.
▲
by
jblow
12y ago
Yes, everyone moved every frame. If I remember correctly, they would get linearly extrapolated until next time the update for that guy ran. I think there was also an option to do the terrain interaction every frame, to avoid any perception
551.
▲
by
jblow
12y ago
No, it's not really different from a hard-sphere type interaction. It's the same thing. But that doesn't matter in this context, because in the system we built, our problem was harder/more-general because we were simulat
552.
▲
by
jblow
12y ago
No offense, but you are living in a kind of unfortunate corner of "industry". Where I am sitting, you absolutely have 10 years (or more) to give toward a specific cause, and the path of the software developer is one of lifelong im
553.
▲
by
jblow
12y ago
Not really. Back in 2002 we did the first game jam where the engine concept was "100,000 guys". That was 13 years ago: http://www.indiegamejam.com/igj0/ Those guys all interacted with each other and the envir
554.
▲
by
jblow
12y ago
And Sony's new VR headset runs at 120Hz. To anyone who thinks 10ms is not noticeable, I encourage you to do the math.
555.
▲
by
jblow
12y ago
San Francisco, both AT&T and Verizon. It's terrible here.
556.
▲
by
jblow
12y ago
I don't even get 4G speeds almost ever. Bandwidth is always massively oversold. Often I can't even successfully load a random web page when I have 4+ bars of "4G".
557.
▲
by
jblow
12y ago
I am not sure I believe this. What studios have you worked for that found lack of source okay? Basically anyone making interesting games needs source, because at some point you want to do things that the engine didn't exactly anticipat
558.
▲
by
jblow
12y ago
Proposal made without any thought as to how scummy app developers are going to game the system. First thing that happens is opening a new development account per app in an attempt to squeak under the $100k as much as possible.
559.
▲
by
jblow
12y ago
I am not sure why Linux people tend to think this is bad. It is how you ship robust software that doesn't break. Linux "solves" this issue by having all kinds of things break all the time and just accepting that breakage and
560.
▲
by
jblow
12y ago
Kernels tend to want to be very specific about how memory is being used. GCs cause the opposite situation. i.e. these "specific requirements and limitations" you mention have a LOT to do with memory.
561.
▲
by
jblow
12y ago
Look, what you are saying just doesn't work. What happens when the pointers are in registers? What happens when the loop is occurring in a thread running on another core? Yes, you can make GC work in these situations, but you are going
562.
▲
by
jblow
12y ago
"any language should be able to generate the exact same optimized assembly as a manual C++ vector iteration" This is absolutely, massively untrue. If you try making compilers sometimes, you will see how very hard it is for compile
563.
▲
by
jblow
12y ago
I have great respect for anyone who undergoes a big project. So I am sad that this project is coming to an end, and I hope his future endeavors go well. But . From my perspective as someone who keeps going back to Linux and trying to use i
564.
▲
by
jblow
12y ago
My point is that you can solve this one symptom but your program will have many other problems due to GC (provided it does a lot of work). It is like whack-a-mole in that there are always more moles.
565.
▲
by
jblow
12y ago
It is only an implementation issue if it is possible to solve the issue. Nobody has ever built a garbage collector that does not slow your program down or cause it to use vastly more resources than it would otherwise. (Claims to the contrar
566.
▲
by
jblow
12y ago
Show me your commits where you've fixed lots of driver bugs. You sound like you have no idea what you're talking about.
567.
▲
by
jblow
12y ago
Which is why people who are serious about memory write their own allocators (or link preferred allocators with known behavior). It is an extremely common thing.
568.
▲
by
jblow
12y ago
It's bad. The reason is because you don't control the GC and don't even necessarily know what exactly drives the decisions it makes. So once you want to go beyond a certain level of performance, there is no right answer. You
569.
▲
by
jblow
12y ago
No, no it isn't. There is always some garbage velocity beyond which any given system is not able to cope. Usually that limit is kinda small compared to what you'd actually like your program to be able to do.
570.
▲
by
jblow
12y ago
When I think of what I want in an operating system, "I wish it would lock up occasionally while everything garbage collects" is not high on the list.
More ›