Thanks for that insightful feedback, I honestly did not even consider that. I'll go ahead and remove the sign in requirement for the create recipe page since it does really work well.
Cooking is hard and even harder when you have to deal with ads and slow pages. Presenting prep-pear, a no fuss site that attempts to solve just that! All you do is pop in any recipe link to strip out the essential details minus all the other fluff. You can then use those recipes to auto generate a meal plan for the week! Hack your kitchen!
And nodejs is 9M a week, python is 8M a week, tensorflow 50M etc. Pull count doesn't mean anything if you can't group it in some meaningful way. I'm a 15+ year PHP veteran and I can safely say I will never use that language again. There are too many other far better choices out there especially when running in a containerized environment. No apache, nginx, FPM, php.ini custom health check scripts, loosing requests when the container starts or stops etc.
Yeah but then who is responsible for maintaining the library? If you have a bunch of internal teams that depend on your library and there is an issue or a feature request, you're back to the same position of being the one that does the work to implement. Better to have a service IMO, you can get telemetry out of it and scale it out or replace internals without having to worry about who will get affected.