Or in this case, it doens't because you're apparently completely ignorant of the GPL.
So if I disagree that the only valid license to use ever is the GPL, it's simply because I'm ignorant of it. Yes, you're just as insane as the guy I just responded to.
I really don't know why I have to repeat this.
Why did you feel compelled to repeat that "pem is ignorant of the GPL"? Does that help your cause? Or maybe that's not what you meant. Does a lack of clarity help your cause?
It's been said in this thread numerous time, repeated in the past many times all over the internet and it's even on the FSF's website.
Repeat after me: repeating something doesn't make it true.
You don't have to agree to the GPL to use the software.
Fine. Point out where I said it did. And then stop being a name-calling dickhead.
There is a huge difference between an interruption (aka NMI) and a diversion (aka the idle loop). One requires context to be saved and restored, and the other doesn't.
A couple of ACs have more than adequately responded to this, and should be modded up, but I will give some specifics:
Fine if you're a commercial site and your client knows your job will take 2-3 weeks and cost a few thousand.
No, this is for small in-house things. For things going out, we do a much better job, with real schematic capture and real layout tools.
If you're just looking for a quick fix, there is no 1-day PCB turnaround under $100.
Sure there is (if you allow a day for shipping). I can get 3 pieces of a miniboard from expresspcb.com for $51 + shipping. IIRC, one-day shipping is a bit over $20, so for $75 I can send off a design before 1:00, and have the boards before 1:00 two days later.
If all you need is 1 print and you're a hobbyist or need something one-off, that is unacceptable.
As I said in my initial email, that depends on whether your time is valuable. In my experience, it takes a lot less total time to get a working prototype with a PCB than without, unless your circuit is very small. So if you can wait a couple of days for your circuit, and you have other things to do in the meantime (e.g. your time is valuable) and you'd like to spend less total time on the board (e.g. your time is valuable), then not laying out a board is unacceptable.
Of course, you can do whatever you want. I've seen people dead-bug 176 pin QFNs and make them work. If you find detailed work like that therapeutic, fine. But if you have other stuff to do, it can quickly become cost-ineffective.
That'd be like etching a pcb without testing the circuit on a breadboard first. Sure, it is what you have to do for large complex projects. But for most small projects it is painfully slow and error prone.
Etching a PCB (well, actually, letting somebody like expresspcb do it) instead of testing a circuit on a breadboard first is something I do all the time.
If you're ready to accept a breadboard, that means you're willing to accept one or two for a start, and they don't have to be pretty, which means that if they were PCBs, you wouldn't mind a few blue-wires.
If you're in that position, and your circuit has more than a few handfuls of nets on it, and your time is valuable and you have other stuff to do before your circuit comes back, and you're halfway proficient at electronics and at double-checking your work...
If all those things are true, you'll have a much nicer working PCB in much less time than it would take to get your crappy, flaky breadboard working.
As the saying goes, YMMV, but that's been my experience over decades of doing this.
How the fuck is the segfault graceful when it aborts a program handling hardware? You're just like one of those idiots who programmed "oh, the best thing to do if I don't know what's going on is to shut down this engine -- the other 3 will still fly the plane OK."
Mod parent up.
Using infinity sorta, kinda makes sense in some (actually many) instances. Using zero is senseless in any mathematical or practical sense.
You said my call could be recorded for quality control or training purposes, but you never gave me an opt-out. Selling it to an outside vendor to use this way is a clear copyright violation, and I'm going to call back to complain!
No, you want to compare likely transportation alternatives. If you're going to go on vacation, a likely decision you'll face is whether to pay for airline tickets and fly, or pay for fuel (and possible rental) and drive.
That's all well and good, but while you're making decisions, you'll also have to decide where you're going on that vacation. Maybe you decide to drive a couple of hundred miles, or maybe you decide to fly to Hawaii.
These things don't happen in a vacuum -- well at least until the space plane becomes a reality -- so while it's entirely possible that, given the current infrastructure, if I want to get from point A to point B, flying may be more environmentally friendly, that's a marginal case. If all the planes disappeared tomorrow, what would that do to our energy consumption?
When you drive, you have to always assume that everyone around you is an idiot with a death wish in a broken-down car and try to correct for this with your driving.
Absolutely. But realistically, 50% of the people in head-on collisions are at fault, and probably well less than 20% of the people who get rear-ended. Even most people who stomp on the brake don't get rear-ended, and most people who pull out in front of others (failing to yield right-of-way) don't get rear-ended, because somebody paying attention manages to go around them. Most serious rear-end accidents are more like this, if not quite so dramatic.
Driving defensively is all well and good, but getting rear-ended like that is often one of the most difficult things to defend against -- if you are stuck in traffic, you may have literally nowhere to go.
Not only do most people realize this, but the law itself realizes this. If you rear-end someone, it will be difficult or impossible to prove you're not at fault. This is why the Pinto was an outrage to the public -- it was expressly designed to blow up the people who were least likely to be at fault.
While I have successfully avoided being rear-ended by inching up into an intersection before, rear-end collisions typically have a lot more to do with how others drive than how you drive.
Virtually every program written has ["caused occasional instability and breakage, and consumed resources unnecessarily"]
Yes and "virtually every program" is something that the user voluntarily and directly starts. Avahi, pulseaudio, and systemd... aren't. Which makes it exceptionally frustrating for both users and developers when there is a problem, both from a standpoint of not knowing where the problem came from, and from the standpoint of finding an alternate program to use instead.
Which is why systems programmers should be held to a higher standard than applications programmers. Their mistakes should be fewer and should also be rectified more quickly.
so that comment of yours makes the rest of your post baseless and not worth replying to.
"There are lots of incompetent programmers so it's no fair pointing out that systemd is written by an incompetent programmer."
Even if I accept everything you write as true, that's still no reason to solve a technical problem with a law.
If a car manufacturer makes something that is dangerous if modded, they should make it tamperproof.
I used to work for A major auto maker, this story is a bit of click bait since more likely what they are talking about is liability issues with modified vehicle controllers. People would over tune there car via third party apps, then end up blowing the motor on race day. They would flash the car back to stock and make a warranty claim.
That sucks, but the answer is better technology that makes that sort of thing easier to prove, or better technology that makes it more idiot-proof (like most cellphones have separate radio and baseband processors), not outlawing hacking.
If you're batteries are completely full, and you don't need any power, your controller simply won't pull any power from the solar panels, so the "heat sink" is merely your panels getting slightly warmer than they would have.
Household inverters will dump power into the grid as long as the grid is being maintained within some tolerance of voltage and frequency. This tolerance is quite wide, because otherwise inverters wouldn't work a lot of the time.
But the utility company would ideally like to be able to control the grid to whatever tolerance makes sense under current conditions, and this problem is not simplified by random (from its perspective) energy sources dotted around.
Also, the utility company has to maintain generation for the base load, and when a cloud greatly reduces the solar it has no control over, it has to quickly ramp generation up and then back down when the cloud goes away.
I haven't tried drugs, but yeah, much of what you describe sounds similar to my experience. A couple of articles I found have descriptions that really resonate with me -- first a more clinical description and then a more informal description of the same information.
Actually, a lot of ADHD people procrastinate on a lot of things, partly because impending doom can be a focusing event that gets them moving.
But while they're procrastinating on things that others would think are important, they are usually working on stuff they think is important. Procrastinating on everything is more likely a sign of something else, perhaps depression.
> I wouldn't call being bad at something you don't like a disease.
I wouldn't either. And I don't call ADHD a disease, but it's not what you describe. The typical ADHDer either would love French and (assuming his ADHD does not coexist alongside learning disabilities) learn it really well, or hate it and not bother.
Actually, the thing is that people often don't understand that for many, if not most, with ADHD, the "deficit" in ADHD is not for all things -- just for things that the "sufferer" doesn't give a shit about.
Slashdot Mirror
So if I disagree that the only valid license to use ever is the GPL, it's simply because I'm ignorant of it. Yes, you're just as insane as the guy I just responded to.
Why did you feel compelled to repeat that "pem is ignorant of the GPL"? Does that help your cause? Or maybe that's not what you meant. Does a lack of clarity help your cause?
Repeat after me: repeating something doesn't make it true.
Fine. Point out where I said it did. And then stop being a name-calling dickhead.
There is a huge difference between an interruption (aka NMI) and a diversion (aka the idle loop). One requires context to be saved and restored, and the other doesn't.
Tell it!
I've always envied people who can see the universe in black and white.
It scares the shit out of me whenever they get any sort of power, though.
Because they prove over and over that they are incapable of rational thought.
No, this is for small in-house things. For things going out, we do a much better job, with real schematic capture and real layout tools.
Sure there is (if you allow a day for shipping). I can get 3 pieces of a miniboard from expresspcb.com for $51 + shipping. IIRC, one-day shipping is a bit over $20, so for $75 I can send off a design before 1:00, and have the boards before 1:00 two days later.
As I said in my initial email, that depends on whether your time is valuable. In my experience, it takes a lot less total time to get a working prototype with a PCB than without, unless your circuit is very small. So if you can wait a couple of days for your circuit, and you have other things to do in the meantime (e.g. your time is valuable) and you'd like to spend less total time on the board (e.g. your time is valuable), then not laying out a board is unacceptable.
Of course, you can do whatever you want. I've seen people dead-bug 176 pin QFNs and make them work. If you find detailed work like that therapeutic, fine. But if you have other stuff to do, it can quickly become cost-ineffective.
Etching a PCB (well, actually, letting somebody like expresspcb do it) instead of testing a circuit on a breadboard first is something I do all the time.
If you're ready to accept a breadboard, that means you're willing to accept one or two for a start, and they don't have to be pretty, which means that if they were PCBs, you wouldn't mind a few blue-wires.
If you're in that position, and your circuit has more than a few handfuls of nets on it, and your time is valuable and you have other stuff to do before your circuit comes back, and you're halfway proficient at electronics and at double-checking your work...
If all those things are true, you'll have a much nicer working PCB in much less time than it would take to get your crappy, flaky breadboard working.
As the saying goes, YMMV, but that's been my experience over decades of doing this.
How the fuck is the segfault graceful when it aborts a program handling hardware? You're just like one of those idiots who programmed "oh, the best thing to do if I don't know what's going on is to shut down this engine -- the other 3 will still fly the plane OK."
Mod parent up. Using infinity sorta, kinda makes sense in some (actually many) instances. Using zero is senseless in any mathematical or practical sense.
I don't think that word means what you think it means.
Huh? What silo? Which parallel universe are you from?
You said my call could be recorded for quality control or training purposes, but you never gave me an opt-out. Selling it to an outside vendor to use this way is a clear copyright violation, and I'm going to call back to complain!
FTFY
Meh. Those will get shot down well before 248 days are up.
That's all well and good, but while you're making decisions, you'll also have to decide where you're going on that vacation. Maybe you decide to drive a couple of hundred miles, or maybe you decide to fly to Hawaii.
These things don't happen in a vacuum -- well at least until the space plane becomes a reality -- so while it's entirely possible that, given the current infrastructure, if I want to get from point A to point B, flying may be more environmentally friendly, that's a marginal case. If all the planes disappeared tomorrow, what would that do to our energy consumption?
Either compare flying a small plane to driving a car, or compare a huge bus to a plane.
Absolutely. But realistically, 50% of the people in head-on collisions are at fault, and probably well less than 20% of the people who get rear-ended. Even most people who stomp on the brake don't get rear-ended, and most people who pull out in front of others (failing to yield right-of-way) don't get rear-ended, because somebody paying attention manages to go around them. Most serious rear-end accidents are more like this, if not quite so dramatic.
Driving defensively is all well and good, but getting rear-ended like that is often one of the most difficult things to defend against -- if you are stuck in traffic, you may have literally nowhere to go.
Not only do most people realize this, but the law itself realizes this. If you rear-end someone, it will be difficult or impossible to prove you're not at fault. This is why the Pinto was an outrage to the public -- it was expressly designed to blow up the people who were least likely to be at fault.
While I have successfully avoided being rear-ended by inching up into an intersection before, rear-end collisions typically have a lot more to do with how others drive than how you drive.
Yes and "virtually every program" is something that the user voluntarily and directly starts. Avahi, pulseaudio, and systemd... aren't. Which makes it exceptionally frustrating for both users and developers when there is a problem, both from a standpoint of not knowing where the problem came from, and from the standpoint of finding an alternate program to use instead.
Which is why systems programmers should be held to a higher standard than applications programmers. Their mistakes should be fewer and should also be rectified more quickly.
"There are lots of incompetent programmers so it's no fair pointing out that systemd is written by an incompetent programmer."
Is that really what you meant to write?
Even if I accept everything you write as true, that's still no reason to solve a technical problem with a law. If a car manufacturer makes something that is dangerous if modded, they should make it tamperproof.
That sucks, but the answer is better technology that makes that sort of thing easier to prove, or better technology that makes it more idiot-proof (like most cellphones have separate radio and baseband processors), not outlawing hacking.
Household inverters will dump power into the grid as long as the grid is being maintained within some tolerance of voltage and frequency. This tolerance is quite wide, because otherwise inverters wouldn't work a lot of the time.
But the utility company would ideally like to be able to control the grid to whatever tolerance makes sense under current conditions, and this problem is not simplified by random (from its perspective) energy sources dotted around.
Also, the utility company has to maintain generation for the base load, and when a cloud greatly reduces the solar it has no control over, it has to quickly ramp generation up and then back down when the cloud goes away.
I haven't tried drugs, but yeah, much of what you describe sounds similar to my experience. A couple of articles I found have descriptions that really resonate with me -- first a more clinical description and then a more informal description of the same information.
But while they're procrastinating on things that others would think are important, they are usually working on stuff they think is important. Procrastinating on everything is more likely a sign of something else, perhaps depression.
I wouldn't either. And I don't call ADHD a disease, but it's not what you describe. The typical ADHDer either would love French and (assuming his ADHD does not coexist alongside learning disabilities) learn it really well, or hate it and not bother.
Actually, the thing is that people often don't understand that for many, if not most, with ADHD, the "deficit" in ADHD is not for all things -- just for things that the "sufferer" doesn't give a shit about.