The Lounge

Smoke and mirrors security at its best.

That was never a problem when I was actively programming, and I believe that was extended as part of their adoption of OOP with version 5.5+. Back in those days, testing was performed by setting up instruments with string commands, then triggering them with events generated by the test code. Reports were collected by reading instrument registers, so string length was never an issue. I was happy with the introduction of named Calls at the time, as everything the company I worked for used procedure calls that had numbers, and the only way to find out how to call them with parameters was to beg the Systems Programming group for documentation on a particular Call. Strange times, and everything was proprietary and dynamic; it wasn't unusual to use three programming languages on one Project. We are so very much better off today! Will Rogers never met me.

Wordle 1,001 4/6* ⬛🟨🟨🟨⬛ 🟨🟩⬛🟨⬛ 🟩🟩🟨🟩⬛ 🟩🟩🟩🟩🟩

Thanks for that tidbit! I may just have to try it, since cables are so cheap. Will Rogers never met me.

Quote: Any POSIX-compliant Operating System" Microsoft Xenix :laugh:

Well, those of us who earned our wings working 40 years ago with Commodore's digital serial protocol (IEC Bus), we don't find USB's spec weird at all. Next! :-D

That's not really Swagger's fault. Swagger is just (generated) documentation of a web API with the ability to test the API. If the API sucks, so will Swagger. If anything, Swagger showed you the API sucked and that you didn't need to invest more time in it. The only "bad experience" I've had with Swagger was it breaking when doing some non-standard API development (like having a single endpoint for all functionality, don't ask...). I can't really expect Swagger to handle such weird edge cases. Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript

Beware the ides of April, it may tax thy soul. "A little time, a little trouble, your better day" Badfinger

Not bad. Rather Pleasant. I sometimes code to that 40 Hz binaural stuff.

The "Three Laws of Robotics" suggested by Isaac Asimov is now revealed to have an assumption id est said laws can be programmed w/o error. Other than human error now of course we know the mode of said programming id est LLM results in occasional hallucinations.

The Senators needed to get their point across.

Interesting. In TX at least, one could get money on empty glass bottles (not much but some). And for awhile one could get money by the pound for aluminum cans crushed into bricks. Not sure how it works these days. I agree there is some incentive to recycle. To be honest, recycling is major process all should take advantage off. "A little time, a little trouble, your better day" Badfinger

The Progress of Invention in the Nineteenth Century, by Edward W. Byrn.[^] ... reading through THIS, you won't find anything about Flash Gordon's spaceships OR running stuff on invisible wires either. Just so ... (I say this because there are lot's of pictures in case you don't like reading)

Sander Rossel wrote: I've got this theory that at least 90% of programmers are a bunch of bunglers My theory is that 80% of people are average. 10% are excellent. 10% are not very good. That after all is basically how normal distribution works. But of course one must keep in mind that people are complex. As such they might suck at one thing but be great at another. Time, complexity and economics will always have an impact on any idealization that one might have started with. Not to mentioned efforts that and up only half done due to some 'better' idealization halfway through. So no point in me agonizing over might have beens when I wasn't even around to see what those people had to go through.

honey the codewitch wrote: Back when I learned to code solving problems like this meant you were a coder. At least for me when it was always 'do it myself' the following was true - There was a lot less available - I didn't know how to find it. - What I could find cost money. Sometimes quite a lot. - I figured no one else could have possibly been doing the same as what I was. honey the codewitch wrote: Now it seems like people just expect that there's a library that will solve whatever problem they're after solving Now it is many years later - Of course someone has already tried to do this before. - There are a lot better ways to find it. - It probably costs nothing or very little (at least compared to long ago.) - My time is better spent evaluating existing solutions and gluing pieces together versus trying to implement everything from scratch. A lot of the above comes from realizing that throwing code is just a tool and not genius. What really matters is that the company sells something so that I keep getting paid.

Far as I know AI relies on volume. So the entire library of New York Times articles. No real people vetted the content first. And text is text. Very consumable as just that.

I didn't read the replies first, but will post my response to the question. I started working on a customers PHP project in Sept 2020, which was written in PHP 4.2 between 2004 to 2010 by some Chinese students from China. They did a terrible job, and everything you can possibly do wrong they did wrong. I can't even read the code. Anyways, it was so bad, that I told the customer that they really need to sort of start from scratch again. Why I chose pure PHP 7.4 for them. Drum roll please .... Because of time and money ... So many of the new technologies are constantly being updated so fast, that it's hard to keep up with the changes. PHP 7.4 is still that Swiss Army knife that can do almost anything, and PHP doesn't bug you to update code, or doesn't require a team of skilled software engineers to maintain over decades. Once you write it and deploy, it can run for a long time without more time and money. I can move on to the next project, and the customer can use their new app for years to come, and pass that app to their next generation of children that will take over the business when they come home from College or University. Our economy in the US has a strong service sector, comprised of small business owners with family involved, and have become generational now spanning their services across decades of time. I look at pure PHP 7.4+ from an economic point of view, and not from a superior technology point of view, considering time, labor, capital investment and maintenance being more stable and predictable across good times and bad. I don't agree with PHP Laravel as being a framework built on PHP, but opted for pure PHP, in which I was able to build a near MVC type of Web Application using modern objects and smarter HTML views with the objects, and include robust HTTP request and response handling, and robust security features. I have no regrets in my decision for my customers path forward, and I'm very happy with the results. Well that's my argument for PHP. May not be what you were expecting to hear or read, but I hope it satisfies your thirst to know why. If it ain't broke don't fix it Discover my world at jkirkerx.com

You rarely go off guesses don't you?