C              modern C++
  "int foo[5]" -> "array foo"

  char *(*(**foo[][8])())[];

  let foo: Vec<[Option Vec>; 8]> = Vec::new();

Another ergonomic aspect of the Rust syntax is that you can easily copy the raw type, without the variable name:

  Vec<[Option Vec>; 8]>

  char *(*(**[][8])())[]

Also, I think C# is generally closer to Rust than to C when it comes to the type syntax. A rough equivalent to the previous example would be:

  var foo = new List>?[]>();

On the other hand, encouraging employees to adopt "AI" in their workflows, while at the same time banning "AI" on interviews, seems a bit hypocritical - at least from my perspective. One might argue that this is about dishonesty, and yes, I agree. However, AI-centric companies apparently include AI usage in employee KPIs, so I'm not sure how much they value the raw/non-augmented skill-set of their individual workers.

Of course, in all other cases, not disclosing AI usage is quite a dick move.

With both Android and Chromium, we're ultimately at Google's mercy.

btw, does anyone know if Huawei is following along with this in their fork?

That's why solutions like this seem a little bit backward to me.

On top of that, all server/desktop OSes I'm familiar with, provide better remote control options after boot (that respect UAC) - but maybe I'm simply not the target demographic here.

These days I usually default to pandoc's markdown, mostly because the raw text is very readable.

A sufficiently advanced web scraper can build a statistical model of fingerprint payloads that are categorized by CF as legit and change their proxy on demand.

The only person who will end up blocked is the regular user.

There is also a huge market of proprietary anti-bot solvers, not to mention services that charge you per captcha-solution. Usually it's just someone who managed to crack the captcha and is generating the solutions automatically, since the response time is usually a few hundred milliseconds.

This is a problem with every commercial Anti-bot/captcha solution and not just CF, but also AWS WAF, Akamai, etc.

Amazon, Akamai, Kasada and other big players in the WAF/Antibot industry will charge you millions for the illusion of protection and half-baked javascript fingerprint collectors.

They usually calculate how "legit" your request is based on ambiguous factors, like the vendor name of your GPU (good luck buying flight tickets in a VM) or how anti-aliasing is implemented on you fonts/canvas. Total bullshit. Most web scrapers know how to bypass it. Especially the malicious ones.

But the biggest reason why I'm against these kind of systems is how they support the browser mono-culture. Your UA is from Servo or Ladybird? You're out of luck. That's why the idea choosing a purely browser-agnostic way of "weighting the soul" of a request resonates highly with me. Keep up the good work!

> AI services are expensive to provide, because they tend to be processor-intensive, but competition between vendors is a likely reason for JetBrains introducing a free tier earlier this month

If it's so expensive, why do they force it on everyone? Sure, a lot of folks want support for this, but enabling it by default is just annoying for their long-time users. Not to mention the costs of full AI-completion, I hope they don't get the idea of also enabling that by default.