TehPers

Can’t speak for everywhere, but in the US, if your first questions are about salary, they’re going to be left wondering if you’re even qualified for the job and if money is all you care about. Even if it is (which is fine most of the time), that’s not really the impression you should give if your goal is to be hired.

Asking about salary later on is usually a much better idea. You know whether you actually are interested in working there, the interviewer knows if they are interested in you, and wanting money it isn’t the first impression you give.

As for Python - leetcode style interviews are common, but almost always worthless. The only real value the company gets from something like that is to check that you actually can write code. They’re pointless beyond that, and a company doing leetcode interviews should be a red flag.

For personal projects, I don’t really care what you do. If someone who doesn’t know how to write a line of code asks an LLM to generate a simple program for them to use on their own, that doesn’t really bother me. Just don’t ask me to look at the code, and definitely don’t ask me to use the tool.

No.

Although I think it’s a symptom of a larger problem. At the very least, consider Rider (or for non-C# code, VS Code/Codium/your terminal editor of choice).

At work, we have to use VS for C# development though, due to us having VS licenses and not Rider licenses. I guess we could use VS Code for C# dev, but I could also use Morse code to type, and neither of those sound like a good time when you take our work tooling into account.

Without context, there’s no reason to compare the performance of these. The compiler is complex enough that what you do in the loop and after the loop matters with regards to optimizations.

Do you have more context? What’s actually happening in the code?

For #4: the 'de lifetime is the lifetime of the deserializer (and input data). It’s used to allow you to deserialize the data into a type without copying it, like deserializing a &'a [u8] buffer into a &'a str. It’s documented here if you want to read more.

Ironically, many languages that violate these rules are spoken in the US natively. People in the US just like to forget that there are other natively spoken languages (spoken since before English was introduced to the continent even).

English. I can go to the store and buy a sandwich for $8.99 all in one sentence, but splitting it on periods gives you two sentences.

Another couple missing:

• every language uses gendered nouns/verbs/adjectives/pronouns/etc
• no language uses gendered nouns/verbs/adjectives/pronouns/etc
• pronouns referring to people are always gendered
• pronouns are always singular (1) or plural (2+)

A fun language to learn regarding these is Hawaiian, where the language uses a-class and o-class rather than masculine and feminine, and which you use is largely based on how much control you have over it.

I think linking to the original article in the description is a good compromise if you’re crossposting. That would still save a click for myself and others who aren’t too interested in Phoronix’s commentary.

Save yourself a click. Here’s the original blog post.

A more serious answer would be that Rust can’t be compiled to all targets. There is a lot of work to get Rust to compile with gcc though, which would help with this tremendously.

It was mentioned in the notes for 1.84.0 that they began migrating to it. They might be doing it without an edition change if it’s backwards compatible (or if the incompatibilities are considered bugs).

I’m not aware of anything that’s specifically drag-and-drop, but slint supposedly has a live preview that could be helpful.

Is there a reason it needs to be specifically in Rust?

Usually the serialization/deserialization code, I keep with the model. The part where a file or whatever comes in, I leave that to the caller to decide on. In other words, the model knows how to serialize and deserialize itself, but not where it’s being serialized to or deserialized from.

Then again, in C#, it’s usually just a couple attributes on my model, and in Rust, it’s usually just a couple derives. It’s rare I actually write much, if any, serialization logic by hand.

FYI I don’t know if you were implying that I downvoted your comment, but the instance my account is on has downvotes disabled. All I see on my end is the original comment has 3 points.

I’m not sure what you’re expecting people to reply with when commenting that in a Rust community. People here tend to use and like Rust, so it’s a bit odd to make sarcastic remarks here about one of Rust’s biggest features and expect people to react well.

It is. You just need to change the extension to .c

If you’re fine with breaking changes now and then, then yes absolutely. I use it everywhere, and it’s been a huge boost in productivity for me.

Yes. This behavior seems strange, so either an explanation or investigation by a compiler dev seems like it would be helpful.

I’ll be honest. I’ve written async code in Rust for years and I don’t think I’ve used select at all. I tend to drop into manually implementing Future before that point. Either way, the issues related to that macro still exist, but the author seemed to call it out and link to an article about it (which doesn’t seem disingenuous at all to me).

As for cancellation, the fact that you can cancel tasks by default in Rust has come up far more for me than any issues with unintended cancellation (which I don’t remember ever coming up, honestly). What I find myself wanting in other languages (especially JS) is the ability to both control when the task starts executing (for initialization logic or to prepare the task and pass it somewhere before it starts executing) and when it stops executing (early termination, for example with debouncing). I don’t get that by default in other languages, or often even at all in JS (unless I pass an abort controller everywhere).