Texting is great for either messages that require no response ("I'll be in the pub from 6, feel free to join me", "It's 's birthday on Friday, thought you might want a reminder", "Arrrghh I hate Mondays/my boss/computers/the weather", etc.), or where a response is not time critical, and likely to be delayed ("Can you tell me ", "Are you free next week sometime"), this sort of thing.
In particular, you don't have to interrupt the other person to get your message across. I may notice a message arriving, and read it at the time, or I may leave it until I'm less busy, or more frequently I'll just not notice for a few hours. On the other hand, if someone calls me, I have to stop what I'm doing, respond to them, then go back to what I'm doing.
Except, this isn't at the "Brightest and smartest" level. This is basic caching. If this was a discussion of the relative merits of linked lists vs doubly linked lists vs hash maps for various different data types, and read/write patterns, we can start thinking best and brightest.
If it went into a discussion on how to store your data in memory so that the data the application is looking for is probably in the processor cache, we can definitely talk best and brightest.
Usefully, with the <object> tag, you can specify alternative objects to render. So you can provide a SVG, and a PNG to render instead, then a GIF to render instead, then a plaintext alternative.
Personally, I find the interface much easier to work with than Linux (and don't even start me on Windows), and the software does indeed "Just work". I still use Linux for servers, where performance is an issue (and therefore we want as much speed for our money as we can get), and much of the software we use server-side is written for Linux, meaning OS X ports can be a little flakey. However, for my desktop, I don't need any serious speed from the system, so a Mac is fine.
Frankly, I doubt this is useful to more than a tiny fraction of/.'ers. My impression is that most of us run Linux or OS X for our desktop/server systems, and only use Windows for games. Okay, a reasonable number of/.'ers will have to use Windows desktops at work, but how many of those actually run memory intensive applications that are too slow currently?
When they games start coming as standard as dual format AMD64/x86, I'll think about switching. In the meantime, don't care (and if more games start getting released on the Mac, I'll just ditch the PC anyway, frankly).
Odd, I can't understand why the FBI warning has to be no-skip. We're not going to decide to read it becase it can't be skipped, we're going to go make coffee instead.
On the subject of which, does anyone know any DVD players that always leave the fast forward button enabled?
Probably a little late to appease the mods, but the most significant issues we've had with IE for Windows (copied out of our FAQ they're so frequently an issue):
Filename supplied when uploading a file includes the full path of the file, and is incorrected escaped (does not conform to RFC 2045 and RFC 2183).
MIME data sent when uploading a file sometimes doesn't conform to multipart/form-data MIME type (HTML 4.01, section 17.13.4).
>I'm not saying IE is bad, do not get me wrong. As a web application developer that's fed up with having to work around IE-ism (particularly the Mac version, but also problems with file uploads in the Windows version), I'll say it's bad:)
...is to find a components and systems supplier you like, and see what they build their systems from. Admittadely, you're more likely to get stable components than blisteringly fast/overclockable, but that's fine for me. So far I've had very good experiences with pretty much duplicating the systems I've seen offered for sale (generally changing only a few components to versions I prefer).
Or more to the point, they're probably someone who feels reasonably confident that, if they want to get laid, they can do in the short to medium term. If someone is a lot less sure when (or if) they'll get another off, I think they're a helluva lot less likely to be in any way picky.
Losing track of my point here. Mostly, I think people who do have something resembling a regular/normal sex life might not realise just how desperate a small but vocal minority of/. users get.
I'm giving up now, taking the karma bonus off, and hoping this isn't too much babblage.
THIS IS NOT INFORMATIVE. It is INTERESTING. If the poster had supplied supporting evidence at all, it would have been a start towards informative.
As it is:
1. Which tutorial was it? 2. Was the problem a fundamental problem with Ruby on Rails, or the tutorial itself. 3. If it was a problem with Ruby on Rails, can it be fixed?
Actually, if I remember correctly (and really can't be bothered trawling through UK copyright law right now, so sorry for lack of a link), the UK's copyright laws don't have an provision for copying for personal use. Doing a very quick search, this seems to have a good summary:
Yikes. Err, okay, last time I checked, recordable optical media really wasn't so great for longevity. It depends on the dyes used, but if you're just using basic off the shelf CD-Rs, stop, and go find out how long they'll last.
Disagree. Blank media that holds data for a year or so is fine for almost everything I want. For archival purposes I'd like something a lot better, and am willing to pay for it, but for burning Linux install CDs, or just moving data between remote machines, basic cheap CD-Rs do the job just fine.
For anything I buy (CDs of music, DVDs with games/videos on, etc.), I expect much better. If we're not talking over a decade at least, I'm not impressed.
This is a very good point; people think they want stable, secure software. They don't, what they actually want is cheapish (but expensive enough that it must be good) software that does what they need, plus plenty of things they think they might want to do another day, which is reasonably easy to use. A feeling that they're using the same software as everyone else (and several million people can't be wrong, right?) never hurts.
Had something similar myself once; someone at work's harddrive stopped working. IT service said it was dead, nothing they could do, so I picked it up and plugged it into a spare computer. It worked okay, turned out what had happened was the partition table had been fried. Which Knoppix fix, yay Knoppix:)
While downloadable TV shows are a good start, I'm not so much interested in watching these more than once. As such, I'd rather pay less, and only be able to watch it once or twice, or maybe only for 24 hours after I first start playing or something similar.
This means I can download the TV shows I want to watch, and watch them on my schedule, without having to pay for the abililty to watch something over and over again, that I won't want to. This also side-steps issues like losing the file, or the company whose DRM it is going out of business, as I won't have the file long enough for it to be a problem.
It's rare, but unless the thief has a sample of your normal handwriting style, how are they to know how your normally write 9s. All you have to do is write all the numbers except the 9, turn the piece of paper upside down, and write a 6:)
Also 3/8 (but takes a little work), and 0, 6 and 9 can look alike. With a lot of work, you can make 2s look like 5 the other way up. Haven't found anything you can do with 4 or 7 yet...
On the PIN number thing, I'm tempted to put a small slip of paper in my wallet, with "0619" written on it. Anyone stealing the wallet may well try it is my PIN, and it won't work. So they turn it upside down (becomes "6190"), and it still doesn't work. If I'm really lucky, they turn it back the other way, try one more time, and the card is now locked.
Slashdot Mirror
Do I, like, have the entire of /.'s quota of lesbians? I'm surrounded by them, and everyone else seems to never meet any. Weird stuff.
Texting is great for either messages that require no response ("I'll be in the pub from 6, feel free to join me", "It's 's birthday on Friday, thought you might want a reminder", "Arrrghh I hate Mondays/my boss/computers/the weather", etc.), or where a response is not time critical, and likely to be delayed ("Can you tell me ", "Are you free next week sometime"), this sort of thing.
In particular, you don't have to interrupt the other person to get your message across. I may notice a message arriving, and read it at the time, or I may leave it until I'm less busy, or more frequently I'll just not notice for a few hours. On the other hand, if someone calls me, I have to stop what I'm doing, respond to them, then go back to what I'm doing.
Except, this isn't at the "Brightest and smartest" level. This is basic caching. If this was a discussion of the relative merits of linked lists vs doubly linked lists vs hash maps for various different data types, and read/write patterns, we can start thinking best and brightest.
If it went into a discussion on how to store your data in memory so that the data the application is looking for is probably in the processor cache, we can definitely talk best and brightest.
Simple caching, however, is basic stuff.
Usefully, with the <object> tag, you can specify alternative objects to render. So you can provide a SVG, and a PNG to render instead, then a GIF to render instead, then a plaintext alternative.
Personally, I find the interface much easier to work with than Linux (and don't even start me on Windows), and the software does indeed "Just work". I still use Linux for servers, where performance is an issue (and therefore we want as much speed for our money as we can get), and much of the software we use server-side is written for Linux, meaning OS X ports can be a little flakey. However, for my desktop, I don't need any serious speed from the system, so a Mac is fine.
Frankly, I doubt this is useful to more than a tiny fraction of /.'ers. My impression is that most of us run Linux or OS X for our desktop/server systems, and only use Windows for games. Okay, a reasonable number of /.'ers will have to use Windows desktops at work, but how many of those actually run memory intensive applications that are too slow currently?
When they games start coming as standard as dual format AMD64/x86, I'll think about switching. In the meantime, don't care (and if more games start getting released on the Mac, I'll just ditch the PC anyway, frankly).
Dang, 'cos I was thinking I must be a genius by now :)
Odd, I can't understand why the FBI warning has to be no-skip. We're not going to decide to read it becase it can't be skipped, we're going to go make coffee instead.
On the subject of which, does anyone know any DVD players that always leave the fast forward button enabled?
We're coding to a specific user base, some of who are a little stuck on MacIE. We're prying them away from it, but it's taking a while.
Don't tell anyone, but apparently it's not the most secure thing ever: http://apache.dataloss.nl/~fred/www.nunce.org/hdcp /hdcp111901.htm
Just a quick quote from that paper:
"HDCP's linear key exchange is a fundamental weaknesses. We can:
Probably a little late to appease the mods, but the most significant issues we've had with IE for Windows (copied out of our FAQ they're so frequently an issue):
Filename supplied when uploading a file includes the full path of the file, and is incorrected escaped (does not conform to RFC 2045 and RFC 2183).
MIME data sent when uploading a file sometimes doesn't conform to multipart/form-data MIME type (HTML 4.01, section 17.13.4).
>I'm not saying IE is bad, do not get me wrong. :)
As a web application developer that's fed up with having to work around IE-ism (particularly the Mac version, but also problems with file uploads in the Windows version), I'll say it's bad
...is to find a components and systems supplier you like, and see what they build their systems from. Admittadely, you're more likely to get stable components than blisteringly fast/overclockable, but that's fine for me. So far I've had very good experiences with pretty much duplicating the systems I've seen offered for sale (generally changing only a few components to versions I prefer).
Or more to the point, they're probably someone who feels reasonably confident that, if they want to get laid, they can do in the short to medium term. If someone is a lot less sure when (or if) they'll get another off, I think they're a helluva lot less likely to be in any way picky.
/. users get.
Losing track of my point here. Mostly, I think people who do have something resembling a regular/normal sex life might not realise just how desperate a small but vocal minority of
I'm giving up now, taking the karma bonus off, and hoping this isn't too much babblage.
Seriously, no matter how horny you are, you wouldn't simply jump on bed with anybody, would you? :)
Yes is so much the wrong answer, isn't it?
Dear Moderators,
THIS IS NOT INFORMATIVE. It is INTERESTING. If the poster had supplied supporting evidence at all, it would have been a start towards informative.
As it is:
1. Which tutorial was it?
2. Was the problem a fundamental problem with Ruby on Rails, or the tutorial itself.
3. If it was a problem with Ruby on Rails, can it be fixed?
Actually, if I remember correctly (and really can't be bothered trawling through UK copyright law right now, so sorry for lack of a link), the UK's copyright laws don't have an provision for copying for personal use. Doing a very quick search, this seems to have a good summary:
i ght.htm
http://www.patent.gov.uk/copy/indetail/usingcopyr
See "But if I've bought something, can't I use it however I like?" specifically.
Sucks, doesn't it.
Yikes. Err, okay, last time I checked, recordable optical media really wasn't so great for longevity. It depends on the dyes used, but if you're just using basic off the shelf CD-Rs, stop, and go find out how long they'll last.
Googled for articles, and found:
Care and Handling of CDs and DVDs
Measures of CD-R Longevity
The first in particular goes into a lot of detail, and references of lot of articles which may make good further reading.
Disagree. Blank media that holds data for a year or so is fine for almost everything I want. For archival purposes I'd like something a lot better, and am willing to pay for it, but for burning Linux install CDs, or just moving data between remote machines, basic cheap CD-Rs do the job just fine.
For anything I buy (CDs of music, DVDs with games/videos on, etc.), I expect much better. If we're not talking over a decade at least, I'm not impressed.
This is a very good point; people think they want stable, secure software. They don't, what they actually want is cheapish (but expensive enough that it must be good) software that does what they need, plus plenty of things they think they might want to do another day, which is reasonably easy to use. A feeling that they're using the same software as everyone else (and several million people can't be wrong, right?) never hurts.
Had something similar myself once; someone at work's harddrive stopped working. IT service said it was dead, nothing they could do, so I picked it up and plugged it into a spare computer. It worked okay, turned out what had happened was the partition table had been fried. Which Knoppix fix, yay Knoppix :)
While downloadable TV shows are a good start, I'm not so much interested in watching these more than once. As such, I'd rather pay less, and only be able to watch it once or twice, or maybe only for 24 hours after I first start playing or something similar.
This means I can download the TV shows I want to watch, and watch them on my schedule, without having to pay for the abililty to watch something over and over again, that I won't want to. This also side-steps issues like losing the file, or the company whose DRM it is going out of business, as I won't have the file long enough for it to be a problem.
It's rare, but unless the thief has a sample of your normal handwriting style, how are they to know how your normally write 9s. All you have to do is write all the numbers except the 9, turn the piece of paper upside down, and write a 6 :)
Also 3/8 (but takes a little work), and 0, 6 and 9 can look alike. With a lot of work, you can make 2s look like 5 the other way up. Haven't found anything you can do with 4 or 7 yet...
On the PIN number thing, I'm tempted to put a small slip of paper in my wallet, with "0619" written on it. Anyone stealing the wallet may well try it is my PIN, and it won't work. So they turn it upside down (becomes "6190"), and it still doesn't work. If I'm really lucky, they turn it back the other way, try one more time, and the card is now locked.