I think it's a lot easier to comply with the GDPR now if you're just starting out as a brand-new company. The difficult bit was if you were an existing, smallish company with (in some ways understandably) lax data collection/tracking policies, and suddenly needed to spend a multiple of your revenue to clean all that up in order to comply with this new law that was coming onto the scene. Big companies also had a lot of trouble getting their systems in order, but often had a lot more resources available to do so.
If you are starting out now, and you want to avoid trouble, you just avoid collecting data about site visitors. And when you do need to collect data (perhaps you need customer accounts), then you spend some time thinking about what it means to furnish that data on request, or to delete that data. No, it's not zero work. But it's a hell of a lot easier to build these sorts of controls into a system from the start, than it is to build it in later. I don't really work with web/full-stack frameworks, but I would be surprised if there aren't built-in or third-party modules for the popular ones to help with this process.
If you are starting out now, and you want to avoid trouble, you just avoid collecting data about site visitors. And when you do need to collect data (perhaps you need customer accounts), then you spend some time thinking about what it means to furnish that data on request, or to delete that data. No, it's not zero work. But it's a hell of a lot easier to build these sorts of controls into a system from the start, than it is to build it in later. I don't really work with web/full-stack frameworks, but I would be surprised if there aren't built-in or third-party modules for the popular ones to help with this process.