I haven't used this place, but here's one place that will do small one-off machining jobs for you: http://www.emachineshop.com/ . That's been sitting in my bookmarks for "future reference" for a while now:)
Looks like they want you to use their own cad software, which apparently can estimate the cost while you work on the design. I bet some googling can find other, similar, shops.
Battery "memory", to an engineer/pedant, is a different phenomenon than the reduced capacity you noticed with batteries for electric power tools. "memory" applies when the battery is discharged by a certain amount, then recharged, then discharged to exactly the same state again. The only believable story I've heard about this involved NiCads in a satellite that discharged during the satellite's night and charged during its day. It was important that the satellite used exactly the same amount of energy each cycle (to within less than 1%). Memory is supposed to be a myth because those conditions rarely apply to anything. Hell, maybe the satellite story is made-up too, I don't know:)
On the other hand, most (all?) types of batteries are expected to lose capacity over time.
According to TFA, the shoppers didn't look for higher ratings when purchasing a sex toy than when purchasing batteries, and they were willing to pay only a $0.60 premium for privacy. And that when the privacy rating is conspicuously flashed at them with some gizmo.
Given the evidence presented in the article, I'd draw the conclusion that shoppers don't care about privacy.
As far as I can tell, using the -e option to GNU diff produces output which does not include any of the original lines. I can't believe that you would be allowed to distribute proprietary versions of linux simply through the loophole that none of your modified lines are overly similar to original lines
The track still seems like a derivative work to me. It wouldn't be legal for somebody to release diffs (or say an ed script such that it contains none of the unmodified code) for the linux kernel under a GPL-incompatible license; isn't this product analogous to doing that?
delta wings often have a fairly predictable stall (high angle of attack, "mush out"). It's also not/that/ bad for low-speeds: see almost any paper airplane:)
Drag gets high at low speed/high AOA, but if the dinosaur was not a very good pilot the wing could make some sense
debian etch is on 4.0.3. Ok it's not "stable" debian but it's not that cutting-edge either. I do a fair amount of coding and haven't noticed a problem.
I switched to dvorak a couple years ago and simply wasn't able to get both layouts in my head at once. I only learned dvorak after I quit qwerty, and then I forgot qwerty! Being on a college campus with lots of public computers, that kind of sucked. I'm now in the process of switching back, and I've got most of my old speed back.
dvorak was really nice and typing with qwerty seems really uncomfortable and strained now, but I wouldn't go dvorak again, at least not for a college student or anyone who uses other people's keyboards a lot.
Maybe others can learn dvorak while still typing qwerty a lot, idunno.
There are several paragraphs in the article which, I think, don't actually say anything. Example:
Imagine, for example, trying to build a compiler able to produce an efficient executable in exactly one pass. Nobody does this now, for obvious design reasons consequent to an underlying sequential processing assumption, but it shouldn't be impossible. "All" it would take is a complete re-appraisal of everything we know about optimization and related issues in a truly concurrent, shared-everything, multi-threading environment with enough threads.
Am I completely out of my depth? What does threading have to do with efficient one-pass optimizing compilers? What's his issue with concurrency under linux anyway?
Or this:
On the other hand, this variation on the main question also raises new issues because many of the changes made to process and memory management between the 2.4 and 2.6 Linux kernels look a bit artificial -- meaning that they don't seem to be direct continuations of code evolution up to 2.4 and thus raise the suspicion that the SCO/IBM lawsuit might be having some unexpected design consequences.
What makes a patch "artificial" ? Whatever that means, how does it imply anything about the sco/ibm lawsuit? Weren't the 2.5 development line split and the major scheduler changes introduced before the lawsuit? Even if not, what would he consider a continuation of the development up to 2.4?
In short, can somebody explain to me what this guy is saying?
Furthermore, there is a fair amount of work being done to place all daemons on OpenBSD in a chroot jail, basically making running things like a mail server or http server no less secure than running without
From the chroot(2) man page (okay, this is on debian but the same applies to obsd):
Note that this call does not change the current working directory, so
that `.' can be outside the tree rooted at `/'. In particular, the
super-user can escape from a `chroot jail' by doing `mkdir foo; chroot
foo; cd..'.
So if you've got an exploit for a chrooted daemon plus an exploit for a kernel bug, you can get root and break out of the jail. Thus, if you don't have untrusted local users on the system, adding more chrooted daemons does endanger your security a bit. Not to mention that even if it couldn't break out of the jail, root can send signals to whatever processes it wants or halt the system.
In the R/C jet community the Alpha 4 is considered the end-all charger. It handles NiCad, NiMH, and wet/gell cells and can handle packs of from 1 to 30 or so NiCad or NiMH cells. Most importantly the packs *never* get hot, even on its fastest charge rates. At least when I got hold of my alpha a few years back, it was basically the only charger that could actually do this. It will also do a peak charge at C/10 rate, to really baby your packs.
Unfortunately they're built by a basement operation and there is always a huge backlog of orders. You have to get a used one off ebay for probably more than new price, which is kind of steep to start with. The other downside is that it will only charge at up to 1 amp, which is slow on very large packs.
Looks like they want you to use their own cad software, which apparently can estimate the cost while you work on the design. I bet some googling can find other, similar, shops.
noticed with batteries for electric power tools. "memory" applies when the battery is discharged by a certain amount, then recharged, then discharged to exactly the same state again. The only believable story I've heard about this involved NiCads in a satellite that discharged during the satellite's night and charged during its day. It was important that the satellite used exactly the same amount of energy each cycle (to within less than 1%). Memory is supposed to be a myth because those conditions rarely apply to anything. Hell, maybe the satellite story is made-up too, I don't know
On the other hand, most (all?) types of batteries are expected to lose capacity over time.
Given the evidence presented in the article, I'd draw the conclusion that shoppers don't care about privacy.
The summary quote uses 108 words to explain that there exists a compiler for this language.
As far as I can tell, using the -e option to GNU diff produces output which does not include any of the original lines. I can't believe that you would be allowed to distribute proprietary versions of linux simply through the loophole that none of your modified lines are overly similar to original lines
Drag gets high at low speed/high AOA, but if the dinosaur was not a very good pilot the wing could make some sense
right I get it, the missing 's'. it's been a slow day.
er no; CS. surely it's not an advanced term though : )
wow. I never heard it except as a joke
The maths required? Is that correct grammar in the uk?
debian etch is on 4.0.3. Ok it's not "stable" debian but it's not that cutting-edge either. I do a fair amount of coding and haven't noticed a problem.
or maybe you meant just opterons
dvorak was really nice and typing with qwerty seems really uncomfortable and strained now, but I wouldn't go dvorak again, at least not for a college student or anyone who uses other people's keyboards a lot.
Maybe others can learn dvorak while still typing qwerty a lot, idunno.
perl -e%::=1,//
I wonder if the writer just found out that you can't run processes concurrently on a uniprocessor system. He acts like that's only true for x86.
Or this: What makes a patch "artificial" ? Whatever that means, how does it imply anything about the sco/ibm lawsuit? Weren't the 2.5 development line split and the major scheduler changes introduced before the lawsuit? Even if not, what would he consider a continuation of the development up to 2.4? In short, can somebody explain to me what this guy is saying?
is the sun. Shouldn't that be extinguished before open source software?
In the R/C jet community the Alpha 4 is considered the end-all charger. It handles NiCad, NiMH, and wet/gell cells and can handle packs of from 1 to 30 or so NiCad or NiMH cells. Most importantly the packs *never* get hot, even on its fastest charge rates. At least when I got hold of my alpha a few years back, it was basically the only charger that could actually do this. It will also do a peak charge at C/10 rate, to really baby your packs. Unfortunately they're built by a basement operation and there is always a huge backlog of orders. You have to get a used one off ebay for probably more than new price, which is kind of steep to start with. The other downside is that it will only charge at up to 1 amp, which is slow on very large packs.