I think with http request failures losing the status code can be a real pain. There’s a big difference between 400, 401, 404 and 500 for instance.

I wouldn’t call bad readability a loaded gun really. Your dev tools will hopefully make it pretty easy to learn the type. It should be a minor inconvenience at best.

The problem with dynamic typing is you can’t always figure out what the type is even with investigation as it can be lots of things based on what is passed or returned. It also allows incorrect values to be passed.

People will indeed make that readability argument but if the type is not obvious and important to understanding the code then it likely shouldn’t be used there.

auto isn’t dynamic typing it’s just type inference. It still has a fixed type you just don’t have to write it. Like var in C#.

Lambdas are just a way of defining methods in place. It has nothing to do with callbacks.

But you’re spot on for memory safety. Managing it yourself is risky and if it can be managed at zero cost it seems stupid not to.

You’re unpleasant to talk to.

I guess you can argue it’s already written in C. So that was always a requirement.

I mean I’ve still yet to hear a reason not to use rust tbf.

But yes that’s what working in a team is like.

I have to do stuff at work so I don’t fuck over the frontend team. I don’t throw a little tantrum about it.

I think the point is they aren’t forcing it at all. It’s being used with the blessing of Linux Jesus and the others are just throwing their toys out of the pram because they don’t want to learn it.

Someone else linked the video on this post. They are rude as hell and the rust dev isn’t even asking them to use it.

Again I think that’s a bad attitude towards technology. Use the best tool for the job and you’d get used to the syntax pretty quickly.

It’s like someone who started on python not wanting to learn a c style language.

It is literally being pushed for its technical merits and traits.

Memory safe code with comparable performance in the kernel seems like an absolute no brainer.

Also if you watch the video all he’s asking for is consistent interfaces for the file systems. He’s not even trying to get them to use rust. And the guy starts screeching about how he’ll code however he wants.

Is it wrong to expect a consistent and well documented interface?

Pretty sure C is actually being pushed against its technical merits here.

Wow what an absolute dick

Here’s the thing, you’re not going to force all of us to learn Rust

That seems like a poor attitude imo.

I would say being more inclusive is bringing value.

There’s a massive issue with women being under-represented in STEM and little things like this only further cement that.

It’s casual sexism. I’m not suggesting they are intentionally hating on women.

Assuming it’s a man because it’s programming is fundamentally sexist.

What downsides would they be?

I didn’t label him a sexist. But that is a sexist act. Assuming a man because programming fundamentally is sexist.

I mean that is sexist tbf

Start with a git GUI application. I use git extensions on windows.

You’ll be able to get a feel for how it all works and it actually shows you the commands it’s running.

I also use bingai a lot when learning. The more specific your question the more likely you are to run into hallucinations and that. But for explaining basic concepts or query things that are well documented it’s really good.

It also sources it’s answers so you can follow the link for further reading if needed.

Just don’t trust it to generate large amounts of code.

A flat 50 column table is usually an indicator of bad design and lack of normalization.

Nosql is absolutely ideal for flat data with lots of columns and huge amounts of rows. It’s like one of its main use cases.

That many parameters is an indicator of poorly structured queries and spaghetti code. There is no way that’s the best way the data can be structured.

While it is popular in the web browser world, it is not inherent to it. Reactive programming is a general programming paradigm that can be applied anywhere, without a UI involved.

Second paragraph

No. This seems like a poorly designed system. Definitely sounds like a nosql database would be a much better fit for this task.

And that many parameters seems like madness haha

100% and if it’s a website I’ll likely lose a few hours digging around to see how it’s done.

I like using Problem detials

It’s fully supported by the .net server pretty much out the box and just seems nice to stick to a standard where possible.