The comment your replying to used Quest 3. No need for Apple. Steam Frame will probably have a color camera module too and be even more flexible as a real computer.

The thing I'd worry about is it slowly handing over control of Linux's direction to the tech companies who control and regulate the AI being used to help develop it. The complexity is only growing. These companies are themselves extremely political and decide what AI is and isn't legal when Linux demands using the most capable models for security reasons. So it would be good at least if the project actually cared and had it's own principles besides ignoring the politics.

But the code being GPL means those companies don't have control over it. They can restrict the use of AI but the codes already generated, they would just go back to writing by hand. Its a non-issue. The same objection came up when Microsoft started contributing to the kernel.

And despite the author’s logical leaps; no it's not impossible to fork the kernel and go another route. The fact it doesn't happen is because its stewardship so far has been exceptional.

It's not a political issue. It's a religious one with the anti AI people raising pitchforks.

Test: 'There is no greater joy in life than typing a sentence, realising it needs a clarification, a caveat, an addendum, but in the same sentence, not a new one, and, guess what, the comma is right there for you. You want to package things neatly together, and the comma lets you do exactly this. Commas make writing feel like you are assembling lego bricks.'

I like using commas for spacing though em dashes do the same thing and avoid the run-on police?

I would always prefer to do:

"There is no greater joy in life than typing a sentence, realising it needs a clarification, a caveat, an addendum (in the same sentence, not a new one) and, guess what, parentheses are right there for you."

> There is no greater joy in life than typing a sentence and realising it needs a clarification, a caveat, an addendum (in the same sentence, not a new one) and guess what? Parentheses are right there for you.

That's what I'd do. Note the conversion of the first comma to "and," as well.

I like this. It feels like more a person talking and less like a prepared speech.

The parentheses bind tightly to "an addendum" and change the meaning

Not with my brain's precedence parsing rules.

That might lead to a lisp singularity.

Your first sentence is a perfect example of why emdashes need to exist. The comma is overloaded, since it can be used both as a list separator and for parenthetical asides. But that first sentence starts using them as a list separator, and then inserts a parenthetical aside into the list. Emdash wins this test.

I think parenthesis are ideal for a parenthetical aside.

I sometimes prefer parenthesis for very short asides—say, three words or fewer.

I find m-dashes easier to read for most other purposes. They’re nicer in longer asides because they’re a little more visually prominent, while also (for some reason) not breaking my mental flow quite so much. They’re far nicer looking when an aside comes at the end of a sentence, as you don’t need to close an m-dash. That always looks like crap with parenthesis, as if the author should have thought of a way to avoid doing that, while with the m-dash there’s no problem at all.

Em dashes don't nest (but that's probably a good thing).

That is a weakness of sorts, but yes, unless one is attempting a particular, niche affect, an urge to nest parenthesis is usually a cue to re-write the sentence instead.

hmmm... three or fewer?

I think it's generally accepted that parentheses are more parenthetical than emdashes.

It's a bit like 2 space indention versus 4 or 8 space. I find the em-dash example pretty compelling because visually relaxes my eye more than commas do — similar to how prefer at least 4 space indention over 2.

(Unrelated: The alt-code for em-dash on Windows is Alt+0151. I just typed my first manual em-dash wow exciting.)

Microsoft recently introduced typing via Windows key plus hyphen (en dash) and plus shift (em dash). Much easier.

I think offsetting the em dash with spaces is contrary to almost every style guide.

Chicago does it one way and AP does it the other.

I definitely prefer it un-spaced, though, personally.

MLA and APA as well as Chicago.

I think this is a localisation issue; in the UK, it's much more common to see space-surrounded em dashes.

As far as I know, the UK styles that recommend spaced dashes are using en dashes where US English would use em dashes, and the ones that actually use em dashes, like Cambridge or Oxford, are unspaced.

I just thought of the most annoying blog in the world. Individual spacing between words, depending on how thoughtful you want the pause to be. And by "individual" I mean a different floating point number denoted amount of em each. em > em-dashes. Or put differently, em dashes em-dashes.

Yeah. They also use em dashes to repeat a word with emphasis, something that is done much better with parentheses and italics.

> And also occasionally — occasionally — one just needs a random dramatic pause.

> And also occasionally (occasionally) one just needs a random dramatic pause.

I know which one I'd rather read. Though, frankly, I'd prefer neither and I'm trying to remove this kind of thing from my own writing.

I can't be the only one that reads those two examples very differently.

In a first example, the second "occasionally" is stressed, when in second example it feels almost whispered.

It's really hard to find style guides on reading specifically.

But what I see from trawling the posts made by narrators, a lot of them do mention that em-dashes are read as interruptions with sudden tonal shift, while cursive implies a non-interuptive tonal shift.

That said, apparently, most audiobook authors actually supplement their own guidance on how to read their books. I haven't found any universal guide yet.

Interesting, I read both as emphasized. To me, the parens make the voice clear but the em dashes make it read like a typo.

I read the parenthesis as a secondary thought that is there if you want to take in additional context but where the main message can be read just as well without, whereas the em block is a deliberate interruption to call attention to context necessary to understand the main message.

I think you demonstrated exactly why avoiding em dashes like the plague makes for hard to read sentences.

why?

I think it was $25,000...

Worked in my Firefox on Steam Deck. I was amazed it could run YouTube.

So funny story, supporting web codecs may have been a bad idea because it led to people using more traffic per session than we assumed at first. We had to add more servers mid HN post

We had completely saturated NICs on like the two original servers

What makes it require that WASM extension you need the flag for in Firefox? Was there really no way to work around it or polyfill it for it to work? It is performance critical?

It is required in order to yield the event loop and force an implicit sync on OffscreenCanvas. There is technically a slower workaround for this but JSPI is coming soon anyway to firefox 153 and safari 27.

Seems easy to fix it and say 'no CORS proxy' and 'no need to host your own server'. It was very confusing to me too.

You are definitely right, going to see if I can talk to the relevant person to fix the wording on it

>Why not route traffic through my actual browser?

Because you can't. Not even an Extension is able to. Browsers don't want you to bypass their content enforcement. I wish we had at least one hacker friendly browser.

Extensions can't, correct but I wanted to bring up a special case regarding this

Isolated web apps a chrome feature for developing apps that run in chromium based on HTML (but tbh only really used in Chromebooks) do support raw TCP sockets so if this was ported to an IWA you could have Firefox on a Chromebook without an external server needed.

Chromium CEF could also embed the Puter proxy inside it too as a standalone application. No luck on Mobile though.

No, it is possible with extensions.

Extensions can inject headers, such as Access-Control-Allow-Origin: *, to unblock cross-origin requests. In the Manifest V3 context, however, that might require patching window.fetch and window.XMLHttpRequest.

For example,

  // content.js
  window.fetch = async (...args) => {
    const request = args[0] instanceof Request ? args[0].url : args[0]
    const config = args[1] || {}

    return new Promise((resolve, reject) => {
      chrome.runtime.sendMessage({ action: "proxyFetch", request, config }, response => {
        if (response.error) {
          const err = new Error(response.error.message)
          err.name = response.error.name
          err.stack = response.error.stack
          if (response.error.cause) err.cause = response.error.cause
          reject(err)
        } else {
          const base64Data = response.dataUrl.split(",")[1]
          const bytes = Uint8Array.from(atob(base64Data), c => c.charCodeAt(0))
          const contentType = response.headers["content-type"] || "application/octet-stream"
          const blob = new Blob([bytes], { type: contentType })

          const status = response.status
          const statusText = response.statusText
          const headers = new Headers(response.headers)
          const body = status === 204 || status === 205 || status === 304 ? null : blob
          resolve(new Response(body, { status, statusText, headers }))
        }
      })
    })
  }

  // Background.js
  chrome.runtime.onMessage.addListener((message, sender, sendResponse) => {
    if (message.action === "proxyFetch") {
      fetch(message.request, message.config)
        .then(async res => {
          const headers = Object.fromEntries(res.headers.entries())
          const blob = await res.blob()
          const reader = new FileReader()
          reader.onloadend = () =>
            sendResponse({ status: res.status, statusText: res.statusText, headers, dataUrl: reader.result })
          reader.readAsDataURL(blob)
        })
        .catch(err => {
          const { name, message, code, stack } = err
          sendResponse({ error: { name, message, code, stack } })
        })

      // Keeps the message channel open for the async fetch
      return true
    }
  })

This is a cors bypass but part of this demo is that it's full Firefox including TLS support. Using this still means intercepting all requests in an inspectable medium and does defeat part of the point

This isn't enough for every website to load normally.

> Browsers don't want you to bypass their content enforcement

I for one am happy that browsers dont let any random web page i visit port scan my internal network.

No one said any site should. Letting a site you control do it is a perfectly valid user choice. Otherwise people are stuck going through third-party proxies which is far worse.

What is the standard non-renewable resource used for the recovery process? What materials are used up as catalysts to convert it back?

Sulfuric acid, hydrogen peroxide, sodium carbonate. Not catalysts but reagents. Most currently come from fossil fuel feedstock but that isn't essential.

Why would any of those compounds come from fossil fuels? Sulfur is mined, hydrogen peroxide is water with some oxygen taken off, and sodium carbonate is made from salt and limestone

Because they can, because when refining petroleum products you get a lot of crap that's not carbohydrates

Sulfur is produced when the H2S is removed from petroleum and natural gas. Elemental sulfur is burned to produce Sulfuric acid using the Contact Process.

> hydrogen peroxide is water with some oxygen taken off

Isn't it water with some oxygen added?

more importantly what is the cost versus getting it the non recyclable way

that way is 100% non-renewable, the important questions are the total long term costs

Pretty slick it has Three.js built in. I've not sure I've seen that in a language before in the standard library.

it's standard r6rs scheme