Try looking at your composer.json and then delete every line. Then you get an idea of what it might be like with no composer and no packagist and no packages
It will never get off the ground because it does not have the ecosystem of php nor the PSR standards that allow it to all hang together
@Snapey Well you never know, Laravel started the same, and nobody knew anything about it at the beginning. The community matters for sure and it will take some time but Go is also a game changer in terms of everything, deployments, speed, concurrency, scalability, and memory management.
@azimidev I agree, Give it 10 years and it might be where Laravel is today. But by then of course Laravel will be 10 year's on and might even have a bridge to Go so that you can use it for things where it excels, or php10 might be crushing Go.
But, without a package manager, its dead in the water.
@Snapey Oh, of course, Go has a package manager called Go Modules FYI. PHP didn't come with Composer until a few years ago. PHP is okay, but even PHP 10 will not have parallel capabilities and remain single-threaded due to its different language philosophy. Comparing Laravel and Goravel is unnecessary; we all have access to the internet. Time spent on a framework is not always the best factor to compare because they can just copy the idea just like Laravel did using Rails and Sinatra. The rise and fall of Ruby on Rails is self-explanatory. It's the programming language difference, not the frameworks themselves.