
You can now follow me on: fosstodon.org/@astrofrog bsky.app/profile/astrofrog.t… I will no longer be posting from Twitter/X going forward 👋

Scientific software developer, lead developer of Glue, Astropy developer, open development advocate. BlueSky: bsky.app/profile/astrofrog.t…

You can now follow me on: fosstodon.org/@astrofrog bsky.app/profile/astrofrog.t… I will no longer be posting from Twitter/X going forward 👋

Excited to announce @aperio_software is hiring - come and work with @StuartMumford @DrewLeonard42 and myself on exciting open-source scientific projects! (we are involved in @astropy, @glueviz, @WWTelescope and more)
Aperio Software is hiring! We are looking for someone to join our team as a software developer to work on a variety of open source scientific software projects. See aperiosoftware.com/jobs for more details.

Come work with me! @WWTelescope and @glueviz are searching for a research software engineer eager to join a multidisciplinary team that's advancing the frontiers of scientific data visualization. Details? Details: 🧵 https://t.co/kBe9HuS7NI

When people said wildlife was doing well as a result of #lockdown, I did not expect to see a 🦊 building a ⛄️ in my garden 🤯

Ministers apparently not familiar with the Cobra effect... (en.wikipedia.org/wiki/Cobra_…)

I almost feel like some people have misunderstood something I wrote on Twitter and/or are distorting what I am saying when quoting me. But that shouldn't be possible, right?!? 😱🤣

And yes I know that upgrading to the new Apple hardware is far more risky - in fact it is almost guaranteed to not work smoothly unless all you do is browse the internet and check emails!

Epilogue: yes, I know that upgrading to Big Sur might work just fine for some, but I also know that it has broken things for others. The key message here is that by upgrading *this early* you are taking unnecessary risks (and this is true of every major OS X version)

That's all I had to say. Thank you for coming to my TED talk. (13/n)

So the bottom line is to wait a bit - at least a few months, if not more. Maybe a better way to think about it is to update once you actually need to, rather than when things are new and shiny! (12/n)

Likewise, while the new Macs are supposed to have blazing fast processors, things are only faster if they work, and some of your favourite research software won't work. (11/n)

Your research computer should be a stable work environment. There is very little in Big Sur that you actually NEED to be a more productive researcher. So resist the temptation to upgrade until you know that your favourite research software will actually work on it. (10/n)

If you want to blame anyone, blame Apple for yet once again creating a lot of extra work for developers - especially for people who volunteer time to maintain open source projects. (9/n)

If you upgrade now, you will likely be frustrated at the number of things that will break or not work anymore - and you will likely be angry at the wrong people, by blaming the maintainers of the packages you use. (8/n)

Python wheels (binary releases) of most packages won't work at all on the new M1 macs, and you'll find yourself suddenly having to build many Python packages from source. (7/n)

I know of several major Python visualization packages that in fact do not work at all on Big Sur at the moment, and users are running into issues even just installing Numpy in certain cases (github.com/numpy/numpy/issue…) (6/n)