Rectangle (and spectacle before it) is one of those absolutely essential tools for me when working on my mac. I didn't realize how essential it was to my workflow until it was accidentally disabled a few days ago and I struggled hard to use my laptop.
Happily donated to the author of an app so essential for my day to day productivity to show my gratitude for making it and making it open source. If the author happens to read this: thank you!
The history of the relationship between Mesos and Docker is definitely an interesting one. If memory serves right, Mesos was not keen of supporting Docker as a containerizer. The devs wanted to stick to improving the Mesos containerizer.
In the end, the community was so vocal about Docker being supported in Mesos that it happened, but the end result was not stellar by all accounts (and a bit of a nightmare to deal with on the framework side to boot).
I'm not privy to what was going at the time since I was just part of the larger Mesos community, but looking back, can't help but wonder what would have happened if they collaborated instead.
> A prof doesn’t care about athletic admissions (those are undergrads anyways?).
This gets into a tangential issue but I wouldn't be so dismissive of the consequences.
Where I went to undergrad the university had invested a lot of money in bringing their basketball team to NCAA Division I.
The program ended up doing a lot of shady stuff to recruit good basketball players, many of them which were discarded from other universities due to their inability to meet academic standards at their institutions.
Guess what happened?
Softball courses created for the athletes (someone has to teach them).
This was followed by rumoured intimidation of instructors by coaches who had the immediate backing of the university's president (who has the power to make your job/life miserable).
In practice, most of those who took the grunt were lecturers but this wasn't a household even name for sports, just some ego driven project for the president of a public university.
Having been a student during that team and paying attention to the reports that came out, I wouldn't discard the possibility of a professor being caught up in major politics as a result of the athletic admissions, so I wouldn't be so quick to dismiss it as a downside.
For the record, and not that it even matters, I was an academic.
I have an open source project that moved from using Jira to track issues and changes to Github. Before, when the project made a release, it would fetch info from Jira to create a changelog.
With this tool, I was able to do something similar using Github as the source of information instead[1].
I fetch the info using the gh tool, output the result into json, and use a python script to format the output which results in a decent looking automatically generated changelog[2].
It's not the most exciting thing, and I could have probably achieved it in a different way using the GraphQL API directly, but for the needs of the project this fit the bill and let me get on with the release.
I had similar feelings when I was hired to write in Go about 3 years ago. Coming from Java where everything (including the kitchen sink) was available for import, it took some time to re-adjust my mindset of having to seek out libraries and thoroughly vet them.
After a while, I kinda started to dig having to do it. You end up having a more personal connection with the dependencies you pick which makes it easier to contribute back upstream.
The one downside of being around in this stage of a language's ecosystem development is you can potentially get some pretty undesirable fragmentation.
A good example that comes to mind is one of the original Go library to interact with Zookeeper. There's like 6 maintained forks of that library due to the original author bowing out of maintaining it.
If you download a package that supports go mod and try to build it, it'll automatically try to fetch dependencies through proxy.golang.org
You can override the proxy, and there are open source implementations of the module datastore[1], but it's not made clear front and centre to the end user that building software will call a Google owned service.
It was a source of contention for some when the default toolchain moved in this direction.[2]
Disclaimer: I'm was part of the Apache Aurora PMC before the project went into the attic.
Not sure what you mean by declarative infrastructure but eventual reconciliation has been implemented in at least one other project (now retired) called Apache Aurora[1] which runs on Apache Mesos[2].
Twitter ran (and probably still runs) a combo of these to huge scale and great success so I don't think it's fair to say that there's nothing else around that does that :).
K8s is great, but we should be careful not to rewrite history.
Happily donated to the author of an app so essential for my day to day productivity to show my gratitude for making it and making it open source. If the author happens to read this: thank you!