If you use Netlify in the free tier you cannot automatically go to pro tier either. Yet they will charge you for bandwidth > 100GB, and THERE IS NO WAY FOR YOU TO SWITCH THAT OFF, even in the free tier.
"Should be fine" is exactly what is not the case here. Better check your Vercel terms again.
From every Vercel document that I can read though is that when you exceed the limits of free tier they are just locked for 30 days unless you upgrade to Pro.
So unless I am mistaken this cannot happen on Vercel.
Would be for a new business. Not a fan of introducing this sort of tail risk & whatever other risks I don't even know about for their managed service, when there are simpler ways to host I've done for years.
The UI is lackluster, since it's just the same one from the normal Spotify Music experience.
Because they bought Joe Rogan they had to add video too and video is horribly implemented. There isn't even an obvious way to turn it off.
I consider myself tech-savy but I gave up trying to turn off and just switched to Apple Podcasts.
Podcasts and Music are not the same.
Please if you really want Podcasts to happen then, Spotify, make a separate App for it.
Spotify podcasts were what made me jump ship to Apple Music. At least back then, Spotify would heavily prioritize their podcasts in the UI. Podcasts were front and center on the main screen. I don't just mean the desktop or mobile UI, but in Apple CarPlay and Android Auto too, where screen space and attention are at a premium. I had to keep fighting the UI to get to what I was paying Spotify for: the music. When I tried out Apple Music and saw that it was music only, it was easy to leave Spotify because their priorities were no longer aligned with mine.
Not a spotify nor Apple Music/Podcast/itunes user here.
Aren't both audio stuff where you press play, pause, stop, rewind and fast forward?
The only difference I can think of is that you might sometimes want to accelerate playback of podcasts but that doesn't mean it can't exist in the same player.
Podcast apps, good ones, have many features you don't need in a simple app like a winamp or vlc.
1) An online catalog of series that is searchable (probably both by name and topic and participants).
2) That catalog must contain metadata both at a series level and an episode level.
3) That online catalog must also be navigable without search, of course.
4) Ability to subscribe to any given series and for the app to have an option to pre-cache an episode for offline use.
5) Several content controls that aren't really required for music listening but are must haves for podcasts such as timed skips (30s, 60s) and playback speed adjustment (only useful in a music player where you probably want to do beat matching).
I think the biggest differentiator though is the episode/series catalog. It makes podcasts actually discoverable.
There are audio players that allows you to find radios by various criterias: genre, bitrates, location, etc.
I don't think it is hard in term of UI nor does it justify a different app when you can have an additionnal tab that allows to find podcast. You just have to change the criterias.
Subscription to podcast is done via rss right? I don't think that is a huge deal either.
It would be cool if you could "import" companies into this and have like a public library of various companies and better understand what they did.
That would make learning about a company way more interactive.
Although I'm not versed enough in startup culture to know how much of this data is even public.
NPM is a very good package manager registry. It's just extremely popular because javascript is extremely popular and the entry barrier is tiny compared to other languages and registries.
These issues would pop up in any package manager, no matter the language, you just need enough users and usecases.
No, NPM has never been thought out well. Many of the improvements in npm over the years were all either (1) due to accidents that many other package managers like NuGet already prevent by default or (2) features that were already implemented in Yarn 1.x.
Any for profit company does not act with 100% pure morale moves. Some do less some do more good, where do you draw the line? Google does a lot of good too, educating, bringing Internet to people who never had it before, being a diverse employer etc.
So because they have some morally questionable choices every developer should quit? There is no black and white.
If you want yaml based configs and running on a non HomeAssistant provided OS you are already making it hard for yourself.
This is not the most popular route and therefore also less supported my advice:
- use a raspberry-pi with Home Assistant OS or buy one of their self made raspberry-pi alternatives Home Assistant Yellow etc.
You can run docker but it's still not straightforward because then you need to passthrough like USB Devices etc, I would recommend against it.
And from there use the yamls to define a very basic config like language, location etc (I'm not sure that you even need to do that). But only use the GUI from there on.
Everything can be done with the GUI, I haven't touched my yaml files in years.
And I regularly upgrade versions too, haven't had any upgrade issues either.
> Everything can be done with the GUI, I haven't touched my yaml files in years.
Command line sensors, REST sensors, some types of virtual sensors, groups (I think), there's a lot of stuff you still can't do in the GUI, and even if you don't mind writing their stupid YAML-based config, the documentation isn't very friendly and in places outdated and contradicting itself.
That's a feature not a problem. It's free software you can run it anywhere you like. And they give you some advice and "ads" which stuff to buy which it runs best one.
You need to manually upgrade.
Unless you need more than the Free-Tier Vercel should be fine.