They aren’t all hype. They are amazing technology.

A lot of the software built with them is completely just hype though.

Scaled absolutely. Works really well. We have a pr ci pipeline. And cd set up on the trunk. Everything is PRed before being merged to the trunk.

As it’s all 1s in binary you can overwrite any character by doing an or with DEL

We have a piece of legacy software and we have to replace certain symbols in text values as there’s manual SQL construction everywhere and none of it uses parameters.

I’ve seen would you rather be alone in the woods with a bear or a random man somewhere in there.

If I had to guess I’d say the email address was sent as part of the request and not verified.

You clearly haven’t lol

AspNetCore works very much the same.

The mediator pattern is a little different though. It doesn’t talk to the service directly.

The controller creates a request object and passes it to the mediator. The mediator finds the correct handler and invokes it. The result is then returned to the controller.

It essentially completely decouples the controller from the service.

Tbh that’s essentially what we do. Just with a mediator between the controller and services. Maybe a better name for it.

The MVC pattern is really good for writing your endpoints.

In C# I use the mediator pattern and vertical slice.

This means the controller handles everything http related and then sends the mediator request and converts the response back to http responses.

This means I can structure my code however I want and the controllers have no awareness of it and just deal with http.

Same. Writing sites that relied on IE was always a stupid decision and kinda invalidated the point of writing a web app.

I think most people knew that and the managers fucked up big time pushing it. At least in my experience.

But that’s very different to choosing a programming language.

When anyone in a professional setting says they don’t like having a mega corp supporting something I lose a bit of respect for their opinion tbh.

Yes we all know mega corps suck.

But if you’re using anything in a professional production environment that is meant to last in the long term this is 100% what you want.

In 15 years I have never actually seen this happen.

As you’ve said writing generically can have big performance implications.

Almost all projects I’ve seen end up locked in one way or another.

A better approach if you want to do this is abstract away the actual database stuff from your main code.

This way you can do whatever provider specific stuff you need and still allow the option to rip it out with minimal refactoring.

Your main code shouldn’t really care what provider you are using. Only code that interacts directly with the database should.

Depends entirely on how you handle errors.

Make it check a lemmy or x account. If you don’t post for 24 hours it should run.

A huge number of exploits rely on unsafe memory bugs.

The fact you have to rely on external tools to manage these issues perfectly illustrates that the language is not memory safe without extra work and it’s easy to miss things.

It seems much more sensible to just use a language that is.

That combobox looks pretty interesting though.

Not needing to know the exact name of the item you are looking for seems great. Cat leading to pet care is a great example.

I think what they mean is don’t spend your personal time learning stuff for work.

If you need tech for work learn it at work.

If you aren’t learning it we’ll enough at work spend more work time learning it.

If they won’t give you that that’s their problem, not yours.

I think the best advice is don’t make huge decisions based on a small amount of research tbh.

Your personal programming shouldn’t be driven by work requirements.

So here’s what I propose (and what I’ve built as a small demo below):

They’re suggesting it should be part of browser behaviour. They couldn’t demonstrate it without JS.

Dependency injection is the actual act of allowing dependencies to be injected. Which this does.

Creating a constructor that takes dependencies is DI.

Using something to inject them automatically is more inversion of control.