|
Chairlift - Bruises[^]
One of my favorite songs ever.
Got stuck in my head this week and I've been listening to it daily 
Quite catchy.
Just watch out you don't fall for it and bruise your knees 
|
|
|
|
|
Bookmarked yet again.
But my sounds of the week, at least this week are going to happen today in the evening.
I'm seeing God Is An Astronaut for the third time, today.
For those who don't know them, this video/song has got me into them.
clickety[^]
|
|
|
|
|
Very nice. I came across them not long ago 
|
|
|
|
|
I like that song. I usually listen to that kind of music when I'm driving or want to chill 
But my song for the week would be "slither" by velvet revolver. Kinda into rock/metal/grunge
|
|
|
|
|
Vincent Maverick Durano wrote: But my song for the week would be "slither" by velvet revolver.
Not bad at all!
|
|
|
|
|
Sander Rossel wrote: Not bad at all!
"Fall to pieces" by velvet is also nice. RIP scott weiland 
|
|
|
|
|
Meh! But this comment is just genius ...
Quote: all I hear is white and gold.
I am not a number. I am a ... no, wait!
|
|
|
|
|
Why is that every song you post here sounds like a direct rip-off of something else?
You should look for a Cure, no matter how much you Love Cats
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Because everything sounds like a rip-off if you want it to? 
|
|
|
|
|
Dawdling network check about marine carnivore. (9)
|
|
|
|
|
POTTERING
(Ping around otter)
|
|
|
|
|
Duncan Edwards Jones wrote: POTTERING
(Ping around otter)
We have a winner ...
|
|
|
|
|
PSHARKING?
(But it doesn't seem to be a word...)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: PSHARKING?
(But it doesn't seem to be a word...)
No, but it should be! I shall be writing to the O.E.D.
|
|
|
|
|
Get them to add contrafibularities at the same time!
C is for Contrafibularity[^]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
|
No, not me. My favorite little microprocessor. It was introduced in 1976 by RCA. Only a few years after the microprocessor was officially invented, it offered some features which made it very innovative at the time. Too innovative for some people who called it 'strange' or an 'odd beast'.
Like its predecessor, the (two chip) CDP1801, it was built in CMOS technology. RCA built the computers for space probes and became a pioneer in CMOS (they called it COSMOS  ) technology because CMOS offers higher noise immunity and extremely low power consumption when compared to other technologies. It also was considered o be slow, because those advantages are based on pairs of MOSFETS (CMOS transistors) doing the switching in the gates. Also, needing twice as many transistors for a gate was not helpful with the very limited densities on a chip.
Today practically everything is CMOS. Processors use billions of MOSFETS and at their high clock frequency they get very hot, despite the low power consumption of CMOS. They would instantly burst into flames if you could magically change the technology.
Besides driving a (relatively) typical microprocessor bus, the CDP1802 offered a few general purpose IO lines which could be controlled by machine language instructions, like microcontrollers. Later versions even had onboard ROM and RAM, resembling a modern microcontroller even more. This hybrid design may appear strange, but it allowed to build very compact single board computers with only very few ICs besides the CPU itself. In my old computer a single output bit did triple duty as rudimentary sound generator, the output signal to the cassete recorder to save programs and the output line of the RS232 serial port. Sound generation, loading and saving from tape and serial communication were done by the CPU in software, only one at a time of course.
And now the 'oddest' feature. The processor does not have many addressing modes. Everything is done by loading an address into a register and access memory over this pointer. Addressing modes are emulated by manipulating the address in the register. Period. That's it. The processor does not even have a stack pointer or a program counter, just generous 16 general purpose registers. You just load an address into any register and designate it to be the program counter or stack pointer. Back then people had no other word than 'strange' for this. It appeared to be spartan, almost primitive. While there was lots of room for improvement, it also easy to understand. I probably could get most people here to write machine code for this little processor within an hour. Later, a similar concept became very sucessful. The most widely used processor of all times uses it and even Intel CPUs use it to implement their complex instruction set in microcode. It's not called 'strange' anymore. Today it's called RISC.
For a few months I have now been designing a 'reboot' of my old computer. It shares much of the old design, but drops the anachronisms. How about a real serial port instead of letting the CPU tag along with 300 baud? How about up 16 megabytes ROM and RAM. Or perhaps delegating IO and graphics to separate CPUs and letting the main CPU run full blast without having to care about interrupts or DMA?
Of all things, the keyboard is still a problem. Kyboards with their own encoder that hook up to the parallel port can only be found in museums. Instead, I could
- Butcher a cherry keyboard for he key switches, pay a chip collector a generous ransom for the (hopefully functional) encoder (a CDP1871), make a costly circuit board and build a brand new oldschool keyboard. This will be somewhat expensive, but easily last another 40 years.
- Program a microcontroller or use a handful of cheap discrete CMOS ICs to build a PS/2 port. I have some PS/2 keyboards lying around and as bonus I can also add a mouse port. This option is not too expensive, but a little too modern for those who like everything to be 'original'. On the other hand: I have a complete and functional old computer which will be left as it is.
- Something really unusual, like tearing the microcontroller out of a PC keyboard, hooking up the key matrix to the CPU bus and an input port. Then the CPU can make dummy memory accesses to scan the keyboard's columns and monitor the input port for responses on the keyboard's rows. This costs next to nothing if you have a keyboard to butcher, but the keyboard will be connected over a wide and awkwardly short ribbon cable. Besides that, the CPU will have to scan and decode the keyboard constantly.
This really is fun. After all those years I finally get my old computer as I always wanted it. Simply buying a Raspberry Pi or something like that would be boring.
Would this little project be of any interest as an article or shall I leave you alone with this dusty oldschool stuff?
Edit: Oooops. This got longer than i thought.
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."
If software development were a circus, we would all be the clowns.
modified 14-Jul-16 4:54am.
|
|
|
|
|
Write an article about about this nerdgasm?
By all means do, please, pretty please, pretty please with a cheery on top! 
"I had the right to remain silent, but I didn't have the ability!"
Ron White, Comedian
|
|
|
|
|
Manfred Rudolf Bihy wrote: Write an article about about this nerdgasm?
Definitely. When I started soldering in 1978, the short era of homebuit computers already was coming to its end. It was a great time for Nrds. There were no rules and everybody built or programmed something as he thought it was right. And then you presented your results to other nerds who immediatly started improving it or discussing it to death. The first software I bought was a debugger and I remember calling the man who wrote it all across the US to talk about some changes. My parents grounded me and took away the computer when they got he telephone bill.
I used the spare time in my room to build a small Z-80 computer from my parts box
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."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
|
Article, definitely! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Reminds me of the ZX81 I put together along with hard wiring an old surplus IBM keyboard to use with it.
|
|
|
|
|
So we are looking at the revers engineering of a major users engine that is so unwieldy it can no longer be supported. It take a minimum of 3 months to change and test a rule!
As it is a very large core requirement it will be done by the IT team. They are proposing Java over a Hadoop data store using Drools as the rules engine. As my experience in this area is extremely limited I put it to the hive mind.
Is Drools a viable rules engine for a very large and complex set of rules. I fear it is like Biz talk is to ETL, designed for "power users" to maintain!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
That sounds like CVDD (Curriculum Vitae driven design) going on right there...
|
|
|
|
|
Thankfully I won't be coding this one, just trying to ride herd on them from a design POV.
Never underestimate the power of human stupidity
RAH
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
