Skip to main content

New XML Editor in VS.Net

Thanks Ted for letting us hear at least a little bit of the new XML editor. Of course, the big thing here is that it MIGHT be available as a standalone download so we don't have to wait until Whidbey (CORRECTION from Previous posts: I thought it read standalone editor - just my wishful thinking)

I know everyone thinks that XML is the NBH (Next Big Hype) and I will admit to being in that group. I love XML as a way for dealing with so many different data streams and more. But, realistically, I think it's important for an editor to exist that makes it easy to:

a) build useful XSL stylesheets quickly
b) understand the structure of the file
c) modify and update the DTD schema

I think that a lot of developers who have been working with XML tools in a theoretical or "tool" based environment miss the point that many developers, who are focused around getting products out, don't have the same time to learn how all of these new functions work, even though they can understand the benefits. They want the tools that allow them to take advantage of XML without having to understand the syntax of XPATH, XSL and other areas. I really hope this is where the new XML editor comes into play. I may be hoping for too much --- but I hope not. Otherwise we (as the entire developer community) will find ourselves in a similar situation as when OOP started becoming more popular and a great many developers who didn't get it immediately became frustrated and as a result, churned out a lot of pretty ugly stuff.

I've seen lots of TERRIBLE XML implementations and pure misunderstandings of what XML looks like. Tools like XML/Spy have great goals but I think the end result misses the boat. I hope the MS XML Editor helps fill the void...

Ted's Radio Weblog

Comments

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...