2
points
compressedgas
Joined 751 karma
The gods, according to an ancient legend, made choice of certain trees to be under their special protection. Jupiter chose the oak, Venus the myrtle, Apollo the laurel, Cybele the pine, and Hercules the poplar. Minerva, wondering why they had preferred trees not yielding fruit, inquired the reason for their choice. Jupiter replied, “It is lest we should seem to covet the honor for the fruit.” But said Minerva, “Let anyone say what he will the olive is more dear to me on account of its fruit.” Then said Jupiter, “My daughter, you are rightly called wise; for unless what we do is useful, the glory of it is vain.”
- compressedgasAnd it is already running. It is too late to escape.
- It is around where CircularWiringError is thrown from the implementation of topological sort. If the instantiation of the objects was not lazy, the topological sort would have been applied to the entire dependency graph. As it is lazy, with objects being created when they are accessed CircularWiringError can be thrown upon access. I think this should never happen as it should be checked for in the Wiring constructor though the application of the topological sort.
- You want a backdrop to your speech. I want to be able to understand what message you presented when all I have is your scenery.
- You seem to be forgetting the people who are years latter reading your slides and don't have a copy of your presentation video. The text is for them. Your latter and larger audience; not for those listening to you present.
- That subdomain is missing. But an article with the same title and slug exists at another subdomain:
https://philosophyofwriting.substack.com/p/a-i-a-i-o-artific...
- I prefer the read and compare method used by https://github.com/ssokolow/fastdupes as it does not have to read everything to find the exact duplicates which the hashing method must.
- Another is the use of "singleTop", "singleTask", "singleInstance", and "singleInstancePerTask" activity launch modes, instead of properly implementing an interface that supports multiple task instances and allows its activities to properly stack on other's tasks that is allowing other applications to call upon your application to do a task and then properly allow the user to return the application from which where the call was made.
- This reminds me of _The Billion-Dollar Fix: Safe Modular Circular Initialisation with Placeholders and Placeholder Types_ https://dl.acm.org/doi/abs/10.1007/978-3-642-39038-8_9 https://ecs.wgtn.ac.nz/foswiki/pub/Main/TechnicalReportSerie...
Apywire reports it can't handle circular dependency: https://github.com/alganet/apywire/blob/1c9a39df36a9385d8b34...
- Reminded me of _Programming with Enumerable Sets of Structures_ https://dl.acm.org/doi/10.1145/2814270.2814323
- Reminds me of Yuzuru Tanaka's Meme Media and Meme Market Architectures (2003) https://onlinelibrary.wiley.com/doi/book/10.1002/047172307X
- > You think Python developers are going to roll their own HAMT
Python already has an HAMT implementation in use by the contextvars module.
- You could have at least included example output so that we can see how badly it does.
- I was expecting examples. There were none.
- I thought an fsync on the containing directories of each of the logs was needed to ensure the that newly created files were durably present in the directories.
- You can see your hidden posts at https://news.ycombinator.com/hidden
- Where's the personal part of this? I couldn't find it.
- By proper encryption they mean https://en.wikipedia.org/wiki/Client-side_encryption