Follow Slashdot stories on Twitter


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:How (Score 1) 301

No, it's not obvious. The person in question may change "their" gender in the future, and then the editors will have to either modify the article (rewriting the history in a 1984-like manner) or to face accusations of bigotry and disrespect.

I know of al least one free software project whose leader had a sex reassignment surgery, and of a well known microprocessor designed by a female-born-male, so that may more common than most people think.

Comment Re:Fake news... (Score 1) 322

If you are unable or unwilling to rebuild a browser from source, you've come to the wrong Web-site...

No shit.

disabling an option is usually a prelude to removing it completely

It is not disabled. It was turned off by default — because it is useless for most users, as TFA mentions. Lots of other options are off by default — such as --with-system- foo:

Have you tested all the possible combinations of those '--enable-*' and '--with-*' options? Any configuration that is not tested and not supported is living on borrowed time.

What do you think will happen when they "accidentally" break the --enable-alsa?

Nobody building firefox for reasons other than purely masturbatory will ever bother to use an unsupported config for such a bloated, fragile and messy piece of shit.

Comment Re:Kerbal Space Program (Score 1) 322

I can get rid of my wrapper script that starts /usr/bin/awful_pos (renamed so that nothing can find /usr/bin/pulseaudio)

no need of any wrapper script, pulseaudio can be started/stopped on demand.

I had to do this shit just because of firefox, when testing some app on their 'current' branch (which has stopped supporting alsa a year or so ago).

$ cat ~/.config/pulse/client.conf
# Applications that uses PulseAudio *directly* will spawn it,
# use it, and pulse will exit itself when done because of the
# exit-idle-time setting in daemon.conf
autospawn = yes
$ cat ~/.config/pulse/daemon.conf
exit-idle-time = 0 # Exit as soon as unneeded
flat-volumes = yes # Prevent messing with the master volume

Comment Re:Javascript really sucks (Score 1) 300

Incorrect. You need to go back to school and review what divide by zero actually means.

However Javascript uses the broken IEEE 754 definition of x/0 = Infinity. This is is retarded because is broken math

Thanks for proving my point. In other words, javascript is buggy because it's using industry standard floating point, instead of some "ideal" real numbers (which couldn't be represented on any actual or theoretical computer, anyway).

Your mistake is assuming Javascript has integers in the first place. Javascript does NOT have signed integers. All values are 64-bit floating point values.

Yes it has. The bitwise operators first convert their operands to a 32bit signed integers, and then return a 32bit signed integer. Look here and here. This is similar to how arithmetic ops first convert their arguments to double, string ops first convert them to strings, etc -- the way that all typeless/dynamic languages work.

If we're down to sending each back to school, I'll give you a smart student question that will earn you extra points: why isn't javascript using 64bit signed integers there?

But what do you expect from a language designed in 10 days.

I'll expect to use IEEE 754 floating point and 2s complement integers like everybody else.

Comment Re:Javascript really sucks (Score 1) 300

Math.tan( Math.PI/2 )

Returns broken 16331239353195370, instead of correct NaN

That's how floating point doubles work in any language. And besides, why should that be NaN? 1/0 is Infinity, not NaN.

console.log( 123456789 << 5 );

Returns broken -344350048 instead of correct 3950617248

That's how 2s complement 32 bit integers work in any language. Is there some standard that says that "big" signed integers should be surreptitiously changed into unsigned ones? Or that javascript should use 64bit longs?

Don't even get me started on the retarded ASI (Automatic Semi-colon Insertion).

I'll get you started, go on.

Comment Re:Multi-monitor and TV use cases (Score 1) 175

If a window spans two screens that have different DPI values, how should the window system behave?

Use the DPI that matches at least one of them? I don't see how using some absurd "middle-ground" (which will make both look ugly) is better than that.

If a PC is connected to a physically large monitor, such as an HDTV, the user is likely to be sitting significantly farther away than arm's length.

An application could easily query the monitor's size via xrandr and adapt. A usage case where someone is tiling an image across screens with different sizes and resolutions is not a very common case -- no need to ruin the experience of 99.99% of users just because of that.

Comment Re:Would DEFPOTEC give a better experience? (Score 1) 175

No, because the monitor reports its own size and resolution via EDID. The default should be the real DPI. All OSs support that since 20 years or so.

$ xrandr | grep VGA
VGA-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 477mm x 268mm
$ echo '1920 / 477 * 25.4' | bc

Comment Re:AMD Ryzen 7 1800X Linux Benchmarks (Score 1) 175

When my mother can use it without me walking her through changing her monitor resolution,

I don't use windows and I don't know your mother, but I know dozens of windows users who bitterly complain about not being able to use their 21" or 23" monitors because the fonts are too small, and not a single one of them was able to figure out by themselves (or even google it) how to change that horrible 96dpi default. In windows it's something like 3 clicks away (and they don't need to change the "resolution"; that would be stupid). The same operation on my father's xfce (linux) desktop is probably 4 or 5 clicks away -- do you think THAT makes any difference?

With the demise or CRTs, usability means a) automatically using the monitor's natural resolution, and b) NOT forcing some 96dpi default just because some moron webdesigners weren't able to design things that scale. Both current windows and linux distros get the first right and fuck up the second (in linux because the xorg guys intentionally crippled the x11 server to make it "windows-compatible")

Comment Re:Same (Score 1) 1001

in practice you notice your code doesn't scale because it's grindingly slow when you test it out.

Do you test it for all possible inputs?

There are a lot of things that run fine most of the time and then go into an exponential trip when confronted with some "unexpected" input. Take for instance the regexp implementation in perl, javascript and anything pcre-based -- absolutely horrible depth first implementation, easy to dos, unusable in any public facing setting. Or most hashtable implementations -- very easy to trick into putting all the stuff into the same bucket and degenerate into a linked list.

The people who wrote that weren't necessarily idiots; they probably did a quick hack, found it useful and were happy with it, and by the time they noticed that it doesn't scale it was already too late

Slashdot Top Deals

"The eleventh commandment was `Thou Shalt Compute' or `Thou Shalt Not Compute' -- I forget which." -- Epigrams in Programming, ACM SIGPLAN Sept. 1982