Apple keyboards are also USB hubs. I prefer my USB devices to be flash upgradeable, especially if they're hubs or will be around for a long time (like a keyboard) or something like that.
Also... keyboards SHOULD be complex. They're the primary input method, and they're inputting codes that get mapped to something very complex: unicode. If I want my keypad-minus to enter a chinese ideograph, even at a unicode console when the GUI hasn't come up (say, because I have a unicode filename with the solution in there) then it should be able to do that.
Play Zelda. I know it may seem silly at the start, but don't judge them by that. Zelda 64 and later all seem to have pretty amazing "journeys" to them, if you play for a while. From what I've heard of people playing older Zeldas, the experience is much the same. Easily some of the best games I've ever played, out of a small selection that I even liked.
Because someone else might have the same idea, and you need to beat them to it.
That's a lot of assumptions about an entire galaxy with lifeforms and tech you've never had any hint of. For all we know, the most warlike race in the galaxy could have its weaponry completely undermined by another race's equivalent of a lego set.
Apple would probably be quite happy to start over on a new arch with Windows. Competing head-to-head on a new platform would be a big catch-up compared to their current position of limited drivers.
The problem isn't the OS, it's the software for the OS. On Linux, you port the kernel, and then simply rebuild your distro (fixing portability bugs in the process relatively rarely). Job done. On Windows, you need mom & pop go to the car boot sale, buy Knitting Extravaganza 4.0, and still have it install/run successfully.
I think this is the whole reason why microsoft is pushing dot-net and higher-level languages -- not because they care about the languages so much, but because they care about abstracting the windows platform away from PCs until a virtual machine, like Java has been doing for years. Whether Windows, OS X, Linux, or something else wins the desktop wars, Java will survive. Microsoft wants to survive that loss too.
This is NOT a null-terminated string. This is an ESCAPE CODE terminated string. You know, like the escape codes a compiler interprets. In other words, it's treating stuff from the net as "source code" (albeit data and not instructions) to compile. Firefox is completely fucked up sometimes. Thankfully it's still not as bad as IE.
CAs should be fixed to not allow garbage in the domain. \0 isn't a legal character in DNS protocol
If it's not allowed in DNS protocol (which wouldn't surprise me, unless punicode-escaped), then primarily, it is the client's job to defend against it. Even if all legitimate DNS information sources are checked, the client shouldn't assume that the next DNS request will go to or be replied to from a real server.
No, I mentioned atexit, but that's only on program exit. try...finally can be used anywhere you want some work done atomically. The closest C has is setjmp and longjmp, but they're scary enough that I've always avoided them, even though I'm happy enough with assembly, whereas try...finally is very clear and usable.
exit() is a standard C-library function ends** the program, and control flow from the main program ends right there at the call. There are "atexit" hooks which can be called, and memory deallocation etc. will be done by exit().
In nicer languages than C that have exceptions, you often also have try...finally blocks, where you can guarantee that your cleanup code will be called, even if you call some function which calls exit(). Essentially, it gives you nice atomic/transactional operations, at every level of code you want them at.
Slashdot Mirror
Just FYI: that was a single sentence with a comma, not two sentences.
Indeed. The rest are just wannabes.
Oh, it's a comment about unit conversions. No offence meant, but I was honestly wondering if it was a comment about fitness.
Apple keyboards are also USB hubs. I prefer my USB devices to be flash upgradeable, especially if they're hubs or will be around for a long time (like a keyboard) or something like that.
Also... keyboards SHOULD be complex. They're the primary input method, and they're inputting codes that get mapped to something very complex: unicode. If I want my keypad-minus to enter a chinese ideograph, even at a unicode console when the GUI hasn't come up (say, because I have a unicode filename with the solution in there) then it should be able to do that.
Play Zelda. I know it may seem silly at the start, but don't judge them by that. Zelda 64 and later all seem to have pretty amazing "journeys" to them, if you play for a while. From what I've heard of people playing older Zeldas, the experience is much the same. Easily some of the best games I've ever played, out of a small selection that I even liked.
Hmm. Doesn't human skin go pure white when you pass a current through it? ;)
Welcome to life.
In other news, Naval research has noted ongoing changes in dolphin behaviour, six days after Linus Torvalds shouted at Alan Cox.
Old consoles aren't selling as if they were cutting edge. Fascinating.
Hopefully any class that has 1984 as required reading will flunk you for using a DRM'd device to read 1984.
I think he means that, when you're surrounded by screens, it's a bit brighter.
That's a lot of assumptions about an entire galaxy with lifeforms and tech you've never had any hint of. For all we know, the most warlike race in the galaxy could have its weaponry completely undermined by another race's equivalent of a lego set.
Mine's an ancient device called 'Outside'.
Apple would probably be quite happy to start over on a new arch with Windows. Competing head-to-head on a new platform would be a big catch-up compared to their current position of limited drivers.
The problem isn't the OS, it's the software for the OS. On Linux, you port the kernel, and then simply rebuild your distro (fixing portability bugs in the process relatively rarely). Job done. On Windows, you need mom & pop go to the car boot sale, buy Knitting Extravaganza 4.0, and still have it install/run successfully.
I think this is the whole reason why microsoft is pushing dot-net and higher-level languages -- not because they care about the languages so much, but because they care about abstracting the windows platform away from PCs until a virtual machine, like Java has been doing for years. Whether Windows, OS X, Linux, or something else wins the desktop wars, Java will survive. Microsoft wants to survive that loss too.
Yeah, but who wants to read actual text when you can scan for tokens? ;)
Apple's special "youth empowerment" team is working on iHurd now. From now on, it's going to be known as iHurdYouTheFirstTime.
Never mind, the write-up mislead me a bit.
Ah, yeah, I guess you're right. Misleading article :/
It's a shame that pearl necklaces didn't become the dominant form of string... oh, never mind.
This is NOT a null-terminated string. This is an ESCAPE CODE terminated string. You know, like the escape codes a compiler interprets. In other words, it's treating stuff from the net as "source code" (albeit data and not instructions) to compile. Firefox is completely fucked up sometimes. Thankfully it's still not as bad as IE.
If it's not allowed in DNS protocol (which wouldn't surprise me, unless punicode-escaped), then primarily, it is the client's job to defend against it. Even if all legitimate DNS information sources are checked, the client shouldn't assume that the next DNS request will go to or be replied to from a real server.
Cheap certificate services are automated, so yes.
The question is... why in hell is firefox treating strings from the net as if they're already escaped?
No, I mentioned atexit, but that's only on program exit. try...finally can be used anywhere you want some work done atomically. The closest C has is setjmp and longjmp, but they're scary enough that I've always avoided them, even though I'm happy enough with assembly, whereas try...finally is very clear and usable.
exit() is a standard C-library function ends** the program, and control flow from the main program ends right there at the call. There are "atexit" hooks which can be called, and memory deallocation etc. will be done by exit().
In nicer languages than C that have exceptions, you often also have try...finally blocks, where you can guarantee that your cleanup code will be called, even if you call some function which calls exit(). Essentially, it gives you nice atomic/transactional operations, at every level of code you want them at.