Then I see the following line in the 'How it compares' section:

"Self-hostable server (open source)": ngrok->No, Cloudflare Tunnel->No, Tailscale->No, Bitbang->Yes

...and I'm like, "It's Open Source Tailscale!"

And now I "get it"! (you know, epiphany, profound enlightenment and all that!) :-)

(Well, it's an open source alternative to Tailscale, to be more precise, and an excellent one at that!)

Great work, Rich LeGrand!

(Another step forward for open source!)

Comments URL: https://news.ycombinator.com/item?id=49127831

Points: 2

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=49078071

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=49038530

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=49038400

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=49023936

Points: 1

# Comments: 0

But:

>"Initially, the Amiga had a reputation for being unstable.

But that was largely because early Amiga software wasn’t very well written. Amiga software was prone to ask for resources, and assume the resources were available. Instead of failing gracefully if the resources it asked for weren’t available, it would simply allocate them, and cause a guru meditation, the Amiga equivalent of a blue screen of death or kernel panic. Except it was red, not blue."

Not true!

Well, not entirely true...

Or at least, that's not an entirely correct, nuanced, contextual historical understanding...

I was an early Amiga owner, so I speak from experience!

Yes, software could crash the system from time to time (any software of the era could crash almost any consumer computer of the era, because CPU's with MMU's and protected memory and protected mode operating systems where kernel/OS code was separate from user/client/program/application/unprivileged code (call it what you will!) either did not exist or were not widely available or inexpensive enough for mass-market adoption by the majority of home/family/mass-market consumers in the early to mid 1980's.

The Amiga 1000 used the Motorola 68000 CPU, which did not have a built-in MMU on it or external MMU working alongside it, which means that there was no protected memory where the OS/kernel code could live, which means that any given program, even the simplest of C programs, could overwrite OS/kernel memory, which means that any given program could crash the computer -- but that's exactly the same as most of the other mass-market consumer computers from other manufacturers of the early to mid 1980's -- the same as early Macintoshes with 68000's, the same as 6510 Commodore 64's, the same as 6502/65C02 Apple IIe's, the same as early 8086/8088 IBM PC's and clones, etc., etc.

Any program could crash any of those.

So if the early Amiga had a "reputation for being unstable" (a reputation which I have never heard about until now, until reading this article what, 41 years or so since the original Amiga 1000 was first produced, I should explain that I've read almost every single early Amiga article (I was a voracious early "Amiga article reader"!) in the 1985-1993 time period) -- then the same thing would have been true about just about every other consumer-grade mass-market computer in the early to mid 1980's... because most didn't have MMU's and run protected mode operating systems...)

If the Amiga 1000 had a "reputation for being unstable" -- then that's either fake news (what are your sources?) or AI-generated copypasta or possibly marketing gossip/slander originating from other jealous less-technologically superior competing computer manufacturers back in the day...

Now, other than that minor point, that minor nuanced contextual understanding (which I apologize for, because it sounds like I'm trying to be a critic of the article -- I am not! I am merely trying to mitigate the spread of "fake historical news" surrounding the original Amiga 1000!) -- other that that minor point, the article is 100% spot-on, a great article, and I'm really glad the author wrote it!

So, to the Author, I say "well done!"

An excellent article overall!

That, and I greatly appreciate any and all articles written about the early Amiga!

Comments URL: https://news.ycombinator.com/item?id=48808482

Points: 832

# Comments: 325

Comments URL: https://news.ycombinator.com/item?id=48791696

Points: 5

# Comments: 1

employees consumed 73.7 trillion tokens in roughly 30 days

, a figure tracked on an internal leaderboard called "Claudeonomics" — a reference to Anthropic's Claude, one of the third-party AI tools widely used inside the company [2]. The leaderboard, which ranked employees and teams by token consumption, inadvertently incentivized usage volume over productive output.

Meta plans to dismantle the leaderboard and replace it with a centralized monitoring platform called "AI Gateway," which will track usage and spending across teams in real time [2]."

This seems to be an interesting upcoming business, that is:

Helping companies centralize and track their AI usage by employee.

Anyway, great article!

if you convert data to logarithms, you can add them and avoid the multiplication overhead entirely.

And, the Napier chip, named after Scottish mathematician, astronomer, and physicist John Napier of the late Renaissance, who invented logarithms and also was an early user of the decimal point and was therefore one of the first geeks to get us on the path to a floating point processing unit, does all of this conversion from matrix to logs all under the covers, invisibly.

Here’s the upshot:

This shift to log math provides more than an order of magnitude better performance

, lower price, and lower power consumption than hybrid architectures from Nvidia and Amazon Web Services."

Comments URL: https://news.ycombinator.com/item?id=48715541

Points: 2

# Comments: 1

https://github.com/antirez/ds4

https://news.ycombinator.com/item?id=48142108

Comments URL: https://news.ycombinator.com/item?id=48636610

Points: 3

# Comments: 1

o Tiny: around 1100 sloc of ANSI C

o Works within a fixed-sized memory region: no additional memory is allocated

o Built-in controls: window, scrollable panel, button, slider, textbox, label, checkbox, wordwrapped text

o Works with any rendering system that can draw rectangles and text

o Designed to allow the user to easily add custom controls

o Simple layout system"

Comments URL: https://news.ycombinator.com/item?id=48569205

Points: 257

# Comments: 87

[...]

"The transceiver receives a differential digital signal from the computer interface and impresses it onto the cable as a level of about 8 volts for a 1, or 0 volts (open circuit) for a 0, through a very fast VMOS power FET. When the cable is idle it is held at 0 volts by the terminations. This simple-minded unipolar scheme is adequate for the medium cable lengths and transmission speeds we are using. The transceiver monitors the cable by comparing it against a reference voltage, and returns a differential signal to the interface. In addition, it detects interference (another transceiver transmitting at the same time as this one) and informs the interface."

Seems like the above would be all that's necessary for the simplest possible "built around first principles" local LAN, if someone wanted to experiment with an early Ethernet-like system...

Anyway, great article!

Comments URL: https://news.ycombinator.com/item?id=48534446

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=48490927

Points: 162

# Comments: 62