Comment Re:Goddamn you, Tor (Score 1) 228
or aliens or robots from the future... whatever, fuck you! You'll watch it anyway.
or aliens or robots from the future... whatever, fuck you! You'll watch it anyway.
How can that be true? If Steve Jobs is living tissue over metal endoskeleton, he should last 120 years with his existing power cell...
How about the same thing the factory worker does when he's replaced by automation or his job is outsourced to cheaper labor markets. Survive. Adapt. Why is it so unthinkable that highly educated people would be put out of work by progress, instead of simply the low wage laborers?
"This article is based on a prerelease version of the
Can I recommend that you find a slightly newer source?
"Mono can't run
Wow, that's funny. I must be on acid, because I thought I just compiled a
"Probably you would have to code in a subset of Mono, this coupled with the fact that Mono will always play catch up to
Let's see how true this is:
http://mono-project.com/Compatibility
So here's what's missing:
CodeContracts - API complete, partial tooling
EntityFrameworks - Not available.
Server-side OData - Depends on Entity Framework.
WCF - silverlight 2.0 subset completed
WPF - no plans to implement
WF - Will implement WF 4 instead on future versions of Mono.
System.Management - does not map to Linux
System.EnterpriseServices - deprecated
So other than the above Microsoft specific technology plus Entity Framework (use NHibernate instead), the entire C# 4.0,
So basically, your entire point against Mono as a multi-platform solution for ISO standards based
Yeah those Mono license fees are expensive. Almost wiped out my company with those fees. It's not like they have
Are you serious? We abandoned C++ Builder for Visual Studio and C#
Oh and by the way, a base class library that requires you to *new* every BCL object but doesn't have garbage collection, simply begs for access violations and memory leaks. Simply idiotic. You couldn't pay us to switch back.
As a bonus, we can compile our
Microsoft hasn't abandoned DOS or Win16???? Have you tried running a DOS program or a Windows 3.x program in Windows 7? I think you'll find that your information is more than a little out of date.
And NT was a complete and total abandonment of the Windows 9x codebase. The entire OS was rewritten from scratch in C, an entire NT API exists under the hood that powers that OS, and then the Win32 API/ABI was added as a compatibility layer on top of that OS. As was their POSIX and OS/2 compatibility layer.
I know you probably can't be bothered to validate what you're saying before you say it, but perhaps a little bit of Google is in order before you spout off? Or try running a DOS app. Or something. Or let the grown ups talk.
I hate having to explain this to non-.NET developers over and over again. Try to follow along.
In Visual Studio, if you select x86 or x64 or Itanium as your target instruction set, CIL (formerly MSIL) is not generated. NATIVE machine language is generated, doing the job that the JIT would normally do. You with me so far? You can target native platforms, and produce native code.
Beyond that, if you do choose to generate an "Any CPU" binary,
http://en.wikipedia.org/wiki/Global_Assembly_Cache
Your argument is like saying, because you have to run a tarball of source through
Again, *know* what you're talking about. We're not talking about just any generic theoretical JIT. We're talking about the
.NET is a great platform, and C# is a great language. All of this
Except AJAX of course. They just pretend Microsoft didn't invent XMLHttpRequest or iframe.
How exactly is
Insightful? Come on mods, do better.
No, as you can see from the following, the standard Win32 message pump isn't an infinite loop...
while(GetMessage(&Msg, NULL, 0, 0) > 0)
{
TranslateMessage(&Msg);
DispatchMessage(&Msg);
}
Non-Affected Software
Windows 7 for 32-bit Systems
Windows 7 for x64-based Systems
Windows Server 2008 R2 for x64-based Systems
Windows Server 2008 R2 for Itanium-based Systems
Direct2D and Direct3D are a part of the "hardware graphics calls in Windows". The fact that it's not in the GDI/GDI+ libraries doesn't change that. DirectX ships with the OS, is required for the OS to function, and thus DirectX IS literally one of the OS APIs for rendering graphics.
A morsel of genuine history is a thing so rare as to be always valuable. -- Thomas Jefferson