Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror

Comment My own calculation (Score 1) 981

I came up with a different answer, based on the summary's wording.

Firstly, the sex of the second child is not determined by the first. Whatever one child is, the other will always be 50% chance of being either.

What we can deduce from the wording is that his other child is not a son born on a tuesday.

We draw a two column, 7 row matrix. The rows are days of the week, and the columns are boy/girl. Write a tick in each cell if that is a valid sex and day for the child. We are left with 14 possibilities. 7 of those are girls (a girl can be born on any day), but only 6 are boys (as according to the wording, only ONE is a son born on tuesday...if the other is a son, it cannot be a tuesday, so we are left with 6 days if it's a boy. We give that probability to the girl column.

Thus we are left with 8 out of 14 chances being a girl, and 6 out of 14 being a boy. In decimal:

Girl: 0.57
Boy: 0.43

QED.

Comment Re:Multi-tasking (Score 1) 568

What I'd like to see on Android, though, is a permission that controls whether an app is allowed to spawn background services, which would be listed alongside others in the confirmation screen when app is installed.

Whilst Android does not have this, since version 2.0 they have vastly improved background process behaviour.

Previous to 2.0, a service (ie background app) could request foreground priority, oblivious to the user. This would flag it as important enough such that it would not be killed when the system needed resources. The intention is things like music players needing to always keep playing the music.

Unfortunately human nature rolled in and every developer felt that _their_ app was the most important one on the system, so had useless crap always running (updates, lots of network polling, etc) and so with many apps installed, the system could become sluggish even if there was only one visible app in the foreground.

Since 2.0, the old system call for this (setForeground()) has been turned into a No-Op, and apps wishing to retain high priority privileges in the background are now forced to display a notification in the status bar. Result? Apps cannot quietly hog system resources, but now must inform the user, which has generally resulted in much less resource hungry apps, snappier performance, and better battery life.

GUI

IDEs With VIM Text Editing Capability? 193

An anonymous reader writes "I am currently looking to move from text editing with vim to a full fledged IDE with gdb integration, integrated command line, etc. Extending VIM with these capabilities is a mortal sin, so I am looking for a linux based GUI IDE. I do not want to give up the efficient text editing capabilities of VIM though. How do I have my cake and eat it too?"

Comment Re:Happy birthday to 180th meridian too ! (Score 3, Interesting) 429

Flying Sydney, Australia to California is similar. There have been numerous times when I departed Sydney after lunch on Saturday, spend 14 hours in a plane, then land at San Francisco in time for breakfast on _the same day_.

Amusing chat over IM with a friend one such day:

Them: How's your Saturday?
Me: Good, had lunch in Sydney then breakfast in San Francisco after that.
Them: wtf???

Internet Explorer

Reports of IE Hijacking NXDOMAINs, Routing To Bing 230

Jaeden Stormes writes "We just started getting word of a new browser hijack from our sales force. 'Some site called Bing?' they said. Sure enough, since the patches last night, their IE6 and IE7 installations are now routing all NXDOMAINs to Bing. Try it out — put in something like www.DoNotHijackMe.com." We've had mixed results here confirming this: one report that up-to-date IE8 behaves as described. Others tried installing all offered updates to systems running IE6 and IE7 and got no hijacking.
Update: 08/11 23:24 GMT by KD : Readers are reporting that it's not Bing that comes up for a nonexistent domain, it's the user's default search engine (noting that at least one Microsoft update in the past changed the default to Bing). There may be nothing new here.

Comment How will current apps cope? (Score 3, Insightful) 125

There are ~3500 android apps out there now, virtually every one of them written assuming HTC Dream hardware.

It will be very interesting to see how they all cope when run on emerging hardware with vastly different characteristics and screens to the opening device.

My own Android game is not exempt and will need better adaptability (yeah, hypocrite).

Comment Re:Features I'm Looking For in My Next Phone (Score 2, Informative) 152

  • Wifi (Must be able to connect to my home network at home)
  • SIP Client (Must be able to connect to my Asterisk server at home)
  • Bluetooth tethering for a MacBook Pro (For those rare times when I'm not near a wifi access point.)

Already possible, alas you need an unlocked G1 for the tethering:

- Wifi, already there

- Sip: http://code.google.com/p/sipdroid/

- Bluetooth tether: http://code.google.com/p/android-wifi-tether/

Comment Re:Beta = Test Environment (Score 1) 109

You can test and test all you want outside of production, and any respectable shop will have every piece of code thoroughly unit tested and will test "significant" changes against simulated (for changes that load can affect) and limited users.

But, for an environment with huge infrastructure, it becomes literally impossible to test every scenario against real user loads with real user patterns ("random" requests is not real).

When your test scripts get timeouts, they gently retry after $TIMEOUT. People arent like that. Never underestimate the power of $BIGNUM users clicking 'reload' every coupla seconds....

Announcements

Slashdot.org Self-Slashdotted 388

Slashdot.org was unreachable for about 75 minutes this evening. Here is the post-mortem from Sourceforge's chief network engineer Uriah Welcome. "What we had was indeed a DoS, however it was not externally originating. At 8:55 PM EST I received a call saying things were horked, at the same time I had also noticed things were not happy. After fighting with our external management servers to login I finally was able to get in and start looking at traffic. What I saw was a massive amount of traffic going across the core switches; by massive I mean 40 Gbit/sec. After further investigation, I was able to eliminate anything outside our network as the cause, as the incoming ports from Savvis showed very little traffic. So I started poking around on the internal switch ports. While I was doing that I kept having timeouts and problems with the core switches. After looking at the logs on each of the core switches they were complaining about being out of CPU, the error message was actually something to do with multicast. As a precautionary measure I rebooted each core just to make sure it wasn't anything silly. After the cores came back online they instantly went back to 100% fabric CPU usage and started shedding connections again. So slowly I started going through all the switch ports on the cores, trying to isolate where the traffic was originating. The problem was all the cabinet switches were showing 10 Gbit/sec of traffic, making it very hard to isolate. Through the process of elimination I was finally able to isolate the problem down to a pair of switches... After shutting the downlink ports to those switches off, the network recovered and everything came back. I fully believe the switches in that cabinet are still sitting there attempting to send 20Gbit/sec of traffic out trying to do something — I just don't know what yet. Luckily we don't have any machines deployed on [that row in that cabinet] yet so no machines are offline. The network came back up around 10:10 PM EST."

Slashdot Top Deals

Logic is a pretty flower that smells bad.

Working...