Video cards don't predict what the next frames will be - they simply let the app continue to render frames, which queue up while waiting for the screen's next refresh.
"Stored procedures" can reduce the amount of traffic between the client/server - with extensions some servers can even perform branching/etc. right in a sproc. The server can also store the VM of the query, so it doesn't have to parse it every time.
"Prepared statements" are can be thought of a temporary stored procedures that live as long as the client.
stuff like sqlite, berkeley db, and sql server compact edition already serve this purpose well. an actual server on a mobile device would be far too expensive.
Is this just a stripped down MySQL? Or is it a fork that actually bring some interesting new scalability features to the table that are otherwise unimplementable in the current MySQL architecture?
Maybe it's my pre-caffeine morning stupor, but the site seems void of any real details.
I got Windows Server 2008 free at the LA launch, so I figured I'd give it a go. I installed it and quickly changed everything to function as a desktop. Then I switched back. Here's why:
Many applications have real dumb incompatibilities. Usually it's just because they check the version, assume Server has everything that Vista has, and attempt to load some DLLs that don't exist on the Server version. This is fixable most of the time.
Some applications have installer issues. Their Windows Live stuff will refuse to install on a Server OS. Unreal Tournament 3 seems to be hardcoded to only install on Vista and below - it should be a laugh when Windows 7 comes out and nobody can install the game on it. The workaround is to dump the DVD to your hard drive, remove the check in the.msi, and install from there.
The sound system is screwy. Priorities are setup for different workloads, resulting in pops and hisses when you play music. This is fixable, but took me a while to figure out how and I still never seemed to get it perfect.
The bluetooth stack is absent. It's not an optional component in the installer, it's just not there. So you don't have the nice integrated solution anymore, and have to install crappy vendor-specific stacks that don't seem to work for everything.
The experience is definitely not a simple "setup windows, modify windows, use as normal" one. Most of the random things that screw up are fixable, but just too much of a pain in the ass and ultimately a waste of time.
Server *can* run faster than Vista, but only because various artificial limits are raised or removed. Most developers work around these limits and most are very good at it, so I doubt any non-developers would ever notice any performance difference. If you're looking to speed up Vista, find one of the various sites that list descriptions of services and which are safe to turn off. Most of the "bloat" of Vista can be turned off through that.
The only reason I could think of would be to reduce latency - scanning a page on demand probably incurs some noticable cost and if you can start a scan before the user clicks the link, you lower the perceived time to scan. But it definitely wasn't very friendly to servers.
The developer should know if he'll need the size of an array or not. Which is why there is a convenient std::vector and std::tr1::array for when you do want the size. Not forcing you to carry around a size is a feature, not a bug - if you don't need the size, it's just a waste of space.
And auto_ptr is likely to be depreciated in C++0x, with unique_ptr and shared_ptr replacing it.
* Pragmas are made specifically for non-standard compiler extensions. There can be no "standard" pragmas. * C++0x is adding support for UTF-8, UTF-16, and UTF-32 character types and literals. * TR1 adds cstdint which includes int32_t etc. types. * NaN and +Inf (not -Inf, though) can be had from std::numeric_limits
alas, if those are the first complaints you think of, you haven't been using C++ long enough to really know the painful bits.
The graphics card industry is cutthroat. The hardware is only part of the story - the drivers also do a lot of optimizing. They are probably worried competitors will use their own tricks against them.
Drivers compile shaders into something the video card can run - maybe they think their compiler optimizes better. On Windows at least, nVidia drivers will try to use SMP to prepare a few frames in advance for more efficient streaming.
Sorting it all Out - a Microsoftie who specializes in i18n/l10n. This is always a joy to read, even for those who don't run Windows.
Sutter's Mill - Anyone doing heavy C++ will know of Herb Sutter. His blog is updated regularly with standards work and other interesting C++-related things.
MAKE Magazine - Making weird stuff just for the hell of it.
Vista had problems too. They changed it to do automatic receive window scaling and it affected some of the cheaper routers. I have not RTFA or anything, but maybe this is something similar.
I don't think that idea will be too popular. Making it stateful would severely impact the scalability, resource demand, and robustness of modern websites.
Just use speech recognition. It's not faster than typing or using the mouse, but it's plenty fast enough if you just want to browse the web or send an occasional email.
When I first looked at Rails years ago, it (and Ruby) had far less than adequate support for i18n. Has this changed at all? I'm sure there are some Rails devs here with experience in that.
If you write your site for Firefox, chances are you can just tell it to use that code for IE8. Assuming, of course, that IE8 comes through with their promises of compliance.
A little pain now for a lot less cumulative pain later. I'll take that!
Slashdot Mirror
Video cards don't predict what the next frames will be - they simply let the app continue to render frames, which queue up while waiting for the screen's next refresh.
Wow, that's got to be some of the coolest tech I've seen in years. I can't wait for some software to come out that uses it. Avisynth plugins, anyone?
straw man much?
If it's LGPL, they can "extend" as much as they want and people can fork whenever they think MS has gone too far.
The newer version supports SetMTMode which works quite well in many cases.
x264 and avisynth can make pretty decent use of threads. check out meGUI.
"Stored procedures" can reduce the amount of traffic between the client/server - with extensions some servers can even perform branching/etc. right in a sproc. The server can also store the VM of the query, so it doesn't have to parse it every time.
"Prepared statements" are can be thought of a temporary stored procedures that live as long as the client.
stuff like sqlite, berkeley db, and sql server compact edition already serve this purpose well. an actual server on a mobile device would be far too expensive.
Is this just a stripped down MySQL? Or is it a fork that actually bring some interesting new scalability features to the table that are otherwise unimplementable in the current MySQL architecture?
Maybe it's my pre-caffeine morning stupor, but the site seems void of any real details.
I got Windows Server 2008 free at the LA launch, so I figured I'd give it a go. I installed it and quickly changed everything to function as a desktop. Then I switched back. Here's why:
The experience is definitely not a simple "setup windows, modify windows, use as normal" one. Most of the random things that screw up are fixable, but just too much of a pain in the ass and ultimately a waste of time.
Server *can* run faster than Vista, but only because various artificial limits are raised or removed. Most developers work around these limits and most are very good at it, so I doubt any non-developers would ever notice any performance difference. If you're looking to speed up Vista, find one of the various sites that list descriptions of services and which are safe to turn off. Most of the "bloat" of Vista can be turned off through that.
The only reason I could think of would be to reduce latency - scanning a page on demand probably incurs some noticable cost and if you can start a scan before the user clicks the link, you lower the perceived time to scan. But it definitely wasn't very friendly to servers.
How is this different from other Open Source editors, like GtkRadiant and QuArK?
Giving DNS, HTTP, etc. a higher priority than torrents is fine with me - I do that with my router.
The developer should know if he'll need the size of an array or not. Which is why there is a convenient std::vector and std::tr1::array for when you do want the size. Not forcing you to carry around a size is a feature, not a bug - if you don't need the size, it's just a waste of space.
And auto_ptr is likely to be depreciated in C++0x, with unique_ptr and shared_ptr replacing it.
* Pragmas are made specifically for non-standard compiler extensions. There can be no "standard" pragmas.
* C++0x is adding support for UTF-8, UTF-16, and UTF-32 character types and literals.
* TR1 adds cstdint which includes int32_t etc. types.
* NaN and +Inf (not -Inf, though) can be had from std::numeric_limits
alas, if those are the first complaints you think of, you haven't been using C++ long enough to really know the painful bits.
If Symbian goes open source, maybe we can get good native code running on it instead of the bastardization of C++ it currently uses.
Countermeasure to fight Android? Hah - Android won't even be in my sights until they let me write native code for it.
The graphics card industry is cutthroat. The hardware is only part of the story - the drivers also do a lot of optimizing. They are probably worried competitors will use their own tricks against them.
Drivers compile shaders into something the video card can run - maybe they think their compiler optimizes better. On Windows at least, nVidia drivers will try to use SMP to prepare a few frames in advance for more efficient streaming.
give increased speeds when you don't leave the network. downloads will complete faster, so less peering will be done.
Vista had problems too. They changed it to do automatic receive window scaling and it affected some of the cheaper routers. I have not RTFA or anything, but maybe this is something similar.
On how many products they can fit into a single slashvertisement.
I don't think that idea will be too popular. Making it stateful would severely impact the scalability, resource demand, and robustness of modern websites.
Just use speech recognition. It's not faster than typing or using the mouse, but it's plenty fast enough if you just want to browse the web or send an occasional email.
When I first looked at Rails years ago, it (and Ruby) had far less than adequate support for i18n. Has this changed at all? I'm sure there are some Rails devs here with experience in that.
If you write your site for Firefox, chances are you can just tell it to use that code for IE8. Assuming, of course, that IE8 comes through with their promises of compliance.
A little pain now for a lot less cumulative pain later. I'll take that!