avidal
avidal on Hacker News
Very cool. I've been using worktrees a lot recently at work, mostly reworking tools or CI jobs that try to manage branches into just using a worktree and cleaning up after yourself.
It's made a big difference in readability and cleanliness. I'll often use, eg, `mktemp -d` with a template argument that's relevant to the usage, then use the base name of the temporary directory as the worktree branch, followed by `git fetch <remote> <remote-branch>:<worktree-branch>`.
I've been thinking about using worktrees more for my general development, since I'm frequently working across multiple branches.
I regret not finding an opportunity to check the old place out on one of my many visits to the SF office, but it's awesome to see that the new place is finally coming to a close.
Didn't realize it had been so long, but I suppose I left Cloudflare like 3.5 years ago and I know it was a bit of a pain in the ass just trying to buy the property here in Austin in the first place.
From context, I'm assuming Microsoft / Amazon / Google, referring to Azure / AWS / Google Cloud respectively.
Heya Dave! I see your name pop up every once in awhile in various places. We first connected on that MUD many many years ago if you don't recall.
vscode.dev is still for local development, not remote. It uses browser filesystem APIs to access your local filesystem. Whereas code-server runs on the remote and exposes a web server for you to connect to which serves up the filesystem on the remote.
This was an incredible resource back when CBVs were first introduced. While I tended to prefer function-based views (when I was still heavily using Django), this page was the first one I opened when I knew I was going to be using a CBV.
Thanks to the authors/maintainers!
Cf has really mature trust and safety as well as security teams and tools. I've no doubt they've taken bad actors into account considering all of the other offerings they have that have also attracted bad actors.
These things are very cool. I buy wood from a local wood yard every year or two (I don't use much here in Texas, but we do love our firepit and fireplace when it's cool enough), but the splits I get are often too large to easily burn. I'll often buy a bag of kindling when I pickup fire wood, but the kindling doesn't last long.
The main reason I didn't get a kindling cracker is because I don't have a stable base to mount it, although I suppose I could manufacture one next to the wood rack. I did, however, get a hydraulic wood splitter[1] which at least helps split some of the really large logs into something more manageable. It's pretty simple to use and very effective, even on the very knotty and hard oak wood out here.
[1] https://www.harborfreight.com/lawn-garden/outdoor-power-tool...
As far as "vote rings" are concerned, the CTO (and others) would emphatically remind people not to upvote to ensure we didn't end up getting flagged.
Have you seen gron[0]? It's similar: flattens JSON documents to make them easily greppable. But it also can revert (ie, ungron) so you can pipe json to gron, grep -v to remove some data, then ungron to get it back to json.
[0] https://github.com/tomnomnom/gron
We're excited about it also :)
I've been at Cloudflare just over a year now, and if there's one message that's been drilled into my head it's Trust. We understand that we're in the position that we're in largely due to trust. I like to believe that even if our CEO is a secret lizard person you'd get whistleblowers coming out of the woodwork if we tried to exploit our users.
I'm curious on what's missing from Cloudflare Workers to allow you to remove the API Gateway usage. We're actively looking for more advanced use cases so we can make sure we prioritize upcoming features. Reply here or send me an email at <username> at cloudflare.com.
It's something we're iterating on, and the results are so far looking promising; but there are a few scenarios in which they may not work (yet). If you reach out to your SE they should be able to get into specifics.
Cloudflare has a transparency report[0], updated twice a year.
In the transparency report there's a warrant canary:
Some things we have never done
Cloudflare has never turned over our SSL keys or our customers' SSL keys to anyone.
Cloudflare has never installed any law enforcement software or equipment anywhere on our network.
Cloudflare has never terminated a customer or taken down content due to political pressure.
Cloudflare has never provided any law enforcement organization a feed of our customers' content transiting our network.
[0]
https://www.cloudflare.com/transparency/
I personally use XXX all the time; but I tend to use it in places where perhaps ATTN or NOTE would be more explicit.
It may be simply an artifact of other code in the past; when I switched to vim ~10 years ago I noticed XXX was specifically highlighted along with FIXME and TODO and so I used it as a third option: here's something that doesn't need to be fixed, isn't really a todo, but you should read and understand.
Interestingly, I just did a quick check in vim to see which prefixes were highlighted and ATTN / HACK were not, but the usual suspects (BUG, FIXME, TODO, NOTE, XXX) were. I should probably use NOTE in most places that I currently use XXX...
Yep. Been a long requested feature. One of the reasons why the post states: "This feature also removes the last significant barrier to migrating legacy MySQL applications to PostgreSQL."
That's what I want to know. There are dozens of es6 transpilers.
Where do you see that @transaction.atomic is deprecated? It's not in the release notes[1] and if I recall correctly, was only introduced in 1.6 as a means to come up with a consistent API for nested transactions and savepoints. Are you implying that it's deprecated as a decorator? Even if that's the case, I still can't find a source.
[1] https://docs.djangoproject.com/en/dev/releases/1.7/
So, you can only bind to '0.0.0.0'? Which means, by default, you're opening up read/write to the specified directory without permissions, to the entire world?
Maybe the default should be 127.0.0.1; and if the user specifies 0.0.0.0 then it comes with a big fat warning?
Seems to me it's actually writing to the database twice for each page view; once to update the render_started_at property on #845, and once again on #881.
The homepage mentions you can use your account here to stream content to any device, including consoles. How does that work? Can we connect to it as a network file server?