If they made the headline something on the line of "replacing protobuf with a native, optimized implementation" would not get the same attention as putting rust in the title to attract the everything-in-rust-is-better crowd.
That never happens. Instead, it always attracts the opposite group, the Rust complainers, where they go and complain about how "the everything-in-rust-is-better crowd created yet another fake headline to pretend that Rust is the panacea". Which results in a lot of engagement. Old ragebait trick.
It's devbait, not many of us can resist bikeshedding about the title which obviously doesn't accurately reflect the article contents. And the article contents are self-aware enough to admit this to itself too, yet the title remains.
Incidentally, when I last played Banished there was a loophole in its simulation and you could just build a few modules consisting of like 3 or 4 basic buildings and that solved all your survival problems with no need for later intervention.
Medical? What's the point? I'm happy with 98% of doctors being able to handle known conditions and only the few percent that are really interested to do research.
It makes the university look better if they do a lot of 'research' even if it's fake. There's not a real reason a doctor needs to do research for an MD.
He didn't need 8 hours, but zero didn't work. The us and india are about 12 hours apart (there are 4 times zones in the us, day light savings time, and india is offset half an hour, but it rounds out to 12 hours for discussion)
> If you needed 8 hour overlap you were micromanaging?
...ok. I didn't need 8 hours of overlap.
As I mentioned in my first comment, I've also now done US/EU and EU/IN. Both of which have only partial overlap and things have gone well.
With US West Coast and India, I was often doing meetings at 7AM and my devs were doing meetings at 9 or 10PM. That was challenging, irrespective of any cultural differences.
I'm big on user first, if that dialog had sirens blaring, a gif and ten arrows pointing that "THIS MAY EXECUTE CODE" and people still didn't get the idea, I'd say it needs fixing. It can't be said that they didn't try or that they hid it though.
So at the end of the day its still unclear whether it executes code or not? Just say "this WILL execute code" and specify exactly which code it tries to execute by default.
I don't know about you people, but I always read this as "it may execute code if you run a build step".
Not "I will execute autorun.inf like an idiot."
And NO. I do not want my IDE to execute code when i open files for editing. I want it to execute code only as part of an explicit step that I initiate.
> with a single and simple set of rules that will apply seamlessly all over our Union
For one, I'm worried about what simple means. Likely something that will not make it as cheap to operate in every EU country, but make it as expensive to do that.
Also, whatever the EU commission/council/whatever they call themselves in order to not call themselves government decides has to be translated into local legislation by all member countries. So it will get twisted in 27 different ways, some of them incompatible. Also 9 of the 27 will take years to finish the process.
> For one, I'm worried about what simple means. Likely something that will not make it as cheap to operate in every EU country, but make it as expensive to do that.
I mean, if that's the case, no-one will use that structure.
In general, having a single set of rules makes things cheaper. That is the whole basis of standardisation.
> Also 9 of the 27 will take years to finish the process.
They're trying so hard to not call themselves a government that they renamed everything so it doesn't sound like what a government does. Maybe they should start with fixing that...
For the record i am in the EU and I think the EU is generally a good thing. Doesn't mean the "commisioners/ministers/whatever" couldn't use a few kicks to bring them more down to earth.
Remember the attempted EU constitution? They discovered at that point that looking too much like a government made the nationalists _very_ upset, so it was recast as the Lisbon treaty (not a constitution, we promise!). A lot of the can't-believe-it's-not-a-government stuff stems from that debacle.
We have soft_deleted as boolean which excludes data from all queries and last_updated which a particular query can use if it needs to.
If over 50% of your data is soft deleted then it's more like historical data for archiving purposes and yes, you need to move it somewhere else. But then maybe you shouldn't use soft delete for it but a separate "archive" procedure?
Checking whether `deleted_at is null` should be extremely cheap, and it avoids the duplication and desynchronisation of having both “deleted” and “deleted_at”.
They changed the persistence system completely. Looks like from a generic solution to something specific to what they're carrying across the wire.
They could have done it in Lua and it would have been 3x faster.
reply