It is called MVCC. Other databases such as oracle and postgres also use this approach. MVCC has its pros and cons. It allows for higher concurrency, but it might require extra copies of data and that translates to more memory and disk space. On a "weak" server it might actually end up being less concurrent.
Properly configured xml systems have common schemas in their catalogs so they never fetch those dtd from remote sites. If they don't have a dtd they would only need to fetch it once.
To summarize: Doctype = good, misconfigured or stupid xml systems = bad
Actually it's the applications that make the most difference. In a typical server most of the cpu time is used for the database (queries etc) and calculations. Optimizing/reducing your queries and application code might save you more a lot more electricity than switching platforms.
The key-signing part is solved (your suggestion should work without issues). The main issue is incompatibility in naming and/or features. If there is a wiki or something similar to document those AND packagers follow the wiki then your suggestion would work.
Another solution is a centralized search-enabled page that allows anyone to submit their repos and keys. It should ideally spider all repos for available packages and network reliability issues.
For your sources.list problem:
You can use apt-cache policy <package> to see what source provides each package.
It's already in the non-free section for Debian in both testing and unstable. So it should be included when etch is released (early next year probably).
I hear this a lot and it's simply not true. *BSD has GTK, QT (on top of X11) but Mac OS X has Cocoa, Carbon.
Their APIs are not similar. How does that make porting any easier?
I don't think there is a reporting solution that works with Mono. Please let me know if you know one that does. The two big players, Crystal Reports and ActiveReports, use Win32 hooks either for licensing or for functionality not present in.NET. Also, many commercial applications use the Infragistics components which also uses Win32 hooks
Native calls or the above libraries are not the only things preventing an application from running on Mono. Did you actually get your commercial application(s) to run on Mono?
The problem is that MS (intentionally or not) left a lot of functionality out of the.NET standard libraries _AND_ made it almost trivial to call native code from within.NET. The end result is that most applications end up using Win32 DLLs directly so wine is still necessary.
It worked for me yesterday without a hitch when I downloaded the DirectX (Dec 2005) SDK with FireFox.
I uninstalled the plugin shortly afterwards (deleted the npSomethingSomething.dll from the plugins folder).
The Windows Genuine Advantage validation plug-in was the biggest surprice for me.
In the download page they even have step-by-step instructions with photos on how to install it on Firefox.
From the email:
"All the drivers of course include source and have been released under the GPL. They have also already been submitted upstream ( kernel.org, alsa.org , x.org) and can be downloaded at intel.com/go/linux."
Slashdot Mirror
Strictly speaking it's +Inf.
It is called MVCC. Other databases such as oracle and postgres also use this approach. MVCC has its pros and cons. It allows for higher concurrency, but it might require extra copies of data and that translates to more memory and disk space. On a "weak" server it might actually end up being less concurrent.
To summarize: Doctype = good, misconfigured or stupid xml systems = bad
Calling this a PC (Personal Computer) is a bit of a stretch :)
Or write a "reference" implementation. It's no substitute for documentation but it will help those that cannot/will not buy the specification.
They left the author name intact.
Actually it's the applications that make the most difference. In a typical server most of the cpu time is used for the database (queries etc) and calculations. Optimizing/reducing your queries and application code might save you more a lot more electricity than switching platforms.
To prevent you from printing the movie frame by frame and scanning the frames in another PC.
It says "license Microsoft code related to...". Code != patents, just like standards != implementation.
It's a necessity and it only works well for client-server stuff. For P2P not so well. Try "torrent NAT" or " NAT" in google and you will see why.
The key-signing part is solved (your suggestion should work without issues). The main issue is incompatibility in naming and/or features. If there is a wiki or something similar to document those AND packagers follow the wiki then your suggestion would work. Another solution is a centralized search-enabled page that allows anyone to submit their repos and keys. It should ideally spider all repos for available packages and network reliability issues.
For your sources.list problem: You can use apt-cache policy <package> to see what source provides each package.
No other religion keeps its teachings secret no matter how idiotic they might seem to non-believers. Why is CoS different?
That's what makes it a cult in my book
For the nvidia kernel module you need to:
Big Pharma could agree to sell them the vaccine at (greatly) reduced prices. That's if they actually cared about saving millions of lives.
Most apache projects use maven so dependencies are handled automatically for them. The learning curve for maven is steep but it's well worth it.
It's already in the non-free section for Debian in both testing and unstable. So it should be included when etch is released (early next year probably).
Does the problem still exist? Yes.
Does the law firm help? Yes
I would call it a "better than nothing" measure but I wouldn't call it a solution.I hear this a lot and it's simply not true. *BSD has GTK, QT (on top of X11) but Mac OS X has Cocoa, Carbon. Their APIs are not similar. How does that make porting any easier?
You mean something like module assistant?
I don't think there is a reporting solution that works with Mono. Please let me know if you know one that does. The two big players, Crystal Reports and ActiveReports, use Win32 hooks either for licensing or for functionality not present in .NET. Also, many commercial applications use the Infragistics components which also uses Win32 hooks
Native calls or the above libraries are not the only things preventing an application from running on Mono. Did you actually get your commercial application(s) to run on Mono?
The problem is that MS (intentionally or not) left a lot of functionality out of the .NET standard libraries _AND_ made it almost trivial to call native code from within .NET.
The end result is that most applications end up using Win32 DLLs directly so wine is still necessary.
It worked for me yesterday without a hitch when I downloaded the DirectX (Dec 2005) SDK with FireFox. I uninstalled the plugin shortly afterwards (deleted the npSomethingSomething.dll from the plugins folder).
The Windows Genuine Advantage validation plug-in was the biggest surprice for me. In the download page they even have step-by-step instructions with photos on how to install it on Firefox.
Visual Studio != C#. When you consume a Web Service, VS writes the necessary code for you.
From the email:
"All the drivers of course include source and have been released under the GPL. They have also already been submitted upstream ( kernel.org, alsa.org , x.org) and can be downloaded at intel.com/go/linux."