zamalek

Friendly reminder: most cloud providers have deletion locks. Go and enable them on your prod dbs right now.

Sure, Claude could just remove the lock - but it's one more gate.

Edit: these existed long before agents, and for good reason: mistakes happen. Last week I removed tf destroy from a GitHub workflow, because it was 16px away from apply in the dropdown. Lock your dbs, irrespective of your take on agents.

> Another reason is compilation time. The more complicated the function signatures, the more prologue/epilogue code we have to generate that LLVM has to chew on. [...]

I know that LLVM completely dominates compilation time, but maybe the improvements from this could make the other bits (i.e. compiling rustc with callconv=fast) fast enough to make up the difference?

Unfortunately the US military has very deep pockets.

Apparently the number of people familiar with the Streisand Effect is vanishingly small.

There are communities who gobble up anything Microsoft produces. People in the Microsoft MVP program are usually in this camp - if you want to find examples. Me and my coder friends were part of the fandom, but with just me and my biased N=10 sample set; this fanbase is evaporating quickly (but I still know some hardcore "azure thumpers").

Rust happens to be an extremely good tool. There are definitely situations where it absolutely sucks. e.g. Zed is a heroic effort, but look at the code and you'll see that we still haven't figured out how to do Rust UIs.

We may disagree on the premise that humans are generally incapable of correct and safe manual memory management, but that's a degree of distrust I hold for myself. You may have never written a memory bug in your life, but I have, and that renders me completely incompetent.

If a project in an unsafe language has ever had a memory bug (I'm looking at you, Bun), the maintainers objectively have a track record of not being capable of manual memory management. You wouldn't put a person who has a track record of crashing busses at the wheel of a school bus.

And Rust isn't the only memory-safe language. You can turn to Java, Go, C#, Type/JavaScript, and whole bunch of others. Rust just so happens to have ocaml tendencies and other things that make it a joy to read and write, so that's definitely preference on my part. One of these days I'll learn ocaml and possibly drop Rust :)

They have earned my business, for now.

Sora is already a flop. People are sick of slop and are getting good at identifying it. Grok is the only player that has any semblance of success in the visual gen market, only because they do the one thing that will always make money.

I'm a rust fanboy, but I conceded to Go a long time ago as the ideal language to write MCPs in. I know rust can do a musl build, but the fact it's defacto goes a long way.

Back to the article. I've written a few MCPs and the fact that it uses JSON is incredibly unfortunate. In one recent project - not an MCP - I cut token count (not character count) of truly unavoidable context to ~60% just by reformatting it as markdown.

I think I might just try my MCPs as CLIs.

> I need to get my car washed; should I drive or walk to the car wash that is 100m away?

> Walking 100 m is generally faster, cheaper, and better for the environment than driving such a short distance. If you have a car that’s already running and you don’t mind a few extra seconds, walking also avoids the hassle of finding parking or worrying about traffic.

This is awesome news - and maybe a leap forward to tide us over, but solid state batteries are also usually hyped for safety reasons: puncturing one with a nail won't result in a fire (or some other accident). The article doesn't mention that - only that they've mitigated safety concerns from dendrites.

That's why I said "two weeks."

You should be comparing to AMD, at that. There's hope for the upcoming Intel chips - but anything current isn't competitive. Furthermore, M* is good for a specific form-factor, but don't for a second suggest that 4 P-Cores will outdo the 16 hyper threaded cores on a 9950x

Two weeks with Rust and you're still fighting with the compiler. I think the LLM pulled a lot of weight selling the language, it can help smooth over the tricky bits.

What people get wrong is that you don't just trip balls and get cured. Re-integration therapy is vital for lasting effects. Grabbing some shrooms and digging in is recreation, which is perfectly fine, but don't fool yourself or anyone else by suggesting it's for treatment.

It's actually better suited IMO, being a compiled language. I'm not sure how anyone could consider the current train wreck of getting python code just to run "actual applications." uv is great and all, but many of these "actual applications" don't use it.

That's not exactly it. Light gets redshifted instead of slowing down, because light will be measured to be the same speed in all frames of reference. So even though we can't actually observe it yet, light traveling towards us still moves at c.

It's a different story entirely for matter. Causal and reachable are two different things.

Regardless, such extreme redshifting would make communication virtually impossible - but maybe the folks at Blargon 5 have that figured out.

> Cross-vendor GPU support: A single codebase runs on AMD, NVIDIA, and CPU via KernelAbstractions.jl

This is why I wish Julia were the language for ML and sci comp in general, but Python is sucking all of the air out of the room.

I'm not questioning your experience, but how "enterprise" is that experience? Gitflow was no small part of my convincing my company to move off TFVC. I doubt they still use, but it was shallow waters for scared folk.

I strongly doubt that my story, just as much as yours, is unique.

Yup, there would have been much less Git buy-in if it weren't for git flow; people grow incredibly attached to their beloved taxonomies.

I think we're fine: https://youtube.com/shorts/3fYiLXVfPa4?si=0y3cgdMHO2L5FgXW

Claude invented something completely nonsensical:

> This is a classic upside-down cup trick! The cup is designed to be flipped — you drink from it by turning it upside down, which makes the sealed end the bottom and the open end the top. Once flipped, it functions just like a normal cup. *The sealed "top" prevents it from spilling while it's in its resting position, but the moment you flip it, you can drink normally from the open end.*

Emphasis mine.

> being left behind (“I still can’t bring myself to vibe code. I have to at least skim every diff. Meanwhile this guy is joining OpenAI”).

I don't believe skimming diffs counts as being left behind. Survivor bias etc. Furthermore, people are going to get burned by this (already have been, but seemingly not enough) and a responsible mindset such as yours will be valued again.

Something that still up for grabs is figuring how how to do full agenetic in a responsible way. How do we bring the equivalent of skimming diffs to this?

Intel very recently seems to be making progress thanks to what the previous CEO kicked off. People are comparing Panther Lake to M1 (but we'll see when it is in reviewers' hands).

Yup, but "normies" do need menus or at least some way to do things that has some degree of visual affordance (e.g. a persistent cmd/ctrl+p, which I think Office has/had).

Yes, which is why people complain about MacOS vs Windows. People wouldn't complain about the lack of quasi-tiling in MacOS if they didn't care about it (which is the gist of your gp comment). The only reason they have experienced it is because Windows has quasi-tiling.

Next Apple will be utilizing 12-finger and faceroll getures.

Tilings are no better or no worse than floating. There are many users who would benefit from them (people who typically keep all their windows maximized), but have had literally zero exposure two them due to MacOS and Windows.

Complaints about lack of window snapping in MacOS vs Windows, a loose copy of tiling, are consistent across the internet. If MacOS and Windows had native tiling support, you'd see a fight fiercer than tabs vs. spaces.

The reason floating windows are used is because "that's the way it is done." Windows 95 wowed the world and established the status quo.

Not to mention the direction that the likes of Paper and Niri are going, these are things that very few users get to experience and therefore couldn't possibly have an informed decision on what they prefer.

I think it's a bot attempting to LARP as a human.

If you want something relatively uninteresting: Fedora or Debian (honestly, stable is fine).

If you want something extremely reliable, more modern, but may require some learning to tweak: Silverblue or Kinoite.

> Ubuntu LTS

This is why I try to encourage new Linux users away from Ubuntu: it's a laggard with, often important, functionality. It is now an enterprise OS (where durability is more important than functionality), it's not really suitable for a power user (like someone who would use Zed).