brianolson

I heard that it was effectively a hasmat site for quite some time with spills of several nasty things including mercury. Also I have fond memories from I popped in there to get some random tech things in the 1990s.

SQL is the worst way to access a database, except for all of the others that have been tried from time to time

Yield. Some fraction of cores had a speck of dust or something, but at 38/40 good cores per chip they got economical yield

> Why aren’t these AI companies submitting to the TOP500 to show off their computing prowess?

my knowledge is 10+ years out of date, but once upon a time if they'd chosen to, Google could have had _several_ entries in the top 10 of the TOP500 list

It's just poker, they didn't want to tip their hand

yup. me too. once upon a time that was a 2 week assignment in graphics class in college

I worked in blockchain ("builder") for 5 years. I started 'eh, there are speculators, whatever, I build good tech' but finished 'holy crap speculators completely dominate and distort everything, nobody cares about good tech'

"In select GC-heavy microbenchmarks ... we observed anywhere from a 10–50% reduction in GC CPU costs"

- Yay!

"The Go compiler benchmarks appear to inconsistently show a very slight regression (0.5%)"

- Boo

"Green Tea is available as an experiment at tip-of-tree and is planned as to be available as an opt-in experiment in Go 1.25"

I definitely know some application code that spends 30% of CPU time in GC that needs to try this.

I designed and named the Transaction Execution Approval Language for the Algorand blockchain in 2020. I'm partial to the original, but as it grew it got rebranded to be the "Algorand Virtual Machine". Glad someone still remembers it as TEAL!

Great concept. Bring back real small trucks. My grandpa ran a farm with a truck this size.

Disappointed in towing capacity of 1000 pounds ish. I can already do 1700lb on my hybrid rav4

I built a 'slice of function pointers' bytecode interpreter in Go in 2019 for the Algorand VM (Blockchain smart contract stuff) and before that the same pattern in C for a toy JVM around 2005.

It's a good pattern!

The Algorand VM was focused on low overhead running thousands of tiny programs per second. Version 1 had no loops and a 1000 instruction limit.

The JVM was focused on low memory, towards possible embedded microcontroller use.

So, 'array of function pointers' is nothing new, but it is a good pattern.

95% of end users don't care; but Bluesky has the right bits built in anyway. There's a grand central aggregator of all 13 million accounts, but it's not _special_, someone else could run one (several hobbiests are processing this level of data). Migration works* (and works better than Mastodon, all your history and network move even better than a masto server move) (*okay, it's a weird command line tool at the moment, but as soon as someone cares that'll get cleaned up). You can run your own Personal Data Server and hook it in to the bsky network and then everyone can see your posts and interact with them. It's newer, only a couple years old, but all the right parts are headed in the right direction.

atproto PDSes are like blog servers with RSS (but better) and bsky.app is the prevailing RSS reader. It's an open protocol because anyone can host a source and anyone can run a different reader.