News for hackers. Stuff that matters.

sblom

Re:Evergreen: A Provably Safe Systems Language on Wednesday November 04, 2026 @10:53AM (#50367366)
It's a really great concept. What guarantees are made by the prover?

Success in programming languages is not simply if-you-build-it-they-will-come. Bootstrapping a community that loves programming in it is the hard part. You'll either need a killer interop story with an already built ecosystem, or you'll need your own HTTP server, JSON parser, etc. etc. etc.

Best of luck! I'll watch this space.

Re:Is It EDT or EST? on Sunday November 01, 2026 @12:30PM (#50327678)
Where in ET is DST ignored? Indiana used to be split on the issue, but my understanding is that they now follow DST, leaving only Arizona and Hawaii without regular time changes.
It's not outside Jason Rohrer's style for this to be... guided output, but it's also not outside his style for this to be the creepiest fully autonomous bot I've ever seen.
That's a great idea. It's also what Tally does.
I love the aesthetics. The cryptographic strength tradeoffs (against UUIDv7) seem rough for a lot of applications, though.
Re:Gitworkshop.dev on Monday October 27, 2025 @06:56PM (#45727307)
Both technologies (cryptocurrency and nostr) are very cipherpunk—I'm not particularly surprised that they draw overlapping crowds.

Another take on decentralized source control with more of an emphasis on "federated" and less of one on "censorship resistant": https://tangled.org/

Re:I am not a supplier (2022) on Tuesday July 01, 2025 @03:46PM (#44437384)
I really love Rob Mensching's framing in Open Source Maintenance Fee[1]. "The _software_ is free. The _project_ (issue tracker, forums, release management, package repository, etc.) is not."

It doesn't solve the supplier problem, but it is a very clever way to square the "free software, but I'd like to cover my expenses" circle.

[1]: https://opensourcemaintenancefee.org/

They have three other approaches that they're considering as well. (Check the About page on TFA.)
In all three cases, they own hardware (Apple in a slightly different sense) that they'd love for you to pay to run your favorite models on, open or closed.
Re:The Roguelike Rule of Thumb on Wednesday February 28, 2024 @05:34PM (#39544355)
A game like Rogue.

Slightly less obtusely, it usually was a procedurally generated dungeon-crawler with potions and scrolls and varied weapons to use against varied mobs. When you died, you were dead. Your character began each time with no knowledge and had to learn what a "cloudy red potion" happens to be this time around by drinking it or using an identify scroll.

Pizza Hutt is Jabba The's cousin. Pizza Hut is the restaurant chain to which you refer.
Re:Substack Notes Launched on Tuesday April 11, 2023 @08:28PM (#35533573)
I'm sure MySpace thought the same thing about their never-before-seen accomplishments. I suspect very few people knew what "something else" was in that case, either.
ChatGPT's threat to Google isn't that Google can't match it--it's that it changes the approach to search results from displaying lists of results where it's "natural" to insert sponsored listings to a more conversational approach where ad opportunities will be rarer (or at least entirely different).

If users prefer the newer, interactive approach to exploring search results, Google's long-standing business model will require a significant update.

This has caused me to realize that I need to replace my old model of vi:

> command mode has primacy; insert mode is a time-bounded special case

with:

> insert mode is every other mundane editor; use the Esc key to enter the matrix (i.e. command mode)

Re:A number that can't be calculated on Tuesday October 25, 2022 @03:34PM (#33335112)
By definition, each program only produces the digits of one number. It's okay for more than one program to produce the same number. Am I misunderstanding your point?
Re:What diversity and inclusion means at Microsoft on Tuesday October 11, 2022 @03:08PM (#33167776)
I _do_ work at Microsoft, and judging by the recent crop of promotions (early September) there was still plenty of opportunity for white males (and everyone else).
Re:FBI Child ID App on Wednesday July 06, 2022 @12:20PM (#32003160)
(That was the joke.)
I think the TLA you were looking for is TRA?
Re:The Berkeley Crossword Solver on Saturday July 02, 2022 @09:29PM (#31964212)
Is this a totally different thing than Dr. Fill [1]?

[1]: https://slate.com/technology/2021/04/american-crossword-puzz...

Re:Games and Puzzles as Multicomputational Systems on Wednesday June 08, 2022 @10:08PM (#31676866)
Stephen Wolfram has really grown on me over the last 10 years or so. He came across as obnoxiously arrogant for the longest time (so much that I still (defensibly) refer to "A New Kind of Science" as "Stephen Wolfram is a MF'n Genius Even If He Does Say So Himself").

These days, he live streams Mathematica design reviews on YouTube and Twitch. The conversations are fairly balanced and he clearly has a decent eye for designing the best god damn computational notebook system on the planet.

Admittedly, campaigning to name what could possibly maybe someday be the next big upgrade to physics after himself ("the Wolfram Physics Project") while he's still around and it's still in development is MIGHTY BOLD. But there's some really really interesting outcomes from the work that they've done so far.

If nothing else, it's a slam dunk proof of how physicists already think of "the speed of light" as actually "the speed limit for causal interaction". You essentially get all of the implications of both special and general relativity out of modeling causal interactions without even attaching it to any sort of specific physics.

I love that he wrote this essay (typical Wolfram long form essay that takes multiple sittings for me to digest) using puzzles and games as the subject of aforementioned causal modeling. Super fun, and also insightful!

Re:Update on Hiring Plans on Thursday June 02, 2022 @05:30PM (#31600755)
As terrible as rescinding offers is, offering severance and job placement assistance is a very interesting approach to minimizing how terrible.
Re:Thoughts on C# and .NET on Wednesday June 01, 2022 @02:00PM (#31585627)
VS Code, while not a fully-fledged IDE, is really good at suggesting code completions across platforms. As others have mentioned, Rider is also a wonderful fully cross-platform IDE (better than Visual Studio at some things).
Re:Blogchain on Monday May 30, 2022 @03:49PM (#31562926)
True in every browser I've tried far. I also had two separate blogchain tabs hard-hang and they had to be killed. I'm not sure I'm ready for all of this mindboggling innovation in UX. :)
Re:The Ring-a-Ding Numeration System by Jim Henle on Tuesday April 05, 2022 @01:22AM (#30915555)
I have no idea why, but I love alternate number systems (p-adics, surreals, base -2, split-complex, etc.). This one is playful.

Anyone know where to find a rigorous maths treatment for it?

Re:GitHub Incident on Tuesday March 22, 2022 @06:13PM (#30772279)
> Those two things cannot be true simultaneously. You cannot say "running big systems is hard" and "they can run a big system better than you can run a small system".

They can absolutely be true simultaneously. In fact, I can't name a logic system where those two statements comprise a contradiction. They are logically completely unrelated to each other.

Re:Why am I building a programming language in private? on Sunday March 13, 2022 @05:06PM (#30665692)
This feels like an "it is what it is"-style viral stunt, even though I actually suspect it's a sincere(?) post about reasons for developing without an audience.

It's gonna end up with more of an audience now, tho... :eye::mouth::eye:

Re:“Sustainability with Rust” post misleading about Go on Wednesday February 23, 2022 @02:14PM (#30445022)
Go was definitely ahead of the curve on a few things.

I'd argue C# was there (or very very close). C# has had value types (and fine-grained memory layout) since the beginning, reified generics since .NET 2.0, and also (lesser-known fact) raw pointer support (inside `unsafe {}` blocks much like Rust's approach). This was all motivated by interoperability with native code (mostly Win32 or other C-like ABIs & COM).

In 2009, the concurrency paradigm in .NET was more like promises and not quite as slick as goroutines. async/await wasn't born until 2012.

It wasn't on your list, but I'll toss in another point that works in favor of your original claim. ;) The main C# project also wasn't TRULY multi-platform until 2014.

Re:“Sustainability with Rust” post misleading about Go on Wednesday February 23, 2022 @01:18PM (#30444359)
No one insulted Java. Why so defensive?

Go and Java make different tradeoffs. If you're unreasonably effective in Java and its tradeoffs work for you, that's completely fine. If you have good tools that make Java more like Go when you need Go-like characteristics, that's cool too.

Re:“Sustainability with Rust” post misleading about Go on Wednesday February 23, 2022 @12:52PM (#30444008)
I struggled for years with a chronic misunderstanding of Go. I kept trying to compare it to the usual suspects in the "next systems language" crowd (D, Rust, Zig). That wasn't quite right.

Once I realized that its sweet spot is large-ish services that you want closer to the metal than Java but for which would be silly to go as low level as C++, Go fans started making a whole lot more sense to me.

I'm still not a Go fan personally—my taste in programming languages slants toward the more expressive end of the scale (C#, Rust, Scala). But at least I'm no longer confused by trying to make Go make sense where it doesn't.

It's a very good tool for its kinds of jobs. Other languages also have their points of unreasonable effectiveness, too.

Re:Chris Lattner left Swift core team on Monday February 21, 2022 @01:00PM (#30418651)
Still being revised in standards committees: https://en.wikipedia.org/wiki/COBOL#COBOL_2014

Older »