Readit News logoReadit News
qw3rty01 commented on Async Rust is not safe with io_uring   tonbo.io/blog/async-rust-... · Posted by u/ethegwo
tsimionescu · 10 months ago
Not leaking resources is a part of Rust's safety model, isn't it?
qw3rty01 · 10 months ago
No, leaking is explicitly safe in rust: https://doc.rust-lang.org/nomicon/leaking.html
qw3rty01 commented on Async Rust is not safe with io_uring   tonbo.io/blog/async-rust-... · Posted by u/ethegwo
ordu · 10 months ago
> The title of this blog might sound a bit dramatic, but everyone has different definitions and understandings of "safety."

Still in Rust community "safety" is used in a very specific understanding, so I don't think it is correct to use any definition you like while speaking about Rust. Or at least, the article should start with your specific definition of safety/unsafety.

I don't want to reject the premise of the article, that this kind of safety is very important, but for Rust unsafety without using "unsafe" is much more important that an OS dying from leaked connections. I have read through the article looking for rust's kind of unsafety and I was found that I was tricked. It is very frustrating, it looks to me as a lie with some lame excuses afterwards.

qw3rty01 · 10 months ago
So in this case it is still a form of safety that’s well-defined in rust: cancel safety. The io-uring library doesn’t have the same cancel safety guarantees that everyone is used to in epoll libraries. In Tokio, the cancel safety of `accept` is well documented even though it works the way you’d expect, but in monoio, it’s literally just documented as `Accept` with no mention of the cancel safety issues when using that function.
qw3rty01 commented on Omnivore Is Joining ElevenLabs   blog.omnivore.app/p/omniv... · Posted by u/janpio
dod9er · 10 months ago
Too bad... I also really liked it and used. Seems like I go for wallabag again. Maybe it will be possible to selfhost omnivore at some point in time ?!
qw3rty01 · 10 months ago
It already has a self-hosting option: https://github.com/omnivore-app/omnivore/tree/main/self-host...

It's just not documented well.

qw3rty01 commented on NixOS 24.05 "Uakari" Released   nixos.org/blog/announceme... · Posted by u/opengears
bsimpson · a year ago
> things become easier

I'm not even sure what that would look like. Nix is such a departure from other Linuxen that I don't think it will magically become easier; I expect you'll always need to understand Nix to use it. Maybe better syntax highlighting etc. would help?

I expect it's much easier to learn Nix in the age of LLMs than it would have been before.

qw3rty01 · a year ago
as someone who has been working to make nix my main system for several months now, there are some very clear areas of improvement that would make things easier:

- [any] documentation, the majority of nix modules are undocumented and so the only way to figure out what settings are available is to find and read the source code (and even then it could be using a module to convert the definitions to the target config format, in which case there’s even more guessing, but at least the official documentation of that package gives you something)

- coding standards; lots of modules have different variations of camel case, snake case, adjective-noun, noun-adjective, etc so it’s not clear what the correct format of a setting is for an arbitrary package

- flakes just need to be both an official feature and set to be the default way to interact with nix, it just has too many upsides

- Better errors, the current errors are just horrible to read and you end up picking out 1 or 2 spots in several paragraphs of irrelevant code snippets and stack traces

- up to date resources, since the official docs aren’t very beginner friendly, third party resources end up being the way people learn (vimjoyer has been a godsend), but half the time when you try to use those resources, they’re out of date and lead to broken nix configs, having solid official updated documentation to help new users get started in nix would go a long way here

qw3rty01 commented on Kite is saying farewell and open-sourcing its code   kite.com/blog/product/kit... · Posted by u/dynamicwebpaige
UncleEntity · 3 years ago
Which was later overturned by the Supreme Court if you read farther down the article you posted the link for.

And was all over the tech news at the time.

I kind of suspect you are intentionally trolling…

qw3rty01 · 3 years ago
Incorrect, the case was appealed to the supreme court and the appeal was denied, so the lower court ruling held.

What was ruled by the supreme court was that Google's usage of the API (which had already determined to be copyrighted) fell under fair use in copyright law.

qw3rty01 commented on Kite is saying farewell and open-sourcing its code   kite.com/blog/product/kit... · Posted by u/dynamicwebpaige
madsbuch · 3 years ago
APIs are not copyrightable (Oracle vs Google). However, the code that interacts with an API might be.

Regardless, it is interesting to think about what domains are easier to generate effective models for. I would expect it to be easier to generate a supervised model <test description> => <test code>. My intuition is also, that it is easier to generate React component code, and harder to generate feature code.

qw3rty01 · 3 years ago
Unfortunately that ruling was overturned and APIs were found to be copyrightable: https://en.wikipedia.org/wiki/Google_LLC_v._Oracle_America,_...
qw3rty01 commented on Heathrow Airport: Two planes in minor collision   bbc.com/news/uk-england-l... · Posted by u/shifty1
bolasanibk · 3 years ago
FAA search page for incidents: https://www.asias.faa.gov/apex/f?p=100:12:::NO:::

List of incidents in the past 10 days: https://www.asias.faa.gov/apex/f?p=100:93:::NO:::

qw3rty01 · 3 years ago
almost all of these are non-commercial; all but 1 of the commercial incidents from the past 10 days are due to striking birds in flight, and nothing with airport taxiing
qw3rty01 commented on The rise of 'stealerships' and the shady economics of car buying   npr.org/sections/money/20... · Posted by u/senthil_rajasek
jeffbee · 3 years ago
Why do people get all worked up over a difference ± a few hundred dollars on a very expensive purchase? When I want to buy a car, which I admit rarely happens, I look at the advertised price and if I'm willing to pay that price then I call the dealer and if I'm not, I don't. If the paperwork shows up with a different number on it then I tell them to leave, and it's their time, not mine, that was wasted.

I just really don't get the whole haggling thing. If you want a lower price, wait until one is being advertised, or substitute a different model, or get a bicycle.

qw3rty01 · 3 years ago
The article answered that question:

> I found some trucks that were literally priced $10,000-$15,000 over MSRP, and I encountered many of the shady business practices that the FTC is now trying to ban.

because it's not ± a few hundred dollars, it's thousands of dollars, and claiming online that it's one price and charging a lot more once you get there

qw3rty01 commented on Running Zig with WASI on Cloudflare Workers   blog.cloudflare.com/runni... · Posted by u/tosh
stavros · 3 years ago
Does the existence of WASI mean that I can also run Rust programs on Workers, compiled to WASM (without the JS shim)? Does anyone know of any tutorials on this? It would be great if I could access the Request object, with all the headers, payload, etc from Rust.
qw3rty01 · 3 years ago
I'm not sure if there's a JS shim or not, but rust has been a supported language for a long time with that workflow: https://developers.cloudflare.com/workers/tutorials/hello-wo...

u/qw3rty01

KarmaCake day481August 21, 2019
About
user list:

cperciva - tarsnap founder, Animats - nagle, zx2c4 - donenfield, jart - justine tunney,

View Original