Monday, March 08, 2004

Eric Gunnerson en su nueva columna explica el impacto que tienen los diferentes mecanismos para invocar código dinamicamente ... muy interesante.   3:18:11 PM    comment []

XAML Con LongHorn y el uso de XAML como protocolo estandard para definir elementos de interface de usuario, Miguel de Icaza y la gente de XIMIAN exploran las posibles consecuencias del éxito de XAML para Linux: "The future of Linux on the desktop is in fact on the line: if enterprise developers and IT developers fall in love with Xaml for building their in-house applications it will marginalize again Linux on the desktop. There are two views of how to solve this problem. The Nat Friedman view of building a matching system in the meantime: leveraging our existing technologies, or the Miggy-view, which is lets implement the Avalon/XAML API. I think we should pursue both paths. By Miguel de Icaza (miguel@novell.com). [Miguel de Icaza]" 3:14:26 PM    comment []

.NET Remoting: "I'm not dead yet!". La aparición de Indigo en un horizonte ya no tan lejano tendrá un impacto importante en los mecanismos de activación de componentes, entre ellos Remoting, sin embargo, aunque: "La aparición de Indigo pondrá en estatus de deprecated a .NET Remoting, este no desaparecerá:" "What we mean by this statement is that when Indigo is released, the semantics of object remoting will be supported through the Indigo infrastructure rather than the current .NET Remoting infrastructure. This will help overcome a number of the limitations that .NET Remoting currently suffers (such as having to share assemblies with callers), whilst extending the many benefits of Indigo to developers requiring Remote object semantics." Is .NET Remoting Dead? [via CSells] [Jeff Key] 2:58:12 PM    comment []

© Copyright 2004 Alberto Borbolla.