Very cool, glad to see more movement in this space. I've used Cloudflare Images quite a bit but found that it seems to regenerate images rather than serve them from the cache more than I'd expect. Look forward to giving this a go. It's a shame the pricing details aren't available yet.
This looks cool, but the pricing isn't exactly clear. Website says $0.50/1K API calls and then the HN title says $0.50/1K map loads. Is a map load === 1 API call?
I feel like everything I have that supports HomeKit requires the manufacturer's app installed so that HomeKit can interface with the accessory through the app. Which always felt like it defeated the purpose to me.
Yeah - "keynote" seemed to imply a big presentation. Not 15 minutes, most of which was literally already released video content. Now confused what is the point of "day 5" if the big reveal is done.
What's more - the public status page of this security incident (https://status.heroku.com/incidents/2413) doesn't mention that these secrets were compromised. They chose to send this notification privately instead.
I think there's still demand for native Mac apps. Look how many people are disappointed to see 1Password go from native to Electron. Sketch, Pixelmator, Nova are just some examples of quality native Mac apps that are doing well.
Interesting, I find it exhausting instead. I'm intrigued by Redwood and glad to hear it hit 1.0 but I'd rather see everything they have to say now instead of having to "stay tuned" for more. I either remember to come back in a few days to see what it was or I forget about it and miss out on what could have helped convert me into a user.
It's crazy how much of the ecosystem is behind, despite Vue 3 technically being available for a while now. Honestly think I'll be looking to migrate away from Vue instead of up to 3.x.
Only semi-related, but why does Cloudflare perform so poorly in Oceania? I've noticed less than stellar performance in Oceania with Cloudflare's CDN, so to see similar stats with workers makes it seem it's not a product-specific issue.
Really excited to see this launch. Cloudflare do a good job at making some complex/painful workflows painless, even if they aren't as feature complete as their competitors.
I was hoping their pricing would undercut some of their competition - doesn't seem like I would save much if I moved from Cloudinary, for example. But definitely something I'll consider on future projects.
I do appreciate this pricing model vs. others like Cloudinary that penalise you for creating more variations. Trying to serve the best image sizes/formats per device is best for the user experience.
Semi-related; I'd like to see Cloudflare improve their CDN performance in the Oceania region.
I love this, this is a great product for them. Cloudflare has clearly been laying the groundwork for this recently with the Image Resizing feature.
I look forward to seeing what the pricing is, it's disappointing they didn't announce it here. I feel like they've tried to obscure the pricing for Image Resizing, and only made it available to Business customers.
Would love to see Cloudflare be more upfront with the pricing around their image products, and make them available to Free/Pro customers as well.
As someone who works with Rails and Laravel, one of the huge benefits I find working with PHP/Laravel are the speed and consistency of releases. PHP seems to release versions more frequently, and Laravel tags every week. It means there's much less lead time to work with new features/functionality as it becomes available (when it's stable, rather than running on edge).
I appreciate that their Twitter account is looking into it, but feel like this should be a pretty quick fix. I'm hesitant to even log into my Backblaze account again until it's sorted.
It's boring having different Rubocop settings and having people argue over new rules. I have preferences too, but I'd rather get on with my life. I can just write code, and have Standard make it standard and consistent across all projects.
It would be nicer if Ruby did this itself (Crystal does, and that's fantastic) but this is the next best thing. Having one attempted standard is better than no standards at all.
(My only quibble is the name makes it sound related to the Standard JS project when it doesn't).
I've played with Crystal a number of times and love it. It ticks a lot of the boxes for what I want in a language.
However, there seemed to be some confusion about whether the language could continue with inferred types or whether you'd need to annotate yourself - and what that would mean for compile speeds. I'm hoping those concerns can be resolved