bsaul

10 ms·

121.
by bsaul 1y ago
Problem with C# isn't the language, it's the enterprise ecosystem. You always feel like you're going to have to pay at some point down the road for using the tech.
122.
by bsaul 1y ago
i do feel much more comfortable with lifetimes than at the beginning. I get the general concept, and i barely have to explicitely set them (i did start by religiously reading the rust book, of course). However, at the moment i still feel i&
123.
by bsaul 1y ago
i didn't "find" it. As i said, it's a well known one : https://github.com/rust-lang/rust/issues/110338 Simply using axum with code using multiple layers of async was enough. But then again
124.
by bsaul 1y ago
Funny. I've been trying rust for the past 2 months fulltime, and i'm really wondering how you can call it a "joy to work with" when compared to java, at least for server development. Rust feels like walking on a minefiel
125.
by bsaul 1y ago
i was thinking it would have used the swift build project https://github.com/swiftlang/swift-build recently released but i didn't find any mention of that. Did i miss something ?
126.
by bsaul 1y ago
i get it, but openai being the hotest stuff happening in software for the past.. x years , i would have assumed there was some kind of official client correctly maintained for rust. I was a bit shocked to be honest. edit : i originally misr
127.
by bsaul 1y ago
i'm asking because openai api has a special endpoint to deal with pdf, different from images. Which part of a pdf file can you use LLMs for ? Pdf is a binary format..
128.
by bsaul 1y ago
i think i prefer swift as a language, and rust as an ecosystem. The amount of quality libraries in rust is astounding. But that may change with swift getting more and more into safety and reaching the limits of how many keywords a language
129.
by bsaul 1y ago
Coding in both swift and rust is really a funny experience. It's like two roads being built going toward the same city, but starting from widely different places.
130.
by bsaul 1y ago
I've come to accept that i wasn't really developing in "rust", but in "tokio-rust", and stopped worrying about async everywhere (it's not fundamentally different from what happens with other lang having as
131.
by bsaul 1y ago
macro seems to compensate for that. there's definitely a "C++ template programming" vibe in some libraries.
132.
by bsaul 1y ago
Random remark: I've noticed the quality of rust libraries too. Which made me really surprised to see the overengineered mess that is the async-openai crate. how can one take an api as simple as openai's one, and turn it to this st
133.
by bsaul 1y ago
great news ! sidenote : Does vision include the ability to read a pdf ?
134.
by bsaul 1y ago
I see why you're saying that, and i almost entirely agree with you. However, i would say that if all you're doing is glueing calls to third party systems (like what most backend code is), then you won't fall into complex life
135.
by bsaul 1y ago
"If we change .set_value() to take a &self instead of a &self" guess it's "instead of a &mut self"
136.
by bsaul 1y ago
senior dev, rust very recent onboarder : my personal experience is that LLM are super helpful at the very very beginning, because they show you the very common rust pattern, and help with the verbose syntax by reducing the amount of typing
137.
by bsaul 1y ago
I haven't coded in C/C++ in years but friends who do and worked on non-trivial codebase in those languages had a really crappy experience with LLMs too. A friend of mine only understood why i was so impressed by LLMs once he had t
138.
by bsaul 1y ago
it could be a weird argument, but as a rust newcomer, i have to say it's really something that jumps to your face. LLMs are practically useless for anything non-basic, and rust contains a lot non-basic things.
139.
by bsaul 1y ago
ok. If you ever want to see the state of the art (IMHO) i recommend you to look at wasmbindgen and uniffi in rust. The code generated for the consumer side of the library is absolutely insane . It makes it completely transparent, even when
140.
by bsaul 1y ago
wonder if active record couldn’t borrow some pattern from coredata with its managedobjectcontext property associated to every object. This lets you work with objects transparently, not having to carry a « db » property everywhere, and the
141.
by bsaul 1y ago
So.. Is your library only exposing simple synchronous functions, with primitive types that map easily to C ? I'm confused..
142.
by bsaul 1y ago
"enums represent a different and incompatible concept in every language I know." Enums has always felt very natural in every modern languages i've tried (swift and rust, for example), even with associated values. The underlyi
143.
by bsaul 1y ago
Interesting, thanks. Do you have a resource that shows basic examples for android & web ? Rust also has a very extensive set of tools to generate bindings ( wasm bindgen & uniffi), and a wide ecosystem of crate for all platforms (ru
144.
by bsaul 1y ago
i tried building cross-platform libraries in swift for the past two years, with no success. I just did it in rust (ios / android / wasm) in a week, knowing nothing about the language. the swift wasm project still uses a forked com
145.
by bsaul 1y ago
The fact that a compiler is crashing really makes me shiver. If the compiler is crashing because of unexpected combinations, then what about the generated code ?
146.
by bsaul 1y ago
i'm using chatgpt for this exact case. It helps me verify my solution is correct, and when it's not, where is my mistake. Without it, i would have simply skipped to the next problem, hoping i didn't make a mistake. It's
147.
by bsaul 1y ago
it is, but it definitely added some weight to the language. At least i think so, i'm not a PL expert. My recent point of comparison is rust, which feels like a much much smaller language, despite sharing a lot of the philosophy (struct
148.
by bsaul 1y ago
Swift as a langage is fine, the problem is the ecosystem. It's been driven by apple for too long now, and suffers a lot from it. You would think that being constrained by one company would ensure the project remains lean, but apple act
149.
by bsaul 1y ago
The swift language is absolutely fantastic. But the constraints (such as objective-c compatibility) made it a juggernaut. It's actually very surprising they managed to get that language work at all given the size of it. In that regard,
150.
by bsaul 1y ago
anecdotally, it was also the first production compiler that i saw crash, and it was on regular code.

More ›