And once it’s done it’s done. The relentlessness does not continue into, “are you sure?”, it’ll be over.

For the record, I’m in the EU and do not want this to pass.

I tried out the most basic possible example, from the linked page:

    Deno.serve(() => new Response("
Hello, desktop
", { headers: { "content-type": "text/html" }, }) );

There's a downside though... that "Hello, desktop" app weight in at 308MB on macOS.

Now, I don't know how that compares to an electron app, or the most lightweight app possible handcrafted specifically for macOS, and there are many, many layers of abstraction between my 1 line of code and the resultant but that is enormous!

The four emboldened headings that make up the whole article sound like they’re straight outta chatgpt:

* what happened

* the devil is in the billing details

* the big but

* bottom line

I’m not sure that I’ve ever read a Fortune article before so maybe this is just their style. But I doubt it.

> Let us be clear. Artificial intelligence was not created out of thin air. The data and language used by generative A.I. tools didn’t just pop into Sam Altman’s head or Elon Musk’s imagination. A.I. is built on our collective intelligence: our books, songs, artwork, journalism, computer code, scientific research, videos, conversations, images and ideas spanning generations.

As one of the below comments says, you just don't know what level of snooping is going on. If you're reading this $CEO, hi!

The really, really scary thing is how uncommon this approach is. I think.

My assumption is that most people roll with automated pre-written reply. Maybe tweaking a few things here and there, but ultimately preferring the all-too-convenient trade-off of the robots having written something close enough to what they wanted to say, using "better" words. Even when what they would have written themselves would have had some personality, even if it was their own flawed human one.

For the record, I am 100% with you on your approach (on the odd occasion that I must use gmail).

If we’re going to do the discovery out in the open.. it would be nice to be able to specify the prompt as part of the Textile (e.g. “Copy the GitHub URL”). And then also showed the clipboard contents it is going to proceed with, before proceeding. A single key press (Enter?) would be ideal to proceed. That protects me from accidentally passing sensitive data through.

For a use-case where I've copied thing 1, then I start my Textile, then I go and copy thing 2 from somewhere, and then Textile continues with the remaining steps with thing 1 and thing 2?

I haven't read this in detail but "Six CVEs are fixed in this release. All six are assigned by VulnCheck as CNA. Affected versions are 3.4.2 and earlier in every case." seems like a pretty solid answer to the "why".

https://download.samba.org/pub/rsync/NEWS#3.4.3

I’ll be using this to add some extra tags to my pages.

It looks like there are some features noted as “required” that are actually required by the spec (e.g. a title tag), and others that are required by opinion (e.g. https) so there’s an element^ of pragmatic best practice being recommended.

I find it curious that setting a colour hint for the browser is recommended. I’m one for letting the browser look as vanilla as possible and letting my pages do the talking.

^Pun not intended, blink and you’ll miss it

To be fair, the huge window by the desk in the article makes it a naturally more appealing space than my own. But it’s enough to make me rethink the layout we have here so far. Especially since we want space for non digital projects too.

I've thought before about trying to render skies on the web as a series of gradients overlaid on top of one another. I expect I could have had some level of success and gotten some mediocre results, but it would be nothing compared to what you've created.

Thank you so much for sharing this; it's inspirational, must have taken you a very long time to put together, and I'm blown away by your results.

  
Unavailable Due to the UK Online Safety Act

^I find that turn of phrase to be particularly pleasing in this context.

Parsing dates with anything other than fromisoformat feels totally backwards in comparison. We were using ciso8601 until fromisoformat was in the standard library. And now things are incredibly simple and reliable.