A RESTful service is (usually as of today) a JSON API. They aren’t mutually exclusive things.

There’s no black and white definition there.

However, when someone is creating a RESTful service, they’re stating that they’ll be paying mind to HTTP Verbs and status codes as a fundamental part of their design.

In the original image posted, that dev clearly wasn’t paying mind to the HTTP layer and as such a commenter called it just a “JSON API”, which is the catchall, ugly, Wild West, typical way of doing things.

Once again tho, it’s not black and white. Others can and will disagree and want to be pedantic. I’ve been a professional dev for 35 years, devs love to argue abt this shit.

I would do a 400 (Bad Request). Then, with varying amounts of detail depending on the scale of the project and the framework capability, the response body would be something like: { “error”:true, “reason”: “validation”, “detail”: “user id should be numeric” }

Coding using an LLM and not even reviewing output

Try the link of the post you’re responding to.

Ah yes. “This energy would then be transmitted to one or more stations on Earth”. Simple eh?

Yeah I have a .engineering for my biz. I also registered mycompanyengineering.com to get through places that won’t take the new TLDs.

Usually banks.

HEAD

lol PS/2 ports are the newer ones. There were larger AT ports and ADB ports in addition to the 25-pin(!) LPT port (printer mostly) and COM ports (random peripherals including early mice, pre ps/2)

That’s a very binary mechanism with little excuse for pulling. And there are typically cameras nowadays. No cameras in the bathroom.

Are you able to cite some more specific examples so I can more fully understand what you mean? And what’s the catalyst for them saying “no” to our business, if that’s what you’re implying?

Schools around the country will disable the keyword functionality very soon. It’s useless in such an environment. Kids can and will say “help 911” every time they leave the bathroom simply “for the lulz”. And there’s no video so they can’t be caught doing it unless you station someone right outside to catch them, rendering the feature useless. Malicious actors are the most difficult design requirement for any system.

Oh? We don’t work together with Taiwan and China and India on manufacturing now? What changed specifically?

You mean like we do?

Good greaf

I feel the same way about your clickbait content behind videos. Please be mindful that this is a text based site used for discussion and enlightenment. Your ancient clickbait is annoying to me.

I’m not alone. Read the room. See the votes.

You’re not required to acknowledge or reply to my opinion. But I felt compelled to share.

Yes. I can read a summary or even a transcription in 10-20 seconds. I’m also not somewhere that I want to blast a video from my device.

I’ve been a dev at 8 places over 28 years and have never heard of this level of incompetence since git came along. Prior to git, with cvs, svn, tfs, vss - yeah, lots of incompetence because the tools sucked. Git solves all those problems tho!

Yeah. As soon as I posted this I started thinking through that and realized that I’m completely wrong. It may actually be better for anyone to have China spy on them. In fact, especially USA citizens.

That depends on where you hold a citizenship

Clickhouse has a unique performance gain when you have a system that isn’t operational data that is normalized and updated often. But rather tables of timeseries data being ingested for write only.

An example, stock prices or order books in real-time. Tens of thousands per second. Clickhouse can write, merge, aggregate records really nicely.

Then selects against ordered data with aggregates are lightning fast. It has lots of nuances to learn and has really powerful capability, but only for this type of use case.

It doesn’t have atomic transactions. Updates and deletes are very poor performing.