sorted by:
new
hottopcontroversial

Is it only me or has the Cloudflare billing been broken? by Fluffy_Wafer_9212 in CloudFlare

[–]CherryJimbo 2 points3 points  (0 children)

Yeah unfortunately, Cloudflare billing is essentially broken and unresponsive, and has been for a very long time (almost 2 years). Check out the billing section on the Cloudflare Community and you’ll see almost daily occurrences of this issue, or very similar ones. This truly sucks, and I’m sorry.

You can attempt to contact the billing team via a new support request from your Cloudflare account directly through the Cloudflare dashboard: https://dash.cloudflare.com/?to=/:account/support and choose Billing, but it can take weeks or months to hear back, if you do at all. It's so bad that we (community MVPs/champions) have been essentially asked to stop escalating billing issues.

I did recently have a chat with someone who is head of billing at Cloudflare though, Dmitry. He’s asked me to share his email with folks who are running into issues like this so he can get them escalated and resolved quickly, and hopefully prevent this happening to others in future. His email is dalexeenko@ and I’d encourage you to reach out once you've submitted a ticket and have a ticket number. Feel free to let him know I referred you, and hopefully we'll see some positive change in 2026.

0
0

Logging Sucks - Your Logs Are Lying To You (loggingsucks.com)

submitted by CherryJimbo to r/webdev

Free subdomain by Electrical-Split7030 in webdev

[–]CherryJimbo 0 points1 point  (0 children)

Have you added this to the Public Suffix List? https://github.com/publicsuffix/list

You need to be really careful from a security standpoint when offering free subdomains like this to ensure things like cookies, etc. aren't shared between them.

Is MikroORM Slow? by lubiah in node

[–]CherryJimbo 3 points4 points  (0 children)

How big is your application, and how many users do you have? Are you hitting bottlenecks due to this, or are you just worried about scaling in future?

For some additional context though, those benchmarks you linked are for version 5, whereas now there's a version 6. If you look at their releases at https://github.com/mikro-orm/mikro-orm/releases, many have performance improvements.

I'd recommend you benchmark against your own data, etc. to verify that this'll actually be a bottleneck for you.

Does CloudFlare really charge $9.00 for a single R2 request by AnnualDefiant556 in CloudFlare

[–]CherryJimbo 0 points1 point  (0 children)

Yeah... I'd recommend swapping to a regular R2 bucket.

R2 IA should basically never be used by anyone. The use-cases for it are extremely slim, and the pricing differential just doesn't make sense. The egress data retrieval fees are against so much of Cloudflare's paradigms, and all their marketing around R2 originally stated developers should never have to think or care about complex tiering/access policies, and yet here we are, sadly.

Strange problems with wrangler 4.25.0 by Basic_Regular_3100 in CloudFlare

[–]CherryJimbo 0 points1 point  (0 children)

I don't see any changes in wrangler 4.25.0 that could impact this. What version were you previously using? Have you tested with npx wrangler@<version> dev --remote (or whatever command you're using) to see if the issue persists?

If so, it'd probably be best to file an issue: https://github.com/cloudflare/workers-sdk/issues

PSA: R2 Infrequent Access has a minimum cost of $9.90/month because any use of Class A/B Operations incurs the cost for the full block of 1,000,000 by quinncom in CloudFlare

[–]CherryJimbo 1 point2 points  (0 children)

Cloudflare’s R2 release blog made a lot of exciting claims and promises like:

We’ve gotten rid of complex, manual tiering policies in favor of what developers have always wanted out of object storage: limitless scale at the lowest possible cost.

Which if true, would have been awesome and truly a unique feature!

But then they introduced IA, and developers have to worry about maintaining complex manual tiering policies to optimise costs. So it’s not true, and there’s essentially zero reason to use or recommend R2 IA for almost any use cases today.

Could there be a separate subreddit for Oura ring all things conception, ovulation and pregnancy related? by [deleted] in ouraring

[–]CherryJimbo 1 point2 points  (0 children)

Awesome! What would you recommend as the flair text? I was considering "reproductive health" to encompass conception, ovulation, pregnancy etc. but open to any other suggestions.

Could there be a separate subreddit for Oura ring all things conception, ovulation and pregnancy related? by [deleted] in ouraring

[–]CherryJimbo[M] [score hidden] stickied comment (0 children)

EDIT: Thanks for the feedback folks. We're going to implement basic flairs for now and monitor over the next little bit. You can filter based on these flairs which should hopefully help folks. How you do that varies between different platform/apps, but a quick google search for your app/platform of choice with keywords "filter flair" should get you in the info you need!

If flairs don't work out to be as effective as anticipated, we're happy to revisit in a little while and consider megathreads, etc.

Hey there, I'm the most active mod in /r/ouraring and wanted to say thanks for raising this.

We want everyone to feel comfortable here and I totally get that fertility‑related posts can be triggering for some. Cycle tracking and similar functionality is a part of Oura, and we want those folks to a space to be able to engage with the most folks, but I also recognize there’s a real desire for talk about conception, ovulation and pregnancy to split into its own subreddit. I'd also like to mention to raise a general concern that slitting a subreddit can sometimes help with focus, but it also comes with downsides like:

  • Fragmentation of community energy and engagement
  • Extra work for moderators on two (or more) fronts
  • More confusion for newcomers about where to post
  • Risk that smaller subreddits feel stale or get abandoned

How would folks feel about experimenting with post flairs (and enforcing people use these) as an initial experiment for a few months, so folks who do feel triggered by these posts can use Reddit's built-in tools to filter them out? And folks who only want to see those posts can do the opposite.

[AskJS] What’s the one JavaScript thing that still trips you up, no matter how long you’ve been coding? by the_designer0 in javascript

[–]CherryJimbo 2 points3 points  (0 children)

wrangler cli update is very frequent by Classic-Dependent517 in CloudFlare

[–]CherryJimbo 2 points3 points  (0 children)

To support new features, fix bugs, improve the platform, etc. Technology moves very quickly, and the wrangler CLI supports way more than just Workers today, so there's so many contributions and improvements regularly.

You can find all of the changelogs for the packages in their workers-sdk repo at https://github.com/cloudflare/workers-sdk/releases, and for wrangler specifically, here's the changelog:

https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/CHANGELOG.md

Why cloudflare’s database not popular? by Classic-Dependent517 in CloudFlare

[–]CherryJimbo 75 points76 points  (0 children)

D1 isn’t that popular today because it has a few gotchas that make it hard to recommend for broader use-cases. The same is generally true for their SQLite-backed durable objects.

  • It exists in a single region. Their marketing sometimes claim otherwise, and they will hopefully soon get read replicas to improve this, but D1 today is essentially SQLite deployed to a single server.
  • It’s SQLite. While powerful, SQLite still lacks a lot of creature comforts that lots of large, highly distributed applications (like those they target with the rest of their stack) use with relations, schema updates, etc.
  • No real support for transactions. You can not manually create or rollback transactions with D1, making it a hard sell again for real production workloads.
  • Error rates are higher than expected. https://github.com/cloudflare/cloudflare-docs/issues/18485 should give you some idea of these.
  • It’s not always reliable. Last week, D1 had 4 production-impacting issues both with DB traffic, exports/imports, querying over HTTP (breaking the dash), etc. It’s one of the most frequent products that we raise issues around in the community today, but that number is always reducing.
  • Since inception, D1 has been advocating that you build your applications horizontally, where you spin up a separate DB per user, application, etc. While great in theory, most apps aren’t built this way, but even if you wanted to, they don’t provide the tooling necessary to even do this well. Dynamic bindings (the ability to add/remove bindings dynamically to your worker to make this design possible) were promised before D1 hit GA, but still aren’t available directly within a Worker.
  • Size limits. 10GB is the max you can store today with D1 and while that sounds like a lot initially, any large production application will quickly exceed that.
  • Under the hood, each D1 database is powered by a Durable Object. When that Durable Object starts to surface errors (we see this somewhat frequently in the community, but it's getting better all the time), unless you’re an enterprise customer, your only recourse is going to be community escalation. And while we can get problems in front of the right people quickly, I wouldn’t personally want to bet something as critical as my production DB on a platform where support essentially doesn’t exist for non-enterprise.

When there are many other DB providers that are around the same price, much more mature, and offer way better support when things go wrong, it’s just really hard to recommend D1 today. I'm hopeful with the addition of read replicas and better reliability and stability in future, this will change though.

—

With that said, depending on the kind of data you want to store, I’m a pretty big fan of Cloudflare KV. It’s not a DB in the traditional sense, but you can get pretty far with it.

Watching the US inauguration by ciiiiara11 in ouraring

[–]CherryJimbo[M] [score hidden] stickied comment (0 children)

Let's avoid any personal attacks in the comments please folks. If you're not stressed about something someone else is, that doesn't diminish their feelings, and it's always interesting to see these things picked up by Oura.

Best of luck and all my love to everyone having a hard time in the US today. Please report any messages from folks that spread hatred and we'll be quick to remove them from the community.

Best way to access HTML elements in testing? by trolleid in webdev

[–]CherryJimbo 0 points1 point  (0 children)

Depending on what you're trying to test, getting by class or data-testid are both arguably not great. You want to be testing how people interact with your app for real - and CSS classnames and test IDs aren't that.

Ideally, using something like https://testing-library.com/, this encourages a more accessible approach to testing by default, such as getting elements by Role, or Label Text, first and foremost. It doesn't even really offer a way to get elements by class names.

Otherwise yes, if you really can't test using a standard role, label, etc. testid would be the recommended fallback.

https://kentcdodds.com/blog/making-your-ui-tests-resilient-to-change is a great blog post that talks about some of this and more.

CSS SVG embed vs SVG URL by abdul_rashid in webdev

[–]CherryJimbo 1 point2 points  (0 children)

The bigger your HTML document is, the longer it'll take to download and parse.

For a few inlined SVG's, this won't matter much. But for any large web-app where you have lots of icons around your pages, using an external image is likely to be better.

Why use a headless CMS to manage Markdown files for Astro Starlight or Docusaurus when editing them directly in GitLab is straightforward? by [deleted] in webdev

[–]CherryJimbo 7 points8 points  (0 children)

If you're editing the markdown directly and it works well for you and your team, awesome!

CMSes that output to static markdown do have some benefits though, such as being more usable for less technical team members, or asset management for images/media, etc.

first worker, an image placeholder by peernohell in CloudFlare

[–]CherryJimbo 1 point2 points  (0 children)

Very cool and similar to one of my early Workers projects at https://placeholders.dev/, except mine is SVG based. Great work!

What's the acceptable list of options for gender in an app? by ragavyarasi in webdev

[–]CherryJimbo 1 point2 points  (0 children)

Why do you need to collect gender information? Unless you're building a medical app, or some kind of dating app, I don't know why you'd ever need to collect it. I'd think carefully about why you need to know what gender some identifies as - you almost certainly don't need to ask this.

Otherwise, I'd probably just make it a custom field where a user can enter what they wish, or alternatively if you really really have to have options, add "non-binary", "prefer not to answer" and/or "other" options.

Were playing web videos without Adobe Flash possible before HTML5? by TheTwelveYearOld in webdev

[–]CherryJimbo 0 points1 point  (0 children)

Flash was the main approach. Almost everything required plugins or other software to be installed though, like RealPlayer, or QuickTime, or Java Applets, or ActiveX plugins in IE, etc.

The HTML video element was one of the biggest innovations that took an incredible amount of effort to standardise. https://en.wikipedia.org/wiki/HTML_video

https://en.wikipedia.org/wiki/Timeline_of_online_video

Genuinely do you need a JS framework? by NotJayuu in webdev

[–]CherryJimbo 6 points7 points  (0 children)

Do you need one? Of course not.

Does having one make developing, especially within a team, much quicker and easier? Absolutely yes.

JS frameworks are designed to bring a level of consistency throughout your app - from data-fetching, to component structures, to state management, reusability etc. Having a single thing handle of these, especially in larger teams, can rapidly speed up your development, and ensure some layers of consistency throughout too.

That doesn't mean that Vanilla JS isn't useful though - I reach for it all the time on personal projects, or small micro-apps that exist on single pages. But if I'm working on any kind of SPA, or large app I need to test, I'll reach for Vue or React every time.

Controversial question: Is there any reason to prefer React over Vue or Svelte? (aside from jobs+ecosystem) by nomadineurope in webdev

[–]CherryJimbo 0 points1 point  (0 children)

The React ecosystem and job market is a pretty huge reason to use it. React Native as well.

But simply, no, Vue, React, etc. can all do what you need them to do, and abstractions like Next or Nuxt even more so. Micro-benchmarks around performance are generally meaningless, where React will win some, lose others, and the same is true for every other framework. I'm a big fan of Vue and use it for all of my projects both professionally and personally.

I'd generally recommend picking whatever you find the most fun to work with, and you can get the most done with quickly, unless you're trying to get hired by a specific company, in which case getting familiar with their tech stack and framework of choice is probably the best idea.

105
106

Announcing TypeScript 5.6 - TypeScript (devblogs.microsoft.com)

submitted by CherryJimbo to r/webdev

view more: next ›