In the animal world, the genomic vaccine revolution has led to two new types of vaccine being produced.
1. The Autogenous vaccine, where a veterinarian submits swabs of offending organisms to a lab that cultures and produces a vaccine specific to that strain to sell back to the clinic. Genomics play a role in determining if the currently circulating strains match the culture that the vaccine is based on.
2. The prescription platform vaccine, where genomic sequences are used to create a custom antigen that is produced in a microbial factory.
The efficacy of these types of vaccines is hotly debated because they do not have to go through clinical trial before distribution. The development of "commercial" (i.e. clinical trial-burdened) vaccines appears to have slowed based on my observations. While I think some of these new vaccines show promise, many autogenous and prescription platform vaccines are just more expensive versions of vaccines already available, or they package organisms that are suspected commensals and market it as something that no one else has done.
It's hard for me to call today a "golden age of vaccine development" in that light. I hope that the article is only taking human vaccines into account and that there is appropriate efficacy data for every vaccine shown in the last chart.
The first argument actually leans in favor of LaTeX or Typst as a better replacement for Docx.
A LaTeX or Typst document can contain both the content and formatting together within the same file. This isn't idiomatic for either language, and my experience is that this is more common for Typst than LaTeX, but both can do so. All of those formatting rules like small caps, table widths, margins, page numbering, etc.? Those can be rigidly defined in either LaTeX or Typst and are better guarded aginst accidental formatting rules breaches from double click, copy/paste, or table cell insertion than in Word.
I'm more sympathetic to the network effect argument. It's hard to envision a reasonable redline system compatible with both Docx and LaTeX/Typst.
> I don't think Julia really solves any problems that aren't already solved by Python.
But isn't the whole point of this article that Matlab is more readable than Python (i.e. solves the readability problem)? The Matlab and Julia code for the provided example are equivalent[1]: which means Julia has more readable math than Python.
[1]: Technically, the article's code will not work in Julia because Julia gives semantic meaning to commas in brackets, while Matlab does not. It is perfectly valid to use spaces as separators in Matlab, meaning that the following Julia code is also valid Matlab which is equivalent to the Matlab code block provided in the article.
X = [ 1 2 3 ];
Y = [ 1 2 3;
4 5 6;
7 8 9 ];
Z = Y * X';
W = [ Z Z ];
> The flakes were the main UX/DX improvement for me. Before them I honestly could not do anything.
Agreed. I think flakes are far more intuitive than channels. In a flake everything is declared in the repo it's used in. I still don't understand channels.
For someone who's used to thinking in channels, I suppose flakes would be jarring. For someone (like me) who came from the world of Project.toml and package.json, flakes make a lot of sense.
I think a lot of people come to Nix and NixOS from Linux and similar environments, where having "repositories" or "registries" is fairly common as a way for distributing indexes of software in their distributions. So it's quite naturally moving in that way.
But for someone coming from OSX/macOS or Windows where there basically is just one index (provided by the companies maintaining the OSes) and you can't really add/remove others, it's a completely new concept, makes sense there is at least a bit of friction as those people wrap their head around it.
I'm not sure I understand your point. You're saying that channels are like apt/sources.list or yum.repos.d, and flakes are like the Apple App Store? Or the other way around?
One thing that probably didn't help my understanding of channels was that I run Nix on non-NixOS systems (primarily MacOS and Fedora). If I'd stuck to NixOS, then thinking of a channel in the same terms as apt/sources.list or yum.repos.d would have been an easier mental model.
Bureau of Labor Statistics says that the mean annual wage of "Automotive Technicians and Repairers (SOC code 49-3020)" is $55,780 as of May 2025, so yeah, something doesn't add up.
For example, by law in California, auto mechanics make double minimum wage if they don't own their tools (so they can go buy some). That works out to about $68k/yr these days.
$120k/yr is not suuuuuper crazy in some areas for some auto work (think restoration). But generally, yes, Ford is not adding up here
> auto mechanics make double minimum wage if they don't own their tools (so they can go buy some)
I think you have that backwards:
"Typically, in California, if your employer wants you to provide and maintain your own work tools, they must pay you at least double the minimum wage. This means that in 2025, with California’s minimum wage at $16.50 per hour, your employer must pay you at least $33.00 per hour before they can require you to supply your own tools."
Auto mechanics make double minimum wage if the do own their own tools.
I remember hearing about that rumen swap experiment. One of my professors at the time said that more substantial changes could be affected by doing repeat rumen content swaps.
The docs recommend setting up KaTeX CSS (which requires either a CDN link or Node), but by changing output to 'mathml,' you can have the browser render equations with zero dependencies.
reply