Not to mention the cost of pulling all those consultants in, overnight, on a weekend...
Also, only the electrical equipment (and structural stuff) was damaged - networking and customer servers are intact (but without power, obviously).
AppEngine lets you use regular HTML. You can ignore the template system entirely and code in traditional CGI style if you really want to. You probably don't/want/ to, but you/can/...
Both Amazon's SimpleDB and Google's 'GQL' query language have limitations placed to improve scalability - eg, no table joins, only one column used in a range query. The idea is to force the user into a schema that will scale well.
Of course, you can always implement joins at the app level, etc, but you'll always be able to shoot yourself in the foot in any system.
They've actually released an open-source (Apache-2) reference implementation of the APIs - right there in the SDK. It's not a very/efficient/ implementation, but if anyone wants to hack on it to make it usable, it's right there.
Google has stated that additional languages are in the works - they've done release partially to get feedback on what to focus on next. Probably the main issue would be porting over the google library bindings, and sandboxing the language in question.
The only caveat I see would be the datastore, which is not a relational database supporting SQL, but I'd have to see how good it is. At least it supports transactions, which are the single most difficult feature to implement in your own storage system.
Note that transactions are semi-limited - you have to loosely partition your data into smallish chunks, and any given transaction can only act within one chunk. (There's no performance penalty to having/too small/ chunks, and indeed the default is to put each row in its own chunk. But if chunks are too large performance will suffer)
Presumably they're only implementing transactions as a local-to-database-replica thing; none of that fancy two-phase commit stuff.
The SDK isn't designed for any degree of efficiency - heck, all queries are a linear search over all entries in the database. Additionally, if you're using google's auth system, well, you'll be stuck. (You have the option of rolling your own of course)
That said, the SDK is all under the apache license, so you could always dig in and optimize it to work well enough. In particular, the query syntax is very similar to SQL (actually, it's a subset of the syntax of SQL), so you could probably toss it onto a mysql server or something... assuming you've not grown to the part where you/need/ the scaling.
The question isn't how much money SCO owes; it's how much of the money in SCO's bank account actually belongs to Novell. This is an important difference, as it lets Novell skip to the head of the line, before all the other creditors (and there are quite a few of those...)
It's not that they go down particularly often, but if there is a hardware failure, amazon generally will not take heroic efforts to recover your data - your instance is terminated, hope you had a backup. Sometimes they'll try to reboot it temporarily, but they won't put the drives in another machine or anything like that. So make sure your app can recover from a complete and permanent server failure, with total data loss on that server.
Also, previously, there was the IP problem, and also you couldn't ensure your instances were hosted at different locations. With these new changes, you could have a backup instance sitting at an independent datacenter, and move your IP over in a matter of minutes (possibly less; it seems to take longer when you're actively watching how long it takes to move, based on my testing)
It's not unprecedented - the first was (controversial) the proof of the four-color theorem. Even today no non-exhaustive method is known to prove the four-color theorem.
Bioshock is, in fact, sold over Steam. However, they added their own layer of copy protection in addition to steam's as well. Had it been pure steam I might have even bought it.
There are two seperate APIs here. The one you're looking at is the public one, and the one that mozilla is using - you add a preference entry to your program's plist. WebKit however, made a call to an undocumented function to disable it at runtime; they did this because otherwise programs/embedding/ webkit, where they do not have access to the plist, would suffer performance regressions otherwise. And they plan to remove it once the root cause of the performance issues is fixed (the call disables deferred updates for the entire program that uses webkit, not just webkit itself)
That's not for transferring copyright interest; it's for waiving it before it's created. In other words, if you're going to create Gnomovision, but you're worried your employer might try to claim it, get them to sign that form. If you already created it for them, and they own the copyright, you'll need something else.
Read TFA. Ray tracing does NOT happen on the graphics card; it happens on your CPU. And they've got Quake 4 at 1280x running at 90 FPS raytraced already. Since raytracing scales almost linearly, as you add more cores to your CPU (which is likely the future direction of CPU technology improvement), you improve raytracing performance by about the same factor.
There is already a microcode loader for Intel chips. If you load bad microware, you run the risk of hosing the chip, or at least crashing, but that's your choice.
The NDA can be likely be enforced; what happens is Red Hat has no legal right to distribute the kernel under those conditions. If it does, it's just plain copyright infringement.
IANAL, etc.
However, the change/is/ being distributed - from red hat to the customers under NDA. Even showing code to contractors can be considered distribution (this is one of the things the GPLv3 addresses, but of course Linux is under v2)
Slashdot Mirror
Not to mention the cost of pulling all those consultants in, overnight, on a weekend... Also, only the electrical equipment (and structural stuff) was damaged - networking and customer servers are intact (but without power, obviously).
By being uploaded to youtube, was it not fixed in a tangible medium?
The link from RU's frontpage seems to be broken - anyone have a mirror?
It *is* a dev board. The whole thing is a PCIe riser card, so you can upload firmware from the host machine etc.
Actually, they don't - that page was based on rumor and/or speculation; there's no actual google hosting at the moment: http://meta.wikimedia.org/wiki/Google_hosting
AppEngine lets you use regular HTML. You can ignore the template system entirely and code in traditional CGI style if you really want to. You probably don't /want/ to, but you /can/...
Both Amazon's SimpleDB and Google's 'GQL' query language have limitations placed to improve scalability - eg, no table joins, only one column used in a range query. The idea is to force the user into a schema that will scale well. Of course, you can always implement joins at the app level, etc, but you'll always be able to shoot yourself in the foot in any system.
They've actually released an open-source (Apache-2) reference implementation of the APIs - right there in the SDK. It's not a very /efficient/ implementation, but if anyone wants to hack on it to make it usable, it's right there.
Google has stated that additional languages are in the works - they've done release partially to get feedback on what to focus on next. Probably the main issue would be porting over the google library bindings, and sandboxing the language in question.
The SDK isn't designed for any degree of efficiency - heck, all queries are a linear search over all entries in the database. Additionally, if you're using google's auth system, well, you'll be stuck. (You have the option of rolling your own of course)
/need/ the scaling.
That said, the SDK is all under the apache license, so you could always dig in and optimize it to work well enough. In particular, the query syntax is very similar to SQL (actually, it's a subset of the syntax of SQL), so you could probably toss it onto a mysql server or something... assuming you've not grown to the part where you
Fortunately, checks don't ask for any of those.
The question isn't how much money SCO owes; it's how much of the money in SCO's bank account actually belongs to Novell. This is an important difference, as it lets Novell skip to the head of the line, before all the other creditors (and there are quite a few of those...)
It's not that they go down particularly often, but if there is a hardware failure, amazon generally will not take heroic efforts to recover your data - your instance is terminated, hope you had a backup. Sometimes they'll try to reboot it temporarily, but they won't put the drives in another machine or anything like that. So make sure your app can recover from a complete and permanent server failure, with total data loss on that server. Also, previously, there was the IP problem, and also you couldn't ensure your instances were hosted at different locations. With these new changes, you could have a backup instance sitting at an independent datacenter, and move your IP over in a matter of minutes (possibly less; it seems to take longer when you're actively watching how long it takes to move, based on my testing)
It's not unprecedented - the first was (controversial) the proof of the four-color theorem. Even today no non-exhaustive method is known to prove the four-color theorem.
Bioshock is, in fact, sold over Steam. However, they added their own layer of copy protection in addition to steam's as well. Had it been pure steam I might have even bought it.
They wouldn't dare admit it, for fear of being held liable for it as legal advice.
There are two seperate APIs here. The one you're looking at is the public one, and the one that mozilla is using - you add a preference entry to your program's plist. WebKit however, made a call to an undocumented function to disable it at runtime; they did this because otherwise programs /embedding/ webkit, where they do not have access to the plist, would suffer performance regressions otherwise. And they plan to remove it once the root cause of the performance issues is fixed (the call disables deferred updates for the entire program that uses webkit, not just webkit itself)
That's not for transferring copyright interest; it's for waiving it before it's created. In other words, if you're going to create Gnomovision, but you're worried your employer might try to claim it, get them to sign that form. If you already created it for them, and they own the copyright, you'll need something else.
Read TFA. Ray tracing does NOT happen on the graphics card; it happens on your CPU. And they've got Quake 4 at 1280x running at 90 FPS raytraced already. Since raytracing scales almost linearly, as you add more cores to your CPU (which is likely the future direction of CPU technology improvement), you improve raytracing performance by about the same factor.
When I go to that link with the bugmenot login, I get:
Not Found: Forum Not Found
The forum you requested does not exist.
Was the article deleted?
There is already a microcode loader for Intel chips. If you load bad microware, you run the risk of hosing the chip, or at least crashing, but that's your choice.
The NDA can be likely be enforced; what happens is Red Hat has no legal right to distribute the kernel under those conditions. If it does, it's just plain copyright infringement. IANAL, etc.
However, the change /is/ being distributed - from red hat to the customers under NDA. Even showing code to contractors can be considered distribution (this is one of the things the GPLv3 addresses, but of course Linux is under v2)
The Japanese dub of south park is surprisingly good, actually. Then again the Japanese dub of the simpsons is horrible, so there you go.