Oops! Mea culpa. Note to self: watch the video before you post it!
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
It was to keep
Now, why would they be asking about a gitHub gist?
I'll bet one of Uber's own developers leaked the key. Presumably, by accident.
I guess they are doing it because descriptive TLDs makes search a tiny little bit less necessary.
On the other hand search - or at least search that might deliver relevant results rather than the spam that Google delivers - would make DNS almost completely unnecessary
Google isn't likely to give us that kind of search. Ever.
Google Scholar notwithstanding.
I think HT actually came from Motorola's designation for their hand-held transceivers, e.g. HT-100. And "Handie-Talkie" is the term that Motorola used, check old product literature.
Motorola trademarked the term (in different forms) in 1948 and 1960.
The absence of this from the summary is what led the GP to ask his quite reasonable question.
You're supposed to read the actual article before opening your yap.
And, as others have noted,
No, he wasn't "nabbed" without process.
The GP never implied that he might have been
Yes, he did. He asked if the guy was "actually" extradited.
What part of "extradited" did you not understand? No, he wasn't "nabbed" without process.
He was arrested in The Netherlands, and the Dutch agreed to extradite him.
My guess is that the 'most dangerous' toy would be a marble.
Small powerful magnets. If you swallow two a few hours apart, you run a real risk of death. Swim goggles would be my guess for #2.
Serialized workflow is the enemy of scalabilty. I would do it in many circumstances because the benefits of the tool (Word in this case) outweigh the costs of the workflow it requires. But I wouldn't confuse that with consciously choosing a serialized workflow.
It many cases were a customer of mine has multi-user editing problems, I find that the root cause is that they store bits of information with different use patterns in the same document. Simply splitting the document often fixes the problem.
Git and SVN are different products. SVN is centralized and git is distributed. If you want to create a centralized repository and only allow people to have access to certain parts of it, SVN is a much better fit for that workflow. Neither allows the user to browse the document repository with first checking it out. Well, they both have web interfaces, but those don't support a good editing workflow.
That's not the whole story. Unfortunately, very few vendors in the market see value in the old fashioned "build a better mousetrap and the world will beat a path to your door" philosophy. Instead, most have some strange profit angle that ends up reducing the utility of the stuff they sell. You see too many ad-ladened smart phone apps, subscription services, or good ole' vendor lock-in in the affordable stuff.
For example, I have a garage door opener that has automation features. Unfortunately, every time IOS or Android update, either me or my wife can't use the smart features for a few months. They have a halfway decent app, but it will never be integrated with anything else and they won't publish an API spec to allow me to use an alternative method of control. This is very short-sighted. Opening up an API won't make the geek money rain down on you tomorrow, but if a critical mass of vendors do it, the market will mature to the point where you can put something together out of cheap components.