I haven't actually played the game, however, I would think that such a character would be covered as a 'political satire' even if they exactly took her image.
>Failed power steering adds resistance, making the car even harder to steer.
Yep, it required a lot of torque to move the wheel. It wasn't safe to drive.
> From what I've heard, a pure manual steering car designed around a plain rack and pinion setup gives a lot more tactile feedback and is more-pleasant to drive.
The effect is not dramatically different, but it does feel a little more connected.
I had exactly this flaw happen in an old Subaru. I was left with a difficult to steer car. I don't remember a recall for it. So Tesla seems to be more diligent.
The RPi sucks a bit for real time control compared to say an Arduino, because it's running Linux and a CPU with less deterministic timing that the slower, simpler CPU in an arduino. I've tried direct control of steppers with a Pi and it gets jerky when the CPU is running a UI or doing other stuff.
So arduinos seen to be the board of choice for motor control in homebrew CNCs and 3D printers, while RPis do nicely doing the thinking (interpreting gcode, presenting a UI, etc). An RPi driving 3 or 4 arduinos, driving 3 or 4 steppers is a common configuration.
There are far better engineered solutions when you sprinkle in a little hardware for motor control, like an FPGA to do the timing and feedback tracking. But software and cheap CPUs are cheaper and more accessible to hobbyists.
Since it's reported that the License is Apache 2.0, it can't be Linux, which is GPL. You *may* be able to put Apache 2.0 code under GPL, I'm not sure, but you can only put GPL software under Apache if you are the copyright holder.
Of course, they could be violating the license, I suppose.
Companies with lawyers like Apache 2.0 because of the clauses that say something to the effect "If you sue me, you lose this license to this software".
The code I write is usually analysis code for me to do my job. It's not for use by others. I sometimes release public code for use by others. E.G. Crypto library support.
My large employer has failed to employ someone who can jump into my job so far. If I get hit by a bus or win the lottery, it's likely to be a problem for my employer.
I program for my job, but at no point did my choice of language have any relevance to my pay.
My expertise in the domain of the things I design and the efficacy with which I do my job is what determines my pay. I don't think people usually know what languages I program in.
As long as the owner of the satellite is a US company, then they are subject to the US licensing laws. If Swarm wishes to relocate to, say, South Sudan, which probably doesn't have a well developed regulatory environment, then they can get a South Sudanese radio license. And operate from South Sudan, have their corporate headquarters in South Sudan, etc.
Needs a license to do what? Sit around while their satellites orbit? If they revoke the license, do the satellites have to stop orbiting immediately?
Good, clear, unambiguous, effective and enforceable rules are usually not trivial to create and deserve at lot of thought and review.
This is true
his is slashdot, People fantasize about new rules for breakfast.
First, talking about rules is how you do a lot of thought and review. Secondly, most of what happens on Slashdot is describing the new rules at a very high level. Clarify, disambiguation, and enforceablity details (e.g. closing loopholes) comes later.
My time writing rules was spent in international standards development where there are a few hundred engineers reviewing your words. In English it is easy to unwittingly be ambiguous. I did a lot of rewording the rules to be unambiguous and clear. Avoiding words like 'it', use of 'and' and 'or' in ways that could be taken as boolean or non boolean ands and ors, the use of 'or' that could be taken as exclusive-or or inclusive-or and lots of other ambiguous forms.
Also the semantic content needed to make sense, be consistent with the rest of the document, be enforceable, testable, and have a direct purpose.
Slashdot Mirror
It's not necessary to be a politician, merely just a well known public figure.
Oops, I did it again
I haven't actually played the game, however, I would think that such a character would be covered as a 'political satire' even if they exactly took her image.
L.L. is a politician? Cool.
>Failed power steering adds resistance, making the car even harder to steer.
Yep, it required a lot of torque to move the wheel. It wasn't safe to drive.
> From what I've heard, a pure manual steering car designed around a plain rack and pinion setup gives a lot more tactile feedback and is more-pleasant to drive.
The effect is not dramatically different, but it does feel a little more connected.
I had exactly this flaw happen in an old Subaru. I was left with a difficult to steer car. I don't remember a recall for it. So Tesla seems to be more diligent.
Photo op for politicians. No laws were broken, at least no one has cited one law that was broken. .
https://www.gov.uk/data-protec...
The UK Data Protection Act. 1998.
That's the law that was broken.
>His business model was founded on undermining the concept of intellectual property.
His business model was selling cloud storage.
The RPi sucks a bit for real time control compared to say an Arduino, because it's running Linux and a CPU with less deterministic timing that the slower, simpler CPU in an arduino. I've tried direct control of steppers with a Pi and it gets jerky when the CPU is running a UI or doing other stuff.
So arduinos seen to be the board of choice for motor control in homebrew CNCs and 3D printers, while RPis do nicely doing the thinking (interpreting gcode, presenting a UI, etc). An RPi driving 3 or 4 arduinos, driving 3 or 4 steppers is a common configuration.
There are far better engineered solutions when you sprinkle in a little hardware for motor control, like an FPGA to do the timing and feedback tracking. But software and cheap CPUs are cheaper and more accessible to hobbyists.
>US Charges Iranians For Global Cyber Attacks on Behalf of Tehran
This makes it sound like the US is doing Tehran a favour by doing some of their legal work for them.
I left right around the time of the redesign Mr. 5,271,228.
There have been so many to choose from Mr 1,312,635.
>and it was a lot easier to make semiconductor chips
If you have 6 biliion dollars to spend on equipment
Get this guy a hacksaw.
But in all seriousness, that's seriously awesome. Was this wet AMD or dry AMD? Because the description doesn't sound like either one.
What? People who get AMD go blind? A reason to buy Intel maybe. Then you won't go blind or lose an ARM.
Since it's reported that the License is Apache 2.0, it can't be Linux, which is GPL. You *may* be able to put Apache 2.0 code under GPL, I'm not sure, but you can only put GPL software under Apache if you are the copyright holder.
Of course, they could be violating the license, I suppose.
Companies with lawyers like Apache 2.0 because of the clauses that say something to the effect "If you sue me, you lose this license to this software".
Only in a state that doesn't charge a business property tax.
This is news to me. Source?
Lots and lots of studies. Go look them up.
Yeah, but you do it with panache. Or is it grenache? It's one of those, I'm pretty sure.
Down int' these parts we call it cranberry juice.
We've got some pretty good ghormez sabzi in the states. The tech is awful though.
And we used to roast pedants around here too.
Sadly, standards are slipping.
That's ok. He was being pernickety. I'm being the pedant in this post.
>by placing sea-based cruise missile launchers on European soil
Wut? Sea based is in the sea. Soil is on the land.
Strictly speaking it is not hacking at all, but cracking.
Indeed. I wondered why the government was punishing people for diligently solving problems.
The code I write is usually analysis code for me to do my job. It's not for use by others.
I sometimes release public code for use by others. E.G. Crypto library support.
My large employer has failed to employ someone who can jump into my job so far. If I get hit by a bus or win the lottery, it's likely to be a problem for my employer.
I program for my job, but at no point did my choice of language have any relevance to my pay.
My expertise in the domain of the things I design and the efficacy with which I do my job is what determines my pay. I don't think people usually know what languages I program in.
As long as the owner of the satellite is a US company, then they are subject to the US licensing laws. If Swarm wishes to relocate to, say, South Sudan, which probably doesn't have a well developed regulatory environment, then they can get a South Sudanese radio license. And operate from South Sudan, have their corporate headquarters in South Sudan, etc.
Needs a license to do what? Sit around while their satellites orbit? If they revoke the license, do the satellites have to stop orbiting immediately?
I'll see your inertial confinement and raise you a polywell fusor.
From the article linked to in the summary:
The FCC is responsible for regulating commercial satellites, including minimizing the chance of accidents in space.
In the USA presumably.
I assume Swarm Technologies can simply keep buying launches from non US providers.
This is true
First, talking about rules is how you do a lot of thought and review. Secondly, most of what happens on Slashdot is describing the new rules at a very high level. Clarify, disambiguation, and enforceablity details (e.g. closing loopholes) comes later.
My time writing rules was spent in international standards development where there are a few hundred engineers reviewing your words. In English it is easy to unwittingly be ambiguous. I did a lot of rewording the rules to be unambiguous and clear. Avoiding words like 'it', use of 'and' and 'or' in ways that could be taken as boolean or non boolean ands and ors, the use of 'or' that could be taken as exclusive-or or inclusive-or and lots of other ambiguous forms.
Also the semantic content needed to make sense, be consistent with the rest of the document, be enforceable, testable, and have a direct purpose.
With a few years of practice, it becomes easy.