Hacker News new | past | comments | ask | show | jobs | submit | zedpm's comments login

$10/month difference is, to use your phrasing, absolutely nothing. It's not worth anyone's time to make that switch unless it's some toy app paid for out of pocket.


Most software businesses start off as "toy apps" and are paid for out of pocket.

The parent's comment is right - that is a lot of money for not a lot of value, particularly when you are early stage.

The trick is in finding balance between paying ridiculous fees (relative to your revenue/customer base) to make things more simple vs. find another way and spend your time instead.

A prime example are identify provider services, such as Auth0. The free tier is good enough for development, but as soon as you expect to onboard customers the free tier starts to feel deliberately gimped. Are you willing to spend $20 a month just to use a custom login domain? For the zero customers you have? $20 a month might feel like "nothing", but it's $20 a month forever and it's $20 a month that could be allocated to other things, such as compute or your accounting software.

It's not always that clear cut, however.


I think it is fairly clear. If you are building a product of passion that you may tinker with for years, by all means cut costs as much as possible.

If you are an actual early stage venture I don't believe those costs meet a high enough threshold to matter.


It depends, as things usually do.

$20 here, $10 there, eventually ends up as $600 monthly or more, and no customer anywhere in sight. That may, or may not be sustainable or make sense.

Flush with cash? Knock yourself out. Bootstrapping? You can spend that money a lot more effectively than just loading up on a bunch of overpriced SaaS products to make life easier. You have to earn the easy route by growing your revenue.


It does not depend though. It’s pretty clear that it’s how you value your time which is what I was getting to.


This math works if you're not paying salary.


Interesting, the use of grammar production rules reminds me of Grammatical Evolution[0], which has shown some promise in constraining the search space when using EAs for e.g. symbolic regression.

[0]: https://en.wikipedia.org/wiki/Grammatical_evolution


Much of what I did in my work was to reduce or constrain the search space.

1. Don't evolve constants or coefficients, use regression to find

2. Leverage associativity and commutativity, simplify with SymPy, sort operands to add/mul

So much effort in GP for SR is spent evaluating models which are effectively the same, even though their "DNA" is different. Computational effort, and algorithmic effort (to deal with loss of population diversity, i.e. premature convergence)

I've seen a few papers since pick up on the idea of local search operators, the simplification, and regression, trying to maintain the evolution aspect. Every algo ends up in local optima and works of effectively the same form by adding useless "DNA". I could see the PGE algo doing this too, going down a branch of the search space that did not add meaningful improvement. With the recent (~5y) advancements in AI, there are some interesting things to try


Lots of reasons. My company started using AWS (and specifically S3) something like 9 years ago; R2 wasn't even on the radar back then. If I were starting from scratch today, I'd be looking seriously at Cloudflare as a platform, but it's only in the last year or two that they've offered these services that would make it possible to build substantial applications.


Jeff Barr posted that AWS is actively working on a resolution for this: https://twitter.com/jeffbarr/status/1785386554372042890 . Given who he is, I take this as a strong indication that there will be a reasonable fix in the near future.


Somewhere, Edward Tufte[0] is weeping.

[0]: https://en.wikipedia.org/wiki/Edward_Tufte


I use Authy on my phone and watch, but not Authy on the desktop for exactly this reason; if my computer is compromised and 1password is accessible, they still don't have access to my TOTP codes. Having it on both my watch and phone means I can break a device and not lose access.


I'm glad to see they didn't forget about HTTP 418[0] in their response code docs[1].

[0]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/418

[1]: https://developer.tesla.com/docs/fleet-api#response-codes


Factotum and South of No North are two of my favorites.


This is very disappointing. I'm kind of amazed that they think this is a good business decision when there are massive numbers of paying customers with mountains of python code using boto3. I imagine much of that code uses the resource interfaces since they're easier to use.

This isn't some fringe feature they're deprecating; the official documentation uses these interfaces in its examples; they're literally telling you that's the correct way to use the library and then the next moment they're telling you it's not.


I’m still using a 2015 MacBook Pro, and it doesn’t feel slow. I’ve done no repairs or maintenance on it in all that time.


I updated to M1 MBP in 2020 because the 2015 MBP I had previously felt slow, and it got progressively worse with each macOS update.


I tried the older 14" MacBook Pro for just over a month, and it's a world of difference going back to my late 2013 13" MacBook Pro.

I've been holding out for the new one and will be placing an order in a bit. :) The splurge will more than make up for the hours of life I'll save from browsing resource-heavy websites.


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: