dmit

> Haskell

https://github.com/Frege/frege

https://github.com/typelead/eta

Of the others you mentioned, I bet there's a couple JVM Prologs out there, but haven't encountered any myself.

> probably thinks the rest of us outside of the Google/elite bubble are subhuman

If you're wondering why your message got flagged, it's a lot of reasons, but mostly this part.

Yes, the only difference.

That's the true meaning of backward compatibility. The [backward] refers to the time scale.

So proud of all the HN denizens that none of us asked lvass about their stance on mandatory baby seats in cars. Or those bars they use to pin you down in your car on roller coasters.

You mean the official nightlies? I like that plan! Should boost coverage by a lot in irl projects.

> I don't think zig best-practices are written in stone yet, but I would expect ReleaseSafe to be the default in production.

Which profile is the default for the Zig compiler itself? What about Bun? TigerBeetle was the only one of the three to use ReleaseSafe by default last I checked? (Edit: in fact, they outright ban ReleaseFast and ReleaseSmall because they care about correctness.) ZLS suggests ReleaseSafe in its README too, if you count it among the prominent Zig projects.

Even when compiling in Debug mode! Where the analogy is closer to a friend who's applying for a cashier job asking you to role play being a customer so they could practice, and then spitting in your face when you go "Hey, Joe! I'll take these" because "No real life customer would do that! Start over."

Ea-Nasir

Us humans are kinda ok at preserving knowledge (and we're getting even better, but not in a good way).

A weekend project tops

Welcome! And also I am so sorry

The author mentions that approach at the end of the post:

> Apart from parsing the SQL query, I also considered an alternative testing approach that I might implement in the future: go through each migration one by one, and insert some dummy data into the database before applying it, to make sure that we test each migration being applied on a non-empty database. The data would either have to be generated automatically based on the current database schema, or we could commit some example DB dataset together with each migration, to make sure that we have some representative data sample available.

Also the r->z substitution. Charles -> Chaz. Barry -> Baz. Jeremy -> Jez. Caroline -> Caz. etc etc

Exactly! Let's go back to the times when things were consistent! Remember when you couldn't tell AIM from ICQ from MSN Messenger from Skype because they looked and behaved consistently?

Just find an old Windows VM and put Winamp next to Sonique next to RealPlayer next to Windows Media Player next to QuickTime -- those sure were the days, until the damn "creatives" came with their stupid "web tech."

As in, any other language at all..?

> gotos are fine if used judiciously

Is there a language feature that is not? :)

> I tend to think Rust isn't suitable to rewrite JavaScript tooling

If only you could have warned all the people that the work they did was untenable before they went and did it.

> Consider Hackernews: hn.js comes with 21,4 kB. The Y logo on the upper left is a 46,32 kB SVG!

hn.js is just north of 5.2kB (2.3kB compressed), and the logo is 315 bytes.

Here's one case. Instead of

  let letters = word.chars().filter(|ch| ch.is_alphabetic());

you can just write

  let letters = word.chars().filter(is_alphabetic);

since the difference between "methods" and "functions" is purely syntactic.

You linked to serde_json and not serde, which this story is about. And the crate sizes listed include not just the source, but also test code and other project files.

A --small flag would provide approximately the same amount of information - you'd still need to read the description to figure out what it does.

And thanks for the UWU.md idea, love it!

We might have different definitions of "usability." Tooling, package management, compiler messages, language documentation. Those are some of the things I think of when I hear "usability" - and those are all top notch. Were you thinking of the learning curve, or did you have issues with some of the above?

I mean, https://www.libcinder.org and https://openframeworks.cc have been mainstays of the creative coding industry for a long time now. A Rust take on the problem shouldn't be too surprising.

You know this, but a tiny nit: it resets to a clean state after every prompt and then replays recent chat history to catch up. The distinction is important in cases like asking it to play a guessing game ("think of a number/person and I'll guess"). The only way it could maintain memory of the secret being guessed between questions is by outputting it as part of a response, which would defeat the purpose of the game.

> film produces a much better overall look than digital

To add one more data point to all the other sibling comments, Vince Gilligan (a self-described huge fan of film) talked on one of the Better Call Saul podcasts about how they did a blind test, and the consensus was that digital looked better. This was around five years ago.

>> GPT-3 took 355 years to train

> Could this be distributed? Put all those mining GPUs to work.

Nope. It's a strictly O(n) process. If it weren't for the foresight of George Patrick Turnbull in 1668, we would not be anywhere close to these amazing results today.

And when all else fails, you reach for Intel VTune. :) Which has provided a free community version for a couple years now, I might add.

> If you're not paying for numbers, what are you paying for then?

Oh honey...

Yes, Europe absolutely detests having a phone that fits in your hand.

In presentation form: https://www.infoq.com/presentations/life-after-java-8/