While I'm excited by such news, let's not jump from "things we don't understand" to "god/magic/aliens".
For now, it's "cool event we don't know how to explain". Good enough. Life is full of that and if we try to force label on it, we miss the fun of figuring out what's going on seriously.
I certainly can’t explain exactly what it is. However, a few facts stand out:
1. Detected object moves erratically at high speeds, with exceptionally high acceleration. Controlled translational and angular acceleration of the object occur in the footage.
2. Navy pilots in both encounters reported that the object was not visible at close range but only showed up on radar, in particular only on radar that was recently updated from a version released in the 1980s.
3. Testimonies were confirmed by multiple independent pilots, cleared by the U.S. Navy, and pilots were deemed to be mentally fit as they were later deployed to active duty in the Middle East.
Those are just facts from the case. Feel free to draw your own hypotheses or conclusions. I certainly had fun doing so. :)
There's no hard evidence that it was an actual physical (massive) object. There is evidence (mostly testimonial) that it was visible to radar, infrared and visible light sensors and the human eye.
Is there anything that has those characteristics and is not an object ? Yes, plasma phenomena are one example.
If a OS is actively sabotaging you, then yes, the only real solution is to replace it with something else. That's the simple and obvious solution.
The simplest way to do this is to not buy a phone with shitty OS in the first place. As in "Don't buy a phone from Xiaomi".
And when users complain about it you tell them that the problem is their phone manufacturer. If you can, of course, give them a work around so the app will work. But eventually they'll plug all the holes that allow for a functional phone. So it may not always be a option.
> tell them that the problem is their phone manufacturer
Despite this being true many will see is as an excuse, or worse just a plain lie, and leave you a 1* (or 0* if possible) review ranting about your attitude and bad coding. How dare you criticize their choice of device?!
I dislike a lot of black decisions and still use it for everything.
My aesthetic taste is less important than getting things done.
If you are not using it, stop arguing and nit picking about your preferences, we, as a community, have more important things to do. It will hurt only a little, I promise.
My team has a handful of junior data scientists that really don't have a lot of experience of coding "well". Black was super helpful in 1, getting people used to decent coding format and 2, removing any effort or discussion around formatting in PRs. I added the formatting to pre-commit and the rest is effortless.
I live in the Python bubble, so I haven't realized until this post that so few people knew about that.
This post is massively popular despite talking about a feature we had since Python 3.6, in 2016, that was posted on HN at the time and that is featured in most popular tutorials.
A good reminder that most of the world doesn't revolve about my favorite language. And that information is not that fast to spread.
> about a feature we had since Python 3.6, in 2016
No, you had that feature in one implementation. Now it's in the language specification. That's vastly different because only now you can rely on it without fearing it can go away with the next release.
First, cPython is 99% of Python deployments. So much that if a script works on it but not on another implementation, people often consider the later broken.
As this post proves that most people don't even know about this feature, you can be pretty sure the vast majority of people don't know about pypy, micropython, etc.
Secondly, even if you want to nit pick, Python 3.7 made it official more than one year ago. We are currently in the 3.9 alpha.
In fact, 3.7 didn't touch the implementation, just merely declared "yep, good idea, let's keep it that way".
There's also the indication that this is official, and not just an implementation quirk. I still used OrderedDict in 3.6 because there was no guarantee 3.7 (or later) wouldn't silently break ordering on the standard dict. At least now it's unlikely to change because it will be considered a breaking change.
BDFL declared Python dict to be ordered in 2017 — It can't be more official than that for Python https://mail.python.org/pipermail/python-dev/2017-December/1...
i.e., Python 3.7 (whatever implementation must keep the insertion order). CPython keeps the order since Python 3.6. Pypy even before that.
I knew about it, because everyone was talking about it.
The origination of the actual information is irrelevant. It was basically interesting gossip for a few weeks.
There's a great talk by David Beazley[0], which I don't remember its title right now, where he bashes all previous python versions except the latest at the time[1], which was 3.6. And he says "since I'm not a core developer, I can tell you this: rely on dicts being ordered so much that eventually they'll make it official". Guess he "won" in the end ;)
[0] Well, he usually gives great talks anyway
[1] Alright, he literally started many talks doing that
Raymond Hettinger does or did a few talks on dictionaries too. He covers the history of dictionaries in python and how they evolved. It was mentioned in the article's comment section.
I have lived in Python ~80% of my career (~50% now) currently), although a large chunk of my career was writing 2.7 compatible with 2.6 (thanks RHEL). For the last year and a half I have written 3.6+ exclusively and I didn't realize that regular dicts were now ordered.
I don't use dicts if I require ordering, but if I did I would probably still reach for collections.OrderedDict...
I wonder what the implications are of dict ordering with the "new" (new for me...) function args and *kwargs...from the hip it sounds pretty handy.
The implications are that now you get to see the order in which keyword args were specified by the caller. And in classes, you get to see the order in which attributes were defined. Both can come in very handy.
If there are no security problems affecting your project, and you don't benefit from new features, there is no urge to update. And even then, it's a cost/benefit ratio.
Updating is a constraint, one you follow either because it solves a problem or avoid a pitfall, not a goal.
I migrated most of my stuff to Python 3 years ago, but for some of my clients, despite that 2.7 is not supported anymore, I advice to just download a copy of everything they need offline as a safety measure and keep the system running as-is forever.
Raw HTML + jQuery + Django 1.x + VPS still deliver fine. Just because I can do react + microservices does not mean it should be a default response.
There are servers running barely touched from one or two decades ago and they do their job perfectly.
So yes, some client side libs are going to be there for years and years. If the UI works, it's alright.
Software is not an end, it's a tool. Being passionate about it, it's easy to forget that, but we use software to help the real world, not the other way around.
Not saying of course you should never update nor use modern technology when appropriate: technical debt must be paid. But it's important to recognize when you need to do it, and when you just want a shiny toy or to look good.
Did that in Mali. It did give me perspective after 2 years, but it didn't fix my narcissism. Just made me more tolerant to incomfort, and made me enjoy civilization more.
I've also experienced physical hardship which helped me to become far more patient and tolerant of physical hardship, but not at all more patient or tolerant with people.
I think it's a mistake to treat 'humility' as if it was one thing.