Negitivefrags

The notion that there is no point saving money because the total amount of debt is high is effectively saying that the problem can never be solved.

A billion dollars is still a billion freaking dollars.

I encounter the same attitude sometimes with program optimization too. Sometimes it’s death by a thousand cuts and you just need to shave off 0.1% at a time until your program is fast.

I find it funny how often people look down on SVN outside of game development. It really is a great tool for that job.

The trunk our of studio's SVN is hundreds of GB and the full repo is many TB. And SVN handles this no problem.

Every car that is sold retires an old one. And the one it retires will be the least valuable.

This happens becauase the person who buys a new car sells their old one to someone else, who sells their old one to someone else, and so on down the chain.

The oldest cars from America go to other cheaper markets replacing the cars in use there.

This isn't really what the article is about, but I don't think that the term "Greedy algorithm" means what the author thinks.

Greedy algorithms are about making locally optimal choices.

They are not "brute force" algorithms or inefficient ones.

In fact, greedy algorithms are almost always faster. They are faster because they consider only local information instead of the entire data set. In exchange for that, a greedy algorithm may produce non-optimal answers.

The other day I made a reference to something from Jurassic Park at work to a fresh graduate, and got a blank stare. So I say "You know, from Jurassic Park". And was told "Oh, I've never seen it".

I have never felt older than in that moment.

On windows at least you can use a code signing certificate in your build tooling and ask the OS to verify any binaries that you download. Just make sure you use a timestamping server for your code signing or things will break when the certificate expires.

The source data is indeed from screen space, but this generates a full 3d data structure by ray marching the depth buffer. Its not using the 2D algorithm. In PoE2s case, it doesn’t need to go further since light sources are not usually going to be behind the camera.

You can gather data in other ways.

This approach was originally developed by Alex Sanikov for Path of Exile 2.

Of course in PoE2 it's used in full 3d.

The benefit of this approach is that you get global illumination with a constant cost for the entire scene and because it doesn't use any temporal acculation, it has zero latency as well.

This means you can rely on it as the lighting for fast effects. For example: https://www.youtube.com/watch?v=p1SvodIDz6E

There is no traditional "lighting" added to these two effects. The light on the nearby surfaces is indirect light from the GI solution that you get for free by just spawning the particles. That means all effects just naturally emit light with no extra work from artists.

On my GPU (which is admittedly a 4090) the GI solution runs in 0.8ms for a 4k scene in "High" quality. This is exactly what it will always cost, no matter what scene you choose.

You could select which storage approach on a per table level. That way the new characteristics don’t surprise anyone.

If you think that’s bad let me tell you about the time we ran into a bug in memmove.

It had to be an unaligned memmove and using a 32 bit binary on a 64 bit system, but still! memmove!

And this bug existed for years.

This caused our database replicas to crash every week or so for a long time.

It can be harmful. In GCC while compiling a 32 bit executable, making an std::map< float, T > can cause infinite loops or crashes in your program.

This is because when you insert a value into the map, it has 80 bit precision, and that number of bits is used when comparing the value you are inserting during the traversal of the tree.

After the float is stored in the tree, it's clamped to 32 bits.

This can cause the element to be inserted into into the wrong order in the tree, and this breaks the assumptions of the algorithm leaidng to the crash or infinite loop.

Compiling for 64 bits or explicitly disabling x87 float math makes this problem go away.

I have actually had this bug in production and it was very hard to track down.

None of that matters if you already bought the H100 and have no use for it. You might as well recoup as much money as you can on it.

The main concern with this is how do you actually get the records of what the cost basis was from someone who is dead?

The usual way this happens is accidentally logging passwords. Or even other cases where passwords happen to be included in something else. It can happen more easily than you think.

Like for example, if you collect server side crash dumps, are you really taking care that there is no sensitive information sitting in the memory image stored in them?

What I don’t like about this argument is that this was originally pitched in the initial video as “All you have to do is release the server you already have, you don’t have to do any extra work”.

And I took that to mean that you just have to provide the server binaries and no support for them.

And fair enough, as a developer of a large online game myself, could get behind that.

But the moment this extends to needing to find solutions for people to be able to actually run it, I would withdraw my support.

I can’t view a video at the moment, so I apologise if this has been answered in that.

If the server software a game uses requires a licence to a third party library, what is the developer expected to do about that?

The concept of doing something at runtime that could be done at compile time is anathema for c++ programmers.

In theory ReFS is the replacement. It hasn’t seen large uptake though.

People were saying things like "Why does twitter need 10,000 employees?" for years and years on end.

We are seeing a reversion to the mean.

It’s worse in a lot of implementations because often SMS is often used as part of a recovery flow in cases where you lose the first factor.

I find it more secure in some contexts to never give a company my phone number at all if possible, so that it simply can’t be used as any kind of authentication no matter what.

If we can’t even reliably know what the speed limit is, how can we even be close to self driving cars?

Not only is it a way simpler problem, but it’s actually a requirement for self driving also.

I think most databases have some method of turning your Reads into Write locks without needing to actually do a write.

Like SELECT FOR UPDATE.

I guess the market isn’t demanding a lot of mortar shells.

If they have fixed costs, why is it a percentage based fee?

Why not just be upfront with a fixed dollar value per year of fees for that part?

I found these videos quite hard to watch. There is a level of cringe that I found a bit unpleasant.

It’s like some kind of uncanny valley of human interaction that I don’t get on nearly the same level with the text version.

That langauge is C++. I almost never do manual memory management in that language, but you can do it if you want.

You care if you have a mortgage and you live in a non-US country where interest rates can actually go up to price you out of it.

I'm not convinced.

People don't say no to increased density because they are worried about increased overall housing supply affecting their house value.

They say no mostly because they like the place they are how it is, and they don't see any reason for it to change because the upside doesn't affect them.

And the rest of the time they are saying no due to a direct downside like having a new large building near them that wasn't there before.

I'm not saying that this attitude should be allowed, but let's be honest about the cause of it.

It’s interesting that you read an article that basically outlined all the structural supply and demand issues around why house prices are the way they are.

And then you turn around and blame the “home is your piggy bank” mentality.

Your preferences are the exact reverse of mine!