←
Thomas Robitaille 🇪🇺4,577 posts
Thomas Robitaille 🇪🇺 avatar

Thomas Robitaille 🇪🇺

@astrofrog

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

◷ Joined April 2009▧ 309 Photos and videos
Thomas Robitaille 🇪🇺 avatar
Thomas Robitaille 🇪🇺@astrofrog·7 May 2021

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.

Peter Williams (hibernating) avatar
⟳ Thomas Robitaille 🇪🇺 retweeted
Peter Williams (hibernating)@pkgw·11 Mar 2021

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

Thomas Robitaille 🇪🇺 avatar
Thomas Robitaille 🇪🇺@astrofrog·22 Nov 2020

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?!? 😱🤣

Thomas Robitaille 🇪🇺 avatar
Thomas Robitaille 🇪🇺@astrofrog·22 Nov 2020

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!

Thomas Robitaille 🇪🇺 avatar
Thomas Robitaille 🇪🇺@astrofrog·22 Nov 2020

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)

Thomas Robitaille 🇪🇺 avatar
Thomas Robitaille 🇪🇺@astrofrog·20 Nov 2020

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)

Thomas Robitaille 🇪🇺 avatar
Thomas Robitaille 🇪🇺@astrofrog·20 Nov 2020

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)

Thomas Robitaille 🇪🇺 avatar
Thomas Robitaille 🇪🇺@astrofrog·20 Nov 2020

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)

Thomas Robitaille 🇪🇺 avatar
Thomas Robitaille 🇪🇺@astrofrog·20 Nov 2020

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)

Thomas Robitaille 🇪🇺 avatar
Thomas Robitaille 🇪🇺@astrofrog·20 Nov 2020

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)

Thomas Robitaille 🇪🇺 avatar
Thomas Robitaille 🇪🇺@astrofrog·20 Nov 2020

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)

Thomas Robitaille 🇪🇺 avatar
Thomas Robitaille 🇪🇺@astrofrog·20 Nov 2020

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)