peter_d_sherman

Joined 12 years ago

Karma
18,863
Submissions
6,050
Member since
Sep 16
Programmer, Student Of Law, Entrepreneur & Comedy Writer.

Open Source, Open Hardware, Transparency & Free Speech enthusiast.

[email protected] www.linkedin.com/in/peter-sherman-a6107a5 https://x.com/peter_d_sherman

"The true knowledge consists of knowing that one knows nothing..."

- Socrates

View on Hacker News

Recent submissions

Comment · 16 hours ago
A series of excellent points!

Hopefully future healthcare policy makers (both in the public and private sector) will read them, and get some good advice from them...

>"Training more doctors would supposedly compromise patient safety because it would mean lowering the bar for admissions and straining existing staff that need to train them. Even if you could admit and train them all, supplying enough doctors to meet market demand would cause a wage collapse breaking the ROI of med school expenses."

There seems to be a vicious circle in place between too much medical regulation requiring a corresponding amount of long and expensive education, and the high cost of medical education in general...

Which one is cause and which one is effect I do not know...

It would seem to the casual observer, that both aspects might feed into one another...

One thing I do know is that doctors from foreign countries, especially if they are third-world countries, typically have had to pay less, sometimes a whole lot less, for their medical education, compared to their U.S. counterparts...

Is that medical education as good as a U.S. medical education? Well, I don't know! Maybe it is in some cases, maybe it isn't in others...

What is known though is that foreign medical educations frequently cost less, sometimes a whole lot less -- than their U.S. counterparts...

Is hiring foreign doctors the solution or part of the solution?

I don't know that either, but I do know that there are a lot of foreign doctors (and previously foreign doctors before becoming U.S. Citizens) in the U.S., and certainly many more abroad...

Is AI the solution, or part of the solution?

It's definitely a wildcard with promise at this point; it'll be interesting to see where it goes in the future...

Anyway, you make some excellent points!

Hopefully future policy makers will read them and act on them...

Comment · 23 hours ago
>You can already buy shares in a nations economy - it is called owning currency.

An interesting point! Yes, that is definitely one way that currency could be looked at...

>The big difference from stocks is that most countries issue new shares (dollars, etc) to keep the price stable (indirectly via careful control of interest rates).

Agreed -- but if we were really to analyze things, scrutinize the way things really work at the highest degree of resolution, then we would have to observe that:

a) There are multiple countries/currencies in the world.

b) That each country's/currency's inflation rate is different than all of the other countries/currencies.

c) If each country's/currency's inflation rate is different, this means that each countries's issuance of new shares (and control of interest rates) -- their financial policies, are, by comparison, either more effective, on par, or less effective than those of other countries used for comparison...

Phrased another way:

All countries do not control the rate of inflation of their currencies equally.

Phrased another way:

Some nations are better at controlling their currency's rate of inflation than other nations.

True or not true?

>I am simplifying terribly

As am I! :-)

>but just as shares represent a fraction of a company, cash represents a share of a nation’s economy.

Again, an interesting point!

And yes, I could agree with that!

Comment · 1 day ago
Some excellent points!

>There's a lot wrong with health insurance in the US but this problem is largely on providers, not payers.

How would you fix it?

Comment · 1 day ago
>"In 2022, a Pulitzer-winning Wall Street Journal investigation analyzed over 31,000 financial disclosures from 12,000 senior government employees, revealing that nearly a quarter of federal officials traded stock in industries their agencies regulated."

Ya know, on the one hand, I wonder how many federal officials own nVidia stock and stock of other AI companies...

But then again, on the other, I wonder how many nVidia employees (and those of other AI companies!) own government T-bills (and other government backed securities!) in their 401K or other investment accounts!

You know, everybody in large corporations and governments owning shares in other large corporations and governments -- adds a whole new level of meaning to "stakeholder capitalism"... :-)

(In the far future, there'll probably be small foreign governments which become their own ticker symbol -- and get publicly traded on various stock exchanges! :-) You know, like: "Would you like to buy a share in Denmark (DNMK) or perhaps Norway (NRWY)? I hear they're very competitive with Apple (AAPL) right now! Great price to earnings (PE) ratio!" :-) )

Comment · 1 day ago
Prevention Vs. Cure...

(aka Proactive Vs. Reactive)

((aka Present Responsibility Vs. Future Response))

"An ounce of Prevention is worth a pound of Cure" (as the old expression goes...)

Observation: Most health insurance policies today, whether they are government or private corporation, national or regional, are based on the idea of paying for medical/health problems AFTER the onset of the health problem...

Prevention, preventative health, preventative medicine, and preventative programs -- would not only do a lot to preempt future health problems, but it would also save a ton of money (a ton of taxpayer money if the health insurance is a government sponsored one), as the above article so eloquently makes clear!

Observation: Some insurance policies do include some preventative health aspects -- but as medicine is complex and there are always new discoveries, there is always another step up, another higher level in what could be delivered...

In other words, these could always be improved...

"An ounce of Prevention is worth a pound of Cure" (as the article implicitly suggests...)

Anyway, great article!

Comment · 2 days ago
Excellent article!

Heck, not just an excellent article, an exceptional one!

This is why I read HN -- to find articles like this one!

The basic problem:

Everybody loves Software! Software, specifically having a huge breadth and variety for a given platform is the key to that platform's success! (Just ask Bill Gates of Microsoft that, about Windows!) Well a lot of Open Source software is on GitHub, but one problem is (or rather was!) that it needed to get built for a whole bunch of platforms... Simple right? Well, not so much for the average user who is not a programmer when there are numerous types of CPU (x86, ARM, RISC-V, etc., etc.), numerous OS platforms, numerous compilers and compiler versions, and (usually) other dependencies on specific versions of other Open Source software packages...

So who could solve this chaotic "wild west" of exponential build combinations?

Well, historically, GNU autotools (aclocal, autoconf, autoheader, automake, autoreconf, autoscan, gnu m4, libtool, etc., which created files such as: aclocal.m4, config.h, config.h.in, config.log, config.status, configure, Makefile, Makefile.in, etc.) tried to solve this problem, and for the most part did so -- but usually only for users who were familiar with using Unix/Linux command-line tools and usually only for GNU compilers, and build processes which had dependencies on other projects or libraries could break rather spectacularly if the exact correct version of those projects or libraries that the base software was dependent on was not known, or not selected correctly.

What was needed was something more generic, and yet more precise.

Enter Eelco Dolstra, and his Ph.D. thesis "The Purely Functional Software Deployment Model": https://edolstra.github.io/pubs/phd-thesis.pdf

Which is the basis for the Nix functional programming language, NixPkgs and NixOS.

Basically, all problems in software deployment (i.e., configuring and building software correctly from source) could be solved if there was the following:

Immutability in Storage: Once a software component is built, it is stored in a centralized location (the Nix Store, typically /nix/store) and marked as strictly read-only. Components are never modified in place.

Purity of the Build Process: Build actions are treated as mathematical functions. A build process is strictly isolated and hermetic—it is stripped of access to external environment variables or network resources, ensuring that the exact same inputs will always produce the exact same cryptographic output.

Well, turns out Eelco Dolstra and Nix / NixOS were right!

Why? Because now there are over 140,000 Open Source software packages in NixPkgs, i.e., installable by the Nix Package Manager. That's more than any other Linux package collection. And the breadth of combinations of CPU's, Platforms, OS'es, etc., far surpasses the build options of any other Linux distro's package collection!

But that's the next problem, and that's the problem this article so brilliantly addresses -- which is, if all of that software ecosystem, all of those build scripts are ultimately tied to Nix language, and the Nix language is hard to understand / hard to modify for newcomers to it, then how to unbind that entire software ecosystem from the Nix language?

And the answer (or at least one answer!) is what this article author suggests, which is "hey, let's convert the Nix language to Typescript"!

And this is (one great!) solution to the following problem:

>"Anyone who wants to explore the store-model space from a different direction, a new language, a new evaluator, a new editor experience, must then start from zero packages. This is the graveyard where other reimplementations or forks of Nix go to die."

Well not anymore!

Anyway, a truly brilliant article!

Comment · 3 days ago
Comment · 3 days ago
Grokipedia is certainly one example of what could be done -- but it might not be the penultimate nor ultimate possibility of what might be expressed by other motivated individuals in the future, in this space...
Comment · 4 days ago
>Wikipedia's Cleanup of AI-Generated Content

What I think is interesting is that in this day and age of AI with free Open Source web server software, unbelievably cheap data storage, and very inexpensive Internet hosting prices,

basically anyone can run their own version of Wikipedia

So, do specific Wikipedia articles lean too far to the left or too far to the right for your tastes?

Do specific Wikipedia articles lean too liberal or too conservative for you?

Do specific Wikipedia articles lean too pro-Democrat or pro-Republican for you?

Maybe you're just a Scientist or Physicist or Electrical Engineer and you don't like the censorship of "Free Energy" articles, er, I mean "Overunity", er, I mean "Cold Fusion", er, I mean "Low Energy Neutron Reactions" (LENR), er, I mean, "Free energy can't possibly exist, and we know this to be absolutely true!"...

Maybe you're a Programmer or Sysadmin, and you have your own opinions on the "systemd is not good" vs. "systemd is good" debate!

Maybe you're a Mathematician and you feel that some of the Wikipedia Math articles are either too complex for anyone to understand them effectively -- or conversely, too simple, and omit important facts!

Heck, maybe you think Chunky is a Soup, but then again, maybe you think it "eats like a meal!" and the associated Wikipedia page doesn't accurately reflect this belief!

Maybe you think New Shimmer is desert topping! But then again, maybe you think it's a floor wax! But you believe that the associated Wikipedia page doesn't present these facts accurately or fairly, in a non-biased way!

Well, there's a simple solution to all of these problems, all of these dilemmas, and more! Which is:

Basically run your own version of Wikipedia!

AI can be used en masse, to clean up the content of any Wikipedia web pages you don't like!

Simply fork Wikipedia, grab copies of its data (which is or should be public domain), write a prompt to look for and change (according to your own political, relgious, moral, or just-plain-common-sense beliefs!) all of the Wikipedia web pages that you feel are not "the truth, the whole truth, and nothing but the truth, so help [them/me/you/they] G-d!", and then host the thing yourself!

It's not impossible in this AI age!

Note that I am not suggesting that everyone do this; I am merely alluding to the fact that with AI, this task is now within the realm of possibility to be accomplished, whereas previously, it would have been significantly difficult...

Anyway, great article!

(And for the record -- Wikipedia is usually about 98%-99% correct on most hard STEM subjects, and an excellent starting point for research, so I'm not saying all of the above to knock Wikipedia in any way! We should all remember that Wikipedia was revolutionary for its time, and remains an excellent starting point for STEM research!)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton