I did it once too, back in the early '90s. I was working on an adware program for Buick, so I used Eras as the font in my IDE (FYI, I was using a Mac, I think the PC guys were using Turbo Pascal) and it worked out real well.
But I prefer monospaced fonts because you can't save your font and tab stop preferences in a plain-text ASCII file, and you don't want your text to look like a complete mess when someone else looks at it. You can only use hard tabs, and 8 spaces is just too wide for most programming.
One thing's for sure... I wish I could type this message that I'm typing right now in a proportional font. Monospaced is horrible for non-code text. But the standard text input area for HTML is monospaced. Slashdot really needs an option for an "advanced editor".
I'm all fine with this as long as nobody named Saxon is in charge of the project.
What about prescription lens wearers?
on
Hot Or Not — 3D TV
·
· Score: 1
I may be one of the few here not to have gone out to see that movie with the blue people yet, so I don't have actual experience, but how well do the various 3D glasses work for us myopics who need prescription lenses to see the screen as something other than a blurry blob? Can they be worn without being completely uncomfortable?
Back in the '90s, there were a couple of times when a store's credit card dialup was not working, and they had to pull out the trusty old Addressograph and get an imprint on carbon paper. The hard part was for them to find the thing.
Apple did exacly this back in what, the late '90s? Double float time not only means no Y2038 problem, but you can represent a date/time with sub-second accuracy, and math to compute delta times can be done with only one potential scaling round-off at the end when adding to a real time. Representing dates in the (very) far past or future simply loses the sub-second precision.
The only reason it wasn't done sooner was probably because for so long floating point hardware was an expensive option, and software float would have been too slow. Also, before IEEE, there really wasn't a standard format.
The bad news is that your patents will have expired by then. The good news is that the Y10K bug means that your patents will un-expire. So get your head jar ready, because you're gonna be RICH!
What? I looked at someone else's link showing the SMS data format, and it is quite clear and consistent. Dates are six nibbles of BCD, with the low nibble coming first in both the date and phone number. The year is in exactly the same format as the month and day: two BCD digits. It's not their fault that so many programmers were morons and couldn't comprehend to process the year (before adding the century) in exactly the same way as the month and day.
As for "lessons learned from Y2K", this is not a situation where you are keeping old data for years and years, nor are you doing date arithmetic or sorting of 50+ years range, not even ten years. Nobody's birthdate will be in the timestamp of an SMS message, nor will the expiration date of their credit card. As a timestamp, the century is explicitly implied* by context, the context being that of the calendar that's hanging on the wall of your cubicle.
If someone were to make a database with years of SMS messages and not include the century as messages were added to the database, then yes, that would be a problem. But it would not be a problem with the SMS message format. When the year 2100 rolls around, and assuming we're even still using SMS, the worst that would happen is "hundred year old" text messages. At least then the low two digits would still be right, unlike the current "2016" stupidity.
They're doing YEAR = BCDYEAR + 2000... hooray for clueless programmers!
What makes it stupider is that with SMS they have to swap the nibbles first... and decode the other fields as BCD too.
And this is clearly a client-only bug, so dozens of codebases will have to be fixed and millions of devices updated. The typical lifetime of a cellphone means that the broken ones may simply get trashed rather than go through the trouble of an update.
As I recall from knowing a couple of people in the Star Trek fanzine community back in the '80s, Star Trek is a special case as far as fanfics go. It seems that Desilu didn't register the copyrights properly for the first season, so fanfics without Chekov are fair game. Or at least that's how they explained it to me.
Of course what you have linked to includes Chekov, so they couldn't use that excuse.
Even the Macintosh started out with a FAT-like file system, called MFS. I've seen what it was like when you tried to use it on a hard drive with 5 megabyte partitions, and it was not pretty.
But Apple didn't just sit on it, and had HFS ready when they released the 800K floppy drive. HFS needed one major change (with MacOS 8.1) to support hard drives larger than 2 gigabytes (and more than 65536 allocation blocks per volume, also a big problem), and HFS+ has stuck around since then, though it has received a LOT of backward-compatible extensions in OS X, including journaling.
I can't believe that MacOS X doesn't have native EXT2/3 support
Blame the GPL license. Most of OS X is under a BSD-style license. Is there even a BSD-licensed EXT2/3 implementation?
There is a pre-built version that you can download and install yourself, however.
Also, the only people who need it are the 2% who use Linux. 2% of 5% isn't much, especially when OS X users have much less need to keep Linux around than Windows users.
And we OS X users already have a very nice filesystem, thank you very much. Apple did add an amazing number of hacks to it so that it can do Unix-y things like inodes and hard links, but it works very well. It can even be made case sensitive should we ever want to compile Linux. (A million curses on whoever required case sensitive filenames in the netfilter code.)
Yo dawg, I heard you like links, so I put some links in your links so you can link your links.
Anyhow, this manual's existence just goes to show that information really does want to be free. Or at least wants to go from classified document to $10.99 a copy.
...unless you're using 10^12 = one billion and 10^9 = one milliard
In any case, it should be an integer number of pennies (or whatever they call the euro-cents), so you're going to have to keep your account under 184 quadrillion, or is that 184 billiard? (balls!)
This sort of shellcode is probably a bit harder to write for the 68000, with its 16-bit instructions that have an "operand mode" field that spans between the two bytes. While a lot of useful instructions are in the 2xxx-7xxx range, and branches are in the 6xxx range, the instructions that do any sort of math are outside it.
It would be interesting to see what can be done with other CPUs as well. In particular, I recall that OS X PPC missed a chance to resist shellcode by ignoring two of the four bytes of the OS trap instruction, rather than forcing them to be nulls.
Except that by political measurements, "Carbon Footprint" (aka CO2 levels) is not just important, it's one of the most important causes of global warming, and we're so far in a hole that we have to put on the emergency brakes NOW. And that is one of the things that the AGW skeptics have a problem with.
Slashdot Mirror
I did it once too, back in the early '90s. I was working on an adware program for Buick, so I used Eras as the font in my IDE (FYI, I was using a Mac, I think the PC guys were using Turbo Pascal) and it worked out real well.
But I prefer monospaced fonts because you can't save your font and tab stop preferences in a plain-text ASCII file, and you don't want your text to look like a complete mess when someone else looks at it. You can only use hard tabs, and 8 spaces is just too wide for most programming.
One thing's for sure... I wish I could type this message that I'm typing right now in a proportional font. Monospaced is horrible for non-code text. But the standard text input area for HTML is monospaced. Slashdot really needs an option for an "advanced editor".
You must be new around here. We've been having anti-administration flamebait for at least eight years so far.
I'm all fine with this as long as nobody named Saxon is in charge of the project.
I may be one of the few here not to have gone out to see that movie with the blue people yet, so I don't have actual experience, but how well do the various 3D glasses work for us myopics who need prescription lenses to see the screen as something other than a blurry blob? Can they be worn without being completely uncomfortable?
Back in the '90s, there were a couple of times when a store's credit card dialup was not working, and they had to pull out the trusty old Addressograph and get an imprint on carbon paper. The hard part was for them to find the thing.
Apple did exacly this back in what, the late '90s? Double float time not only means no Y2038 problem, but you can represent a date/time with sub-second accuracy, and math to compute delta times can be done with only one potential scaling round-off at the end when adding to a real time. Representing dates in the (very) far past or future simply loses the sub-second precision.
The only reason it wasn't done sooner was probably because for so long floating point hardware was an expensive option, and software float would have been too slow. Also, before IEEE, there really wasn't a standard format.
The bad news is that your patents will have expired by then. The good news is that the Y10K bug means that your patents will un-expire. So get your head jar ready, because you're gonna be RICH!
Just wait until we get a Mr. Fusion.
(posting because I fumbled my moderation from Funny to Overrated - one chance pop-up menus suck)
What? I looked at someone else's link showing the SMS data format, and it is quite clear and consistent. Dates are six nibbles of BCD, with the low nibble coming first in both the date and phone number. The year is in exactly the same format as the month and day: two BCD digits. It's not their fault that so many programmers were morons and couldn't comprehend to process the year (before adding the century) in exactly the same way as the month and day.
As for "lessons learned from Y2K", this is not a situation where you are keeping old data for years and years, nor are you doing date arithmetic or sorting of 50+ years range, not even ten years. Nobody's birthdate will be in the timestamp of an SMS message, nor will the expiration date of their credit card. As a timestamp, the century is explicitly implied* by context, the context being that of the calendar that's hanging on the wall of your cubicle.
If someone were to make a database with years of SMS messages and not include the century as messages were added to the database, then yes, that would be a problem. But it would not be a problem with the SMS message format. When the year 2100 rolls around, and assuming we're even still using SMS, the worst that would happen is "hundred year old" text messages. At least then the low two digits would still be right, unlike the current "2016" stupidity.
*that's an awesome combination of words
They're doing YEAR = BCDYEAR + 2000... hooray for clueless programmers!
What makes it stupider is that with SMS they have to swap the nibbles first... and decode the other fields as BCD too.
And this is clearly a client-only bug, so dozens of codebases will have to be fixed and millions of devices updated. The typical lifetime of a cellphone means that the broken ones may simply get trashed rather than go through the trouble of an update.
As I recall from knowing a couple of people in the Star Trek fanzine community back in the '80s, Star Trek is a special case as far as fanfics go. It seems that Desilu didn't register the copyrights properly for the first season, so fanfics without Chekov are fair game. Or at least that's how they explained it to me.
Of course what you have linked to includes Chekov, so they couldn't use that excuse.
If they can't make it there, they can't make it anywhere?
The 360 advances via its mass-produced red LEDs.
That could have been the Black Sea flooding. It would have been just as impressive. And a bit later than the Mediterranean.
Sounds more like a warning to me.
Even the Macintosh started out with a FAT-like file system, called MFS. I've seen what it was like when you tried to use it on a hard drive with 5 megabyte partitions, and it was not pretty.
But Apple didn't just sit on it, and had HFS ready when they released the 800K floppy drive. HFS needed one major change (with MacOS 8.1) to support hard drives larger than 2 gigabytes (and more than 65536 allocation blocks per volume, also a big problem), and HFS+ has stuck around since then, though it has received a LOT of backward-compatible extensions in OS X, including journaling.
I can't believe that MacOS X doesn't have native EXT2/3 support
Blame the GPL license. Most of OS X is under a BSD-style license. Is there even a BSD-licensed EXT2/3 implementation?
There is a pre-built version that you can download and install yourself, however.
Also, the only people who need it are the 2% who use Linux. 2% of 5% isn't much, especially when OS X users have much less need to keep Linux around than Windows users.
And we OS X users already have a very nice filesystem, thank you very much. Apple did add an amazing number of hacks to it so that it can do Unix-y things like inodes and hard links, but it works very well. It can even be made case sensitive should we ever want to compile Linux. (A million curses on whoever required case sensitive filenames in the netfilter code.)
It's that one with that whatshername, you know the one that dated that guy, she's been in ALL the gossip shows lately.
The Star Wars Holiday Special
...a multi-generation copy, where one of the intermediate copies had the tape crunched somewhere in the middle.
Oh, and would it have hurt someone to put ANY sort of link in TFS?
Yo dawg, I heard you like links, so I put some links in your links so you can link your links.
Anyhow, this manual's existence just goes to show that information really does want to be free. Or at least wants to go from classified document to $10.99 a copy.
...unless you're using 10^12 = one billion and 10^9 = one milliard
In any case, it should be an integer number of pennies (or whatever they call the euro-cents), so you're going to have to keep your account under 184 quadrillion, or is that 184 billiard? (balls!)
This sort of shellcode is probably a bit harder to write for the 68000, with its 16-bit instructions that have an "operand mode" field that spans between the two bytes. While a lot of useful instructions are in the 2xxx-7xxx range, and branches are in the 6xxx range, the instructions that do any sort of math are outside it.
It would be interesting to see what can be done with other CPUs as well. In particular, I recall that OS X PPC missed a chance to resist shellcode by ignoring two of the four bytes of the OS trap instruction, rather than forcing them to be nulls.
Did somsone spell Microsoft with a dollar sign?
Except that by political measurements, "Carbon Footprint" (aka CO2 levels) is not just important, it's one of the most important causes of global warming, and we're so far in a hole that we have to put on the emergency brakes NOW. And that is one of the things that the AGW skeptics have a problem with.