not saying it's going to scratch all the itches that Spotify would, but it definitely will scratch some you didnt realize you had, which is a fun experience on it's own
458 karma · joined May 4, 2015
not saying it's going to scratch all the itches that Spotify would, but it definitely will scratch some you didnt realize you had, which is a fun experience on it's own
I’ve found though that often when clients say they need something that only a headless solution can provide, they actually don’t truly need it. And once the actual requirements are focused, a well built Shopify theme is plenty sufficient.
Maybe we are working at a different scale of companies though.
The main advantage of headless to me is the ability to get the speed of the site way up. But the nature of e-commerce is to add tons of pixels and other junk so it can defeat the advantages (and much harder to talk them out of adding pixels sadly…)
I’ve come into working on multiple different headless sites developed by others who then walked away and left an entirely non-technical team to sort it out.
A well-built Shopify theme works great and plenty fast for even medium sized companies.
JS with Ramda (and an FRP library, if needed) is the sweet spot for me. I use a lot of pipes() but usually don't break them down into smaller functions until there is a reason to; but FP makes it trivial to do so.
Granted there is the blue feedback if you are on the flower, but it’s confusing when you are trying to plan ahead.
edit: Fun puzzle though!
Because of the enforced formality of how data is flowing around, the ability to split these streams up is trivial in a way that was a revelation to me. In the past, I'd be far less confident that I was going to mess up something unintentionally, to the point where I would maybe not bother.
And yeah, I think it's totally valid to take larger blocks of streams/transformations and wrap in a named function that takes a stream and returns a stream.
Over the years I've gotten out of the habit of always using FRP for every problem. There are many cases where async/await is totally fine and simple. I still always use Ramda, which gives me the same self-documenting qualities (which is really a function of the strictness of FP, not so much the R in FRP, now that I think about it).
But whenever I have to coordinate multiple inputs with different time delays (i.e. multiple AJAX requests or UI input) or process a bunch of data where each item creates its own stream of fetching and processing, the "reactive" bit is extremely handy.
I agree the code can balloon in size, and gets a bit hard to organize at some point, but the self-documenting aspect of it is amazing.
I combine an FRP framework (bacon.js) with Ramda.
I’ll admit I’ve had trouble working with things like React because I’m so used to wiring everything up explicitly and there being no “magic” behavior.
The explicitness is probably what makes it seem so unwieldy as the code/team scales
it’s a website. not everything needs to be found, let alone searched for
Maybe you disagree, but I don't get why people are acting like this is sinister.
The wholesale store functionality has customer based price lists. I've also added products to cart with a discount amount as line item property, which is then picked up and discounted by line item script. Some concern there with people manipulating it but I think it's pretty theoretical and there are ways to combat that. Both those require Plus though.
They announced the new backend pricing API/web assembly script thing a couple weeks ago that seems like it will solve this issue for real.
Similarly to how the subscription stuff was pretty janky with apps until the selling plan stuff. That said, it got the job done even if it wasnt ideal, and now they have a good solution. I prefer that model to just rolling out a bunch of half baked features.
Responding more to the parent than you now, but in most cases if a business claims to critically need some specific feature, I wonder if they are not just married to the specific solution they have in mind and not the underlying problem. But if they really do need a specific thing, then certainly looking for the platform that offers it makes sense.
is this an announcement of a breakthrough or a challenge to find a breakthrough?