code logs -> 2018 -> Wed, 11 Jul 2018< code.20180710.log - code.20180712.log >
--- Log opened Wed Jul 11 00:00:53 2018
00:28 celticminstrel [celticminst@Nightstar-adnja8.dsl.bell.ca] has joined #code
00:28 mode/#code [+o celticminstrel] by ChanServ
00:40 Vornotron [Vorn@Nightstar-sjaki9.res.rr.com] has quit [Ping timeout: 121 seconds]
01:16 JustLurk [justbob@ServerAdministrator.Nightstar.Net] has joined #code
01:16 JustBob [justbob@Nightstar.Customer.Dissatisfaction.Administrator] has quit [NickServ (RECOVER command used by JustLurk)]
01:16 mode/#code [+o JustLurk] by ChanServ
01:16 JustLurk is now known as JustBob
01:16 JustBob [justbob@Nightstar.Customer.Dissatisfaction.Administrator] has quit [[NS] Quit: ]
01:17 JustBob [justbob@ServerAdministrator.Nightstar.Net] has joined #code
01:17 mode/#code [+o JustBob] by ChanServ
01:19 Derakon[AFK] is now known as Derakon
01:27 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Ping timeout: 121 seconds]
03:21 Degi [Degi@Nightstar-t42vg9.dyn.telefonica.de] has quit [Connection closed]
05:02 mac [macdjord@Nightstar-grpbnp.mc.videotron.ca] has joined #code
05:02 mode/#code [+o mac] by ChanServ
05:04 macdjord [macdjord@Nightstar-grpbnp.mc.videotron.ca] has quit [Ping timeout: 121 seconds]
05:05 celticminstrel [celticminst@Nightstar-adnja8.dsl.bell.ca] has quit [[NS] Quit: And lo! The computer falls into a deep sleep, to awake again some other day!]
05:30 Derakon is now known as Derakon[AFK]
05:32 Kindamoody[zZz] is now known as Kindamoody|afk
06:43 Vornotron [Vorn@Nightstar-sjaki9.res.rr.com] has joined #code
06:43 mode/#code [+qo Vornotron Vornotron] by ChanServ
07:14 Vornotron [Vorn@Nightstar-sjaki9.res.rr.com] has quit [Ping timeout: 121 seconds]
07:18 Vornotron [Vorn@Nightstar-sjaki9.res.rr.com] has joined #code
07:18 mode/#code [+qo Vornotron Vornotron] by ChanServ
07:21 Vorntastic_ [uid293981@Nightstar-6br85t.irccloud.com] has joined #code
07:23 Vornotron [Vorn@Nightstar-sjaki9.res.rr.com] has quit [Ping timeout: 121 seconds]
09:50 Vorntastic_ is now known as Vorntastic
10:16 * TheWatcher eyes https://twitter.com/___discovery/status/1016760577958522882 , chuckles
10:16
<@TheWatcher>
It's not wrong...
12:16
<@Pi>
s/react //g, really.
13:16 celticminstrel [celticminst@Nightstar-adnja8.dsl.bell.ca] has joined #code
13:16 mode/#code [+o celticminstrel] by ChanServ
13:58 celticminstrel [celticminst@Nightstar-adnja8.dsl.bell.ca] has quit [[NS] Quit: And lo! The computer falls into a deep sleep, to awake again some other day!]
14:06 himi [sjjf@Nightstar-v37cpe.internode.on.net] has quit [Ping timeout: 121 seconds]
14:11 Degi [Degi@Nightstar-32ngtn.dyn.telefonica.de] has joined #code
14:20 Degi- [Degi@Nightstar-32ngtn.dyn.telefonica.de] has joined #code
14:21 Degi [Degi@Nightstar-32ngtn.dyn.telefonica.de] has quit [Ping timeout: 121 seconds]
14:22 Degi- is now known as Degi
14:42 Degi_ [Degi@Nightstar-e2tdi9.dyn.telefonica.de] has joined #code
14:43 Degi [Degi@Nightstar-32ngtn.dyn.telefonica.de] has quit [Ping timeout: 121 seconds]
15:11 Vorntastic [uid293981@Nightstar-6br85t.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity]
15:13 Vornotron [Vorn@Nightstar-sjaki9.res.rr.com] has joined #code
15:13 mode/#code [+qo Vornotron Vornotron] by ChanServ
15:21
<~Vornotron>
actually I wonder if you can get regex to do this. I have a sequence of letters with blanks in such as "XZAN_HOR_ANAO". The goal is to fill in the blanks with one letter each such that a substring that includes both filled letters is a word - so XZ(ANCHORMAN)AO would work for instance. I wonder if there is a regex that would work to determine whether a given word can be found as a substring of this.
15:24
<~Vornotron>
/(((X?)Z)?A)?N)?.HOR.(A(N(AO?)?)?)?/ think that does it.
15:31 Degi_ is now known as Degi
15:32
<~Vornotron>
corrected: /^(((x?z)?a)?n)?.hor.(a(n(ao?)?)?)?$/
16:07 Degi [Degi@Nightstar-e2tdi9.dyn.telefonica.de] has quit [Connection closed]
16:33 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has joined #code
18:41
<&ToxicFrog>
Naming problem.
18:41
<&ToxicFrog>
I have an archive file format. Each entry contains both data and metadata.
18:41
<&ToxicFrog>
archive:read() returns the data, archive:stat() returns the metadata.
18:41
<&ToxicFrog>
I now also need two iterators: one over just the metadata, and one over the (metadata,data) pairs
18:42
<&ToxicFrog>
(ok, I don't need the latter, the caller can roll their own using the former, but it's convenient)
18:42
<&ToxicFrog>
The reason I don't just have one with the latter behaviour is that returning the data is potentially expensive.
18:44
<~Vornotron>
ls, cat
18:44
<~Vornotron>
not cat
18:45
<~Vornotron>
but yes ls
18:45
<&ToxicFrog>
I'm considering just having archive:contents(return_data=false)
18:46
<&ToxicFrog>
Hmm. archive:ls() for the former, archive:contents() for the latter?
18:47
<~Vornotron>
sure
18:52
<&ToxicFrog>
(working on the translation tool has inadvertently caused me to completely redesign my ss1 res file library in passing)
19:02
<@Tamber>
Oh, er. Conclusion to my thrilling fight with wifi on my phone a while back: My brother has his phone (A Sony Xperia thing?) turned off, and my phone connects to wifi nigh-instantly every time without issue.
19:41 * Tamber resumes fist-shaking at some old iron.
20:04
<@TheWatcher>
.... wat
20:07
<@Tamber>
Considering all the other problems he's had with that phone, it wouldn't surprise me if it was screwing up the wifi, too~
20:08
<@TheWatcher>
That would be impressive, but not impossible, aye
20:08
<@TheWatcher>
Especially since wifi is so fucking fragile
20:25 Kindamoody|afk is now known as Kindamoody
20:28 * Tamber headscratches
20:29
<@Tamber>
ARCBios refuses to load /bsd, with the "inappropriate file type or format" error. Will quite happily load and boot /bsd.51. diff claims that /bsd and /bsd.51 have no differences.
20:39
<&[R]>
Did it work before?
20:40
<@Tamber>
Well, it stopped working at the point I tried to upgrade from 5.1 to 5.2. That was when it started with the "inappropriate file [...]" stuff.
20:40 Jessikat [Jessikat@Nightstar-bt5k4h.81.in-addr.arpa] has joined #code
20:40
<@Tamber>
But I still had the 5.1 kernel saved, for reasons like this.
20:43 macdjord|slep [macdjord@Nightstar-grpbnp.mc.videotron.ca] has joined #code
20:43 mode/#code [+o macdjord|slep] by ChanServ
20:44
<@Tamber>
Okay, just copied /bsd.51 over /bsd, and now it'll boot that no problem. So one weirdness down.
20:44
<@Tamber>
(Even though diff claimed they were identical already. *shrug*)
20:44
<&[R]>
Are you sure diff would print anything if you were comparing binaries?
20:46 mac [macdjord@Nightstar-grpbnp.mc.videotron.ca] has quit [Ping timeout: 121 seconds]
20:46
<&McMartin>
It normally does, though it normally redacts the result
20:46
<&McMartin>
"Binary files $FILE_A and $FILE_B differ"
20:47
<@Tamber>
Yeah, it'll tell you if they differ; and, as is Right and Good, be silent if they match
20:48
<&McMartin>
Now, whether *this ancient version of diff* would, I could not tell you
20:49
<@Tamber>
# diff -s /bsd.51 /bsd
20:49
<@Tamber>
Files /bsd.51 and /bsd are identical
20:49
<&McMartin>
Concern resolved
20:49
<@Tamber>
I'm not entirely sure how to show what version `diff` is, though.
20:50
<@Tamber>
(And, surely, bsd 5.2 isn't so old as to be ancient... ...is it? :p)
20:50
<@Tamber>
(okay, 2013, so~)
20:51
<&McMartin>
(I think I've been traumatized excessively by the differences between bsd and gnu versions of tar)
20:51
<@Tamber>
hehe
20:51
<@Tamber>
One involves significantly more feathers?
20:52
<&McMartin>
If I remember the dumb jokes of several generations before my time, the "feathering" that happened after tarring an archive was "running it through compress or gzip or whatever"
20:53
<@Tamber>
that makes sense :)
20:56 * Tamber continues prodding and poking.
20:59
<@Tamber>
Hm. It won't boot the 5.1 /bsd.rd, either.
21:02 himi [sjjf@Nightstar-v37cpe.internode.on.net] has joined #code
21:02 mode/#code [+o himi] by ChanServ
21:30 * TheWatcher ponders Tamber
21:31
<@TheWatcher>
Is there some reason you're not just copying data elsewhere and then just wiping and starting from scratch on this thing? >.>
21:32
<@Tamber>
Well, I'd like to, but it won't boot the 6.3 bsd.rd either. :p
21:32
<@TheWatcher>
Because strikes me it might be a bit easier at this point...
21:33
<@Tamber>
There's nothing bloody easy about this thing. :)
21:33
<@Tamber>
This is a leftover from when I used to enjoy tinkering with computers, and decided to get into a little bit of retrocomputing. I should probably pass it on to someone else who would do something with it, but *shrug*
21:34 mac [macdjord@Nightstar-grpbnp.mc.videotron.ca] has joined #code
21:34 mode/#code [+o mac] by ChanServ
21:34
<@Tamber>
The only reason it's been sat since 2011 is that I got it to boot BSD, then went "...now what?"
21:36
<@Tamber>
And that was about at the time I just threw my hands up and gave up on trying to get my boot in the door working in any sort of computer-related industry; moved on to steel fabrication, and just kinda... ran out of enthusiasm for technology for its own sake.
21:36
<@TheWatcher>
Fair enough
21:37 macdjord|slep [macdjord@Nightstar-grpbnp.mc.videotron.ca] has quit [Ping timeout: 121 seconds]
21:37
<@Tamber>
(Because apparently it takes a huge wodge of qualifications, and 5 years of already working in The Industryâ„¢, to get an entry level job that pays peanuts, in the IT world~)
21:38
<@Tamber>
Whereas I walked pretty much straight into an apprenticeship that paid peanuts, doing steel fab, and it was more fun.XD
21:44
<@TheWatcher>
Plus, you're probably treated better
22:09 * Tamber cries a little.
22:09
<@Tamber>
I was at the first place I worked.
22:10
<@Tamber>
Now I'm at a hardware shop that runs by game-dev shop deadline rules~
22:18
<@Tamber>
(I worked a grand total of 1 (8hr) day's worth of overtime at the first place, in 2 years I was there. At my current place, in 3.5 years, I've done the equivalent of 77.25 8-hr days as overtime. Most of that is staying late to meet nigh-impossible "Yeah, sure, we can have that ready for you" deadlines.)
22:22
<@TheWatcher>
Blegh
22:23
<@Tamber>
Cherry on the top of that is we've recently taken on a new sales guy, because we weren't struggling enough to meet deadlines already.
22:26
<@TheWatcher>
Ah, management by the "If you get stuff done on time, you don't have enough to do!" system
22:27
<@Tamber>
Management by the "Well, you managed it last time (with a heroic effort and significant overtime), so it's clearly perfectly feasible again!" system.
22:28
<@TheWatcher>
same thing~
22:28
<@Tamber>
Working at 120% is something that can be done in short bursts, with corresponding reduction in output to recover later; but there is no reduction in demand of output, nor recovery. Every bloody week, it's a crazy rush to get a job out of the door.
22:30
<@Tamber>
Anyway, I've been ranty enough about that already today.
22:31
<@TheWatcher>
We have a new head of admin, who has a head full of wooly management bullshit, but in relevant part has changed the way she wants various section heads to report status to her. PArt of this change is a weeking thing that apparently includes a section "What help do you need?"
22:32
<@TheWatcher>
I'm trying to persuade my boss to simply leave that as "Hire another 3 team members" every week >.>
22:35
<@TheWatcher>
(Not going to happen, because it's apparently fine to drop a billion on a bunch of new buildings, but actually hiring enough staff and paying people properly? Good gods, no)
22:40 ErikMesoy [Bruker@Nightstar-hq72t5.customer.cdi.no] has quit [Connection closed]
22:45 VirusJTG [VirusJTG@Nightstar-42s.jso.104.208.IP] has quit [Connection closed]
23:23 VirusJTG [VirusJTG@Nightstar-42s.jso.104.208.IP] has joined #code
23:23 mode/#code [+ao VirusJTG VirusJTG] by ChanServ
23:29 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Ping timeout: 121 seconds]
23:30 himi [sjjf@Nightstar-v37cpe.internode.on.net] has quit [Ping timeout: 121 seconds]
23:35 Vornotron [Vorn@Nightstar-sjaki9.res.rr.com] has quit [Ping timeout: 121 seconds]
23:42 Degi [Degi@Nightstar-e2tdi9.dyn.telefonica.de] has joined #code
--- Log closed Thu Jul 12 00:00:54 2018
code logs -> 2018 -> Wed, 11 Jul 2018< code.20180710.log - code.20180712.log >

[ Latest log file ]