Archives
-
Miguel de Icaza on .NET vs J2EE
Miguel has interesting comments about Java and .NET.
-
DataSets and Serialization
We all know DataSets are not good when you want to serialize them, because they always are serialized as XML + the XML-Schema even if you are using a binary formatter. This implies you get a big serialization payload and bad serialization performance each time you transfer a DataSet using Remoting or when you store a DataSet in a ASP.NET session variable, just to mention two common scenarios.
-
DataSets and Serialization
We all know DataSets are not good when you want to serialize them, because they always are serialized as XML + the XMLSchema even if you are using a binary formatter. This implies you get a big serialization payload and bad serialization performance each time you send a DataSet using Remoting or when you store a DataSet in a ASP.NET session variable, just to mention two common scenarios.
-
The problem with code generators
It's quite usual to hear "the problem with code generators is that if you change the code they generate, you lose the changes the next time you generate the code".
-
Surface area
I'm really happy to hear that see Don Box keeps talking about that they need to reduce surface area of the .NET framework.
-
Abstraction vs Concretion
When we design software we usually build abstractions on top of other abstractions that we or someone else built.
-
Platforms and surface area
Both .NET and Java want to win the heart of the 'corporate developer' (aka known as the VB6/Powerbuilder/OracleTools/VisualFoxpro developer). If there is a winner in the .NET/Java war, it will be the one who captures that market.
-
SYS-CON Media Readers Choice Awards
These are the total number of votes for all of their magazines:
-
New Java APIs
Two more JSRs from the 'let's catch .NET' chapter: