dureuill

7 ms·

1.
by dureuill 5mo ago
Except their customer's data isn't actually theirs: OP requested their private data to be deleted from the system. So OP expressed a clear intent for their data not to be used by Flock's customer. We could say that the data t
2.
by dureuill 7mo ago
To be clear I'm not saying that Pike's response is appropriate in a professional setting. "This project does not accept fully generated contributions, so this contribution is not respecting the contribution rules and is rejec
3.
by dureuill 7mo ago
The project states a boundary clearly: code by LLMs not backed by a human is not accepted. The correct response when someone oversteps your stated boundaries is not debate. It is telling them to stop. There is no one to convince about the l
4.
by dureuill 1y ago
> The commons are still as available as they ever were, That is false. As a direct consequence of LLMs: 1. The web is increasingly closed to automated scraping, and more marginally to people as well. Owners of websites like reddit now ha
5.
by dureuill 1y ago
hello, I implemented hybrid search in Meilisearch. Whether it uses re-ranking or not depends on how you want to stretch the definition. Meilisearch does not use the rank of the documents in each list of results to compute the final list of
6.
by dureuill 2y ago
> We aim to make Meilisearch updates seamless. Our vision includes avoiding dumps for non-major updates and reserving them only for significant version changes. We will implement a system to version internal databases and structures. Wit
7.
by dureuill 2y ago
I agree the answer is no in the abstract, but it is not very useful in practice. Nobody writing Rust needs to cover this "basic use case" you're referring to, so it is the same as people saying "unsafe exists so Rust is
8.
by dureuill 2y ago
I'm not sure I understand the use case here. Are you asking if you can depend on two versions of the same crate, for a crate that exports a `#[no_mangle]` or `#[export_name]` function? I guess you could slap a `#[used]` attribute on yo
9.
by dureuill 2y ago
Very disappointing read. Starts with an interesting claim "don't optimize for typing", but then it completely fails to prove it, and confuses itself in thinking that `auto` is an optimization for typing. `auto` is: - A way to
10.
by dureuill 2y ago
Some good advice, some bad advice in here. This is necessarily going to be opinionated. > Provide a development container Generally unneeded. It is expected that a Rust project can build with cargo build, don't deviate from that. Pe
11.
by dureuill 2y ago
> You are actually just arguing for the sake of arguing here. I'm very much not doing that. I'm just really tired of reading claims that "C++ is actually safe if you follow these very very simple rules", and then the
12.
by dureuill 2y ago
> no raw loops and not raw pointer access - Do these rules allow iterators? - Under the "no raw pointer" rule, how do you express view objects? For instance, is `std::string_view` forbidden under your rules? If no, then you can
13.
by dureuill 2y ago
> Ironically I see with your last point regarding golang that we are very different people ans thats fine. For me I would much rather lean back towards C if I can guarantee safety than the more abstract and high level rust. Honestly I am
14.
by dureuill 2y ago
> Rust also has UB and you should still be runnig fuzzers and sanitizers on your rust code, that is true for C++. Safe Rust doesn't have UB[1], and safe Rust is what I review 99% of the time. For unsafe modules, you should indeed be
15.
by dureuill 2y ago
> There are many languages that fit this description I find that in practice not, especially if you further limit that to imperative languages. Note that I mentioned memory safe AND heavily favors correctness. In that regard, Rust is uni
16.
by dureuill 2y ago
> As someone who has some large projects in C++ and co tribute to OSS C++ projects I find this isn't true. Well, that goes contrary to my personal experience (professional dev in C++11 and up for a decade), and also to the data rece
17.
by dureuill 2y ago
This feels very shortsighted to me. "Easy to learn" and "easy to hire for" are an advantage in the first few weeks. Besides, we now have data indicating that ramp up time in Rust is not longer than in other languages. On
18.
by dureuill 2y ago
Thank you for the answer! The limited range of compatibility of RAM components makes me wonder if the promise of upgradeability actually delivers
19.
by dureuill 2y ago
Hello, what kind of RAM is supported for the Intel configuration? I have a 32GB DDR4 SO DIMM 2400MHz sitting around, can I repurpose it for a new Framework config (and spare the corresponding 180€)?
20.
by dureuill 2y ago
hey, thanks for posting my article :-) It's a bug postmortem about tokio and rayon. Would be interested to know if anybody else encountered similar issues with these libraries or mixing other libraries that "own" threads
21.
Are We Modules Yet?(arewemodulesyet.org)
96 points by dureuill 2y ago|90 comments
22.
by dureuill 2y ago
More than just that, Result in general also prevents from accessing the value when there is an error and accessing an error when there is a value.
23.
by dureuill 2y ago
> But for those few cases you can add an annotation. not in other people's code. My main concern is that gradual typing makes understanding other people's code more difficult. Idiomatic Haskell warns against missing signatures[
24.
by dureuill 2y ago
> Those who like explicit types can add as many annotations as they need in OCaml. They cannot add it in other people's libraries. > did not stop Python rising to conqueror the world I wasn't talking popularity, I was talkin
25.
by dureuill 2y ago
Global type inference is not a positive in my book. In my experience it becomes very hard to understand the types involved if they are not explicit at systems boundaries. I can also imagine that it must be hard to maintain, like sometimes t
26.
by dureuill 2y ago
As personal anecdata, this checks out. 10 years C++, mostly C++11 once it started to exist and be available. After a few years of Rust on the side, I was x2 to x3 more productive in Rust than in C++. I regularly think that the way I express
27.
by dureuill 2y ago
In the Q&A from the video, there's a question very similar to yours. As an answer, Lars specifies that these are regular engineers who were asked to learn Rust, and not early adopters who like shiny things.
28.
by dureuill 3y ago
Hello, I have a few questions: - how much time to insert 15 millions of vectors of 768 f32? - how much RAM needed for this operation? - if inserting another vector, how incremental is the insertion? Is it faster than reindexing the 15M + 1
29.
by dureuill 3y ago
> it'll still down your service and damn you to a crashloop. Nope. Your service will be structured such that it is subdivided in tasks, each task being wrapped in a `catch_unwind`[1], such that a panic merely kills the task it occur
30.
by dureuill 3y ago
> What do you do now? Look for another job > You’d be amazed at how many C++ codebase in the wild that are a core part of a successful product earning millions and they basically do not compile. Wow I really hope this is hyperbole. I

More ›