A lot of what the other comments have said is right, but also add that to on top of all the layoffs theyve had and they keep telling their devs to double their efforts. Its been in so many meetings that at this point a single engineer should be able to do the work of the whole company…

the shareholders keep demanding doubling pace from their engineers but they just wont listen smh

They should just fire all the engineers already theyre clearly slacking off /s

I just stated python’s color in the graph cause it wasn’t in the legend. Nothing more.

It has dominated for the past 16 years

OP certainly has a funny definition of the word dominated.

green is python

Is that accurate though? Assume a satellite is in a decaying orbit (thus too low to contribute to Kessler syndrome on its own) and another satellite is in a different orbit eccentricity-wise but they both collide. Are we certain that none of the pieces from the collision would acquire enough speed to become boloids that contribute to Kessler syndrome?

Time to go down the rabbit hole that is orbital mechanics for me again. Byeeee lol

Edit: looks like the lowest orbit for starlink’s first shell is at 550km which is very much above VLEO and would definitely be a factor in Kessler Syndrome.

Most starlink satellites are set to deorbit themselves upon failure to avoid this. However the de orbiting could still fail and then it should take about a year or so to deorbit itself?

So it looks like there is a low possibility of it initiating Kessler syndrome. But it’s not negligible.

Down vote cause no arch. (no I didn’t.)

But in all seriousness, don’t use arch as a Linux noob.

Agreed, ai slop is stealing all the attention.

The lines between fact (…) and opinion can be blurry at times

Are they though?

Pretty sure that would count as monopoly as well and the sale wouldn’t be approved.

That… Somehow makes it even worse.

This doesn’t make that behavior any less scummy, but have you tried using any Google website on a browser that isn’t chrome?

So your logic is that since we already have some toxic we should just go ahead and make it more toxic?

I used to work in a really big project written in C and C++ (and even some asm in there) and the build was non-deterministic. However the funky part was there was a C file in all of this that had a couple dozen of commented nee lines with a line at the top saying: ‘don’t remove this or the build will fail’ That remains my favorite code comment to this day.

I don’t have a great solution for this particular problem.

However any solution that you come up with has to be resilient enough that the nodes that execute such scenario are always available.

You don’t just want a system with high availability, you want a system that will stand the test of time. For example, it might trigger 30 or 50 years from now. You might not want to use AWS or Google or Azure or any sort of system like that. They don’t seem to keep their solutions available for that long. So you’ll need to host something yourself and make sure it’s resilient to a multitude of scenarios that might bring the “back end” down.

You’d also need to set-up some sort of test for the system to make sure it’s still running and it’ll do what you want it to. Maybe it runs every 3 months or so like a fire system drill.

Honestly the trigger can be something as simple as you hitting a button connected to your system every week with a way for it to ping and prompt you to do it you if you haven’t “reset” the counter in a timely fashion.

I would probably do something like that with a weekly cadence and a whole other week to make sure I don’t miss the reset.

You probably also want to be able to set it to different modes if you think you will be away for a while. Like a vacation mode or oh shit I’m in the hospital mode.

Additionally, I also wouldn’t be as fatalistic as sending goodbyes to everyone. I would use it more as a system to sound an alarm that I’m not okay and something has happened to me and communicate that with people who could do something about it. Like verify if I’m alive or not, or contact local authorities to post a missing persons report.

This same system of notifying could also allow closer people to me to trigger an “oh shit I’m dead mode” which would then execute whatever is in that idea of yours.

These are all situations that you would want to alert your loved ones though. And the power outage one will probably be solved faster than your switch hopefully.

At least what I see with this experiment/article is that is overly verbose, he takes a long time to get to the point. And then when he does his methodology shows an experiment that cannot be verified. Even when something is “subjective” we can still draw conclusions from it if we set up proper non-subjective ways of evaluating the results we see (ie. Rubrics). The fact that he doesn’t really say what leads him to say in detail what is a “terrible/v. bad/bad/good result” is a massive red flag in his method.

After seeing that, I no longer read the rest of it. Any conclusions drawn from a flawed methodology are inherently fallacies or hearsay.

If in any case it is further explained in the article and that somehow refutes what I’ve postulated later on, then I would have to say that the article is poorly written.

All this to say… I agree with you, not worth the read.

That was the point. That’s what the whole daughter’s plot is about.

Missed opportunity for toiletarian paper