June 2004 - Posts
Brad mentioned it, I have been snowed under with interview stuff so forgot to blog it (whoops :). Some really great stuff
Hoping Chris will talk a little about hosting. In answer to Brad's question, members of the Rotor team on Channel 9 would really, really rock !
From the Mono feed :)
Be the first kid in your block to install the it-took-us-three-years-but-we-did-it development platform.
Well blogged by now, I saw it first on Jesse's blog so he gets the mention :) Mono 1.0, bang on time and at the 1.0 milestone. Well done to everyone, its going to be a fun ride.
Today I turned 28, the big three zero gets closer and closer.
Matt has a note on a Flex talk he is giving at the event. No word yet on other speakers, my money is on
Christophe,
Brandon,
Waldo and
Sean. I also had money on Steve/Ali but this
post confirms that :) IMHO its going be very cool to see them speak about Flex, a real shame I will miss it.
Joel explains the draught of posts with a recent visit to a Rotor workshop in Singapore. Exploring some of the links
Dom has a great blog with some very interesting posts on F#, subscribed. Slides from the event would be great to see.
Sean has some notes on this post about Microsoft, developments tools and developers keeping up. In addition he makes some notes on Mono. Starting with the Microsoft tools.
The learning curve between one tool and the next for developers can be something that gets in the way, not all development houses can buy in the tools so they stick with what they have got and make the migration when they can. Those that can afford it want to take advantage of what Microsoft are doing, how they are forever pushing the edges of what they doing, how they are listening to developers and crafting the tools that developers want. Thats not a bad thing, in our industry sitting still is rather a bad thing.
Mono, its too early to say what will happen with Mono. Plans for running windows form apps and such forth are afoot but again its too early in the day. Let me say this, its an opensource project lead by a very smart bunch of people. What ever they decide for Mono it will be what folks want for the project. I don't see Longhorn effecting Mono, .NET 2.0, the CLR and C# specs are not one and the same. Longhorn failing would not effect a system thats running on other platforms, other windows and hosted Mono platforms alike. Anything wrong with Java, no nothing, but finding risk in Mono is like finding risk in Java.
A great
article on Whitehorse in this months MSDN mag. Yet more to look foward to in Whidby.
During my time with Team Macromedia helping out with (the now retired) Generator there were also several other Generator like products. . I was stunned to recently learn that one of these products the open source Java based JGenerator has been licensed by Macromedia. As yet I still don't know fully what it means, Macromedia have licensed the sourcecode and the agreement states that the product can no longer be sold by JZox (its developers). Will Macromedia develop the product, will they sell it? The date on the news article is 12/11/2003 so this agreement has been in place for well over six months.
Macromedia's Sean Neville has an interesting post on the Flex list
The .NET version of the AMF gateway supports ADO.NET data marshaling, and
the web service proxy supports data set marshaling through SOAP, but perhaps
more important than the underlying mechanisms is general support for the
pattern language, as it is philosophically different from Java.
A Java enterprise developer, if he adheres to patterns and best practices
for his platform, typically tackles a problem by sketching a domain model
based on the requirements, breaking that domain model into sequences and
class hierarchies (this is called the dominant decomposition), and then
dealing with issues such as security, distribution, and persistence as
aspects of that domain model. A .NET developer, on the other hand, typically
tackles the same sort of problem by sketching a data model rather than a
domain model first, and creating hierarchies of data objects rather than
domain objects. Rather than creating a pure OO model to which O/R tools,
CMP, Hibernate, DAO's, Data Transfer Objects, etc. can be applied, the
typical .NET developer composes a data model to which objects, xml,
relational data, documents, etc. can be applied. It may seem a subtle
difference, or it may seem impure in OO terms to Java patterns purists, but
one of its strengths is that it is by and large a simple and extremely
flexible way of managing data across tiers. .NET has no CMP equivalent per
se, and escapes debates about JDO vs. EJB vs. Hibernate by simply making
data objects a top-level first class design element rather than an aspect of
a domain model.
I'm not espousing one approach over the other, merely pointing out that
there are architectural differences in the way data is typically managed on
the two platforms and that we're addressing it in Flex as well. At a
practical level, this means support for ADO.NET-style data binding and
first-class handling of ADO.NET data sets
Would be interested to hear folks thoughts?
Been a while since I checked this show out, very pleased to see my old friend (and Flash god) Chrissy Rey getting her JobVibe web site nominated. I was surprised not to see Flex in the sessions, my other surprise was show speaker Manuel Clement a product designer working on next generation development tools at Microsoft. Its very, very cool to hear that Microsoft have such a Flash pro on staff, can anyone say Sparkle ;-)
More Posts
Next page »