We had that in 1999 - JScript

I did a similar project back in 2003. MS CRM 1.2. MS Great Plains. Integrating with an OS/390 via DB2 and MQSeries. Fun stuff. I survived. MS CRM wasn’t even the biggest pain points!

Pretty sure all of it has been hacked in the past 10 years anyway. At least phone, address, ssn all got taken several times now.

Very different. This means default ignore all errors and continue to the next line. You’d have to explicitly catch every line in most(all?) other languages.

You do get a feel for where the important parts of the error actually are

Yes, after decades of scanning large pages of text - code, errors, logs, search results, etc - a programmers ability to apply pattern recognition to screens of letters can be truly remarkable.

Your entire comment is argument from fallacy. Lol

Ah yes. Life before Agile was wonderful.

Closed as a duplicate

Yeah and it won’t tell you that it hasn’t seen this pattern before. It will just make things up out of the blue which seem like they might be correct.

Stay away from ChatGPT for bleeding edge things.

What OS do you run? Are you planning on sharing this app with others? Should it be a web app?

Happy to help!

In my 30 years of experience, it is usually the devs.

I’m well aware how async works in the single threaded js environment. All code blocks the main thread! Calling await on an async operation yields back.

You’re right, async is commonly mixed up with multi-threaded. And in fact in many languages the two things work hand in hand. I’m very aware of how it works in JavaScript.

We are agreeing. Don’t need more info.

Yes I’m simplifying a LOT, but in the context of background web calls, that was what callbacks became so important for. XMLHttpRequest in IE 5 sparked the Ajax movement and adventures in nested callbacks.

Prior to that, the browser had window.setTimeout and its callback for delays and animation and such - but that’s it.

The main purpose of all this async callback stuff was originally, and arguably still is (in the browser), for allowing the ui event loop to run while network requests are made.

NodeJS didn’t come into the picture for almost 10 years or so.

It can lock up a UI doing cpu bound work. Making a web request, no. Preventing the ui thread from waiting on native IO is what async was created for.

Symlink a git tag?

It’s domestic as well. Red vs Blue is just a distraction and you can’t point this out because nearly everyone is divided along those lines to the point of ignoring getting fucked up the ass.

Interesting. I never really realized how it was more my path changing than the entire industry.

Isn’t all hosting containerized at this point? Is hosted, language specific servers still a thing?

I’ve been out of the market for a while now and just run everything as containers on aws and gcp

I’ve done 35 years, but the first 25 years on the dark side M$.

How do u learn this voodoo