I have really been enjoying using it. It seems very good at handling simple but time consuming problems although I find longer chats it seems to forget about the previous code and gets muddled. I am using it in Zed and also with a Claude account as I find I can hit the daily limit when using it for a few hours.
I only checked HN as I started getting service unavailable error pages in the middle of it helping me rewrite some code.
Only really tried it with embedded C and Next.js stuff and it can make a few unsafe mistakes but when I need a helper function it is much quicker than me finding one myself.
It’s a e-commerce style site with ISR. Product pages are cached for 24h with pricing fetched on the client to save the revalidate. I think I worked out what the price increase is though and it’s the edge network £2.40 (London) per million requests. From what I can tell most requests are bots and scrapers so it might not be too easy reduce. The pricing actually seems quite high when compared to other CDNs but I might have misunderstood it.
The tone of the email was a bit strange for a $960 a year increase suggesting we optimise but not yet providing what the cost increases are from. I appreciate we will get the updated usage metrics later in the month but it makes it slightly hard to explain to management why costs are increasing.
Most of our increases I assume will be the data cache pricing and the only real way to optimise that is to move data fetching out of data cache and use our own cheaper caching layer.
I am really disappointed by this. One of the reasons we moved to GCP from AWS was the ability to create multiple clusters at no extra charge. Now it looks like the pricing matches EKS.
Just wanted to add there is a bridge for Linux but it's in beta. You just need to email them at [email protected] and although it sucks there is no full text search most of the attraction is that your emails are not indexed in plain text.
I just can't stand Celery as a project. It takes ages to stay up to date and I have had a few issues with it which just should not happen for such a large project
GitHub is the website 90% of the packages I use are hosted on. All our company code and hundreds of hours are invested into whats hosted on it. I would hate to see this change...
We have kind of the same thing. All data is in an API which is less than a cheap VPS and display messages to them about using the API if they get blocked but they just come back with a new IP every time.
Please don't remove these tags. Our system needs them to tie up your orders to where you came from and your personal information. Which we can use to analyse and ensure we spend more money on targeting people like you.
I think the real issue here is that zooming does not fix it. I can understand most people don't test every screen size (although we test loads) and would be happy to zoom out for some pages. What I ended up doing was using dev tools to switch to a normal size which was kinda annoying.
Linux Chrome 65.0.3315.3. Resolution 2560x1440. Looks like it just gets bigger the larger the view width `font-size: 1.7vw;` Probably want to constrain that. See https://i.imgur.com/erOZkOT.png
I only checked HN as I started getting service unavailable error pages in the middle of it helping me rewrite some code.
Only really tried it with embedded C and Next.js stuff and it can make a few unsafe mistakes but when I need a helper function it is much quicker than me finding one myself.