gruiiik.bsky.social
gruiiik.bsky.social
@gruiiik.bsky.social
I will have to resuscitate my porting branch, but I think I also had some errors, but probably due to some hacky way we are using 4.
May 16, 2025 at 7:53 PM
Ok, I will keep that in mind. Anyway to disable these while keeping debug build ? Because the performance in some of our views were really bad ( we have a property window which is highly dynamic and contains quite a bit of components )
May 16, 2025 at 7:38 PM
My code absolutely did not run faster - quite the opposite. I got to the point where most of the applications were running but we had performance issues compared to 4. Might be my own problem though.
May 16, 2025 at 7:33 PM
Does not work very well for us, and it will disappear in 6
May 16, 2025 at 7:07 PM
For now at least, we concluded that porting to 5 would not be a viable option. So stuck to 4, which is great anyway, hoping it does not end up as a technical debt.
May 16, 2025 at 9:50 AM
Yes, that is what i started doing when I was trying to port, but it's not the only problem for my use case.
May 16, 2025 at 9:49 AM
3 and 4 were just perfect for us in our use case ( we came from Ember / Ember data and having svelte that did not force you to wrap your data around something was just so amazing ).
May 15, 2025 at 3:53 PM
It's a bit more involved than that. The bottom line is, we probably hacked around 4 quite a bit to fit our needs, and going to 5 would mean a lot of rewrite. Now I have a quite big software running on a deprecated framework with no clear upgrade path.
May 15, 2025 at 3:51 PM
Sorry English is not my native language. This is the task I created a while back : github.com/sveltejs/sve... while investigating svelte 5 port.

For info this is our software, fully made in svelte 4 ( sorry for the music .. www.linkedin.com/posts/future... )
add a way to force update a state variable · Issue #14520 · sveltejs/svelte
Describe the problem I'm using a custom made data store with realtime update. In svelte 4, when the value got updated, I was just doing value = value to refresh different bindings. In svelte 5 it i...
github.com
May 15, 2025 at 3:37 PM
It means that I will duplicate my data : once as an object into my data middleware, and another time in svelte "state.raw", it was not the case in 4.
May 15, 2025 at 3:22 PM
That would not work for us as we use our own data middleware. 4 has the huge advantage of not modifying your data structure while 5 puts its "fingers" everywhere. I personally think proxies should have not been used ( but of course it's my personal use case ).
May 15, 2025 at 2:03 PM
I'm sad that svelte 5 is a major turn off for our company, so we will be missing in new features like that.

We have to stay on svelte 4, not because of runes, which are cool, but because of these damn proxies.
May 15, 2025 at 1:37 PM
J'en cherche aussi :/
March 17, 2025 at 11:03 AM
C'est pas au lab ça ?
March 17, 2025 at 9:50 AM
Ping me next time you come ! Miss you :)
March 5, 2025 at 9:42 PM
I'm sorry for you and I care as well. But I don't think there is anything I can do since I'm not a us citizen. Keep your french passport at least, it will not change.
January 28, 2025 at 7:51 PM
Yeah, good luck with that :/ hopefully in California it might be a bit better ?
January 23, 2025 at 11:05 AM
Sorry to hear that :/
January 22, 2025 at 8:11 PM
You are moving to the US ?
January 22, 2025 at 7:41 PM
Ho but wait :
January 22, 2025 at 4:34 AM
It never will be. You have a lot of people that love you, the rest are just just sad humans.
January 22, 2025 at 4:27 AM
They cared as long as it was necessary for their coporation. Now doing the opposite is more beneficial to them hence the turn coat. But don't worry, if someone with other ideas comes up, they will follow as well.
January 21, 2025 at 4:28 PM