I tried several times to port Node projects to Deno. Each time compatibility had "improved" but I still didn't have a working build after a few days of effort.
I don't know how Deno is today. I switched to Bun and porting went a lot smoother.
Philosophically, I like that Bun sees Node compatibility as an obvious top priority. Deno sees it as a grudging necessity after losing the fight to do things differently.
Which makes sense given that a big impetus for Deno's existence was the creator of Node/Deno (Ryan Dahl) wanting to correct things he viewed as design mistakes in Node.
My first guess is ESP pricing. Just to pull numbers out of thin air to anchor the conversation, mailing to 20,000 subscribers costs $200–$400/mo at Mailchimp/ConvertKit/Klaviyo, three of the top choices in the space. If it's 50,000 subscribers, that's $380–$800/mo.
These are email marketing platforms, not bulk transaction email platforms, and I don't see why they can't do with the latter. At a bulk transaction platform, such a tiny amount would cost at most $20-$50/mo. If you're willing to do a bit of work to use AWS SES, that would be $2-$5 a month. Azure ACS would be even cheaper.
Just playing devils advocate, but why not just switch to posting on a free hosted blog platform? The information can be there for all to see, it doesnt need to be distributed directly into mailboxes by premium mailer services.
You could just notify the user to add you to their contact list. Like :
Emails will be sent from feed@example.com. If you're not seeing any email, please check your spam inbox and add this address to your contact list,...[rest of notice].
I largely agree, but I think there's merit to Rebble's argument that Core Devices could be here today, gone tomorrow. I'd hate to see Pebble die again only for Rebble to have disbanded in the meanwhile. Then the community has nothing but code repos.
