When I first discovered Livewire, yeah, my first thought was that it's very similar to the way that October's Data Attributes API works. I've used this the Data Attributes API in October for years and I really love it.
But I agree with JimRed, October's Data Attributes system just isn't as fully featured as Livewire and I don't like the idea of having to write JS in an October or Laravel app for something that should really be quite straightforward to stick in an HTML tag. If I wanted to write JS, I guess I'd learn Angular, Vue or React. But, personally, I like PHP and I'd rather write that and HTML and let a framework deal with the JS for me. I think a lot of PHP devs are like me and feel uncomfortable with JS.
From the October docs: "The data attributes API lets you issue AJAX requests without any JavaScript. " -- well, yes, it does, and this was pretty cutting edge when it was first added. I was blown away with how easy it was to use. But people expect a lot more from an AJAX framework these days. JimRed mentioned onBlur. How about the History API as another example?
I'm not saying that I necessarily want to see Livewire integrated into October (although I wouldn't mind!) but I do think that the October Data Attributes API could do with updating. The expectation to be able to wield real JS power on the client without writing any actual JS is becoming more and more common in PHP development now. Laravel's Jetstream is an example of this.
It's beyond my skillset but if anyone wants to propose a PR to add decent History API support to October's AJAX framework then I'd definitely be willing contribute a little bit financially.