18. Beatcha. And I'm younger to boot (though I've still done a whole bunch of assembly, but for PIC16s and PIC18s instead)
Seriously though, who doesn't have at least the first few memorized? Even Joe Average remembers at least the first 9 or so (whether they like it or not), especially from RAM sizes. 1, 2, 4, 8, 16, 32, 64, 128, 256, 512 will probably ring a bell for most people who have bought a computer at some point.
Actually, though my first guess was that is was a HID driver as well, it turns out that it simply exposes the speed control via sysfs. It's a very simple driver (159 lines long). In fact, it's a very good example on how to write a basic USB driver for Linux. See drivers/usb/misc/trancevibrator.c
You're thinking digital cameras. Webcams are kernel-space.
Geez, what's up today with the "USB=userspace" stuff? Some drivers are in kernelspace, some are in userspace. Heck, I rarely use anything libusb-based on my system - even the printer uses the usblp kernel-side driver (though all of the actual high-level comms is done in hplip, but you get the point). Every other USB device that I have is handled directly in the kernel, with no userspace intervention (except to make use of the services that the device provides).
Compiling isn't much different than any other disk activity. Now if you run Gentoo it might make a difference, but random one-off programs from class? That's probably equivalent to saving your average OOo document a few times.
Devices that use userspace USB drivers: - Printers (CUPS) - Scanners (SANE) - Cameras (gPhoto2) Devices that use kernelspace USB drivers: - USB Mass storage (card readers/pendrives/media players/etc) - USB Networking - USB Bluetooth - USB to serial/parallel converters - USB HID Input - USB Audio - USB Video Capture
That USB devices are a userspace issue is a lie. They go both ways.
Besides, Trance Vibrator support is already in... the kernel.
I have a GeForce 6600 and an Athlon64 3000+, and I can run it decently with medium settings at 1024x768. Your system should run it as well (heck, my brother used to run the Source engine on a GeForce2, though that was on Windows).
It's not 100% perfect, of course, but it works. For me, the only noticeable problems are that occasionally it will stutter for a split second, and that the sound buffer loops around during loading screens. Also, you might need to manually change your screen resolution if you play fullscreen at a different resolution than your desktop (use xrandr to do it easily), since otherwise it will appear to start up fine but then the main screen will come up in the middle of your previous desktop, while your viewport is the top-left corner. In general, video mode changes tend to screw things up, but restarting the game fixes things.
Old genres aren't completely gone. In fact, they're being rediscovered all the time. Look at Super Paper Mario, for example. It's an RPG, but it has 2D side-scroller mechanics with a 3-D element to them (well, later on in the game it touches just about every game genre in existence, but I don't want to spoil them).
Granted, there are many remakes of remakes being made of the same gameplay over and over again, but there is a trickle of new and old-but-new games showing up. You just have to find them.
But you can always just stream the content. 27Mbps is good enough for DVD and even decently compressed HD. 100Mbps Ethernet will stream HD without any trouble.
Well, Bluetooth has a HID specification too, but you can be damn sure they don't use it (Wii remote is a special protocol, XBox controllers require "special" Windows drivers too).
The Wiimote uses Bluetooth HID. It's just that they layer their own higher-level protocol on top of a nondescriptive HID report descriptor. However, all the lower level stuff is the same, and the Wiimote is a legal HID device - it's just that no host knows what to do with its data without some extra drivers. Try it for yourself: press 1+2 on the Wiimote and scan for devices with your computer. The Wiimote will register in any BT host as a HID compatible game controller.
Xbox 360 controllers use a proprietary wireless protocol. Xbox (1) controllers (and USB 360 controllers) are similar to the Wiimote in that they use the USB HID protocol, but with no descriptor (and a few extra vendor-specific commands). PS3 pads are crippled Bluetooth devices IIRC.
I said it was possible; I never said it was possible using the current situation under Windows. The OS vendors have to set up such a system in the first place. "People" refers to everyone, not just application developers. OS vendors need to provide such a framework and applications need to use it.
Hooking into OS functions can be done dynamically. Providing a framework for applications to auto-run on startup and/or override OS functionality while still remaining in a self-contained package isn't hard.
Just because people don't do it doesn't mean it can't be done.
That's the point. You want thick wires - that is the most important attribute (low resistance). Any random power cable will actually work quite well for speaker wiring. That WILL make a difference, especially if the original cables are crappy. Spending $Xk on the wiring won't.
The overhead of using Wine is very small. It is a thin layer on top of native Linux, and Windows itself isn't emulated. The difference between Linux and Windows is much more important with regard to performance. As it turns out, sometimes the Windows drivers are faster and sometimes the Linux drivers are faster. I've seen games run faster under Wine than under native Windows.
I don't even know what the name for that growth rate is, but it's faster than exponential (since the base also changes). As you increase the number of cities, the extra 5/64 becomes completely insignificant.
5/64 is 1/12.8. That means that with that constant factor, you need 12.8 times less power to solve the problem.
Going from 4 cities to 5 requires 12.2 times as much power. Going from 20 cities to 21 requires 55.7 times as much power. Going from 100 cities to 101 requires 273.1 times as much power.
Realistically, all that the 5/64 factor means is that with a small number of cities, you can add an extra one or two. Then again, you can solve TSP for five cities using a desktop computer. With a larger number of cities, the extra factor is insignificant.
There is no such thing as a green laser diode. Green lasers use a powerful infrared diode (like the one in this article, but infrared) pumped into an Nd:YVO4 crystal which resonates together with a KTP crystal to produce green light.
Color has nothing to do with heating power - that's what the mW rating is for, and the wavelength doesn't change the amount of power it puts out. However, different materials absorb different wavelengths, so it depends on *what* you want to burn. But that's obvious (same reason why wearing a white t-shirt on sunny days keeps you cooler). If you have an object that absorbs every visible wavelength (i.e. it is mostly black), then the wavelength of the laser doesn't change power.
However, the eye is much more sensitive to green, power-wise, than red. That is why green lasers look a lot brighter. In fact, I'd argue they are safer at the same power levels than red - they look so bright you will quickly turn away and treat them with more respect than a crappy deep-red pointer that looks like nothing but actually puts out the same amount of power.
The reason green pointers can be "overclocked" more than red pointers is because the crystals themselves tend to withstand quite a bit of abuse, and the pump diode is already a high-power diode which tends not to have too much trouble going further. The cheap 5mW diodes in red pointers will die quickly if you try to push them further. Green pointers are very inefficient.
Slashdot Mirror
No you can't. You can use capacitors with AC, which just means they charge and discharge periodically, but you can't store AC in a capacitor.
It's not x86 compatible. It's inspired by x86.
18. Beatcha. And I'm younger to boot (though I've still done a whole bunch of assembly, but for PIC16s and PIC18s instead)
Seriously though, who doesn't have at least the first few memorized? Even Joe Average remembers at least the first 9 or so (whether they like it or not), especially from RAM sizes. 1, 2, 4, 8, 16, 32, 64, 128, 256, 512 will probably ring a bell for most people who have bought a computer at some point.
Then there's us. 1024, 2048, 4096, 8192, 16384, 32768, 65536, 131072, 262144.
There, fixed that for you.
Actually, though my first guess was that is was a HID driver as well, it turns out that it simply exposes the speed control via sysfs. It's a very simple driver (159 lines long). In fact, it's a very good example on how to write a basic USB driver for Linux. See drivers/usb/misc/trancevibrator.c
lm_sensors supports a huge set of sensors, together with the Hardware Monitoring support in the kernel.
You're thinking digital cameras. Webcams are kernel-space.
Geez, what's up today with the "USB=userspace" stuff? Some drivers are in kernelspace, some are in userspace. Heck, I rarely use anything libusb-based on my system - even the printer uses the usblp kernel-side driver (though all of the actual high-level comms is done in hplip, but you get the point). Every other USB device that I have is handled directly in the kernel, with no userspace intervention (except to make use of the services that the device provides).
Compiling isn't much different than any other disk activity. Now if you run Gentoo it might make a difference, but random one-off programs from class? That's probably equivalent to saving your average OOo document a few times.
Devices that use userspace USB drivers:
- Printers (CUPS)
- Scanners (SANE)
- Cameras (gPhoto2)
Devices that use kernelspace USB drivers:
- USB Mass storage (card readers/pendrives/media players/etc)
- USB Networking
- USB Bluetooth
- USB to serial/parallel converters
- USB HID Input
- USB Audio
- USB Video Capture
That USB devices are a userspace issue is a lie. They go both ways.
Besides, Trance Vibrator support is already in... the kernel.
That's like saying PCs are toys, because banks use mainframes to handle your credit card transactions.
That a device or program isn't suited for a certain task doesn't mean it's a toy.
I have a GeForce 6600 and an Athlon64 3000+, and I can run it decently with medium settings at 1024x768. Your system should run it as well (heck, my brother used to run the Source engine on a GeForce2, though that was on Windows).
It's not 100% perfect, of course, but it works. For me, the only noticeable problems are that occasionally it will stutter for a split second, and that the sound buffer loops around during loading screens. Also, you might need to manually change your screen resolution if you play fullscreen at a different resolution than your desktop (use xrandr to do it easily), since otherwise it will appear to start up fine but then the main screen will come up in the middle of your previous desktop, while your viewport is the top-left corner. In general, video mode changes tend to screw things up, but restarting the game fixes things.
Old genres aren't completely gone. In fact, they're being rediscovered all the time. Look at Super Paper Mario, for example. It's an RPG, but it has 2D side-scroller mechanics with a 3-D element to them (well, later on in the game it touches just about every game genre in existence, but I don't want to spoil them).
Granted, there are many remakes of remakes being made of the same gameplay over and over again, but there is a trickle of new and old-but-new games showing up. You just have to find them.
For what it's worth, it works pretty much perfectly under Wine.
Now these points of data make a beautiful line
And we're out of beta; we're releasing on time!
But you can always just stream the content. 27Mbps is good enough for DVD and even decently compressed HD. 100Mbps Ethernet will stream HD without any trouble.
The Wiimote uses Bluetooth HID. It's just that they layer their own higher-level protocol on top of a nondescriptive HID report descriptor. However, all the lower level stuff is the same, and the Wiimote is a legal HID device - it's just that no host knows what to do with its data without some extra drivers. Try it for yourself: press 1+2 on the Wiimote and scan for devices with your computer. The Wiimote will register in any BT host as a HID compatible game controller.
Xbox 360 controllers use a proprietary wireless protocol. Xbox (1) controllers (and USB 360 controllers) are similar to the Wiimote in that they use the USB HID protocol, but with no descriptor (and a few extra vendor-specific commands). PS3 pads are crippled Bluetooth devices IIRC.
They've had it at Something Awful for ages. Not Mind Safe (NMS).
In retrospect, it's probably a bad thing that they've had the need for it for so many years now.
I said it was possible; I never said it was possible using the current situation under Windows. The OS vendors have to set up such a system in the first place. "People" refers to everyone, not just application developers. OS vendors need to provide such a framework and applications need to use it.
Hooking into OS functions can be done dynamically. Providing a framework for applications to auto-run on startup and/or override OS functionality while still remaining in a self-contained package isn't hard.
Just because people don't do it doesn't mean it can't be done.
That's the point. You want thick wires - that is the most important attribute (low resistance). Any random power cable will actually work quite well for speaker wiring. That WILL make a difference, especially if the original cables are crappy. Spending $Xk on the wiring won't.
Wine Is Not an Emulator.
The overhead of using Wine is very small. It is a thin layer on top of native Linux, and Windows itself isn't emulated. The difference between Linux and Windows is much more important with regard to performance. As it turns out, sometimes the Windows drivers are faster and sometimes the Linux drivers are faster. I've seen games run faster under Wine than under native Windows.
A beam balance will easily tell you the mass of an object no matter what planet you're on.
Sadly, it even beats Duke Nukem Forever.
Now take a minute for that to sink in.
I don't even know what the name for that growth rate is, but it's faster than exponential (since the base also changes). As you increase the number of cities, the extra 5/64 becomes completely insignificant.
5/64 is 1/12.8. That means that with that constant factor, you need 12.8 times less power to solve the problem.
Going from 4 cities to 5 requires 12.2 times as much power.
Going from 20 cities to 21 requires 55.7 times as much power.
Going from 100 cities to 101 requires 273.1 times as much power.
Realistically, all that the 5/64 factor means is that with a small number of cities, you can add an extra one or two. Then again, you can solve TSP for five cities using a desktop computer. With a larger number of cities, the extra factor is insignificant.
There is no such thing as a green laser diode. Green lasers use a powerful infrared diode (like the one in this article, but infrared) pumped into an Nd:YVO4 crystal which resonates together with a KTP crystal to produce green light.
Color has nothing to do with heating power - that's what the mW rating is for, and the wavelength doesn't change the amount of power it puts out. However, different materials absorb different wavelengths, so it depends on *what* you want to burn. But that's obvious (same reason why wearing a white t-shirt on sunny days keeps you cooler). If you have an object that absorbs every visible wavelength (i.e. it is mostly black), then the wavelength of the laser doesn't change power.
However, the eye is much more sensitive to green, power-wise, than red. That is why green lasers look a lot brighter. In fact, I'd argue they are safer at the same power levels than red - they look so bright you will quickly turn away and treat them with more respect than a crappy deep-red pointer that looks like nothing but actually puts out the same amount of power.
The reason green pointers can be "overclocked" more than red pointers is because the crystals themselves tend to withstand quite a bit of abuse, and the pump diode is already a high-power diode which tends not to have too much trouble going further. The cheap 5mW diodes in red pointers will die quickly if you try to push them further. Green pointers are very inefficient.