Thank you for the comment. This is not in my area of expertise, so I hope you can clarify - how does one test that "mitochondria and other energy-related biochem phenomena work as expected"?
Chris Masterjohn is a noted quack. He takes bits of actual science and research and weaves them together into narratives that make it sound like he has everything figured out with his unique protocols, but it doesn’t hold up to actual scrutiny. People spend years following his ever changing protocols without getting anywhere (beyond placebo effect and a large bill for supplements)
I know I won’t convince the parent commenter but hopefully I can convince other readers not to go down this road or invest any money in anything related to him.
Pure ad hominem FUD. “This guy sometimes disagrees with scientists employed by the government, don’t listen to him!”.
The technical details are beyond my understanding but I’ve heard from a PhD in the field that Masterjohn’s understanding of metabolism is second to none. Whether his protocols work or not is certainly a case by case matter (like any health protocol), but he always appears to substantiate it with well-cited lines of argument, and is willing to engage with interlocutors.
As for spending years with changing protocols without getting anywhere besides spending lots of money, well that can be said for people with complex issues who go the institutionally approved route as well. It isn’t discrediting in its own right that a protocol didn’t work for some.
I've been looking at Iceberg for a while, but in the end went with Delta Lake because it doesn't have a dependency on a catalog. It also has good support for reading and writing from it without needing Spark.
Does anyone know if Iceberg has plans to support similar use cases?
Iceberg has the hdfs catalog, which also relies only on dirs and files.
That said, a catalog (which Delta also can have) helps a lot to keep things tidy. For example, I can write a dataset with Spark, transform it with dbt and a query engine (such as Trino) and consume the resulting dataset with any client that supports Iceberg. If I use a catalog, all happens without having to register the dataset location in each of these components.
Why don't you want a catalog? The SQL or REST catalogs are pretty light to set up. I have my eye on lakekeeper[0], but Polaris (from Snowflake) is a good option too.
PyIceberg is likely the easiest way to write without Spark.
We did an evaluation of various REST catalog options and went with Open Catalog from Snowflake (a Polaris-based managed service that works independently from their data warehousing solution). Lakekeeper is nice - it's one of the few catalogs with FGAC and table maintenance.
PyIceberg is nice but we had to drop it because it's behind Java API and it's unclear when it will match up, so depending on which features are needed I'd look it up
Wait, those high frequency sounds in Tokyo are teenage repellents? I thought they are bird/insect repellants. I could hear the sounds and was literally getting mini headaches walking around.
They're extremely annoying, aren't they? I was the only one that could hear them out of 5 people in my group, all aged about 35, and they definitely caused me to avoid walking by that shop. Hell, I would have avoided ever buying anything there if I were a local.
Yes you can even adjust the frequency based on which demographics you want to keep from loitering. There is a predictable hearing loss curve for the highest frequencies. You could set it to 20kHz to keep little kids away, or even go as low as 16kHz if you want to keep everyone younger than about college age away. This also happens to be an easy way to test the degree of your own hearing loss compared to your age group.
I just want to say - thank you! I've been using ZSH since it became the default on macOS and one thing that started annoying me recently is the slow startup time. Your snippet tangibly improved that.
Do you by chance have any good resources on optimising my config further?
Beyond zprof (https://www.bigbinary.com/blog/zsh-profiling) not really I'm afraid. I did the majority of my zsh-prompt hacking 10 years ago and haven't thought about it since. That snippet could be from anywhere.
Fetching git/hg/... info is always slow, so try and speed that up where you can (as to how to do that, uhh... I know my prompt has a dirty-state check nicked from pure for speed reasons). You can also cache any `asdf init zsh` or similar to a file and do the same "run in background" trick so the next shell will have any changes.
The biggest improvement I can remember was dropping zprezto for my own much smaller config, I really did not need much comparatively. Mostly some git info and "good default" options. I use zgenom for a plugin manager but only have 3 plugins, probably I should just dump it and inline the plugins to avoid getting owned one day.
On the topic of AGSI, the company I work for published a Python client to work with their API in case you're interested: https://github.com/ROITI-Ltd/alsi-py
Edit: Correction, it's for ALSI, not AGSI, sorry about that. We should add AGSI now that the API is available.
I personally hate when apps crowd my Menu Bar when they don't need to e.g. Dropbox, NordVPN, Keybase etc. I always try to disable the Menu Bar icon for an app if possible, and if I can't I will delete the app if I can find a suitable alternative.
There are so many advantages to a dock icon:
- Richer, colorful icon
- Support for badges, configurable by user
- Won't be hidden by the system (macOS will hide icons in a crowded Menu Bar)
- Can be hidden by the user (Dock Autohide)
- Icon can be repositioned by the user
The Apple HIG makes it pretty clear that most apps don't need the Menu Bar, and should use the Dock instead. But we're in a vicious circle where users have been trained to use the Menu Bar (even though it's inferior), so that's what developers do.
That's pretty much the same place where I started as well (the RW tutorial).
For the library: HotKey is exactly what I used. Simple to set up, works with the Xcode Package manager and does exactly what it says.
reply