I prefer laravel as well but it’s definitely not as snappy as an spa since I have to load a full page of html at each click. What are you doing differently that I should be doing?
Currently, I’m doing a hybrid sometimes where I’ll have jquery do a call inside the page when I want one particular area to be fast.
@pumpkinman - IMO in regards to business viability it’s just as valuable to see someone’s process of how they came to the conclusion as the conclusion itself
I’m not so sure it’s complete bs. Ive worked with Steph on a dozen design projects through his brand. Typically I’m actually only interfacing with his team so I’ve only met him personally a few times and only for a few minutes. The last project I got to meet him again at the roll out. I pitched the idea of creating NFTs for his foundation to the guy running his foundation. The guy was totally interested. A few seconds later Steph walked by (and wasn’t being mobbed by everyone around) and the guy told Steph “this guys talking about NFTs” … Steph did a triple take and eyes wide and seemed genuinely juiced to talk about it. Moments later he got mobbed by kids for autographs and that was it.
Not saying NFTs are not a sham, just that I was super surprised at how interested he seemed in the subject.
Maybe less true now, but it seemed like when products had public APIs in rest, they were different endpoints than what their own internal teams used.
Whereas with Gql it seems like internal and public frontend people used the exact same endpoints, which gave the public apis more power.
In this thread below, it seems like a lot of people on HN don’t like GQL.
https://news.ycombinator.com/item?id=31284846