|
not sure what you're saying? You believe that continued punishment is the answer because "they will learn eventually"?
Well that is true. That's exactly how torture works on people. Continued abuse to break the will to resist. That sure works! good on you- totrure your kids for a quiet life (and your dog, too, by the sounds of it!)
Incidentally we have three dogs, none of which poo in the house, and none of which have had their noses rubbed in it, ever. We just trained them - and in fact it is quite easy because generally animals don't sh*t in their dens anyway.
Michael Martin wrote: Getting a flogging when we got caught was par for the course and taught us either not to do it again or at least not get caught by parents.
So what was the point of the flogging? it didn't stop the behaviour - isn't that what your parents wanted? Or did they just not want to know?
Michael Martin wrote: Never did me no harm
You're sure about that?
Michael Martin wrote: even the f***wits from the 70's are better people than 95% of the helicopter parented no idea protected from themselves twat coming out today.
Taking it to extremes doesn't help! You can go too far in any direction - and I do know parents whose kids are absolute monsters - but that's not because they don't hit them, it's because they let them do whatever they want without boundaries - so they know they can get away with anything as mum and dad will just tut.
Depending on the child, it is perfectly possible to explain to them the consequences of their actions, stick to known, discussed boundaries, and consequences.
for example - taking a teenager's phone from them for a day is a far worse punishment in many cases than beating them - and has far fewer problems.
Michael Martin wrote: interrupting my or my wifes work day or weekends. I told the school to either cane them or get f***ed. They chose themselves to get f***ed
What excellent parenting skills, and a great example to your children!
If instead you had supported the school, gone out of your way a couple of times, your kids would know jut how pissed off you were with them having to take them to school on a Saturday, and would try to avoid it (and hopefully not because you belted them for getting a detention!)
As it is they are in the position of knowing the school cannot give them a detention, and so behaviour modification is out the window!
Honestly, if I was that school I'd consider just phoning you to confirm whatever behaviour was at issue, every time, and let you deal with it in your own way. Sounds like your kids are probably scared enough of you that they would try to avoid that at all costs!
PooperPig - Coming Soon
|
|
|
|
|
My son is using the "naughty corner" style on his little terrors. When we looked after them it was, you muck up and granpa will whack you, hard. It only took one good whack and they behaved all weekend.
A little pain is a great educator.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
On the positive side, it could have read "I IS Not aloud....".
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
|
|
|
|
|
She got all F's... I can see where she got it from
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
They don't speak English in the Americas, anyway. The degree of upward screwing of the language isn't as important as the fact that the language is screwed up.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
According to Wikipedia, this piece of history clocked at 3.25 MHz. I'm having a hard time believing that, when a VIC-20 clocked at 1Mhz, a BBC Micro 2MHz.
Can anyone confirm this?
Regards,
Rob Philpott.
|
|
|
|
|
|
It sounds possible. The 8080 on which the very first IBM PC was based, clocked just north of 4 MHz. This was late 1970s technology.
|
|
|
|
|
The ZX-81 used the same processor as the ZX-80: a Z80A @ 3.25Mz. (or the NEC µPD780C-1 equivalent, depending on the manufacturer stock).
This was not as fast as it sounds in comparison to the BBC and VIC-20 as the whole thing was designed to be as cheap as possible and was horribly slow.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: This was not as fast as it sounds in comparison to the BBC and VIC-20
Why not though? Both 8 bit processors presumably with similar instruction sets (I'm familiar with the 6502, not the Z80), so I would have thought that clock speed would be a good indicator of performance.
Regards,
Rob Philpott.
|
|
|
|
|
Processor is only one part of a system: think how slow a Windows PC gets if you have too little RAM, for example.
The ZX81 had only four chips IIRC - processor, RAM (1K), ROM (8K), and a programmable logic chip to tie it all together and provide the chip selects etc.
The BBC had a lot of hardware to do things the Sinclair had to do in software - so more instructions need to do the same task.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
No. The 6502 actually was a snail when compared to a Z80 at the same frequency. Then again, in such contests algorithmic optimizations often had more effect and triggered the next round when the opponent did the same optimizations on 'his' processor.
It has been decades since I wrote code for a 6502, but from my deepest memories comes 'zero page addressing' as one of the causes of the 6502's slowness.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
|
|
|
|
|
CDP1802 wrote: but from my deepest memories comes 'zero page addressing' as one of the causes of the 6502's slowness
I might be a bit old now, but wasn't the point with Zero Page Addressing that you only needed two bytes instead of three when addressing and thereby making it 30% faster if you could fit the core of the code into the first page?
Personally I remember swearing over just having three registers.
|
|
|
|
|
Yes, I think you are right. It has been a while, but not so long I used a C compiler for the 6502 to write some stuff for the 8 bit Ataris and a C64. The author of the C compiler also did not think that the 6502 was ideal for C. Nor any other 8 bit processor, I think. Still, it's real fun to chase some oldschool sprites around the screen with C.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
|
|
|
|
|
Also, the Motorola 6502 and Intel 8080 used the clocks differently - the 6502 was '2 cycle' and the 8080 was '4 cycle' for the same instruction processing unit, so 1 a 4 MHz 8080 was *roughly* equivalent to a 2 MHz 6502.
According to my calculations, I should be able to retire about 5 years after I die.
|
|
|
|
|
Other sources seems to be reporting the same CPU speed.
I'd rather be phishing!
|
|
|
|
|
Yeah that's a little hard to believe. But if you go to this[^] vintage site they say the same thing.
New version: WinHeist Version 2.1.0
My goal in life is to have a psychiatric disorder named after me.
I'm currently unsupervised, I know it freaks me out too but the possibilities are endless.
|
|
|
|
|
I think he had a 6.5MHz clock, the 3.25 being derived from it for the processor.
|
|
|
|
|
Yes, that bit makes sense. I think computers of the day tended to have the cpu on one clock cycle, the graphics chip on the next. It's just the speed that surprises me.
Regards,
Rob Philpott.
|
|
|
|
|
Just checked and it is also documented in the English wiki. My source was a French site for Vintage computing technology.
|
|
|
|
|
The 6502 was a RISC CPU running at max 1MHz and you can think an average of 2-3 cycles per op.
The Z80A was more a CISC CPU running at max 4MHz.
Let's say the Z80 was a bit more sophisticated and easy to program than the 6502, which was much like a bunch of raw flip-flops...
Just kidding: loved 6502!
|
|
|
|
|
Mario Vernari wrote: The 6502 was a RISC CPU
Urgh! You've opened up a can of worms there. I fall into the CISC camp.
Regards,
Rob Philpott.
|
|
|
|
|
Aaaargh!
The 6502 was no RISC CPU! Look at it's register set and addressing mode. Does not really look reduced, right?
Could it be that you mean the CDP1802, which probably really was the first RISC CPU on a single chip. The predecessor, the CDP1801, still was made up of two chips. And by the way, it also was one of the earliest CMOS CPUs.
Both things made it unpopular. CMOS was considered to be slow and RISC (for lack of the proper words) was usually just called 'weird'.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
|
|
|
|
|
Well, you're right from a theoretical viewpoint. From a practical one, 6502 and other cores such as the Motorola 6805 and big bros were RISC when compared to Z80 and Intel's.
The internal architecture and the BUS was even much simpler than Z80.
Thanks for point it out, though...it's roughly 30 years I don't use them...
|
|
|
|
|
Who told you that? RISC does not really mean that a processor is inferior and only has a spartan instruction set.
A RISC processor usually has a large set of general purpose registers, CISC processors have a small set of registers, each dedicated to a specific purpose. In this respect the 6502 is definitely CISC.
A CISC processor usually has many different address modes and several variants of each instruction to support different combination of source parameter and destination parameter addressing. In this resprct the 6502 again is CISC. A RISC processor does not have all those addressing modes and emulates them over the general purpose registers. The 'reduced instruction set' means only that there are not a hundred variants of each instruction to support all the addressing modes.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
|
|
|
|