I'm doing something similar with reading – 50 pages minimum everyday. I've read more books in the last 4 months than in the last 4 years by just keeping the streak alive.
Which then leads me to the next question, what is the practical way to write rules against that operation?
But as expected, you can validate the incoming data as well https://firebase.google.com/docs/firestore/security/rules-co... but this would need to be done for any attribute that might lead to a change of ownership.
```
// Allow create new object if user is authenticated
allow create: if request.auth != null;
// Allow update or delete document if user is owner of document
allow update, delete: if request.auth.uid == resource.data.ownerUID
```
Laravel has single handedly made PHP development cool again, and the way they did that was offering an integrated developer experience focused on ease of starting and quick productivity.
They flattened the learning curve of other "full" frameworks (like Django/Rails) by offering recommended (and official) tools and services out of the box. This cuts down a lot of the analysis paralysis faced by junior developers and they have an easy way to start adopting necessary complex tooling when it becomes relevant for them.
Have a look at the `Ecosystem` mentioned at https://laravel.com/ – Django doesn't have an official local development GUI or Rails doesn't have an official APM – which is a boon for power users that know how they want to setup their local development environment or what they want in an APM service, but they're exhaustingly complex choices for a web developer just getting started.
I've observed Laravel gain a tremendous following with developers here in India, I believe because of this ease of getting started and being productive quickly.
I don't even feel like the funding amount is ridiculous. For comparison, have a look at some of the funding raised by smaller frameworks/libraries (CMSes, "JAM Stack", etc) without such an extensive set of revenue making services, in the JS world.
If they continue to pour the money on expanding their ecosystem while staying true to their value proposition to developers, they will do great. I, for one, am looking forward to this next generation of PHP/Laravel-powered web (maybe even mobile with this funding?) products.
Tom (and Fenn) had rockstar status back when I was involved in university CS+Entrepreneurship clubs in Melbourne around 2009/2010 (mostly led by fine students at UniMelb, but I was helping spread the word at Monash) because they were the first(maybe one of the first?) Aussies to be accepted by YC. They always generously gave their time and advice at these student events, even dropped by the SiliconBeach networking meets to share their experiences and turned out to be exceptionally kind human beings in person. Definitely the right choice for moding this community!