819 karma · joined August 1, 2014
Web: http://jonathangreen.ca Email: me[at]jonathangreen[dot]ca
Another part of our mission is providing libraries an open source ebook and audiobook reader called Palace. Our project is on GitHub here https://github.com/thepalaceproject.
1) Installing applications within Docker containers. While wheels have improved this situation, I was surprised that building a package for easy copying into a container and running without the need for installing build tools and extensions in the final container image was not straightforward, especially coming from other languages.
2) Distributing Python utilities to end users across various platforms in an easily installable manner without requiring them to follow lengthy instructions to set up all the dependencies has been another challenge.
We use Poetry and have largely "solved" #1 with a somewhat complicated Docker build. It works well now, so no one has to think about it much. That made deploying Python server-side fairly easy. However, #2 has been much more of a challenge, and I wonder if that is where other folks in this thread are feeling the most pain.
> If the price ends in a one, two, six, or seven it gets rounded down to 0 or 5; and rounded up if it ends in three, four, eight or nine.
https://www.cbc.ca/news/canada/canada-s-penny-withdrawal-all...
It's great to see the Palace Project mentioned as an alternative in this post! I'm one of the developers working on Palace. The idea behind the project is to create a single app that aggregates all of a library's digital content and makes it readily available to library patrons.
If anyone here is interested in it, all our code is open source: https://github.com/thepalaceproject.
https://status.zoom.us/ - All Systems Operational
Seems fine to me.
Edit: Looks like the status page says MAJOR OUTAGE now.
I think it would be fascinating to read the "First thing - read this" file on his phone. I can see why they don't go into more detail it would probably be pretty personal info in there.
Still as a mental exercise, its interesting to think about what I would write down in that file for myself.
[1] https://forums.macrumors.com/threads/16-is-hot-noisy-with-an...
There was an extension that did this, but the API it relies on was removed in FF 57 with the switch to the extension API.
> The government may steal a dollar, but it cannot erase the idea that earned it. I wrote this book, Permanent Record, for you, and I hope the government's ruthless desperation to prevent its publication only inspires you read it—and then gift it to another.
> The court's ruling is a hack intended to circumvent First Amendment limits on what the gov't can censor. They can't (yet) ban the book, so they ban profit to try and prevent such books from being written in the first place.
> "It's a prototype for sure," said McDougall, "but in every way it's a high-tech piece of equipment, which is kind of ironic considering the airframe that it's attached to is actually one year younger than me — 62 years old."
> McDougall's flight is the first exercise in what is expected to be a two-year process to get the e-plane certified for commercial use.
For some context Harbour Air is a scheduled floatplane airline operating primarily between Vancouver and Victoria in BC. Since there is no bridge connecting the capital Victoria to the largest city Vancouver, they offer short flights on seaplanes that connect downtown to downtown as an alternative to ferries or larger airplanes that arrive at the airports further outside of the downtown core of either city.
In this constrained context it seems like an electric airplane could work really well and provide fuel savings and a quieter ride. They also seem to have some ambition with these electric aircraft to provide other short range flights.
> MagniX CEO Roei Ganzarski said Dec. 10, 2019, will go down in history as the start of the electric aviation age, and believes the e-plane will eventually revolutionize how people travel by making short- to mid-range flights more economical than driving. "It means you can stop driving for three, five, seven hours to get to a destination because there's no other way to get there," he said. "It means you can fly in a small aircraft from a small airport to a small airport.... It's faster, cheaper and more convenient than any other method of travel, including going with a standard airline."
> The very definition of a contractor implies a contract. And a government contract starts with fixed requirements that only change with contract modifications. That makes sense when the problem and solution are known. But when they are unknown the traditional methods of contracting fail.
This I think is the biggest failure in public private partnerships. These arrangements were supposed to save the taxpayer money by allowing nimble contractors to come in and do the heavy lifting on projects.
However what it really did is:
1) Create an adversarial relationship between between the government and the contracting entity, which is very much filled with even more red tape then it was were trying to replace.
2) Hollow out the talent in the government, causing more reliance on the private sector.
I'm not convinced these relationships can exist in a healthy way. If there isn't a lot of red tape and strict contracts then it's likely the government will get robbed blind and that leads to stricter contracts and more red tape: a virtuous cycle of red tape and lack of progress.
I think less emphases needs to be put on these partnerships and more on developing talent within the government that can innovate from within. This creates the possibility of empowered leaders within government departments that can run projects like agile mini-startups.
> A thing that keeps me up at night is that there is almost certainly, today, something which might not be shaped like penicillin but has a similar level of impact, and which is really sweating the next thousand dollars.
There are two types of reactions to the Therac-25 story.
1) We need to put a lot of process in place to review and test and ensure we have proper interlocks in place.
2) They just didn't have enough talent on the team. It couldn't happen here.
You want some people with reaction 1 working on a safety critical system.
Watching it has me wondering a lot about how bad the accident actually was. I've done a little research and the number of fatalities seem to vary wildly depending on the source.
Does anyone have any reasonably good un-biased sources of information about the accident?
https://toddwschneider.com/dashboards/hacker-news-trends/?q=...
Google seems to be the favourite there.
This one in particular worries me. Having access mailing list conversations and IRC logs provides such a rich history of open source development. I worry about every open source project moving to github / slack, where we may not have nearly as good a record of conversations that formed the software in 20 - 30 years.
On the other hand you won't see any argument from me that these services provide an easier workflow than what existed before, and maybe that easier workflow opening development up to a wider community is more important.
> Industrial espionage was implicated in the capacitor plague, in connection with the theft of an electrolyte formula. A materials scientist working for Rubycon in Japan left the company, taking the secret water-based electrolyte formula for Rubycon's ZA and ZL series capacitors, and began working for a Chinese company. The scientist then developed a copy of this electrolyte. Then, some staff members who defected from the Chinese company copied an incomplete version of the formula and began to market it to many of the aluminium electrolytic manufacturers in Taiwan, undercutting the prices of the Japanese manufacturers. This incomplete electrolyte lacked important proprietary ingredients which were essential to the long-term stability of the capacitors and was unstable when packaged in a finished aluminum capacitor. This faulty electrolyte allowed the unimpeded formation of hydroxide and produced hydrogen gas. [2]
[1] https://news.ycombinator.com/item?id=19606691
[2] https://en.wikipedia.org/wiki/Capacitor_plague#Implications_...