https://discord.cloudflare.com logo
Join Discord
Powered by
# workers-discussions
  • c
    Thinking either Python or Golang
  • c
    I’m anxious about Golang as I haven’t seen a lot of web stuff for it and Google has a history of discontinuing products
  • c
    Also not sure how many companies want Go vs Python devs
  • k
    omg lol
  • k
    that was not what i was expecting to wake up to this morning
  • i
    I wasn't expecting it to come out as well... I guess an NDA was broken somewhere.
  • a
    yeah this is an awkward way for the world to hear about Pages. Will update when it's available for everyone to use 🙂
  • i
    Yeah. At least put Access in front of the Docs now. Those TODO aren't the best ahahah
  • c
    😂
  • i
    Although, I'm more excited than I was before. I'm still hopeful for the week coming up.
  • c
    I'll be switching away from a Wrangler action to pages on a handful of my sites once it's out.
  • c
    Is Cloudflare still gonna test on production 😂
  • c
    Everyone has a development environment. Some are lucky enough to have it separate from production.
  • c
    haha
  • i
    I guess they should have put Access in front at least.
  • c
    haha
  • c
    how about we promise to keep it a secret for our good friends at the workers team 😉
  • c
    Our friends @User @User @User and anyone I failed to mention are super cool
  • i
    Well, the person in question literally mentioned Cloudflare, so I guess the secret is out ahah
  • a
    Reminds me of when someone found out about Cron Triggers, also through the docs.
  • a
    I would say we should use a fork but people found Durable Objects through a doc fork too.
  • c
    😂
  • c
    Announce features before they're even made.
  • c

    https://tenor.com/Gxh8.gif▾

  • u
    100 forks of the docs for random features so no one leaks the real ones
  • i
    We as MVPs, for almost all weeks of announcements (in particular the big ones) have a private topic where we try to guess. Last year's I got all of them at the Birthday week ahah
  • j
    If anyone has a suggested workaround for https://github.com/cloudflare/kv-asset-handler/issues/158, I'd appreciate it! I'm a bit of a performance fanatic, so if I could dynamically route requests for 
    image.png
    to 
    image.avif
    or 
    image.webp
    where supported (as per the 
    accept
    ) header with 
    kv-asset-handler
    , that would be 👌
  • i
    Couldn't you simply rewrite the path if the specific 
    accept
    header is there?
  • j
    I could reconstruct a new 
    FetchEvent
    , attach a new 
    Request
    with an updated URL, and pass that into 
    kv-asset-handler
    I guess - that's pretty hacky though. As far as I know (and had no luck trying), you can't just override an existing 
    event.request.url
    for example, since that's read-only.
  • i
    It would just be 
    new Request(new URL(...), event.request)
    , it's basically the same code used in the default catch for not found assets. It's remapping to 
    ${new URL(req.url).origin}/404.html
    .
1...131415...2509Latest