20 February 2003

Macromedia and Perl I agree with Dave, this would rock. 5:35:07 PM    comment []

Macromedia blogs on 1 server Told you so ;-) 5:28:00 PM    comment []

C# and the CLI... on a Mac Sean Corfield (Director of Architecture in IT at Macromedia) notes in his Blog how Rotor can run on the Mac OSX (yeap the build is not fast but when you are building 1 millon lines of code its never turbo). One comment of interest. C# is..Microsoft's version of Java, as far as I'm concerned Your welcome to your opinion I just hope its not a shared one. 5:23:36 PM    comment []

First commerical .NET tool from Borland First commercial tool I have seen from Borland is a .NET profiler tool so you can see GC stats, memory useage etc. 12:49:23 PM    comment []

How can Macromedia serve bloggers - via John Dowdell With the Google news it seems that Blogs are about to hit the main stream very quickly. Macromedia's Kevin Lynch asks what can Macromedia do to aid Bloggers. Already left my comments ;-) 12:43:21 PM    comment []

Microsoft tests the Blogging tool waters - via Microsoft Watch Billed on this website as news coming in the aftermath of the Google/Blogger purchase. What this is not is Microsoft attempting to break into Blog software its just some sample code to let you build your own homegrown Blog software. I do hate it when hype takes over, folk should know better. 12:35:55 PM    comment []

Python and .NET Written by Brian Lloyd the CEO of Zope this Python on .NET implementation allows the CPython runtime to run inside the CLR. Brian has stated that he wants to get it running on Mono and thus could allow current Python programs on Linux and Windows machines to be extended with the FCL. 8:58:41 AM    comment []

CLR and Patents Microsoft has announced that is it to patent the CLR. Following a recent mailing list thread over concerns on its impact on Rotor, Microsoft stated that the patent would not impact folk who wanted to develop the ECMA standard portions of the CLR ( a la Rotor). A few folk have asked what about the other parts, ASP.NET, ADO.NET, Win Forms and people who want to implement these (Mono and GNU .NET), the response from Microsoft is unclear but they did state that you should know which parts of the CLR are standards and which parts are not and what the patent effects. Reading into this it seems that open source projects such as Mono may be impacted if they try to port the non standard parts. I know that open source projects have stated ways around this but it could bring a lot of legal trouble. So in a nutshell while I can understand Microsoft wanting to protect its self I think this is going to do more harm than good and will only give the anti-microsoft/pro-anything-but-microsoft crowd something to cheer about. I do think that Microsoft had got to spell out what effects what in a clear fashion to the whole .NET community, at the moment it looks like the whole .NET movement is going to be delt a very severe blow.  8:45:50 AM    comment []