Hey,
Splide for slides has been dead for 2 years, is there another implementation planned? For example Embla or similar?
I think Embla will be the way to go if I’m honest, the only issue is all the sites currently running splides.
2 Likes
I’m of the same opinion!
That’s gonna be a fun few days, converting all the sliders. But yes, dead software is meh.
1 Like
Would love to know what the plan is here too : )
Bricks already have a swiper lib, which helped me to build a filterable slider (how to add a custom swiper).
Splide is not working with filters, btw
@Matej @matejmohar Do you think you could try to tell us some plans for the future? I think this feature is really crucial. 
yea im not liking the splide, it does not allow you to use all the effects for free, we need something that can do things like revolution slider…
For now, we don’t have any plans to move or implement another slider library (like Embla mentioned above).
But, we are keeping an eye on this.
1 Like
I think that building such a used element off a dead dependency is borderline irresponsible. Similar to the way you upgraded containers at some point and provided a transform tool you should start working on a new slider element that uses an actively developed library and then provide a transform tool.
It wasn’t dead when Bricks first came to life. In fact, it was actively developed until ~2 years ago.
I meant “to keep building” such a used element. I know it was maintained back then, but 2 years is quite a long time in web dev years.
1 Like
I find it strange why Splide was used for the Nestable sliders anyway, if Swiper was already used for non-nestable sliders… Both splide.js and swiper.js basically does the same thing. Was someone trying to avoid tech debt and accidentally got us into even bigger debt? 
But yeah, it would be nice to simplify stuff and just use one active library instead of two libraries.
1 Like
I’ve been using Splide on every project for years with zero issues. It’s only ~30 KB minified (vs. ~145 KB for Swiper), fully customizable, and has nice extensions like auto-scroll. Even without recent updates, it’s been rock-solid in my experience.
That said, I understand the concern about long-term support. If the Bricks team decides to replace it with something more actively maintained, I trust they’ll make a smart decision that balances performance and flexibility.
+1
1 Like
The only weakness I see in Nestable slider is the excessive layout shift when the page loads, and I’m not sure if this is because the library hasn’t been updated.
The size of splide is very optimal. But ultimately it is the decision of the bricks team whether they want to continue with splide, or gradually move away from it. Because leaving it in one version is not possible in my opinion.
But the possibility that Splide may never release an update (which is very likely) cannot be ignored. I hope the bricks team makes the best decision as always.
layout shift almost always related to how you setup the dom and styles/css
doesnt matter if it is tabs or slides or accordions all the same
2 Likes
There was a pole in the FB group, Splide won. The overall consensus had been that it’s better to go with the lightweight option as the default for the builder, which can do 90% of stuff you want and then people are free to add complexity if they wanted. Rather than starting with something heavier.