This is a nice idea, but it's empty. There were widely reported ICE operations in Minnesota over the past few days, yet it's blank on the map. Seems like a fun vibe-code project, but not useful w/o data.
Legal-tech: Using AI to help attorneys bill flat-rate instead of hourly. It's data intensive, but possible if you go through their old time entries and tell them the flat-rate price of all of their hourly work. 93% of attorneys bill hourly, primarily b/c they don't have any sense of the cost of the upcoming work. DM me if you want to work on these problems.
Saw both the movie and the real thing multiple times. Subject of numerous a heist fantasy… even today though, the MTA guys collecting money from the machines are escorted by NYPD conspicuously showing their firearms while giving you the eye. The attitude remains.
“Power is not a material possession that can be given, it is the ability to act.
Power must be taken, it is never given.”
“‘This country, with its institutions, belongs to the people who inhabit it. Whenever they shall grow weary of the existing Government, they can exercise their constitutional right of amending it, or their revolutionary right to dismember or overthrow it.’
Abraham Lincoln”
> Instead, we should be using game-style "data oriented programming" a.k.a. "column databases" for a much higher performance.
This makes logical sense, but I don’t buy it in practice. Most of the heavy data reads are handled by databases, which do optimize for this stuff. I just doubt that, in most software, a significant amount of software performance issues are a result of poor memory alignment of data structures.
> I don't think that being able to replace a library at runtime is a useful enough feature to justify the high maintenance cost of shared libraries.
We’re moving to a world where every program is containerized or sandboxed. There is no more real “sharing” of libraries, everything gets “statically linked” in a Docker image anyway.
You can do Unicode in Python 2. You can do Unicode faster and easier in Python 3. But by gaining that ability, they set the existing community back by 10 years.
> There are literally savings accounts with interest rate over my mortgage interest, meaning there is a zero risk arbitrage opportunity.
Many utilities give an 8-9% interest rate on bonds, with very little risk (Comcast isn't going bankrupt soon). That said, there's no such thing as zero-risk arbitrage.
> It is often best to avoid non-ASCII characters in source code. ...
>> Depends of the language. In Python 3, files are expected to be utf8 by default, and you can change that by adding a "# coding: <charset>" header.
It's interesting that many languages avoid unicode and non-ASCII text, yet they make assumptions about file and directory structures about the underlying system. It's as if interpreting directory and file system structures is "okay", but interpreting file formats is not.
> In fact, it's one of the reasons it was a breaking release in the first place, and being able to put non-ASCII characters in strings and comments in my source code are a huge plus.
Sorry, but as a Python dev that went from 2 to 3, yes native unicode features are nice, but no, it was not worth breaking two decades of existing code.
> they've been heralding the death of Moore's law since he started and that the "one trick ponies" just keep coming. He says he doesn't doubt that they will continue.
The situation is clearly far worse than what you suggest. Back in the 1990s and early 2000s, apparent computer performance was doubling roughly every two years. Your shiny new desktop was obsolete in 24 months.
Today, we're lucky to get a 15% gain in two years. The "one-trick ponies" help narrow the "apparent performance" gap, but by definition, are implemented out of desperation. They aren't enough to keep Moore's law alive (it's already dead), and their very existence is evidence of the death of Moore's law.
> We should all be happy for the millions of people that didn't starve to death, and for the millions who didn't have to walk their children off of cliffs or have the family hug a grenade.
Before we thank ourselves for all the lives we "saved", we should remember all of those that died in the name of an unnecessary exercise in human greed and cruelty.
Time is an illusion. Science tells us it's linear, measured in precise nano-seconds. But humans measure time differently, it's based more on the depth of connection we have to others. You can have a life-changing event in a day, or waste away doing nothing for a decade. The more connected one is to the surrounding people and environment, the denser and more fulfilling time becomes.
The M1 processor is a direct result of the death of Moore's law. It's an amazing processor, but a sad sign of things to come.
The performance gains from Moore's law have typically come from shrinking die size. That has ended, you can't juice more performance from general purpose CPUs. If general purpose processors no longer advance quickly enough, the only way to get performance gains is to build custom chips for common specific tasks. That's what we're seeing now with the M1. The M1 buys us a few more years of exponential-appearing performance gains, but it's a one-trick pony. You can turn code into an ASIC once, but after that, your performance is at the mercy of the foundry and physics.
The death of Moore's law has many consequences, the rise of ASICs and custom co-processor chips is just one of them.