"You can do everything in C"

Including shooting yourself in the foot.

/Rust

/dev/null

jars are just zip files renamed

Inspired by how NeXTSTEP bundles work.

People keep missing Java's ideas due to OpenSTEP collaboration before Java came to be.

https://cs.gmu.edu/~sean/stuff/java-objc.html

https://en.wikipedia.org/wiki/Distributed_Objects_Everywhere

I guess there’s a reason that Cocoa was called Cocoa… it’s also a hot beverage like Java, just sweeter ;)

also unlike java, cocoa doesn't cause jitters

JAR has additional structure to it, though it's mostly optional stuff, like metadata and code signing:

https://docs.oracle.com/en/java/javase/21/docs/specs/jar/jar...

Don't forget to delete META-INF!

Wait until you learn what an iOS app's .ipa file is.

What’s that saying, there are 3 kinds of files?

zips, text files, and binary files

The old macos classic was a lot of fun, i remember using resedit on some apps at school.

I remember the first time a saw Perl, it looked like some kind of alien language from outer space, all the symbols it used looked insane.

But once you get it, its pretty intuitive to use.

The worst part about it was the syntax for object oriented programming, which in raku (perl 6) is a lot better and intuitive.

Raku has some great ideas like grammars, but has a lot of new magic symbology and lost what i thought was an intuitive way of regular expressions in Perl 5.

=~ vs ~~

“Warning: Smartmatch is experimental at foobar.pl line 42.”

If only I had a dollar for every time I’ve seen this message.

lazy_static with either a mutex or a RwLock.

I actually love how rust gatekeeps the idiots from programming it, probably why Linus Torvalds allowed rust into the kernel, but not C++.

Its really easy to use, you download, login and start working.

Its a step up from copy-pasting from an llm.

But claude code is on another level.

Imagine hardening the regex library, its already as slow as molasses.

There are lots of parts of the standard library that nobody uses, and hardening has no performance impacts in code you don't call.

That and the fact they can self-fund the whole AI venture and don't require outside investment.

The most fun fact about all the developments post-ChatGPT is that people apparently forgot that Google was doing actual AI before AI meant (only) ML and GenAI/LLMs, and they were top players at it.

Arguably main OpenAI raison d'être was to be a counterweight to that pre-2023 Google AI dominance. But I'd also argue that OpenAI lost its way.

And they forgot to pay those people so most of them left.

To be fair, they weren't increasing Ads revenue.

They literally gave away their secret sauce to OpenAI and pretended like it wasn’t a big opportunity.

Just as expected from a big firm with slower organizational speed. They can afford to make those mistakes.

That and they were harvesting data way before it was cool, and now that it is cool, they're in a privileged position since almost no-one can afford to block GoogleBot.

They do voluntarily offer a way to signal that the data GoogleBot sees is not to be used for training, for now, and assuming you take them at their word, but AFAIK there is no way to stop them doing RAG on your content without destroying your SEO in the process.

But they also collect the data without causing denial of service, and respect robots.txt, which is more than you can say of most LLM scrapers...

Do people still get organic search traffic from google?

Wow, they really got folks by the short hairs if that is true...

It was bad coding.

.unwrap() is not required to be used.

use:

if let Some(value)=something_to_unwrap{

}else{ // log an error and exit!! }

Fun fact: that's what an unwrap does. It panics, which causes the error to be logged and the thread ended.

And one of the fun things about how unwrap() does that automatically, is that if you are working with an orchestrator with retry logic, you won't need to (re-re-re-re-re-)write your own for the entire program - the orchestrator will see the error, log its output, and try again in high volume workloads, or move on to the next request - this is incredible and nice to use especially when a failure in one request doesn't need to fail the entire application for all requests.

I shy away from unwrap() in almost all cases (as should anyone!) but if you are running a modular system, then unwrap when placed strategically can be incredibly useful.

I think the commenter meant "return a Result<_>" instead of exit. Your snark is perhaps amusing, but not particularly charitable.

Maybe rust should put a function in the core library which does this! Send a PR!