End of life?

[marcelaerts]

Hi there, is this plugin end of life? A lot of issues and last commit over 6 months ago? It's really easy to use and wish it will continue.

[marcj]

Yepp, dead. Time to switch.

[michaelegan]

Anybody have similar alternatives to share?

[lorvent]

oops, i am just planning to switch from owl-carousel to this one. now this is also dead?

[ghost]

@michaelegan try Slick http://kenwheeler.github.io/slick/ or Flickity https://flickity.metafizzy.co/

[marcelaerts]

https://swiperjs.com/

[Teisi]

switch to what?

• swiper? To big.
• Slick - only with jquery so that is not an alternative
• flickity? not open source/free and it seems that sich slider is dead too

[marcelaerts]

@Teisi , what do you suggest?

[Teisi]

@marcelaerts I don't know, that's why I'm asking... :)

[leastbad]

It is a sad statement on the state of JS ecosystem standards when a library that was last updated ~7 months ago is declared "dead" and "EOL".

"Time to switch". At this rate of change, why rely on 3rd-party code?

[marcelaerts]

@leastbad as you can clearly see I asked if it was EOL. In my case issues not being answered is more important then no updates. I just want to know if the developer(s) are going to continue.

[marcj]

@leastbad calm down. Its daily business in open-source, especially in fast moving JS/frontend business, that if you don't keep your project up2date and responsive, people will quickly pick a new one. Especially in a field like this slider that is not a third-party dependency and could break anytime when a new IE, Chrome, or mobile Safari release is being published.

Also let's be honest, until you pay this guy, this procedure is going on and on. Obviously he has no priority for this project since half a year and doesn't even answer to this kind of issues.

I agree with @marcelaerts that being responsive to issues is more important than actual code changes. A software can be feature complete, but questions/bugs will always pop up.

However, no pressure to the author. I know the feeling of letting a project go. People should just accept that free code is often limited and has a short lifetime. Also most of the time (not always), even when the maintainer answers now, that doesn't mean anything as only actions count. He may simply have a bad conscience. You should only evaluate a OSS project by actions, never by promises, since the author is not accountable for anything -- only if you have a contract and pay him.

[ghost]

Well said 👌🏼 @marcj

[leastbad]

No. Not well said.

My position is by definition calm; you're the ones acting like a gang of tweakers because someone took half a year off from working on an open-source project. The notion that something modified in the last year is abandonware is fundamentally absurd. All of this talk about having a bad conscience and actions mattering more than promises sounds like a screenplay for a cliched crime movie.

If this is totally fine and normal for the JS ecosystem - to decide the creator of a carousel library might have a "bad conscience" - then the culture of your ecosystem is toxic and immature, because you're operating under the mistaken belief that August 2019 is old and outdated. tiny-slider seems like a perfectly good library. If there's something wrong with it that is burning your house down, fork it and fix it. That's what we do in literally every other language community. It's completely normal to not see changes to important libraries for years at a time. It's not because they are broken, it's because they are stable.

[marcj]

You have a lot of false conclusions and disrespectful accusations here.

That's what we do in literally every other language community

You obviously don't understand the dynamics of big open source communities. The vast majority of people don't fork and fix libraries. They switch just to another one if the current one doesn't suit anymore. You have plenty of alternatives to chose from. Only in smaller communities like your Ruby community where you're coming from might it be the case that people fork and fix more. I know this from the C++ community, where forking and fixing is also way more common. You barely see "Is this end of life" threads, but it's very common in the JS community. But that's not the result of a nicer (c++/ruby/...) community, but plain from the fact that you run out of alternative libraries -- precisely because the (active) community is small. The by far biggest developer community of the world works here differently.

All of your other accusations here especially about the bad conscience is something I won't try to explain to you since you obviously are neither interested in a polite discussion nor do you have the experience of being a maintainer of a successful library in this community. So you better back off and stop your wild accusations.

Instead of accusing us of toxic behavior and other wild stuff, you should get used to this simple fact.

[leastbad]

@marcj You're the one who suggested that the project owned might have a "bad conscience" - not me.

As for whether it's simple, a fact, whether it's something I should or have to "get used to"... all of these things are choices you have to make. Do you feel like you deserve better, or do you not? I clearly have chosen to put my time into communities that don't equate old == bad.

Meanwhile: I stand by the fact that you all sound like a bunch of raving tweakers.

[smartcorestudio]

@michaelegan https://splidejs.com - modern, lightweight, customizable, free

[lems3]

For people recommending Slick : We were looking to move away from it. It has a lot of issues and a real absence of support. Author have dropped the project and tried to give it to other people, and it clearly failed.

[Whiax]

What's the matter? If it works for most usages, support or updates aren't required. Do we expect to have the same lib redeveloped over and over? owl => tiny-slider => splide => etc..

[alvinkonda]

thumbs up for @smartcorestudio for sharing splidejs.com. Looks perfect for my project

[addison74]

I was a big fan of Owl Carousel for many years. Seeing Tiny Slider going in the same direction like OC I started to evaluate a replacement and I found Splide JS to be a perfect choice. Tons of options packed in a lightweight js file. It is 10 times less as size comparing with Swiper JS. The developer solved a conflict with Prototype.js library in less than an hour from reporting the issue on GitHub. If I will learn to create my own extensions/components to extend its functionality I will be very happy. Probably if more of us will use it we will get new features like complex transitions. At least for sliding videos (HTML, YouTube, Vimeo) it works as expected.

[ganlanyuan]

Thanks for your concerns and interest in this project and sorry for the very late response. Just want to let you know, I will continue to work on this project. I won't be able to check the issues and PRs everyday but at least 2 times a week.

[leastbad]

Thanks for all of your hard work, Willliam.

[ganlanyuan]

You’re welcome

Sent from ProtonMail Mobile

On Mon, May 4, 2020 at 8:26 PM, leastbad notifications@github.com wrote:

Thanks for all of your hard work, Willliam.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

[AeShevch]

Glide.js

[nicped]

We just made this slider - https://github.com/dynamicweb/swiffy-slider, less than 3.5kb in CSS and Vanilla js

[Yapac]

I advise all people to migrate to: https://react-slick.neostack.com/ I migrated from OwlCarousel to Slick in like a half day, and it improved my app alot