At least 3 co's featured robots or androids (lower-case) in their ads. The child-bot was featured twice, and creepy both times. Hawking insurance I think.
Another bot ad was a big cellphone telecom, I forgot which; and a 3rd was somebody worried about a robot taking his job during a bad dream. I think it was hawking a home security system. It had a dumb catch-line along the lines of: "You have enough worries outside, at least make your home secure."
Rumor has it that Siri's AI is kind of out-dated and clunky. There may have been an internal debate about whether to incrementally retrofit the existing system, or deprecate it and start over. I suspect Stasior advocated for incremental, but seems the brass felt otherwise.
The video doesn't show any extra sensors, so I'm assuming the arm only has motors and encoders to determine how far the motors turned. So how did the robot know...?
1. Make the baby "cry" when it's not really crying to mess with the parents.
2. Make the baby say phrases that borderline actual English and random baby gibberish. "I make doody shaped like Daddy's head" and the like. The parents will look at each other and go, "Did I hear what I think I heard?"
3. Have the baby fart loudly when guests are over.
I disagree with a vast majority of "his" policies, but this one he got mostly right. H1B's were being used for IT "bodyshops" of de-facto indentured servants instead of what they were intended for: hard-to-find specialists. Kudos to the obnoxious wall-less one.
A found a box of my old clothes. Other than size issues (shuddup), they came back in style. The new UX/UI's resemble the original Mac. In a few years, the Windows 95 look may be back too. And then the flashing Geocities look with rotating logos... Gag me with a groovy spoon.
If some bug or malware afflicted masses of planes, trains, and/or automobiles at the same time; it could clog up a large portion of the population's commute, commerce, and emergency handlers.
Many orgs inadvertently/incompetently hard-wired their applications to IE10 and it may not be easy to convert. In some cases it's Active-X or Silverlight dependency. They will be ticked.
all the young programmers can't believe the demo when my system can do something in half a second that usually takes 10 times longer using something else.
Do you mean development time or run time? I'll assume you mean runtime. In certain domains raw execution speed matters, such as video display drivers, but not in most I know. The bottleneck is often inter-layer communication, such as DB-to-app, app-to-network, etc. You may argue we don't need lawyers, I mean layers, but that's a different topic.
There's usually multiple factors in weighing tool-sets, and app speed shouldn't be the overriding factor most of the time. Don't heavily focus on a single factor above others unless it's actually important in the domain.
Microsoft.NET Core breaks away from the "Windows Only" mold and literally gives us a near-universal runtime where solutions can run on the backend of your choice. And it's all FOSS, including their editor, Visual Studio Code, which many developers have made their de facto JavaScript editor. All this while Oracle is rounding up its corporate customers and fleecing them for even more licensing fees for any Java implementations.
Sounds great on paper, but MS often sneaks in tricks and gimmicks that lean you toward Windows without you even knowing it (until it's too late). MS's 30+ year reputation for vendor-lockin shenanigans will be hard for IT shops forget.
Granted, Oracle also has been playing games, jerking around with Java on the legal front, and that's part of the reason for the growth of Python.
I remember reading that there were known spots on the circuit boards such that if that spot cracked due to the cold, the entire rover would fail.
They were known weak-points which lacked redundancy, but the cost of the avoiding them was considered too high. The rovers have roughly 90% redundancy, but approaching 100% apparently has a steep cost curve.
For example, at some point the redundant systems have to coordinate with each other to make sure both are not trying to do something at the same time, which could waste power or put noise into instrument readings. These coordination points are not easy to also make redundant. You need redundancy handlers to manage the redundancy handlers in almost a fractal way, requiring redundant "turtles all the way down", filling the rover with bunches of circuits.
Slashdot Mirror
How much did they pay you to be in that ad?
At least 3 co's featured robots or androids (lower-case) in their ads. The child-bot was featured twice, and creepy both times. Hawking insurance I think.
Another bot ad was a big cellphone telecom, I forgot which; and a 3rd was somebody worried about a robot taking his job during a bad dream. I think it was hawking a home security system. It had a dumb catch-line along the lines of: "You have enough worries outside, at least make your home secure."
May you drink lumpy milk.
Kind of reminds me of this.
The worst ad was the lumpy milk ad. Nobody wanted to eat snacks after that. The co's with food ads should sue them.
I tried to use a Fitbit to cheat, but having to move my legs gave it away.
Oracle's API lawsuits and other shenanigans means that no big co will want to bet the farm on it.
Rumor has it that Siri's AI is kind of out-dated and clunky. There may have been an internal debate about whether to incrementally retrofit the existing system, or deprecate it and start over. I suspect Stasior advocated for incremental, but seems the brass felt otherwise.
Robot: "Alexa, what am I?"
He blew an opportunity:
1. Make the baby "cry" when it's not really crying to mess with the parents.
2. Make the baby say phrases that borderline actual English and random baby gibberish. "I make doody shaped like Daddy's head" and the like. The parents will look at each other and go, "Did I hear what I think I heard?"
3. Have the baby fart loudly when guests are over.
I disagree with a vast majority of "his" policies, but this one he got mostly right. H1B's were being used for IT "bodyshops" of de-facto indentured servants instead of what they were intended for: hard-to-find specialists. Kudos to the obnoxious wall-less one.
How is that news? The "other guy" or the "other party" is always to blame for every unpleasant event. Politicians point fingers out of reflex.
Grab them by the ... cat.
No headphone jack and non-replaceable batteries. Actually, the iStogie has a jack.
E-Cigarettes are obsolete. F-Cigarettes and G-Cigarettes are already shipping. Get with the times or be outsourced to cheap hungry countries.
A found a box of my old clothes. Other than size issues (shuddup), they came back in style. The new UX/UI's resemble the original Mac. In a few years, the Windows 95 look may be back too. And then the flashing Geocities look with rotating logos... Gag me with a groovy spoon.
I wonder how that might affect a prominent politician?
You are assuming that jerks/nuts are usually rational and non-suicidal.
If some bug or malware afflicted masses of planes, trains, and/or automobiles at the same time; it could clog up a large portion of the population's commute, commerce, and emergency handlers.
Many orgs inadvertently/incompetently hard-wired their applications to IE10 and it may not be easy to convert. In some cases it's Active-X or Silverlight dependency. They will be ticked.
Do you mean development time or run time? I'll assume you mean runtime. In certain domains raw execution speed matters, such as video display drivers, but not in most I know. The bottleneck is often inter-layer communication, such as DB-to-app, app-to-network, etc. You may argue we don't need lawyers, I mean layers, but that's a different topic.
There's usually multiple factors in weighing tool-sets, and app speed shouldn't be the overriding factor most of the time. Don't heavily focus on a single factor above others unless it's actually important in the domain.
Sounds great on paper, but MS often sneaks in tricks and gimmicks that lean you toward Windows without you even knowing it (until it's too late). MS's 30+ year reputation for vendor-lockin shenanigans will be hard for IT shops forget.
Granted, Oracle also has been playing games, jerking around with Java on the legal front, and that's part of the reason for the growth of Python.
Go ahead and put FireFox in the spotlight, M$.
Mexico won't pay for FF's advertising, but it looks like M$ will.
Is a "Gluein Award" like a Darwin Award for devices?
I remember reading that there were known spots on the circuit boards such that if that spot cracked due to the cold, the entire rover would fail.
They were known weak-points which lacked redundancy, but the cost of the avoiding them was considered too high. The rovers have roughly 90% redundancy, but approaching 100% apparently has a steep cost curve.
For example, at some point the redundant systems have to coordinate with each other to make sure both are not trying to do something at the same time, which could waste power or put noise into instrument readings. These coordination points are not easy to also make redundant. You need redundancy handlers to manage the redundancy handlers in almost a fractal way, requiring redundant "turtles all the way down", filling the rover with bunches of circuits.