Become a fan of Slashdot on Facebook


Forgot your password?

Comment Re:If I was Microsoft, here's what I'd do. (Score 1) 90

I think either yours or my idea or even both would be a good move to add more Windows Phone users.

Realize that I don't necessarily believe that more Windows phones are automatically a social good; I just believe that if that were Microsoft's goal, the way to achieve it would be for Microsoft to encourages developers to target them as a platform. This would incidentally benefit Microsoft by having developers target their code to Microsoft's IDE, rather than X Code or Eclipse.

Again, this is only about Microsoft's best interests in regard to establishing market share, and not about what I believe is necessarily a social good.

Comment Re:If I was Microsoft, here's what I'd do. (Score 1, Insightful) 90

I'm not sure if this is legal or not, but if they made an iOS and Android emulator so you could run both iOS and Android apps on the Windows phones, some people might get a Windows Phone then who'd otherwise be getting one or the other because they figure they get all types of compatibility.

This would be the third worst tactical blunder of all time. The most famous of which is "never get involved in a land war in Asia" - but only slightly less well-known is this: "Never go in against a Sicilian when death is on the line"!

The correct thing to do is build Windows emulators for iOS and Android, rather than the other way around.

This will cause developers to target their development for Windows, rather than targeting iOS or Android. This get Microsoft native apps, and at the same time, detracts from having those same apps native on iOS or Android.

FreeBSD made the mistake of building a Linux emulation layer for FreeBSD, instead of a FreeBSD emulation layer for Linux, which would have had developers working on FreeBSD native code, rather than Linux native code.

Comment Re:The best summation I've seen (Score 1) 99

They know, but the people paying their bills don't care, so the "don't care" trickles down through the ad networks.

Brand X wants an in your face ad. Ad company Y can persuade brand X with common sense, but then Brand X isn't filled with marketers full of common sense, just avarice. So Ad company Y sells Brand X's "vision" of an ad because Ad Company Y's employees need to eat.

The only way to fix this is to do a eugenics program on marketers.


Comment Re:Pseudonyms have a cost to social networks (Score 1) 232

>And they aren't obligated to provide you with anything.

And I'm not obligated to give them anything either.

>you have no rights to anything they provide.

They put it up for free use. I'm going to use it. If they want to make money legitimately, they can paywall it. They don't arrest the people who walk the shopping mall every day for exercise and don't buy anything.

You really are some sort of fascist.


Comment Re:Documentation is rarely valued as a contributio (Score 1) 683

I can't speak for other people, but personally I do value documentation. Not that I want to spend all my time documenting someone else's work, but when I need to learn about something, documentation is invaluable. No, it isn't as fun as writing code, but that doesn't make it useless. If someone else wants to contribute to FOSS and isn't a coder, but can do tech writing, I for one would appreciate their contribution to documentation.

I value documentation as well.

The problem is that the people changing the code out from under the documentation, so that the documentation quickly becomes out of date, or, worse, incorrect and misleading, is those people who are doing that to the code *not appreciating* the documentation effort.

At worst, there needs to be an agreement that things will stay the same for a while, or for at least a major version number, before the documentation goes out of date. And as you've noted with git: when things grow organically and incrementally, it's going to be near impossible to keep the docs in lock-step with the code -- particularly if the only way to make them match up is reverse engineering the code until you know enough about it to document it accurately and completely.

At one point in time, I wrote a rather complete internals book on FreeBSD; but the OS changed out from under the book too quickly, and so it was inaccurate, except for a particular major revision. And even then, there were sufficient differences even in the point releases (to the odd minor version number) that, unless I'd included a CDROM set or DVD with the book itself, there was no way that it was going to be useful for its intended purpose as a college textbook.

So yeah, documentation would be nice, but it's only going to get there as a divided labor effort if we agree to write design documents up front, and then follow a cathedral model for both the docs and the code that come out of those designs.

I think one of the major problems is that when you make something understandable by documenting it ... it makes it a whole lot easier for someone to step in and know how to "improve" things, until the docs are out of date again. At least, that has been my personal experience.

Comment Documentation is rarely valued as a contribution. (Score 2) 683

If women don't care about making code faster and more compact, maybe they should work on other aspects of FOSS. For instance, most of it could use a lot of help in the documentation department.

Documentation is rarely valued as a contribution. We specifically had to go out of our way to hire a technical writer for Mac OS X to get the man pages covered for the UNIX Conformance requirement. And those were just command line commands, Libc, and the kernel interfaces that had coverage requirements.

It's definitely not valued nearly as well as code. The most common comment with regard to it is advice to "RTFS" and some variant of "If it was hard to write, it should be hard to understand". This is seen in the tools, as well. For example, git is written in such a way that you pretty much have to understand all of it to use any of it. This steepness of the learning curve appears to be intention, and viewed as a merit badge for when someone gets their head around it and Groks it. In the same way that you can do anything in Perl in half a dozen or a dozen different ways, the same is true of git.

Also, your verbal vs. visual thinking bias is showing. Personally, I process software in the same part of my brain that does auditory processing of music (meaning I have a hard time coding if I'm listening to music, as verified by FMRI of the dorsolateral frontal cortex and inferior frontal gyrus, Broca's, and Wernicke's areas, among other areas). Language centers tend to be common for processing both sound and software in many coders.

Ironically, if you are good with languages, you tend to be good with code as well, assuming you have a number of computer languages under your belt to generalize from. But if the tools have a crappy learning curve, then it takes a bit of OCD to be willing to invest the time necessary to overcome it. Staying overnight in a computer lab so that you can get time on the machines is not something most people do these days.

Comment Re:Pseudonyms have a cost to social networks (Score 1) 232

What a load of corporatist bullshit.

>alias users are misfits or troublemakers

No. Fucking NO.

You have the right to call yourself whatever you want in real life so long as you are not trying to defraud anyone while doing this. That this right supposedly suddenly doesn't exist because a corporation demands it is insane.

This does not make you a misfit. It does not make you a troublemaker.

Aliases have a history going back decades online and thousands of years offline. This sudden "hurr, you must use your real name" in a contract-of-adhesion is such bullshit.

You may believe that corporations have special rights to deny you your rights, but I don't, and neither do a lot of other sane individuals.

If Facebook's share price loses a few pennies because people like me use aliases, it's not my problem. They can find another business model.


Comment Re:What kind of dumbass company... (Score 1) 136

Port it? are you really that completely clueless?

You simply fucking compile it with the same compiler flags you used for the first version. Compiling android 5.1 for a 4.4.4 phone is absolutely trivial.

You obviously do not *get* how Android partner companies deal with porting android. Most of the bits for various phones do *not* get integrated back into the main line sources.

Any given android version on any given phone is generally a stable snapshot of whatever was top of tree when the work on the phone started, plus local additions for device support.

Internally, Samsung treats each new phone as a one-off porting job. They've got an entire group that does nothing but one-off ports of whatever is a top of tree to the new phone hardware they are coming out with.

I know you'd love for this not to be the case, but it pretty much is the way things are.

Comment Re: Not wasted (Score 1) 178

I think you are confusing image capture resolution with image display resolution.

It doesn't matter what image image capture resolution you have if your display resolution is orders of magnitude less.

So no, I'm not confusing the two.

>I said 7 years ago

'Splain to me how RI Hospital had access to Retina display resolution. Give three examples.

I'm pretty sure it is you who are confused.


Comment Re:Does the submitter know .... (Score 1) 28

The Isle of Man TT is a thing of fucking beauty.

There is nothing else like it anywhere. Oh yes, there are moto races that are longer and "less boring" to the NASCAR crowd, but if you pay attention for even 5 minutes to this race, you will be hooked like I was.

It is motorcycle erotica. Not porn, erotica.

And they've started racing electric bikes a couple of years ago.


Comment Re: Not wasted (Score 2) 178

>It's probably industrial

Or medical.

X-rays are sent 'round the hospital not on film these days, but as files. 7-8 years ago XGA flat panels and similar were pretty standard at RI Hospital. The thing is, when you have a fracture that is the head of your radius pushed into your radius, it's very difficult to see the actual break with that fuzzy resolution (because it looks normal). After going home with some Oxycontin (urgh, never again) I had to take the actual films to my orthopedist who put them on a wall mounted light-table and then it was plain to see. Even my untrained eye caught it.

If it was an 8k display at RI Hospital, they would have seen it.

(there is nothing you can really do for that kind of fracture anyway except to use a sling when the pain gets irritating - if a doctor puts a cast on you in the ER, go to your ortho and have it cut off the next couple of days, or else you're looking at surgery on your elbow later (my ortho told me this and he was right)).


Comment What kind of dumbass company... (Score 1) 136

What kind of dumbass company is going to spend money porting a new version of an OS to an old platform, with no payday for doing so?

Mobile phone vendors make their money selling new phones. You want a new Android, get a new phone. Your contract will be up in 2 years, and at 18 months, you will be offered a new phone with early renewal, so just wait until the contract is up, re-up the contract, and get the new phone with the fix.


There can be no twisted thought without a twisted molecule. -- R. W. Gerard