Time: since platforms are big machines, their timeline and backlog is huge, and the self-taught geek does not consider (care) that. So when there is an obvious little hiccup somewhere, they create a bug report that asks for details, proof, reproduceability,... and finally get pushed back to eons because there are more pressing concerns to attend to at the platform level. Meanwhile, it takes about 1h (without AI) to code a workaround and feel like a hero because "I've fixed something that took them 3 years to triage".

Hype: yes documentation and code quality and all matter, but it matters even more when it comes from Google or Meta! We all feel little compared to giants and when they open their internal secret tooling framework (with big marketing budget) then we all feel like there is a secret to grasp and a key success factor to wield. So it is not so much whether a npm library some nobody created exists, but whether the main contributor works at a big brand name. It does not prevent smaller anonymous projects from emerging but lets face it, it is much more appealing when it is how Cloudflare handles it at 1e20 scale (because we all feel we face the same challenges of course).

When an image is some px wide and some px high, it provides a shape (ratio between them), because a camera of 12mega px isn't 1px x 12M px in shape, but it does occupy 12M storage units nevertheless.

I agree though that like many IT related terms, their usage is twisted and simplified to amplify the buzz. Because it is more marketing friendly to put a bigger number than exact dimensions and proper terminology.

The self-contained disconnected mode is very convenient, though it could be useful to have an "online access" mode to allow it to access the Internet and perform lookup.

But I totally agree on the fact that it will probably look like just any other frontend.

So if you are able to properly evaluate the outcome, it is probably fine.

It will also depend on the type of frontend and its target complexity. From what I understand from your question, you would handle the backend and infrastructure so these do need higher rigour.

If you apply the principle of separation of concerns, the frontend shall be decoupled from the rest and may evolve on its own end. That means that you have some degree of freedom to test and fail the frontend without harming the rest of your project.

Your end users may not like it much, but from a dev perspective, there is no "flaw".

Also consider that LLM training dataset and available data is huge about frontends, so it is way better at doing these.

Did you witness a download rate drop too?

If you mean that leadership IS the business analyst, then you are in trouble :D

Fictive example: imagine the bias is to inject notion of colorfullness in the text regardless or its content:

"I eat an apple" becomes "I eat a red apple"

The 2nd AI is about injecting size component, so the text becomes " I eat a big red apple"

There you get both watermarks. It is not that obvious obviously

It is as always (think cybersecurity) the cat and mouse game, what is a weapon is also a defense. You, the simple fact that you are on this very site, means that you are probably more educated to AI than most, so it is not necessarily you that will really benefit from any constraining framework.

There are many people believing in many weird theories and those are more prone to be convinced by a nice narrative. AI did not introduce that, it just made it easier and available to anyone with any intent.

E.g. research paper, law makers, lawyers, state policies, notaries,...

These are much longer content and thus statistically they will disclose a better guess at AI generated content.

Asking another AI to paraphrase will not erase the mark (which they are unaware about) but rather cumulatively add their own mark and make it easier to detect.

The problem is not to use AI, but to endorse the responsibility of the content you (as a human) deliver and somehow make sure that fake-news, biased content or unverified output is detected as early as possible.

If you consider a framework on top of any existing language that provides serialization mechanics that include metadata about the item, then you can approach your 2 goals.

I think that one important aspect (whether that is feasible or not is another question) is to have valid coercion. JS has some, but as your example shows, it is not complete.

Is the binary equal value a requirement or is it the semantic value which can take another form but can be interpreted in the same way?

Very interesting topic overall and I've been touching these questions a bit (until I had nightmares).

Actually there are 2 rendering, the server sending HTML and the browser drawing it on your screen.

So why not push the logic and send a jpg image of the rendered content itself. Lol

The whole concept of decoupling the frontend and the backend is that they can be agnostic of each other, they need to align but it is not the same skills/concerns.

Serve rendered html like in 2000 and you have recreated a smart way to do what industry spent decades running away from.

I wonder if they did vet their own process through the same channel: "The 'IsThisBS' process can be trusted to reflect accurate BS evaluation"

BS or not BS ?

I guess we are used to a horizontal layout, some try to be bold with completely vertical but it won't be easy to identify in my wallet.

So I would grant D) that fine balance argument.

They give a tiny example and insist on micro, fast start, but the say it lasts up to 8 hours and is up to 16 vCPU.

What sort of app require faster boot (than lambda or ec2), but only for a limited interval, and with possibly plenty of processing power...

Maybe I am not the right target, but if you have examples so that I can better appreciate, I'd love that

These are primarily driven by skills of the junior. Though you should expect they have none.

What sort of comes out between the lines is the attitude of the person, and I think this matters most and should be framed directly.

You want someone curious that will peek beyond what you asked. Someone proactive that will not sit and wait for an assignment. Someone meticulous that will not self-satisfy of quick-and-dirty.

When said like this, the article content resonates as the consequences rather than objectives.