There are a few standards now, DKIM, SFP, DMARC, maybe more now, I don’t know. If you send emails without these configured correctly the reputation of the domain and IP are lowered.

Past some internal threshold, you go from inbox to spam, and from spam to silently dropped.

Further, if you send too many emails in a short time, or more emails than usual, your reputation is lowered.

I’m sure there’s more, but these are the kind of things that make it difficult. You make a config error, don’t realize, then people start not getting your emails. You fix the config, but there’s no way to get the reputation back and nobody at Microsoft or Google to ask to re-evaluate you.

Deliverability to major providers like Google or Microsoft. Can be just getting your emails flagged as spam, or them being sikently dropped and never delivered even to spam. Making it impossible know if your emails are being ignored by the recipient or not even delivered to their inbox. It’s also impossible to troubleshoot.

Mostly reputation of your IP address and domain, things which are hard to untangle. If you manage to get a clean IP you might be all clear.

There’s other configurations that are required and if not right can harm your reputation, it isn’t something you can set and forget.

I hate that it’s come to this, but you are right.

It’s not that it’s too difficult, it’s that there are too many things beyond your control due to the central duopoly of Google and Microsoft for email. If you end up in their bad graces it’s hard to get out, and they don’t care about you, there’s no support or someone to talk to to get off the ban list.

Not who you asked, and I don’t mean this to sound pompous. I don’t believe (there’s probably some but go with me for a minute) there’s any software task I couldn’t do, given enough time to research the domain and understand the problem space.

When folks say they couldn’t do it before, it doesn’t mean they aren’t mentally capable to do the task, it’s the time or speed constraints that are in play. What coding agents do help you close that gap. It doesn’t make you an expert in the field, but as an example it can help you understand the domain, nomenclature, acronyms that you would have had to research.

This doesn’t invalidate your ability to judge a solution as good or bad. It also doesn’t prevent the agent from using code you don’t understand either, so you still have to figure things out but it can help speed some of those up.

Believe it or not, the mcdonakds by me no longer offers counter service. You order at a kiosk and then someone brings you your food. It’s as bad as it sounds.

Mono is not great because for the last ten years Microsoft shipped .net runtime has run native on Mac and linux without wine, so mono has not been seen the investment.

I see your point, but I’m here for Android 17.Are you in the wrong thread? Or am I?

Pushing SSL was probably the last big tech effort/push that actually benefited users. Sure it made self hosting a little harder, and probably consolidated some tracking behind bigger players, but overall end users did benefit.

Most of what I see now is purely for their benefit and users don’t benefit.

While true, the latest opus model has 1m token context. Which is a lot more than the previous 200k limit. Hard to fill that up with regular work, but easy if you try to oneshot a whole product.

Believe it or not in some ways they are better and more flexible and in other ways they’re more limited. Basically they are totally separate situations to the same problem.

Since they now have the same owner, you’ve already identified which one is gaining features and fixes.

While I agree with this, and I’m not defending skirting regulations, before rideshare apps, taking taxis was an awful experience. At least half the time, if you try to pay with a credit card, the machine was “broken”, if you wanted to get a ride at a specific time you had to call ahead and hope that a taxi would show up.

Rideshsre apps forced regular taxis to up their game and provide better service, some did and now have their own apps.

I mostly agree. It won’t replace people directly, but it might let companies do more with fewer developers.

Not to say they don’t need anyone, but maybe they get by with 75 instead of 100 developers? Hard to say where that falls because the outcomes if ai usage are so variable based on skill of operator and the target codebase.

There’s value in brevity and clarity, I took two paragraphs and the other was two words. I don’t like it either, but it does seem to be the way most people talk.

Let’s be generous for a moment and assume good intent, how else would you describe the situation where the llm doesn’t consider a negative response to its actions due to its training and context being limited?

Sure it gives the llm a more human like persona, but so far I’ve yet to read a better way to describing its behaviour, it is designed to emulate human behavior so using human descriptors helps convey the intent.

Non developers and non technical people that are already accustomed to bad software, basically following the broken window problem combined with lack of knowledge to do better.

I’m not saying I agree, and I hope saner heads prevail, but I can definitely see the future trending this direction not because it’s best but because it’s easier and maybe cheaper (by some measurement).

I can only assume he’s got you confused with this guy. @SatansMaggotyCumFart@lemmy.world

I hate that you are right. Giving up electron would likely mean less Linux and mac compatibility. It’s a shame, but it’s likely true.

I have been really enjoying working with Avalonia, it is a .NET library that works across windows, Linux, and Mac and allows you to use C# for desktop app development on those environments. Its what MAUI should have been.

So you’re saying mining crypto is gonna come back into fashion?