Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

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).

×

Comment: Necessity of search (Score 1) 165

by jtara (#49154399) Attached to: Google Taking Over New TLDs

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.

Comment: Re:HT? (Score 2) 131

by jtara (#49133127) Attached to: Developers Disclose Schematics For 50-1000 MHz Software-Defined Transceiver

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.

http://tmsearch.uspto.gov/bin/...

Comment: Re:Extradition? (Score 1) 88

by jtara (#49084081) Attached to: Russian Man Extradited To US For Heartland, Dow Jones Cyberattacks

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, ..tse would have been rude. I was relatively nice, but unforgivingly direct. I mean, not even Linus-rude. Heck, I might not even have been Matz-rude, and that's not very rude! It's /. Respect the culture.

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.

Comment: Re:You are asking the wrong queston... (Score 1) 343

by Jaime2 (#49074837) Attached to: Ask Slashdot: Version Control For Non-Developers?

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.

Comment: Re:You are asking the wrong queston... (Score 1) 343

by Jaime2 (#49074491) Attached to: Ask Slashdot: Version Control For Non-Developers?
You are trying to shoehorn the process into one that works with the limitations of desktop document editing programs. Switching to collaborative editing solutions, or moving the data from documents to databases would likely bypass the need to restrict the process to one editor at a time. I'm not saying that either is a better solution than your suggestion, but I have shown that what you are suggesting is only one of many ways forward.

Comment: Re:Use GIT (Score 3, Insightful) 343

by Jaime2 (#49074421) Attached to: Ask Slashdot: Version Control For Non-Developers?

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.

Comment: Re:There's a reason the REAL gear is expensive (Score 1) 248

by Jaime2 (#49050905) Attached to: Smart Homes Often Dumb, Never Simple

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.

Avoid strange women and temporary variables.

Working...