That seems obvious, but a consequence of that is that people who are sceptical of ai (like me) only use it when they've exhausted other resources (like google). You ask very specific questions where not a lot of documentation is available and inevetably even o3 ends up being pretty useless.

Conversely there's people who love ai and use it for everything, and since the majority of the stuff they ask about is fairly simple and well documented (eg "Write me some typescript"), they rarely have a negative experience.

I think that Evan generally wrote code that was as simple as possible — there was no unnecessary complexity. In this case there indeed is some inherent, unavoidable complexity due to the math involved and the performance requirements, but otherwise I found our text rendering pipeline very understandable.

Evan actually wrote about it if you're curious to learn more: https://medium.com/@evanwallace/easy-scalable-text-rendering...

All of the methods defined here:

https://github.com/Helion-Engine/Helion/blob/20300d89ee4091c...

Are available in the kitchen sink:

https://learn.microsoft.com/en-us/dotnet/api/system.numerics...

Same idea applies to methods like GetProjection, which could be replaced with methods like:

https://learn.microsoft.com/en-us/dotnet/api/system.numerics...

Advantages of using this library are that it is uses intrinsics (SIMD) to accelerate operations. There is a lot of Microsoft money & time that has been invested into these code piles.

Compare with a simple pipeline in bash:

  grep needle < haystack.txt | sed 's/foo/bar/g' | xargs wc -l

Compare Ruby:

  data = File.readlines("haystack.txt")
    .map(&:strip)
    .grep(/needle/)
    .map { |i| i.gsub('foo', 'bar') }
    .map { |i| File.readlines(i).count }

Despite being clean and readable, I don't tend to do it any more, because it's harder to debug. More often these days, I write things like this:

  data = File.readlines("haystack.txt")
  data = data.map(&:strip)
  data = data.grep(/needle/)
  data = data.map { |i| i.gsub('foo', 'bar') }
  data = data.map { |i| File.readlines(i).count }

If you are poor you can't go anywhere or buy anything. You're not free if you're poor. If you are sick, you may be confined to a hospital bed or not feel good enough to do anything. If you are sick you're not free.

Putting fluoride in water reduces dental costs and incidence of cavities and therefore tooth infections, particularly among societies poorest. Therefore, due to fluoridation in water some people are less sick and have more money and therefore are more free.

The contrasting view is that putting fluoride in water is literally medicating people without their affirmative consent. It is the government forcing you to take a medication. It is coercive and therefore an attack on your freedom to not take medication. It is the government interfering in your life.

The contrast between positive freedom, the freedom to do something, and negative freedom, the freedom from interference in your life, is the core political argument in America right now. Negative freedom, freedom from government interference, is being promoted by those seeking to weaken the government enough to supplant it. People who are poor and sick are likely unable to stand up for themselves or participate in solidarity against authority. This individual issue is relatively small, but you take 100's of issues like this, and the effect is to create a class of people who aren't able to do anything but be obedient workers.