Follow Slashdot stories on Twitter


Forgot your password?

Comment Re:It's pretty simple, really. (Score 1) 684

I'm not so quick to believe it happened so shortly afterwards (the relationship) when there's some evidence to suggest that might not be true.

Either way though, it's not a review. This is the problem: the entire thing was based on a false premise.

Also, I think you may be looking at it with a little bias.

I'm not sure what qualifies as bias in this context. Most of what I've read about gamergaters paints them in a rather poor light. So these days I'm biased against them, but I don't think it's unreasonable to judge people based on their behaviour.

Is there an real problem with their being so few females in coding?

It depends. If there's simply something fundemental about women which makes them on average less likely to prefer coding on average and the differences in numbers are simply a reflection of that, then no, there's no problem.

If there's other causes which are pushing out people who would otherwise like and be good at programming then yes, I think that is a problem, just as much as it's a problem that there's huge pressure for men to not be infants and junior school teachers these days.

I seldom see them asked and answered by rational people with data

Surely you want them answered by people with data :)

But yes, data is good. We have of course piles of anecdotes and things we may have personally observed (I've seen some conferences where women have been subjected to some rather shoddy behaviour and other ones where there has been nothing wrong at all---curiously IME the quality of behaviour correlates strongly with the quality of conference). I have many more anecdotes of course.

But as to hard data, it's difficult to get. That said people have tried a few controlled trials with various things, such as submitting CVs to jobs and have in some cases found bias.

There's also some interesting effects:

essentially given a group with some bigoted members equally distributed then a minority sub-group will be disporportionately on the receiving end of bigorty. This means that in essentially any industry where there's s significant gender imbalance, the minority will be on the receiving end of quite a lot of shoddy behaviour.

The result is that even if the gender imbalance is perfectly natural, then one still needs to put in effort to make sure the minority is not mistreated.

Truth be told, I have neither a nickel invested nor a care in the world.

Well that's fine. At the moment I'm not in a position where I can have any real effect, or be affected by it (employees? Ha! I need revenue first). I have been in the past. I suppose when I see bad behaviour going on around me, with people I can influence, I can either try to influence it, or I can accept it.

I've become less and less comfortable passively accepting such things as time has gone on. There's lots of nice quotes and platitudes I could wheel out along those lines, but ultimately it's a personal choice based on feelings, or if you prefer axioms. After all, logic does cannot underlie everything: it has to have an axiomatic foundation on which it rests.

Comment Re:I guess they realised... (Score 1) 105

Man, this explains a lot. Mainstream Linux GUIs have been going backwards for a long time. But at least we have, uh, well, we already had most of it back then, come to think of it.

Indeed and it really pains me. What Linux/unix had way back when was far from perfect. However, it had some awesomely brilliant features that neither Windows nor MacOS and then OSX had. The desire to blindly chase Windows 95 then XP then OSX has systematically stripped out almost all of the unique but superior features giving us what is essentially a barstardised and inferior hybrid of Windows and OSX.

And you know what? That chasing was a complete fools errand. It didn't "win" us linux on the desktop, all it did was take a system which was superior to all others for some people and make it superior for even fewer.

Comment Re:I guess they realised... (Score 1) 105

There is one BIG flaw in X11 that wasn't mentioned: by design, every program that hooks into X also gets access to ALL input X gets. Meaning by design you cannot prevent any keyloggers from logging your sudo password. Wayland only allows access to all input to the compositor itself, and with a sandbox it can prevent any other program from keylogging.

Indeed, though entertainingly this isn't part of the X protocol, but part of the Xinput extension brought to you by the folks now working on Wayland. However, I don't see any reason that the compositor model of X11 can't be updated to intercept all events: it already has to intercept all events anyway because it needs to be able to arbitrarily mangle them before feeding them into the various captured windows.

So this flaw could be fixed for compositing window managers with a small update to the API. Given the architecture of X, the 10 remaining people like me using non compositing window managers could do it with an external compositor. However, one of the main bonkers criticism of X is that the API sometimes receives updates. So make of that what you will.

Comment Re:Dell mathematics (Score 0) 69

K was never uniformly 1024 in computer parlance. You're simply ignoring history and the computer industry outside your own experience if you believe it.

K as Ki (i.e. 1024) was always the case for RAM because powers of 2 were extremely natural because of the nature of it.

For everything else, not so much. Baud rates were always in kilo, not kibi, i.e. 1000s of symbols per second and this rather naturally translated to kb/s not kib/s. Using kib makes no sense for serial protocols. And basically everything using serial protocols which includes networking and tape drives have always been in SI units not binary style ones.

Bit-rates have ALWAYS been metric.

And hard disks prior to the 80s, when they were still large and expensive were usually in actual bits/words not in funny binary units: those made no sense anyway under the old CHS style of thinking.

The original Shugart 5.25" floppy drive was always 100k as in 100,000 bytes.

Then the double density 360k one came along in 1024 notation.

Then the 1.44 floppy came along which used both notations at once, one M in the 1.44M being 1000*1024 bytes.

Unix and Microsoft always liked to do file sizes in kib and mib.

The long, rich history of prevarication and confusion has been carefully documented here:

TL;DR k was never always equal to 1024 in computer parlance.

Comment Re:I guess they realised... (Score 5, Informative) 105

No one asked Henry Ford to make cars, either.

And you know what? No one asked the Stanley Motor Carriage Company to make cars either.

Simply being new doesn't mean it's better. The trouble with Wayland, or rather why I'm deeply suspicious of it is that some of the claims from the devs about waykand and X11---and bear in mind they're X11 devs too---are flat out wrong at best and deeply deveptive at worst. Why the need for a FUD attack? If Wayland is better it ought to win on merit, not FUD.

Tahe for example this article:

Going through one at a time.

1. Extensions are what X11 calls API updates. Wayland will get API updates too, so this is not an advantage of wayland beyond version 1.0.

1. A, B, C: Almost all extension version updates add new API calls and keep the old ones. Sending Foo 2.0 calls to Foo 2.2 works just fine. Not to say that versioning isn't a problem, but then fixing the API is apparently bad for X but nothing else.

2. Well core X11 is super simple and a tiny setup of Xinput 2. This leaves essentially 2 input systems left of any complexity, 2.2 and 2.0, and as far as I can tell 2.0 isn't actually separate from 2.2. So, basically X has one major input system which actually looks kinda similar to the Wayland one.

3. That's a misunderstanding of "mechanism not policy"

4. So Xorg and Xfree86 got a bit crazy and then got refactored. Apparently historical cleanups are a bad thing? This happens in any project of any age.

5. Apparently it's impossible to add a new API call for synchronisation because from (1) that X11 isn't allowed api updates unlike every other system.

6. Yeah OK, fonts are not great.

7A A badly designed chunk of Xorg is apparently a problem with X11 now. Oh and it's been fixed so it's not a problem at all. But apparently every misstep in one implementation of an X server fixed 5 years ago is a reson it's bad now.

7B That was pure fud in 2013 when it was written. Xrandr and monitor hotplugging has worked flawlessly for years.

7C Huh? There's been xrandr front ends for years which remember certain layouts. Hell, Arandr, the nice GUI point and click one in all the repos remembers layouts just fine.

7D That smells like bullshit to me. Unless the second monitor is a separate screen (X11 term for something little used now) they it'd be impossible for one to have compositing and one not. I've not heard of anyone using screens in years.

8 Yeah and real toolkits are poorer for it. The window tree is a really nice thing when you have latency. Because with tree'd systems the server remembers which sub-sub-sub window a mouse click went to, and you could ignore the absolute position. With a treeless system all you have to go on is the position.

With latency, if you click, then the display updates then it processes the click, your click goes not where you want, but where the GUI is now. This I find happens more often than I'd like in web "apps". With tree based systems, sure the widget moved, but the assignment of the click to the window was latency free, so your click ends up correctly on the now-moved widged.

IOW tree based systems are superior. Many toolkits abandoned it for compatibility with non tree based systems. What we have now is actually fundementally worse in high latency environments.

9 Yes this is finally a genuine, no-nuance flaw.

10 C this is not correct if you have a compositing window manager, because it can do whatever it likes with the final display.

10 D their solution is to make the compositor do all this shit in Wayland. That could be done equally well in X. Sure, the current convention has a small flaw, but X11 now supports the Wayland way too.

10 E just use the features of the compositing window manager. It intercepts all key presses and windows anyway.

So without getting into the merits or demerits of Wayland, it's disappointing to see the devs engaging in a colossal FUDstorm.

Comment Re:"Women don't like trash talk, be more sensitive (Score 1) 920

You always consider your argument "won" - even when you don't actually "win" anything

The point whee you give up on any semblance of reasonableness and start simply making up stuff that you claim I've said---any reasonable person would consider the argument won.

Basically if you've got nothing left but lies you have lost.


Comment Re:"Women don't like trash talk, be more sensitive (Score 1) 920

Lovely - when you do it "context matters"

Yes context does matter, which is why you're a fool for pretending it does not.

"they are hostile".

Ah this is the point where having lost the argument thoroughly you simply resort to making up stuff that I never said. My arguments with you always end this way. At the point you simply start making stuff up, I generally consider the argument won.

To communicate is the beginning of understanding. -- AT&T