Generally yes, though I remember seeing a post on hacker news in the past month where a SAAS sent an invoice after the free trial ended rather than terminating it.
I always expect a failed billing or no billing info after a trial to cancel and not be pursued (I regularly do trials with a temp card that I immediately de-activate so it cannot be billed in case I forget to cancel)
“The Real Dad Podcast” is by far my favorite podcast! It feels like hanging out with friends. I smile, I laugh, and I get some decent parenting stories to learn from.
I highly recommend it to anyone with kids or about to have kids (perhaps give it a shot if you don’t have kids?)
Saying FACEIT has cheaters “by all accounts” feels like a bad faith argument without including that it has significantly fewer cheaters (at least at higher ranks). As well as having the ability to report to real human moderators.
I have too many hours in cs:go and cs2 and am level 10 FACEIT. I have had many awful cheater experiences in the native competitive systems but have never had an obvious cheater (never reported someone) in a FACEIT match.
It works. It raises the bar high enough that cheating is significantly less frequent.
I think this makes a lot of sense in the context of Zed’s multiplayer editing. Maybe that works well for a small team working on a single product, but that doesn’t seem like it’d scale super well. I loved tight collaboration long ago on online notepads despite constantly breaking stuff for each person…
Smaller more frequent price increases is potentially better than larger less frequent price increases assuming they need the increase to stay profitable? Sounds like they didn’t predict the continued increasing costs.
The company I work for uses GCP and we preciously had intermittent CloudSQL connection errors for a few hours. We reached out and they resolved it after a day or so and said there was a minor incident but I don’t think it was ever publically reported.
Yeah that is a “stacked” pr. The tooling is nice especially when have a larger stack and make changes to the first branch. Update refs + push all branches, same with merging and rebasing onto main.
Thanks. I was curious if someone was going to address the weird use of “CATASTROPHIC” to describe source maps being available for front-end code. It’s already public. Minified is better for the regular user, and should be in production, but it’s like by far the least problematic thing in this article.
I always expect a failed billing or no billing info after a trial to cancel and not be pursued (I regularly do trials with a temp card that I immediately de-activate so it cannot be billed in case I forget to cancel)