iagolast
@iagolast.bsky.social
Files are deleted after 5 minutes.
I think it looks nice.
I think it looks nice.
March 9, 2025 at 4:07 PM
Files are deleted after 5 minutes.
I think it looks nice.
I think it looks nice.
Si alguien quiere probarlo (o poner un anuncio) que me escriba un DM ❤️
March 6, 2025 at 7:14 PM
Si alguien quiere probarlo (o poner un anuncio) que me escriba un DM ❤️
Esto lo he pensado puedo probarlo..
January 23, 2025 at 2:36 PM
Esto lo he pensado puedo probarlo..
No, el problema va mas por como acelerar un foreach para no bloquear el hilo de UI
January 23, 2025 at 2:35 PM
No, el problema va mas por como acelerar un foreach para no bloquear el hilo de UI
Mi problema con react es que tengo X listas con Y elementos. (Dos for anidados).
La UI se queda totalmente frita hasta que se renderizan todos los elementos.
Hay alguna forma de acelerar esto? Que el primer render devuelva null y luego asincronamente se vuelva a renderizar?
La UI se queda totalmente frita hasta que se renderizan todos los elementos.
Hay alguna forma de acelerar esto? Que el primer render devuelva null y luego asincronamente se vuelva a renderizar?
January 23, 2025 at 11:34 AM
Mi problema con react es que tengo X listas con Y elementos. (Dos for anidados).
La UI se queda totalmente frita hasta que se renderizan todos los elementos.
Hay alguna forma de acelerar esto? Que el primer render devuelva null y luego asincronamente se vuelva a renderizar?
La UI se queda totalmente frita hasta que se renderizan todos los elementos.
Hay alguna forma de acelerar esto? Que el primer render devuelva null y luego asincronamente se vuelva a renderizar?
Nice!! How hard it would be to implement a “navigate” method?
With vitest/jsdom I usually do “full tests” where I navigate to a page, render the whole app and I interact with the ui.
Last time I’ve tried with vitest/browser I struggled to navigate to an url 🥲
With vitest/jsdom I usually do “full tests” where I navigate to a page, render the whole app and I interact with the ui.
Last time I’ve tried with vitest/browser I struggled to navigate to an url 🥲
December 9, 2024 at 10:26 AM
Nice!! How hard it would be to implement a “navigate” method?
With vitest/jsdom I usually do “full tests” where I navigate to a page, render the whole app and I interact with the ui.
Last time I’ve tried with vitest/browser I struggled to navigate to an url 🥲
With vitest/jsdom I usually do “full tests” where I navigate to a page, render the whole app and I interact with the ui.
Last time I’ve tried with vitest/browser I struggled to navigate to an url 🥲
Yes, but las time I checked it has lots of server stuff integrated
December 1, 2024 at 9:12 PM
Yes, but las time I checked it has lots of server stuff integrated
Related: This week I was playing around with RR7 and your router and I felt the impulse of starting a fork focused on SPAs
Imo, all the server stuff adds too much complexity that’s not always required.
Imo, all the server stuff adds too much complexity that’s not always required.
December 1, 2024 at 5:29 PM
Related: This week I was playing around with RR7 and your router and I felt the impulse of starting a fork focused on SPAs
Imo, all the server stuff adds too much complexity that’s not always required.
Imo, all the server stuff adds too much complexity that’s not always required.
+10 years in the front end business.
I would say 90% “client side”. (Dashboards, apps etc)
Server side only for websites/marketing
I would say 90% “client side”. (Dashboards, apps etc)
Server side only for websites/marketing
December 1, 2024 at 5:29 PM
+10 years in the front end business.
I would say 90% “client side”. (Dashboards, apps etc)
Server side only for websites/marketing
I would say 90% “client side”. (Dashboards, apps etc)
Server side only for websites/marketing