threepointone

I touch upon this a little in the epilogue section https://sunilpai.dev/posts/seven-ways/#epilogue-ok-but-doesn... I was thinking what work there really is for "juniors" in this new future, and I suspect the answer then that their "job" is to develop the understanding of the codebase, approaching changes from the edges, and learning how to introduce new changes. (very similar to how people would onboard to a codebase pre-llms: by writing tests, doing smaller changes, poking about the code by adding console statements, etc). The good news is that the coding agent is a very good tool to do that as well. I plan on writing more about this soon.

Curious how you think about state that changes outside of a workflow’s scope (like user info in a database)

It is indeed excellent. y-partykit is a library for building a backend on PartyKit, but PartyKit itself isn't tied to Y.js; you can deploy any tech you want on to it.

via twitter: https://twitter.com/tldraw/status/1624739379557109760

Hello! I'm on the team that implemented this. I'll be writing a longer post on the design considerations and implementation details, but roughly - rust wasn't a good case for something that was mostly held back by i/o to the edge; further, the actual cpu/mem intensive part was handed off to webpack which was written in javascript. So wrangler v2 flips that design around, using typescript for the outer shell, which makes it easier for our users and community to contribute to the tool, and esbuild for the core part of parsing/bundling code (we may switch esbuild to a rust based bundler like swc in the future).

Yeah agreed, this is pretty ad-hoc right now, smeared across different commands and config. We're working on a better solution, will share more details when we have something. Thank you for your feedback!

Could you share more detail about your usecase? What kind of checks are you looking for? I'd be happy to have a look at that (and presumably if we could do it before it gets uploaded, that would be great)

Also, every page has an "Edit on Github" link so you can go straight to the page you're seeing (in this case - https://github.com/cloudflare/cloudflare-docs/blob/productio...)

Fun fact, that post 3 months ago was what got us folks at cloudflare in touch with the author, who then interned with us for 2 months (today was his last day!)

Great feedback! Some quick replies -

- > `wrangler login` doesn't work if I'm not already logged in to CloudFlare website This should be fixed in our last release!

- `wrangler dev` is slow. Agreed. We're working on making it faster, but miniflare is a great option for the fastest dev experience at the moment.

- Regarding DNS/domains/Workers, this is all great feedback. We should be making this more painless/intuitive. We'll work on it!

No specifics to share just yet, but we're definitely going to integrate wrangler more deeply with miniflare.

Errors - We're getting better at this. You can now use `--inspect` and use chrome devtools which should log proper exceptions (details to setup https://blog.cloudflare.com/profiling-your-workers-with-wran...) Console.logs - same as above! Real devtools, interactive and everything. Timeouts and crashes - This should be better now, timeouts and sessions expires now transparently heal and restart, so you shouldn't face errors (Please file an issue if you see different!)

Overall we're working hard on making this experience better, please feel free to file issues if you see anything that's not expected. Thank you!

We should definitely not have examples on the docs that don't actually work. I'll fix this.

That sounds like a terrible experience. I've reopened your issue and assigned it to myself, will investigate it soon.

I've faced this too, where you'll save, then hit refresh, and it show the previous version; despite the fact that we "know" that the code is changed. SO we should be able to queue requests when we have a new version uploading (and of course, make the whole thing faster). Thanks for your feedback!

This is amazing feedback, thank you very much! I'm going to work on each of these; but quickly - we definitely shouldn't have something that works in `wrangler dev` but not in the platform, and we should warn/error on that, our docs shouldn't have examples that don't work :facepalm:, and we should be spec compliant where we can. Thank you so much!

I'm so sorry you had to deal with that. We're working on removing a lot of friction from the onboarding process, and making it easier to introspect what everything's doing. Thank you for your feedback!

Honestly, agreed. Lemme take this back to the team.

We also don't have a lockin to webpack anymore (you can choose custom builds with the "javascript" type, which I admit is a little confusing). We're going to move away from even this dependency and make everything much faster and lighter, stay tuned.

Ohhh I remember this too, I hated how it consistently dropped connections. A community member fixed this for us (here https://github.com/cloudflare/wrangler/pull/2008) so that it transparently and automatically reconnects now and the experience has gotten so much better.

And of course, miniflare reduces even the chance of that to zero :)

Yeah, we recently made improvements so `wrangler tail` works without falling over, and we also show logs directly in the dashboard now (https://blog.cloudflare.com/introducing-workers-dashboard-lo...) More improvements coming, I promise.

That bad, huh :( But I hear you. I'm working on making this better right now, I'd be happy to hear any complaints you have, and I hope we can get you back.

Hi there! I'm on the team, and we're going to invest a bunch of time and effort on making this experience much better. Happy to hear any specific feedback if you'd like, and I'll prioritise it. Feel free to reply here, or DM me on twitter @threepointone.

Stay tuned, things should get better soon.

How do I blacklist my own urls from this website?

merged and published, thanks!

Hi folks, author here. I wrote this for myself for a docs site I'm building, and didn't want to ship a markdown parser to the browser. It's mostly for aesthetics, without sacrificing performance. Custom components for primitives are a nice addition, especially for styling.

I don't know whether it's a good idea, but I like it so far.

ahem. my bet - https://github.com/facebook/css-layout

cannot wait for more details.

https://i.imgur.com/sBGycyF.png

(would give - curl 'https://news.ycombinator.com/news.css?Iufnib6nCakqGh6wo0m6' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36' --compressed )

I'll quote it here anyway, for the benefit of other readers -

What’s A Backdoor? • A method to bypass data encryption or security • Does not require the password or passphrase to be known • Saves time, cost and effort to access encrypted or secured data • Allows data to be accessed, copied and even modified without tipping off the owner • Currently available for major encryption software – Microsoft Bitlocker, FileVault, BestCrypt, TrueCrypt, etc • Currently implemented by major cloud storage provider to comply with NCMEC requirements

sudo gem install