I took parent's message to be asking why the standard library fs primitives don't use `at` functions under the hood, not that they wanted the `at` functions directly exposed.
> why the standard library fs primitives don't use `at` functions under the hood
In this case it wouldn't seem to make sense to use `at` functions to back the standard file opening interface that Rust presents, because it requires different parameters, so a different API would need to be designed. Someone above mentioned that such an API is being considered for inclusion in libstd in this issue: https://github.com/rust-lang/rust/issues/120426
There are lots of unstable things in Rust that have been unstable for many years, and the intentional segregating of unstable means that it's a nonstarter for most use cases, like libraries. It's unstable because there's significant enough issues that nobody wants to mark it as stable, no matter what those issues are.
As long as it's unstable it's totally fair to say Rust's stdlib does not expose them. You might as well say it's fixed because someone posted a patch on a mailing list somewhere.
There are lots of unstable things in Rust that have been unstable for many years, but this isn't one of them. openat() was added in September, and the next PR in the series implementing unlinkat() and removeat() received a code review three weeks ago and is currently waiting on the author for minor revisions.
> As long as it's unstable it's totally fair to say Rust's stdlib does not expose them. You might as well say it's fixed because someone posted a patch on a mailing list somewhere
Agreed. My comment was intended to be read as "it's planned and being worked on", not "it's available".
Claude uses up its 6 hour or whatever quota in a couple coding prompts. Buying extra credits for the same amount as a monthly subscription and it's used up in 3 hours.
Kimi gives me about double what Claude does per window but uses up its entire weekly quota in the same time, for the same price as Claude. And I get worse results.
Gemini worked OK for a day or two and now is running one tool every 30m and getting nothing done, apparently they've been in constant outage status for for nearly a month: https://aistudio.google.com/status
I haven't tried ChatGPT because of ethical issues but well, I'm not sure that makes any sense.
Four prompts a day isn't something where I go, wow, this has revolutionized my programming. I might very well be getting more done if I wasn't fighting with the constant CLI bugs and work left half finished for 3h to 5 days when my quota is used up.
I think that's an interesting idea, but you hit the landing page and there's loads of syntax thrown in your face and you're like, man, I need to learn a lot.
But I think this kind of brings up another problem, which is that you can choose not to use stuff if you're writing, but if you're reading other people's docs or editing them, then you need to know all the syntax they use. Most OSS projects with markdown docs today, anyone can open an MR to improve them.
> "Oceans" is a kinetic sculpture that embodies the dynamism of the world's oceans within the arid landscape of Las Vegas. Crafted from 483 motorized elements known as "Brixels," this piece mimics the movement of the sea's surface. The sculpture is alive with the pulse of the planet's waters, ...
BREAKFAST (AKA Zolty) here. The “ocean” aspect of the piece is in how it moves and the real-time API data that drives the wave-like motion. It grabs live tide data from a different coastal city each minute and changes based on that. The gold and marble bricks took inspiration from the Fontainebleau art deco style of their original Miami hotel (this piece lives in their Vegas location).
Sorry, I was half joking, half of me gets the metaphor, but the other me is seeing a wall of bricks of gold in a Las Vegas casino and gets another metaphor.
Can someone explain the “Fontainebleau art deco style”? I have been to Fountainbleau and I remember it as much older renaissance style architecture and geometric/baroque gardens.
How is this different from Terraform? Generally if something fails during a TF apply it saves the state of all the stuff that worked and just retries the thing that failed when you next run it. And reverting your TF stack and doing apply again should walk changes back.
There are specific things where that's not possible, and there are bugs, but it doesn't seem like what you said unless you meant that you just support a limited subset of resources that are known to be robust to reverts? But that's a fairly different claim.
The main difference is granularity. Terraform runs a plan and applies it as a batch. If something fails, you re-run apply and it retries from the last saved state... but that state is per-resource, not per-API-call.
Alien tracks state at the individual API call level. A single resource creation might involve 5-10 API calls (create IAM role -> attach policy -> create function -> configure triggers -> set up DNS...). If it fails at step 7, it resumes from step 7. Terraform would retry the entire resource.
The other difference is that Alien runs continuously, not as a one-shot apply. It's a long-running control plane that watches the environment, detects drift, and reconciles. Terraform assumes you run it, it converges, and then nothing changes until you run it again.
Speaking of granularity, I noticed that the 2 states of a resource seem to be:
> Frozen: Alien can only monitor it. Created once during setup, then Alien has no permissions to modify or delete it.
> Live: Alien can manage it from your cloud. Push code updates, roll config changes, redeploy — without the customer's involvement.
Is that really all? What about something like "Alien can run these 37 maintenance and debugging commands but cannot touch the firewall or modify routes or change any other access methods to internal resources"?
The whole psyop thing is only an issue if you use "popularity" and mass appeal (people following in instagram, etc) as a signal for finding stuff.
The alternative is to listen to less filtered/signalless stuff (which isn't hard - bandcamp new releases lists (or my bandhiking app) or even their trending charts which seem to be unpopular enough that it's not entirely controlled by marketing (lots of unlistenable stuff makes it onto the chart) and meet/hang out with other people who do the same for a minor filtering pass.
Popularity is the most popular (!) signal because this isn't really about the music - it's to have something to talk about with your friends, whether to bond over shared interest or signal something about yourself to your group. The same is true about any other interest: most people care a lot (arguably, primarily) about their interest being recognized and supported by other people.
Those of us who care about an interest for the sake of that interest, are called nerds.
> which Rust's stdlib chose not to expose
i.e. expose through things like `File::open()`.
reply