code logs -> 2011 -> Tue, 22 Feb 2011< code.20110221.log - code.20110223.log >
--- Log opened Tue Feb 22 00:00:22 2011
--- Day changed Tue Feb 22 2011
00:00
< Namegduf>
I just started up my desktop replacement laptop on battery.
00:00
< Namegduf>
It ran for three minutes then suspended itself due to critical battery status.
00:01
< Tamber>
A bit power-hungry, then?
00:01
< Namegduf>
Yes.
00:01
< Namegduf>
The battery is also basically dead.
00:01
< Namegduf>
It used to run for an hour.
00:26 Outpost [tua01910@Nightstar-c2f5078f.east.verizon.net] has quit [[NS] Quit: ]
00:30 You're now known as TheWatcher[T-2]
00:31 * Alek twitches.
00:31
< Alek>
that... is a little excessive, as power consumption goes.
00:32
< Alek>
a standard laptop, with good settings, should get at least 5 hours.
00:32
< Alek>
AT LEAST.
00:32
< Namegduf>
...not two years ago.
00:32
< Namegduf>
Well, three now.
00:33
< Alek>
even 10 years ago, laptops could expect at least 4 to 5 hours.
00:33
< Namegduf>
No, they couldn't.
00:33
< Namegduf>
Average laptops had 3-4 hours unless you were paying for fancy ultraportables.
00:33
< Alek>
I remember looking at laptops 15 years ago. Which could run for at least 3 hours.
00:33
< Namegduf>
I think you may be extrapolating from insufficient data.
00:33
< Namegduf>
I remember looking at laptops when I bought this laptop.
00:34
< Namegduf>
Advertising silly hours was common, but it's only recently they've ever been able to actually do them.
00:34 You're now known as TheWatcher[zZzZ]
00:34
< Namegduf>
Reviews regularly tested them doing things like word processing and web browsing and got 3-4 hours.
00:35 Attilla [Some.Dude@Nightstar-92c9199f.cable.virginmedia.com] has joined #code
00:35 mode/#code [+o Attilla] by Reiver
01:22 Attilla [Some.Dude@Nightstar-92c9199f.cable.virginmedia.com] has quit [Ping timeout: 121 seconds]
01:40 Stalker [Z@3A600C.A966FF.5BF32D.8E7ABA] has quit [Ping timeout: 121 seconds]
02:27 kwsn [kwsn@Nightstar-2d125add.dyn.centurytel.net] has joined #code
02:27 kwsn is now known as kwsn\blargh
02:38 gnolam [lenin@Nightstar-38637aa0.priv.bahnhof.se] has quit [[NS] Quit: Z?]
03:32 shade_of_cpux is now known as cpux
03:34
< kwsn\blargh>
http://sovxroux.tumblr.com/photo/1280/3375672409/1/tumblr_lgskfuypXS1qg9cwm
03:35
< kwsn\blargh>
-stamps TRUTH on that-
04:14 cpux is now known as shade_of_cpux
04:20 Kindamoody is now known as Kindamoody[zZz]
04:40 Rhamphoryncus [rhamph@C06FE3.F5723C.BE3FEB.9D4666] has joined #code
04:43 Tarinaky [Tarinaky@Nightstar-f349ca6d.plus.com] has quit [Client closed the connection]
05:33 Vornicus-Latens is now known as Vornicus
05:45 Kindamoody[zZz] [Kindamoody@Nightstar-4764665d.tbcn.telia.com] has quit [Ping timeout: 121 seconds]
05:50 Kindamoody[zZz] [Kindamoody@Nightstar-4764665d.tbcn.telia.com] has joined #code
06:11 celticminstrel [celticminstre@Nightstar-f8b608eb.cable.rogers.com] has quit [[NS] Quit: And lo! The computer falls into a deep sleep, to awake again some other day!]
06:11 AnnoDomini [annodomini@Nightstar-1b02aa7c.adsl.tpnet.pl] has joined #code
06:11 mode/#code [+o AnnoDomini] by Reiver
06:27 kwsn\blargh [kwsn@Nightstar-2d125add.dyn.centurytel.net] has quit [[NS] Quit: ]
06:34 Derakon is now known as Derakon[AFK]
07:25 Kindamoody[zZz] is now known as Kindamoody
07:36 Kindamoody is now known as Kindamoody|out
09:06 Stalker [Z@3A600C.A966FF.5BF32D.8E7ABA] has joined #code
09:08 Kindamoody|out [Kindamoody@Nightstar-4764665d.tbcn.telia.com] has quit [Ping timeout: 121 seconds]
09:16 You're now known as TheWatcher
09:28 Kindamoody [Kindamoody@Nightstar-4764665d.tbcn.telia.com] has joined #code
09:33 Vornicus is now known as Vornicus-Latens
09:45 Kindamoody [Kindamoody@Nightstar-4764665d.tbcn.telia.com] has quit [Ping timeout: 121 seconds]
09:46 Kindamoody [Kindamoody@Nightstar-4764665d.tbcn.telia.com] has joined #code
09:50 Kindamoody [Kindamoody@Nightstar-4764665d.tbcn.telia.com] has quit [Ping timeout: 121 seconds]
10:19 Kindamoody [Kindamoody@Nightstar-4764665d.tbcn.telia.com] has joined #code
10:28 Stalker [Z@3A600C.A966FF.5BF32D.8E7ABA] has quit [Ping timeout: 121 seconds]
10:30 Kindamoody [Kindamoody@Nightstar-4764665d.tbcn.telia.com] has quit [Client exited]
10:33 Kindamoody [Kindamoody@Nightstar-4764665d.tbcn.telia.com] has joined #code
10:38 AnnoDomini [annodomini@Nightstar-1b02aa7c.adsl.tpnet.pl] has quit [Ping timeout: 121 seconds]
10:40 AnnoDomini [annodomini@Nightstar-fedf24ee.adsl.tpnet.pl] has joined #code
10:40 mode/#code [+o AnnoDomini] by Reiver
12:52 Stalker [Z@26ECB6.A4B64C.298B52.D80DA0] has joined #code
13:04 Kindamoody is now known as Kindamoody|out
13:31 Kindamoody|out [Kindamoody@Nightstar-4764665d.tbcn.telia.com] has quit [Ping timeout: 121 seconds]
13:48 gnolam [lenin@Nightstar-38637aa0.priv.bahnhof.se] has joined #code
13:59
< gnolam>
http://i.imgur.com/lZd0q.jpg
15:06 celticminstrel [celticminst@Nightstar-f8b608eb.cable.rogers.com] has joined #code
15:25
< celticminstrel>
Do sockets lack a timeout setting by default? Should I be calling socket.settimeout to set one?
15:41 Kindamoody [Kindamoody@Nightstar-cb6cfe15.cust.tele2.se] has joined #code
16:45 Stalker [Z@26ECB6.A4B64C.298B52.D80DA0] has quit [[NS] Quit: If the world didn't suck, we'd all fall off.]
16:48 Stalker [Z@26ECB6.A4B64C.298B52.D80DA0] has joined #code
16:52 Serah [Z@26ECB6.A4B64C.298B52.D80DA0] has joined #code
16:54 Stalker [Z@26ECB6.A4B64C.298B52.D80DA0] has quit [Ping timeout: 121 seconds]
16:58
<@ToxicFrog>
celticminstrel: don't know the language, but in most cases yes, that is correct.
16:59
< celticminstrel>
What sort of timeout is normal? Thirty seconds too short or too long?
17:01 Tarinaky [Tarinaky@Nightstar-f349ca6d.plus.com] has joined #code
17:02
<@ToxicFrog>
Depends on what you're doing.
17:02
< celticminstrel>
IRC bot.
17:07
<@ToxicFrog>
30s is probably ok then
17:33
<@Vornicus-Latens>
(if on the other hand you're building a realtime game or something, 2s might be nearly too long.)
17:42
< celticminstrel>
Good to know, since I have ideas to that effect floating around. :P
18:14 Kindamoody [Kindamoody@Nightstar-cb6cfe15.cust.tele2.se] has quit [Ping timeout: 121 seconds]
18:14 Kindamoody [Kindamoody@Nightstar-fa404abf.cust.tele2.se] has joined #code
18:19 KiMo [Kindamoody@Nightstar-fa404abf.cust.tele2.se] has joined #code
18:27
< Phox>
Hey, is there a standard library in C that allows timer resolution greater than 1 second?
18:27
< Phox>
Err, time resolution, rather
18:27
< Phox>
I need to know the system time to at least 100 milliseconds
18:29
< Phox>
As it is, I'm using GetSystemTime for seconds, and then Delay(.1). That has an obvious flaw, though
18:31 KiMo [Kindamoody@Nightstar-fa404abf.cust.tele2.se] has quit [Client exited]
18:35
< celticminstrel>
I think the closest to a standard library in C for timers would be POSIX, not stdc.
18:36
< celticminstrel>
Though I could be wrong.
18:44
<@ToxicFrog>
Phox: in POSIX? clock_gettime() (replacing gettimeofday()) and nanosleep() (replacing usleep())
18:46
<@ToxicFrog>
You're not going to find anything in ANSI.
18:49
< Phox>
Yeah, just getting it right now. Thanks
18:59
< gnolam>
What are you using it for?
19:01
< Phox>
I have to timestamp an automated test.
19:21 SmithKurosaki [smith@Nightstar-7820a96a.dsl.teksavvy.com] has joined #code
19:21
<@McMartin>
POSIX systems will usually have 10ms resolution
19:22
<@McMartin>
If you're on Windows and use the kernel32 calls (which escape me at the moment) they will usually have 1ms resolution
19:22
<@McMartin>
In each case because that's the timeslice.
20:40 Kindamoody [Kindamoody@Nightstar-fa404abf.cust.tele2.se] has quit [Ping timeout: 121 seconds]
20:47 Kindamoody [Kindamoody@Nightstar-186ac2e1.cust.tele2.se] has joined #code
21:23 Serah [Z@26ECB6.A4B64C.298B52.D80DA0] has quit [Ping timeout: 121 seconds]
22:21 Stalker [Z@3A600C.A966FF.5BF32D.8E7ABA] has joined #code
22:41 AnnoDomini [annodomini@Nightstar-fedf24ee.adsl.tpnet.pl] has quit [[NS] Quit: Sleep.]
22:59
< Reiv>
Windows has smaller timeslices?
23:05 Kindamoody is now known as Kindamoody|out
23:10 Vornicus-Latens is now known as Vornicus
23:11
< Phox>
r this
23:11
< Phox>
Damn, kicked mid-sentence
23:12
< gnolam>
So. What's a good Python IDE nowadays?
23:12
< Tarinaky>
Eclipse is pretty good.
23:14
< gnolam>
I have... bad experiences with Eclipse.
23:14
< Tarinaky>
Who doesn't?
23:14
< gnolam>
+had
23:15
<@Vornicus>
gnolam: I've never IDE'd with Python.
23:16
< gnolam>
Once you get used to proper autocompletion, it's hard to go back. :P
23:16 * gnolam hugs IntelliSense.
23:16
< Namegduf>
I've never liked autocompletion myself.
23:18
< gnolam>
Why?
23:18
< gnolam>
It doesn't just save on typing - more importantly, it saves on looking up definitions.
23:19
<@Vornicus>
I find actually that autocomplete often slows me down - I have to actually look at what I'm typing and think further than "I know the name of the thing I want!"
23:22
< gnolam>
That's fine if you're perfectly certain of that name. So if it's all your own code, written reasonably recently, sure. It doesn't matter much.
23:23
< gnolam>
But when you're digging through classes 10 levels of inheritance down, in a codebase of approximately a gazillion files, of code you didn't write... it's a godsend.
23:27 yesplease [yesplease@Nightstar-ac56e6a0.ptr.magnet.ie] has joined #code
23:31
< Alek>
...
23:38 yesplease [yesplease@Nightstar-ac56e6a0.ptr.magnet.ie] has quit [[NS] Quit: http://irc2go.com/]
23:43 shade_of_cpux is now known as cpux
23:49 Kindamoody|out is now known as Kindamoody
--- Log closed Wed Feb 23 00:00:33 2011
code logs -> 2011 -> Tue, 22 Feb 2011< code.20110221.log - code.20110223.log >