When V3? #5585
Replies: 35 comments 19 replies
-
|
Thanks Caleb. We appreciate the good work |
Beta Was this translation helpful? Give feedback.
-
|
The introduction of v3 was quite exciting, there are some exciting innovations worth waiting for. I hope you will complete it as soon as possible |
Beta Was this translation helpful? Give feedback.
-
|
Good things take time. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
We're all excited about what's to come, but we trust that you're taking the necessary time to do it right. |
Beta Was this translation helpful? Give feedback.
-
|
You’re doing great, man! Grateful for you! |
Beta Was this translation helpful? Give feedback.
-
|
I get the no specific date ,but is there an approximation at least? a quarter or smth? :P |
Beta Was this translation helpful? Give feedback.
-
|
You are doing amazing, keep up the awesome work 🔥🔥🔥 |
Beta Was this translation helpful? Give feedback.
-
Pretty excited about this. Take your time Caleb! |
Beta Was this translation helpful? Give feedback.
-
|
@calebporzio Impressive that you're working on quality for the future! Don't hurry much. Such work should be done carefully. I hope you also take a look into the issue of wire:model's rollbacks, as it is the major drawback of Livewire compared to the popular front-end frameworks. @joshhanley definitely knows what I'm talking about. Once V3 is released, I'm eager to update the Livewire Best Practices 😉 |
Beta Was this translation helpful? Give feedback.
-
|
Every person needs to sponsor @calebporzio to let him make the best possible v3 and wait patiently. |
Beta Was this translation helpful? Give feedback.
-
|
take your time. Thanks for being transparent about this |
Beta Was this translation helpful? Give feedback.
-
|
Your rational is correct as far as I am concerned. Thanks for such great package. |
Beta Was this translation helpful? Give feedback.
-
|
Keep it up. No rush. |
Beta Was this translation helpful? Give feedback.
-
|
Your genuine and transparent approach is better than a deadline. Thank you for everything. |
Beta Was this translation helpful? Give feedback.
-
|
@calebporzio thank you, |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, @calebporzio for letting this know. I was desperately waiting for this. |
Beta Was this translation helpful? Give feedback.
-
|
We are grateful for your time and efforts, you have made great impact on the Laravel community. |
Beta Was this translation helpful? Give feedback.
-
|
People are asking for a date because they are excited about it. I think this is a good thing! |
Beta Was this translation helpful? Give feedback.
-
|
Totally worth the wait. @calebporzio we are always grateful to you for working so hard to ease our lives. 🙌🏾 |
Beta Was this translation helpful? Give feedback.
-
|
I think the thing that most people got excited is that it was introduced half a year ago. 😂 |
Beta Was this translation helpful? Give feedback.
-
|
Hi. I am sponsoring this project since the day I found how much fit to all I develop and complete replaced need to use Vue. As we don't hear many updates can we at least get a confirmation that there will be version 3 and work is continuing. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Only 45 days left until LaraconUS! It's possible that we'll receive some updates from the event. 🤞 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the transparency and the hard work Caleb! My biggest question and concern, admittedly, is around sustainability. Do you have a team helping you? What can we do to help it be something sustainable for you to create and support it for years to come? Is simply supporting you on Github enough to ensure this is a product we can count on to be around for a while? As always, we appreciate everything you guys are doing. Livewire is one of the coolest things to come in the industry for a while, and I really hope it can find a solid foundation where large businesses can trust it's worth the investment for the next several years at least. |
Beta Was this translation helpful? Give feedback.
-
|
Finally we have a public announcement 😍
|
Beta Was this translation helpful? Give feedback.
-
|
Ah! Finally it's coming on July 20th.. |
Beta Was this translation helpful? Give feedback.
-
|
Exciting times a head |
Beta Was this translation helpful? Give feedback.
-
|
Which devtools @calebporzio installed there in laracon US? |
Beta Was this translation helpful? Give feedback.
-
|
hello, i tried to install V3 according to documentation, but it is not working. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Livewire peeps.
"When V3?"
Right now I can't give you a date, but I CAN be transparent about the process and my progress, so here's what I would type to everyone who asks if I had time:
"Why can't you set a date?"
Because I don't know that I can stick to one and I don't want to say something and then go back on it. I COULD set a deadline for myself and ship no matter what, but I really don't want to be forced to skimp on things to get it out the door.
"Deadlines and concessions are good when shipping software. Shipped is better than perfect"
In general, I agree. If I ran a software company, I would want every developer to think like this. However, Livewire V3 is a ground-up rewrite that will likely be the codebase we will all work with and use for a very long time. If it's rushed and I don't like it, I won't be happy maintaining it and I won't be excited to add new features.
"Aren't rewrites almost always a bad idea?"
Yeah, almost always. And maybe even in this case too. In an alternate universe, I incrementally improved the codebase and shipped things as I went. However, Livewire is such a complex tool I'm not sure I would have been able to incrementally find better abstractions and performance enhancements without starting from scratch.
I'm trying to lay a foundation for a VERY bright future for Livewire. I want to take this tool as far as I possibly can, and this is the foundation of that.
"Is Livewire really THAT complex of a tool?"
I often find myself asking the same question. Hypothetically, one could write a super simple version of Livewire that would be extremely simple to build (I actually did this as a thought experiment in a Laracasts series called "Building Livewire from scratch"). But you would be missing key features that make Livewire worth using. For example: nesting components,
wire:modelbinding, morphdom, security stuff, non-primitive public properties, etc... This list feels endless actually.So again, yeah, I've asked myself this a thousand times and always come back with: yeah, it is. lol.
"Why not involve the community more in this process?"
I'm trying to do that more with this "V3" discussion section. Getting feedback from the community is super valuable to me, but opening up the codebase and accepting pull requests and such would actually make this process much slower. For now, I still want to be able to "move fast and break things" with the V3 codebase until I land on the right architecture and abstractions. So I will try to be better about looping in the community, but less on a: "here's the codebase, let's write V3 together" and more a "here's what I'm thinking about doing with X, what do you think?"
"How much do you have left to do? I mean, you demoed a working version at Laracon right? Can't you just ship it?"
I don't regret demoing it at Laracon, but I can see how it might feel weird that it's taking me so long.
What I demoed at Laracon was very experimental. It was a codebase that had all the V3 features, but only had hacky versions of the V2 features I needed for the talk.
The bulk of the work since has been supporting every single feature in V2 so that every single unit and browser test passes with the new codebase. We are nearly finished with that process, so now what's left is:
"When will you release a beta version?"
I still don't have a date or anything, but I can say I've already put together an "alpha" and sent it to a few folks to try out. Once I have a "feature-complete" version for both V2 and V3 features I'm going to put it in "beta" and start sending it to more folks. Please hold off on asking for beta access until I'm at that point.
"How will you launch it when it's time?"
Well with lots of theatre of course! I'd like to do a small, online, event for the launch to properly show you everything live. That's just an idea right now and nothing more though.
So there you go, a giant thought spew of everything I think when someone says "when V3?".
TLDR: Can't give a date, but I can tell you I'm working every single day on getting it out the door.
387 votes ·
Beta Was this translation helpful? Give feedback.
All reactions