Bad news to all you AMD fans (yours truly included), Microsoft has announced that the upcoming Windows 2003, 64 bit edition will *not* have support for Opteron's 64 bit mode!
Bad move Microsoft. Your new mantra is supposed to be "competition is good", but this reeks of a side deal with Intel. Us, the users, want 64 bit power, but until competition helps lower costs, we can't afford it.
Ok, maybe 64 bit is supposed to be for big iron, but someone once said that 640K would be all the memory we'd ever need. What can we do to get you to change your mind MS?
Few five years olds have had as much impact as our little XML has these last few years. What started out as just structured storage as really changed into computer technology.
Now that Verizon has been ordered to rat out their users to the RIAA, Internet privacy is over...but maybe for the better. Sure I loved the high-flying days of song swapping, but where is the line between privacy and intrusion.
In the last few weeks a number of comparison between Java and .NET have been floating around. As much as I am interested in these comparisons on an intellectual level, I really don't care on a practical level. Do most day-to-day developers really care? Sure, the number of jobs out there for any particular skill set move with the tides so most of us care. But on a purely technological comparison, the differences is minimal.
These comparisons just help fuel the religious fervor between the Sun v. MS camps. I thought that today's world was more interopability and web services we could perhaps just put the differences aside and stop caring about which specific features are better or worse in each platform. Truth be known, most every project could be developed in either toolset with little change.
Last February Bill Gates announced that he was halting development until every project could be reviewed for security and make sure every developer knew how to write secure code. In fact, a pretty great book came out of the process. So did it work?
I've been in the market for a new laptop for the last few months. With the upcoming new laptop ideas coming out (Tablet PC's, Smart Displays, etc.), I decided to wait for the technology to catch up to my desires. Finally everything is out!
Back in ancient history (the mid '90's), I worked with Toshiba tablet systems running Windows 95 for a vertical market package. I loved the form factor and secretly wished for a touch display for my laptop for years now.
Ok, maybe this may be petty, but why do so many sites require that 'www' before the names? I have wasted lot sof time trying to navigate to sites by just their domain name, only to find out that I need the 'www'. What do I mean? Both of these should work:
But then why would some develop a site that doesn't work like that. For example (with apologies to Brent Rector):
I recently read about the reemergence of Code Generation on Chris Sells' News page. It seems that John Lam has been converted, but not by Chris. As some may know, I worked with Chris Sells while he lead the team that built DevelopMentor's Gen<X> so that I have been thinking about this code generation question quite a long time now.
When I first read the SOAP specification I could not decide whether it was meant to be a replacement for DCOM/RPC or whether it was a messaging protocol. I loved the fact that the ligua franca of SOAP was XML. But at the same time, Section 5 supported the RPC view of SOAP. Unfortunately this section seemed to just confuse the issue between the RPC world and the document/literal world.
In a great MSDN Article, Tim Ewald argues against support for Section 5 support. I guess I haven't been keeping up, but I am excited to hear that Section 5 support is now optional in SOAP 1.2 specification. Yeah...but will Section 5 really ever die?
|Vue.js by Example (New Lower Price)|
|Bootstrap 4 by Example (New Lower Price)|
|Intro to Font Awesome 5 (Free Course)|
|Building an API with ASP.NET Core (New Course)|
|Building a Web App with ASP.NET Core, MVC6, EF Core, Bootstrap and Angular (updated for 2.2)|
|Less: Getting Started (New)|
|Using Visual Studio Code for ASP.NET Core Projects|
|Implementing ASP.NET Web API|
|Application Name||WilderBlog||Environment Name||Production|
|Application Ver||v4.0.30319||Runtime Framework||x86|
|App Path||D:\home\site\wwwroot\||Runtime Version||.NET Core 4.6.27317.03|
|Operating System||Microsoft Windows 10.0.14393||Runtime Arch||X86|