strictfp

There's also Minecraft NBT. It's a bit obscure but quite nice. https://minecraft.fandom.com/wiki/NBT_format

Another big problem was that you rarely want exactly the same code on client and server.

Speculation is a problem for sure. I think USA is experiencing the burn for not being the number one financial power anymore. If the global market is hurting you, you'll need to protect yourselves by regulation. It's easy to be pro-globalization when you're king of the hill, but not always so great when you're getting the short end of the stick.

Oh, and I didn't know about the Vienna model, but Stockholm tried to massively expand housing in the 60s in something called the Million Program, as so many others did. Although that solved the immediate problem, it has been a catastrophy for the cityscape.

Isn't lack of housing sort of a side-effect of the very concept of a city?

I live in Sweden and I can tell you that it's not so clear-cut. Rent control means that people have to queue for many years for decent rental apartments.

We also have a lot of black market labour. The unions have historically had a strong grip, but are under attack by political forces that want to undermine that market with unskilled workers.

And on top of all this I think that people simply always prioritize living expenses above all else. As long as there is less supply than demand, prices are going to rise until some are out-competed.

People will have to pay, either with their time or with their money.

Having tried many techniques for program-to-program interfacing, I must say that text still is the lingua franca, and I think it's the best "non-standard" to set.

I've seen bad user input, one very unusual char, bring down a whole self-healing geographically redundant cluster of machines running an expensive commercial cluster software. Any connected devices can bring each other down.

I think the anonymous internet was way better. People tend to group anyway, so it's not like everyone is forced into the same room.

I'm familiar with how they operate and my opinion is that they screwed it up by hiring too many devs and setting up the teams based on software components.

Very hard to get anything meaningful done.

Maintain a backlog for them, at least an idea backlog

The whole idea behind Node.js was to write a super-efficient completely nonblocking http server in C, while keeping all the business logic in a simple scripting language.

You should not expect the Node.js parser to be simple.

Interesting! As by pure chance, my current project already incorporates EnTT, so I will definitely give this a closer look. Thank you.

Agree. The movie industry hasn't been disrupted in the same way that Spotify disrupted music distribution. The same balkanization used to happen with music licenses. Spotify disrupted that by simply pirating and offering the record companies a piece of the cake after the fact.

Someone would need to pull something similar with the movie industry.

Put AJAX back in the bottle.

That's true, but you can get all that without taking over the entire system. Upstart was a more lightweigh contender to systemd which would give you all that but none of the "Enterprise Linux Userspace Daemon" crap.

Yup,and this is excerbarated by the fact that c++ doesn't really offer any convenient equivalent of virtual methods with static dispatch.

std::variant is almost it, but it's interface is quite horrendous as of now.

Another interesting thing is that c++ also intermingles dynamic allocation with polymorphism, which can lead to a lot of unnecessary pointer chasing

I'm also involved with Microsoft, and my view is that the culture is to move on to the next goal too soon after the next gen solutions have been developed.

So they make control panel 2.0, reach 70% coverage, launch, and never move the remaining features into the new version so they can sunset the old one.

Love this. I also have a silly question; is the sunset commission subject to the same principle?

I wanted to show support to the engineers in the sense that I don't think you should encourage a working culture where you have "massive post-mortems" and expect people to feel bad for extended periods of time over simple mistakes. By not making a big deal out of it, you can also support your staff.

But I think our disagreement mainly stems from how we interpreted the parent comment. I thought it was very double, at one hand claiming to show support, at the other hand emphasizing how big of a catastrophy this was.

I just wanted to say that I think it most likely was a completely natural mistake, only exerbarated by the scale of the company, and that while you should take some action to prevent it in the future, you should not spend so much time dwelling on it. Shit happens, it's fine.

Yeah, that's my experience as well. I thought it meant "we have no idea what's going on" though.

Meh. Losing sleep sounds like an over-reaction. No system is foolproof. Of course Fastly should do what they can to prevent downtime, but it's still expected that they will go down.

I would blame anyone who claimed otherwise or couldn't deal with it while not having a fallback.

That completely depends on the specifics. If you expand your house with extra spaces or buy gadgets, you typically also lower security. Security always requires a principled approach.

Ah, Shopping Cart DB is at it again :)

Really? Google drive sync has been hot garbage for me. Before that program came everything was fine and dandy, but drive sync constantly stumbles over it's own feet, restarts and fails to up- and download files. I'm longing back to Rsync or even FTP after trying to use google drive to move data.

Maybe try wine? Seriously, it might be very low effort to get the binary to run on wine.

I would setup an async replication to another table or data source for the full-text search.

Reminds me of the hack of using auxiliary information such as AWS group metadata to determine ordering.

If there's already an ordering system in place, directly or indirectly, why not use it?

When working on networked control systems I realized that ordered networking is the reason why automation still uses proprietary protocols and interconnects such as Profibus and Profinet.

If you want good guarantees you need determinism.

That's not the whole story. IE was innovative (albeit through embrace and extend) until they won and stagnated.

It's not like the competitors are any better, in the desktop space at least.

The problem in my eyes is plateauing. Once a project moves past the first couple of iterations, it rarely interests the original authors enough to make incremental improvements. And since there is no financial incentive to continue, the project usually cools down to eventually be replaced by the following iteration. This means that you rarely get mature software.

Found out that QNAP have an official response with instructions, sounds like their malware remover should detect it: https://www.qnap.com/en/security-news/2021/response-to-qlock...