You're viewing a single thread.
I always found it fascinating that Darth Vader created C3PO.
C-3PO was a parts kit. It wasn't that Anakin designed his own brand new droid, he gathered enough parts from scrap yards to mash together his own based on schematics that would have been available to anyone who regularly works on droids. In our time it was about as impressive of a feat as building a bookshelf out of lumber you salvaged from a local dump pile. Impressive for a boy that age, but anyone with the time and tools could do it.
In our time it was about as impressive of a feat as building a bookshelf out of lumber you salvaged from a local dump pile.
Ehhh, I would say it's probably more like assembling a functioning PC out of various parts found in dumpsters, etc. Definitely a much more impressive feat imo
I'd say assembling a functional PC from dumpster parts is far far far far far easier than even building a bookshelf from raw lumber. Computer parts are designed to go together (excepting Macintosh computers of course). You just have to wait for one that functions.
From well kept recycled parts which are labeled? Not much of a challenge.
From DUMPSTER parts? I'd say that's more impressive, as you need the knowledge and tools to know what works and what doesn't.
Yeah, sure, given a limitless timeframe, you can sit there until you get lucky enough for someone to drop a completely functioning but disassembled PC on your lap. But building one? You might need to clean parts, research what they are to get the proper drivers and OS even if you manage to find a set that actually fits together. Tracking down and fixing tiny shorts in circuits? That's not the same skills as putting together some Legos.
I've been in IT support in cities and schools and even when there's a massive pile of computers and hardware that are known to not be broken, it's sometimes a challenge.
You know how hard it is building a bookshelf? Take a piece of wood. Put book(s) on it. Now you've a bookshelf.
So many electronics are thrown out every day, that I'd wager you could find everything you need in just a day. The biggest issue is that they throw things in dumpsters, rather than gently putting them there, which tends to break electronics. But then again there's so much garbage you could probably find ten of every component and see what works
and things are usually thrown out cause they are new and work great
Do you want to build a computer or a brand new computer? And no, most PCs are not thrown away because all components inside stopped working. It's usually either because they're too slow for the user or just one component broke and the user was incapable of fixing the problem and opted to get a new faster machine instead.
gonna be in there trying to adjust pins or blown supplies for all eternity, attempting to cobble together a working machine out of mystery problems. people throw shit out because it is trash. not even taking into account the fact that computer parts arnt just plug and play on all boards.
My son is about Anakin's age from SW I. LOL, he's too uncoordinated to learn a box knife, let alone a power saw.
fr people waaaayyy downplaying anis skills here lol
Red oak. Hand cut on an antique mitre box. Fuckin miserable lol. I'll build computers all day.
Who said it needed to be a nice bookshelf?
My fascination is with the derpy friendly nature of C3PO and him aiding in his own creators downbringing. The stark contrast between Vader and C3PO. One would not assume they were related. Im indifferent to Anakins tech skills.
I guess the implication is that given it's a kit build, anyone else building to such schematics would get a droid with the same derpy friendly nature since that's presumably what it's designed to be like.
The other protocol droids we meet are a lot less emotional. They're all business, don't speak unless spoken to most of the time. They wouldn't brag about being programmed for over 6 million types of communication. They wouldn't get into an argument with an R2 unit. They wouldn't mourn their masters being crushed by a trash compactor.
Well I must admit I've only really seen bits of various Star Wars films save for being taken to see Episode 1 as a kid so I don't really know much about it, besides what you can pick up from pop culture, I was just following what seemed a logical inference. Are "protocol droids" one and the same as whatever C3P0 is? I guess I figured a "kit build" in my mind is something like an amateur, enthusiast's project for kids or something so the fun and silly "personality" would be part and parcel with that design while ubiquitous robots made for more serious utilitarian reasons would I guess be less inclined have such features as they'd not be of great use to anyone.
Protocol droids are butlers, ambassadors, and receptionists. "I am fluent in over six million forms of communication." He's a translator. Luke's uncle bought him to translate R2-D2's beeps and whirrs into basic (the language Luke speaks). On starships, they're used for jobs like communicating with highly alien life forms, serving drinks, and delegating to droid crews. Jabba the Hutt has a protocol droid to translate for him, because he thinks he's too important to deign to speak basic like some commoner, and not every visitor knows Huttese. After Anakin meets Padme, he ends up giving C3PO to her, because as a queen/senator/ambassador, he's way more useful to her.
In short, Anakin made a super fancy high society robot that's mostly useless for any kind of manual labour, and made him way more annoying than diplomat robots are supposed to be.
And this makes a lot of sense, because Anakin's day job is working on pit droids and other kinds of useful technology. He's an expert on that. Anakin's hobby project was something completely useless to him and his boss, made from parts that nobody cared about. But making a fancy domestic servant robot to help your mum out around the house is a really sweet thing for a kid to do.
He also built a race car. And won a race with it.
Red neck rockets strapped to a chair that drift vs recycled multilingual protocol droid.
Going to have to know information to make a determination.