Estaría bien saber la opinión de @juanrallo sobre este artículo Spain's economy expands: Why is it outperforming its European peers?

🔄 to err is human // to undo, d̶i̶v̶i̶n̶e̶ Universe’s newest feature. because grids aren’t just for designers. they’re for experimenters. dreamers. makers. so dive back into your site and push your creative boundaries. you can always undo yourself back to safety.

Sigue en directo el preestreno de 'Muchachada Fui' con Toño Pérez (@sigabuscando), autor del podcast, Joaquín Reyes (@enjutomojamuto) y Ernesto Sevilla. #RTVEPlayPodcast https://t.co/D8JwcbeVkZ

Autosave is now live in the editor. If the app closes unexpectedly or you take a phone call - your work will be saved. Word is our social media manager is pretty thrilled about this. Support-related DMs are projected to go down. Collective relief—way up.

New Panels version v2.12 with nested collections support. We have completely rewritten our library engine. Read more here: https://t.co/QU6yYq1UsQ

"El Helmitas" (parte 1/2)

Here’s my latest blogpost for @jobandtalentEng

Jobandtalent's iOS lead @luisrecuenco has written an interesting blog post talking about "value integrity in Swift". Don't miss it!

Substack comics on the Panels app, by @SubstackInc

Créditos: ifluent

Talked with team today about ObjC interop, how KMM devs with Android background are like "Don't worry, it's just your regular iOS framework" and iOS devs who see these interop declarations for the first time are like "HELL NO". Ten minutes later @KathrinPetrova sends me this pic:

Algún día tenia que llegar @pedro_g_s

Buenos días. Vengo a soltar un "te lo dije" y ya me voy. Durante años he repetido por activa y por pasiva que Ruby On Rails me parece una de las herramientas peor utilizadas de la industria del software. Una herramienta sacada de contexto. Usada en situaciones donde no encaja.

I would like to know if someday KMM will be able to generate fully Swift code. That day, I will fall in love with KMM. @kotlin

With this, I don't want to say that KMM is not useful for other projects. Sharing code between Android and iOS is the Holy Grail of mobile development. But in our project losing the possibility of using Value Types makes KMM a non-valid option for us yet.

There are more issues like transforming a List into an NSArray, or not transforming properly non-optional parameters into Optionals. We don't know why KMM has created Kotlin non-optional values into optional values in Swift. ¯\_(ツ)_/¯

Here comes for us the worst thing about KMM. It has transformed a Kotlin Generic into an AnyObject. To sum-up, this forces the consumers of our library to use only reference types so forget about using Structs or Enums to interact with our architecture.

As far as I know, everything is going to be a subclass of KotlinBase and therefore a subclass of our old friend NSObject. This is not really bad but our generated code will lack value types.

And this is the generated Swift code. Let's analysed the most important things.