Slashdot editors are anti-Microsoft? Sheesh, next thing you know they'll be telling me that Linux is some sort of superior operating system or something...
Use InnoDB tables instead of MyISAM tables and you can have foreign key contraints. Also, if you consider an application where data is only ever input through the web or some other front-end GUI, foreign key contrains aren't necessarily needed (I'll admit they're still good to have and use), because you can control the input through restricted UI elements like drop-downs, radio buttons, etc.
And MySQL 4.1 HAS been certified production-ready, for what that's worth.
Coding without subqueries is a pain though, you're absolutely right, although not a deal-breaker. We got by with temporary tables for a long time, and now we can use subqueries to do the same thing.
Views are on the 5.0 agenda I know, not so sure about synonyms, but I'll not try to argue that you can do everything with MySQL that you could with Postgres. I think what it boils down to is that very many of the common applications of MySQL out there simply do not NEED the extra functionality these tools provide, so it's a fine choice.
Funny. I got a phone in early December (also T-Mobile). The sales rep checked my number elegibility and started the transfer process. I called about 2 weeks later, they had a problem because they thought the number was from SPRINT, not SPRINT PCS (DUH!). So they fixed that and resubmitted the data, or so they said. Call back another 2 weeks later... Your request has been cancelled (this was appearently a good thing, because they had to cancel the old one before they could start the new one). Call back in ANOTHER 2 weeks. "It's being processed." Call back in another week (c'mon, it was being processed). "Your request has been cancelled."
Turns out my number was NOT elegible for transfer... my area, despite being home to a big 10 university, somehow eludes the infamous "top 100" cell phone markets. Honestly. So now I have an extra phone which I paid decent money for which will be 6+ months old by the time I get to use it for the first time.
I tested this in Moz 1.5 and it works fine up to 150 (I didn't try 175 or anything >150 and <200). Above that the left column text gets too big to fit in its current fixed-width box.
The solution to this is not to keep using table cells which can dynamically resize themselves, but to either use overflow: hidden, overflow: auto, or write an entirely new style sheet for those individuals with vision disabilities or those who simply prefer to read their text at a larger size for whatever reason.
It could incorporate high-constrast color schemes and add more spacing between sections to make it easier on the eye for those who might already be having trouble seeing. It could also get rid of the italics, which are hideous to read en masse, although okay now and then for emphasis, like the em tag suggests.
It would be easy to let users select their preferred style sheet and view the page using that, just storing the info alongside the 15,000/. preferences in another cookie. You could even let users specify an absolutely-qualified URL or local filepath (but this wouldn't migrate well) for their own custom stylesheet.
Maybe we could have a "design a/. style sheet" contest (give away some silly prize like a subscription)... the winners could become the set of "official" stylesheets available for users to choose from. Of course, the default can still be the simple green & white we all know and... well, let's not go too far.:)
It's inaccurate to call Farscape a miniseries. It was a regular tv show, running 4 seasons with 22 episodes in each. Perhaps the author was confused after reading the article (although that would seem to imply he read the article, which on/., seems unlikely...), that mentions that the new project will be a miniseries.
Even if it's just a miniseries, maybe they can bring some closure to the series, or at the very least the end of the last season. Of course, this thing could still be a long way off, and there's a lot that could go wrong, so I'm going to try not to get too excited too early.
It may also be possible to defeat this with a little creative CSS. It's a little-known but well-supported feature of CSS that you can give any object a background image. So create a for your ads, give them an id (something obscure, a number or something), and load a background image with the css for that div.
This will be a little harder if you need rotating banner ads that don't just pull from a common URL... you'll probably want to create the style for that div (or all the divs like that you have) in a seperate CSS file that gets attached in addition to your normal one. Using CGI, you can randomly select one of the extra CSS files to include, and it will load a different set of banners (or it will have randomly selected the same set) when each user comes to or reloads the page.
Lastly, you could always try embedding the images using <object> tags instead of <img>, which is not supported in XHTML 2.0 anyway, not that anyone's using that yet.:) Of course, many browsers don't support object right yet either, so that's probably a bad option.
You CAN do 2 audio streams in AVI, just like you CAN do VBR MP3 in AVI, but it's not a good idea. By default, most media players will render both audio streams simulatenously, which is not what you want, unless the user has a filter like Morgan's Stream Switcher installed or uses an advanced player like BSPlayer or ZoomPlayer.
Using VBR MP3 in AVI requires the well-known "Nandub hack" now available in a few other programs as well. AVI is NOT designed to handle VBR audio formats, and it's time to let the format die.
If you mux subtitles into an AVI, I don't know that you can, for instance, move them into the area of the display below the video when running fullscreen if you have a widescreen movie.
MKV (Matroska) and Ogg (they don't officially recognize OGM) are good options because they support multiple audio streams easily and their filters are designed for it. VBR isn't a problem either... try seeking in a file using MKV or OGM and you can see that the audio and video stay right in synch from the moment you jump. With AVI, you're usually waiting until the next keyframe for them to get it in step. Furthermore, when you do mix multiple languages (audio or subtitle), you can encode a description with them, so you know which track is which language, a nice bonus. Lastly, both formats have less overhead than AVI, about 5-8 MB in 90 minutes or so, I forget the exact numbers, but that's more space you can use for your video if encoding yourself.
Don't forget they're all backwards compatible too... it's easy to pull the streams OUT of an MKV into their component parts and mux them back into AVI if you want (but you will take up more space, and I've never heard of AVI with 3+ audio streams).
In the beginning, Stanford created the Google. And they saw that it was good. And there was text-based searching, and there was in-degree ranking, the first algorithms. On the second algorithm, Larry Page and Sergey Brin created the PageRank. And they saw that it was good. And there was text-based searching, and there was structure-based searching, the second algorithms....
Googlsis 1:1-2, New Internet Version
(Of course, this suggests that Stanford and/or Page & Brin is/are God, not Google itself, but let's not split hairs.)
Non Googlia est, ergo non est. (It doesn't exist in Google, therefore it doesn't exist.)
PageRank is a one-dimensional recursive weighting for a web page. Intially you assume all pages were created equal. Now for each page, compute an updated PageRank based on indegree (number of pages linking to the site). You usually also introduce a weighting factor which is designed to simulate some random chance that you "jump" to the next page by just typing a URL, not following a link. After that, you typically normalize the scores (sum of squares must equal one is the preferred norm).
Now you have to iterate, but on subsequent iterations, you're no longer consider with purely indegree. You care about the PageRank of pages linking to you. Pages that are "popular" and have high PageRank will boost your score. Typically you iterate until the values converge to within a given threshold. If you know linear algebra, you can also cheat and use eigenvalues, but that's not the point.
There are better algorithms, like Kleinberg's, which gives each page a "hub" and "authority" score, where just linking to a page isn't enough, and you can learn more about that in a Web Algorithms course.
So what you're saying is...
on
C
·
· Score: 1, Redundant
All in all, you'd give the book a grade about... "C"?:)
I read a good chunk of the posts and it seems that the main advantage of the iPod besides no SDMI is its firewire interface... are there any other players using firewire, or any supporting USB 2.0? I'm looking into getting one of these for Christmas, but I want to make sure I invest wisely.:)
After attending some wonderful lectures at today's Critical Issues Symposium at lovely Hope College, I heard the idea tossed around that Napster could move to a new business model, one where users pay a subscription fee per month for unlimited downloads. This money would then be distributed to artists on a basis of whose songs were downloaded. [This idea came from Dr. Marshall Van Alstyne (U. Mich).] I thought I'd throw that out here for discussion... I know I personally wouldn't mind something like that... we're talking roughly $5 a month for all the music your bandwidth can handle... and if you want to share with your roommates/housemates, you would be able to and save more money... seems like it could work.
"Recta non toleranda futuaris nisi irrisus ridebis"
Maybe it wasn't just a coincidence. Maybe this was actually a test of Hubble's new weapons system. Doesn't anyone else find it a little convenient that NASA "happened" to be looking in the right direction at the right time? Today, LINEAR, tomorrow, target practice in the Asteroid Belt. Just wait until Pluto blows up!
"Recta non toleranda futuaris nisi irrisus ridebis"
It would certainly have its problems, but in lieu of a system implemented directly into Napster, couldn't we setup a blacklist website, where users could post account names of people they downloaded "bugged" MP3z from. Other users could then look at the page and see if the people they're downloading from are on the blacklist. Or heck, it wouldn't take too much work to script up an e-bay style moderation system. Maybe put a hard cap at +50. We just need someone willing to host the site and then get the word out so Napster users without excessive bandwith can check the list out before wasting time downloading bugged MP3z.
"Recta non toleranda futuaris nisi irrisus ridebis"
I say Rob, Jeff, and the rest of the guys go get themselves scanned and make their skins publicy accessible. Especially Katz. Heck, you could charge for his skin and people would still get it. (Not that I don't like Katz...) Then anytime someone posts a story you don't like or you just randomly feel like fragging someone, just fire up Q3A, bust out the RL, and go for it!
It could include such options as: Natalie Portman Natalie Portman naked Natalie Portman naked and covered in hot grits a troll and... "We're sorry, CmdrTaco's girlfriend copyrighted her looks so they couldn't be reprinted on/." --Carl
I've been looking at way to link several smaller buildings with internal networks to a large network with the main servers and the T1 connections. Digging up streets, while fun and amusing, is extremely costly, so we thought we'd check out wireless. It's my understanding that you can a wired-to-wireless bridge, run a patch cable to it (connects to uplink port on a hub), stick it out on the roof (assuming it's an outdoor model), add an antenna if needed and then do the same thing on the other side and you're good to go. These would primarily be M$ Win9x machines, but we would prefer an interplatform solution. Does anyone know for sure that that works, and if so, what products have you used?
Lucas did an interview on Entertainment Tonight where viewers could submit questions and the most popular/best ones got picked to be asked (hey, that sounds vaguely familiar). He said then that he would not release the videos on DVD until he had finished ALL the prequels. So, if we aren't all ready to lynch Lucas and if DVD hasn't grown obsolete by 2005 or 2006, maybe then we can buy them.
Maybe.
"Futuaris nisi irrisus ridebis" --Carlton in Eric Idle's The Road to Mars
Slashdot Mirror
Slashdot editors are anti-Microsoft? Sheesh, next thing you know they'll be telling me that Linux is some sort of superior operating system or something...
uhm you see Harry Potter is a fictional character Oh sure just burst my bubble! :( What next, you'll tell me that CowboyNeal isn't real either?
Use InnoDB tables instead of MyISAM tables and you can have foreign key contraints. Also, if you consider an application where data is only ever input through the web or some other front-end GUI, foreign key contrains aren't necessarily needed (I'll admit they're still good to have and use), because you can control the input through restricted UI elements like drop-downs, radio buttons, etc.
And MySQL 4.1 HAS been certified production-ready, for what that's worth.
Coding without subqueries is a pain though, you're absolutely right, although not a deal-breaker. We got by with temporary tables for a long time, and now we can use subqueries to do the same thing.
Views are on the 5.0 agenda I know, not so sure about synonyms, but I'll not try to argue that you can do everything with MySQL that you could with Postgres. I think what it boils down to is that very many of the common applications of MySQL out there simply do not NEED the extra functionality these tools provide, so it's a fine choice.
You don't understand--I went to school with him--he's not joking.
Funny. I got a phone in early December (also T-Mobile). The sales rep checked my number elegibility and started the transfer process. I called about 2 weeks later, they had a problem because they thought the number was from SPRINT, not SPRINT PCS (DUH!). So they fixed that and resubmitted the data, or so they said. Call back another 2 weeks later... Your request has been cancelled (this was appearently a good thing, because they had to cancel the old one before they could start the new one). Call back in ANOTHER 2 weeks. "It's being processed." Call back in another week (c'mon, it was being processed). "Your request has been cancelled."
Turns out my number was NOT elegible for transfer... my area, despite being home to a big 10 university, somehow eludes the infamous "top 100" cell phone markets. Honestly. So now I have an extra phone which I paid decent money for which will be 6+ months old by the time I get to use it for the first time.
I tested this in Moz 1.5 and it works fine up to 150 (I didn't try 175 or anything >150 and <200). Above that the left column text gets too big to fit in its current fixed-width box.
The solution to this is not to keep using table cells which can dynamically resize themselves, but to either use overflow: hidden, overflow: auto, or write an entirely new style sheet for those individuals with vision disabilities or those who simply prefer to read their text at a larger size for whatever reason.
It could incorporate high-constrast color schemes and add more spacing between sections to make it easier on the eye for those who might already be having trouble seeing. It could also get rid of the italics, which are hideous to read en masse, although okay now and then for emphasis, like the em tag suggests.
It would be easy to let users select their preferred style sheet and view the page using that, just storing the info alongside the 15,000 /. preferences in another cookie. You could even let users specify an absolutely-qualified URL or local filepath (but this wouldn't migrate well) for their own custom stylesheet.
Maybe we could have a "design a /. style sheet" contest (give away some silly prize like a subscription)... the winners could become the set of "official" stylesheets available for users to choose from. Of course, the default can still be the simple green & white we all know and... well, let's not go too far. :)
It's inaccurate to call Farscape a miniseries. It was a regular tv show, running 4 seasons with 22 episodes in each. Perhaps the author was confused after reading the article (although that would seem to imply he read the article, which on /., seems unlikely...), that mentions that the new project will be a miniseries.
Even if it's just a miniseries, maybe they can bring some closure to the series, or at the very least the end of the last season. Of course, this thing could still be a long way off, and there's a lot that could go wrong, so I'm going to try not to get too excited too early.
It may also be possible to defeat this with a little creative CSS. It's a little-known but well-supported feature of CSS that you can give any object a background image. So create a for your ads, give them an id (something obscure, a number or something), and load a background image with the css for that div.
:) Of course, many browsers don't support object right yet either, so that's probably a bad option.
This will be a little harder if you need rotating banner ads that don't just pull from a common URL... you'll probably want to create the style for that div (or all the divs like that you have) in a seperate CSS file that gets attached in addition to your normal one. Using CGI, you can randomly select one of the extra CSS files to include, and it will load a different set of banners (or it will have randomly selected the same set) when each user comes to or reloads the page.
Lastly, you could always try embedding the images using <object> tags instead of <img>, which is not supported in XHTML 2.0 anyway, not that anyone's using that yet.
(Not a comprehensive list ;)
You CAN do 2 audio streams in AVI, just like you CAN do VBR MP3 in AVI, but it's not a good idea. By default, most media players will render both audio streams simulatenously, which is not what you want, unless the user has a filter like Morgan's Stream Switcher installed or uses an advanced player like BSPlayer or ZoomPlayer.
Using VBR MP3 in AVI requires the well-known "Nandub hack" now available in a few other programs as well. AVI is NOT designed to handle VBR audio formats, and it's time to let the format die.
If you mux subtitles into an AVI, I don't know that you can, for instance, move them into the area of the display below the video when running fullscreen if you have a widescreen movie.
MKV (Matroska) and Ogg (they don't officially recognize OGM) are good options because they support multiple audio streams easily and their filters are designed for it. VBR isn't a problem either... try seeking in a file using MKV or OGM and you can see that the audio and video stay right in synch from the moment you jump. With AVI, you're usually waiting until the next keyframe for them to get it in step. Furthermore, when you do mix multiple languages (audio or subtitle), you can encode a description with them, so you know which track is which language, a nice bonus. Lastly, both formats have less overhead than AVI, about 5-8 MB in 90 minutes or so, I forget the exact numbers, but that's more space you can use for your video if encoding yourself.
Don't forget they're all backwards compatible too... it's easy to pull the streams OUT of an MKV into their component parts and mux them back into AVI if you want (but you will take up more space, and I've never heard of AVI with 3+ audio streams).
In the beginning, Stanford created the Google. And they saw that it was good. And there was text-based searching, and there was in-degree ranking, the first algorithms. On the second algorithm, Larry Page and Sergey Brin created the PageRank. And they saw that it was good. And there was text-based searching, and there was structure-based searching, the second algorithms....
Googlsis 1:1-2, New Internet Version
(Of course, this suggests that Stanford and/or Page & Brin is/are God, not Google itself, but let's not split hairs.)
Non Googlia est, ergo non est. (It doesn't exist in Google, therefore it doesn't exist.)
PageRank is a one-dimensional recursive weighting for a web page. Intially you assume all pages were created equal. Now for each page, compute an updated PageRank based on indegree (number of pages linking to the site). You usually also introduce a weighting factor which is designed to simulate some random chance that you "jump" to the next page by just typing a URL, not following a link. After that, you typically normalize the scores (sum of squares must equal one is the preferred norm).
Now you have to iterate, but on subsequent iterations, you're no longer consider with purely indegree. You care about the PageRank of pages linking to you. Pages that are "popular" and have high PageRank will boost your score. Typically you iterate until the values converge to within a given threshold. If you know linear algebra, you can also cheat and use eigenvalues, but that's not the point.
There are better algorithms, like Kleinberg's, which gives each page a "hub" and "authority" score, where just linking to a page isn't enough, and you can learn more about that in a Web Algorithms course.
All in all, you'd give the book a grade about... "C"? :)
I read a good chunk of the posts and it seems that the main advantage of the iPod besides no SDMI is its firewire interface... are there any other players using firewire, or any supporting USB 2.0? I'm looking into getting one of these for Christmas, but I want to make sure I invest wisely. :)
http://www.msnbc.com/m/lv/default.asp?0cv=c642
"Recta non toleranda futuaris nisi irrisus ridebis"
"Recta non toleranda futuaris nisi irrisus ridebis"
"Recta non toleranda futuaris nisi irrisus ridebis"
"Recta non toleranda futuaris nisi irrisus ridebis"
"Recta non toleranda futuaris nisi irrisus ridebis"
"Futuaris nisi irrisus ridebis"
"Futuaris nisi irrisus ridebis"
"Futuaris nisi irrisus ridebis"
"Futuaris nisi irrisus ridebis"
Maybe.
"Futuaris nisi irrisus ridebis"
--Carlton in Eric Idle's The Road to Mars
"Futuaris nisi irrisus ridebis"