Skip to main content

Ted on past paths of Microsoft

This was an older post (from the 15th) but for some reason it shows up as an updated note in Newsgator but I'm glad it did. Great reading and reminder for those who continue to put all of their eggs in one basket.

As I noted in Ted's comments, this is why it's important to build your solution architecture so that you can switch technology where needed. Microsoft isn't the only one who does this - but certainly Visual Studio's CLR makes it much easier to switch between different languages.

But it's still challenging to do so many things that are easier in other tools (er, um, Visual FoxPro ) - this is why the work that the Fox team and others are doing to make it easier for VFP developers to harness the "Good" stuff from DotNet is so important.


Ted Roche: The Old Microsoft Internet Head Fake?

Comments

Ted Roche said…
Thanks for the link, ARM.

The blog post showed up due to republishing my blog, but you're pointing to a (badly configured) echo of the blog on Blogspot; the correct web site is http://radio.weblogs.com/0117767. The BlogSpot site is a temporary one created with the RadioAtomBridge, and it's buggy and not working out well and will probably be discontinued.

Re: Switching languages in DotNet: switching from VB.NET to C#.NET is, to use your metaphor, switching eggs in the same basket. I find your claim that Microsoft allows you to switch to be incongruous. What other vendors or platforms offer language portability for DotNet code on the level of C, Perl, Python, Ruby, etc?

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 .

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...

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...