| --- Log opened Wed Jun 24 00:00:20 2020 |
| 00:15 | | Kindamoody is now known as Kindamoody[zZz] |
| 00:17 | | Alek [Alek@Nightstar-kaiguq.il.comcast.net] has quit [Ping timeout: 121 seconds] |
| 00:21 | | Alek [Alek@Nightstar-kaiguq.il.comcast.net] has joined #code |
| 00:21 | | mode/#code [+o Alek] by ChanServ |
| 00:27 | | Alek [Alek@Nightstar-kaiguq.il.comcast.net] has quit [Ping timeout: 121 seconds] |
| 00:30 | | Alek [Alek@Nightstar-kaiguq.il.comcast.net] has joined #code |
| 00:30 | | mode/#code [+o Alek] by ChanServ |
| 00:46 | | himi [sjjf@Nightstar-1drtbs.anu.edu.au] has joined #code |
| 00:46 | | mode/#code [+o himi] by ChanServ |
| 01:32 | | catalyst [catalyst@Nightstar-bs4gg4.dab.02.net] has joined #code |
| 01:32 | | catalyst [catalyst@Nightstar-bs4gg4.dab.02.net] has quit [[NS] Quit: -a- IRC for Android 2.1.56] |
| 01:33 | | catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has joined #code |
| 02:12 | | Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed] |
| 02:21 | | catalyst` [catalyst@Nightstar-v6lb30.cable.virginm.net] has joined #code |
| 02:23 | | Pink [user1@Nightstar-g7hdo5.dyn.optonline.net] has joined #code |
| 02:25 | | Pinkhair [user1@Nightstar-g7hdo5.dyn.optonline.net] has quit [Ping timeout: 121 seconds] |
| 02:40 | | catalyst` [catalyst@Nightstar-v6lb30.cable.virginm.net] has quit [Connection reset by peer] |
| 03:03 | | Degi [Degi@Nightstar-1gnbge.dyn.telefonica.de] has quit [Ping timeout: 121 seconds] |
| 03:04 | | Degi [Degi@Nightstar-jmkkv1.dyn.telefonica.de] has joined #code |
| 03:42 | | VirusJTG [VirusJTG@Nightstar-42s.jso.104.208.IP] has quit [Connection closed] |
| 03:42 | | VirusJTG [VirusJTG@Nightstar-42s.jso.104.208.IP] has joined #code |
| 03:42 | | mode/#code [+ao VirusJTG VirusJTG] by ChanServ |
| 03:51 | | Pinkhair [user1@Nightstar-g7hdo5.dyn.optonline.net] has joined #code |
| 03:51 | | Pink [user1@Nightstar-g7hdo5.dyn.optonline.net] has quit [Ping timeout: 121 seconds] |
| 04:33 | | Pink [user1@Nightstar-g7hdo5.dyn.optonline.net] has joined #code |
| 04:35 | | Pinkhair [user1@Nightstar-g7hdo5.dyn.optonline.net] has quit [Ping timeout: 121 seconds] |
| 05:50 | | himi [sjjf@Nightstar-1drtbs.anu.edu.au] has quit [Ping timeout: 121 seconds] |
| 05:57 | | celticminstrel [celticminst@Nightstar-olm4vg.dsl.bell.ca] has quit [[NS] Quit: And lo! The computer falls into a deep sleep, to awake again some other day!] |
| 06:35 | | * abudhabi sets up nomachine for remote desktop needs. Seems pretty good! (Unlike VNC.) |
| 07:16 | <&[R]> | VNC is disturbingly laggy |
| 07:20 | < Mahal> | I don't like interviewing |
| 07:20 | < Mahal> | not least because my last hire was a FUCKING TOTAL WASTE OF SPACE that we had to fire |
| 07:20 | < Mahal> | he interviewed _so_ well |
| 07:20 | < Mahal> | it was awaful |
| 07:21 | <&[R]> | D: |
| 07:22 | <&[R]> | My newest exboss wasn't great at hiring people (but our industry is so obscure that it's hard to even find people) |
| 07:22 | <&[R]> | One guy he hired was basically perma-baked |
| 07:24 | <&[R]> | Always on his phone (on a fucking phone call), took 20+ minutes to scan a grid (takes 4-8 minutes depending on size). We were even working in an active industrial plant and he was on his phone while working |
| 07:24 | <&[R]> | Like WTF dude. |
| 07:24 | < Mahal> | the ... crowning moment of the Twit's career with us was probably giving out the local admin password to end users |
| 07:24 | < Mahal> | multiple |
| 07:25 | < Mahal> | Oh, and he managed to delete the head of HR's AD account (although we couldn't technically prove that one) |
| 07:25 | < Mahal> | but we know |
| 07:26 | < Mahal> | (The saving grace on the former bit was - he typoed it) |
| 07:26 | < Mahal> | (And we caught it because the user called up, all innocent, to ask for more help) |
| 07:26 | < Mahal> | (Then I went rummaging in the Twit's mail and message history to find who else he'd given it to :\ ) |
| 07:27 | < Mahal> | (then I went rummaging in _everyone's_ mail and message history to see where it was) |
| 08:46 | <@gnolam> | >_< |
| 09:11 | | himi [sjjf@Nightstar-v37cpe.internode.on.net] has joined #code |
| 09:11 | | mode/#code [+o himi] by ChanServ |
| 09:18 | | Kindamoody[zZz] is now known as Kindamoody |
| 09:21 | | catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has quit [[NS] Quit: -a- IRC for Android 2.1.56] |
| 09:37 | | Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has joined #code |
| 09:43 | | Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Ping timeout: 121 seconds] |
| 10:21 | | Kindamoody is now known as Kindamoody|out |
| 10:25 | <&jeroud> | Yay, github just redesigned their UI and now I need to buy a wider display. |
| 10:27 | <&jeroud> | Anyone who rolls out major UI changes with no warning and no opt-out needs to be forced to use tools that randomly change underneath them for at least a year. |
| 10:28 | <&[R]> | lol |
| 10:53 | <@TheWatcher> | jeroud: your ideas are intriguing to me, and I wish to subscribe to your newsletter. |
| 10:58 | <&jeroud> | I have always found that the best way to incentivise particular results is to have the people responsible for delivering those results feel that particular pain of said results not being delivered. |
| 10:59 | <&jeroud> | An obvious example being that if you want programmers to write software that is easy to deploy, make them deploy it. |
| 11:00 | <&jeroud> | A nice side effect of that is that if they don't make their software easy to deploy, at least they're the ones feeling the pain instead of you. |
| 11:02 | <&jeroud> | Unfortunately, some people either don't care about the particular kind of pain they inflict or actually relish it. |
| 11:02 | <@TheWatcher> | Yeah, or they're so used to the pain they don't notice it anymore |
| 11:02 | | * TheWatcher eyes the gitlab devs |
| 11:03 | <&jeroud> | Another problem is that people actually need to be competent to do the things they're supposed to be doing. |
| 11:04 | <&jeroud> | And while it's easy to blame the incompetents, most of the time they're incompetent because nobody's bothered to train them. |
| 11:05 | < Mahal> | you know |
| 11:05 | < Mahal> | I have tried to train my own incompetents |
| 11:05 | < Mahal> | ... |
| 11:18 | <&jerith> | Yeah, it's not always easy. |
| 11:18 | <&jerith> | Sometimes the incompetents need to be trained in caring about things that are important. |
| 11:19 | <&jerith> | By the time they reach someone willing to train them, a lot of the damage has already been done. :-/ |
| 11:45 | <&[R]> | Speaking of horrible UI |
| 11:45 | <&[R]> | Pressing right arrow when your cursor is at the end of the line in the new mysql shell makes the cursor go left one |
| 11:45 | <&[R]> | Because that's sane an desirable behavior.... |
| 11:48 | | Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has joined #code |
| 11:48 | | mode/#code [+o Reiv] by ChanServ |
| 12:01 | | Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code |
| 12:01 | | mode/#code [+qo Vornicus Vornicus] by ChanServ |
| 12:09 | <@abudhabi> | Reiv: What I don't like about VNC is that it creates a new session, rather than just showing me what's on my normal session I use when directly accessing the PC. |
| 12:11 | <@abudhabi> | Err, [R]. |
| 12:13 | <&[R]> | Also whoever thought that enabling litagigures (sp?) when using monospaced fonts needs to be shot |
| 12:13 | <&[R]> | I mean, they're horribly ugly all-in-all, but just excessively so when monospaced fonts are in use |
| 12:52 | | celticminstrel [celticminst@Nightstar-olm4vg.dsl.bell.ca] has joined #code |
| 12:52 | | mode/#code [+o celticminstrel] by ChanServ |
| 12:58 | <&jerith> | Ligatures are a typography hack, but they're a pretty elegant one. |
| 13:00 | <&jerith> | They only really make sense in variable-width typefaces, though, because their purpose is clean up kerning issues with specific pairs of glyphs. |
| 13:03 | <&jerith> | For example, "fi" -> "fi" makes the combination a lot less awkward by avoiding ugly overlap beween the top of the "f" and the dot on the "i" while also not putting too much space between the letters. |
| 13:05 | <&jerith> | Of course, since the hack exists and support for it has been added to most typographic rendering engines, it gets abused. |
| 13:06 | <&jerith> | Sometimes the abuse is also quite elegant, like replacing "->" with "→" and such. (But this should, of course, be configurable.) |
| 13:08 | <@celticminstrel> | My reaction to programming ligature fonts is "why the hell would you want that!?". |
| 13:09 | <&jerith> | Using stylistic ligatures with monospace typefaces by default is, IMHO, a bug. |
| 13:10 | <&jerith> | celticminstrel: It's popular with certain (usually functional-style) languages that have operators for everything. |
| 13:11 | <@celticminstrel> | I think the language I've seen it with is JavaScript. |
| 13:33 | | Kindamoody|out is now known as Kindamoody |
| 15:54 | <&McMartin> | I'm pretty sure I've seen one for Haskell but I cannot actually summon up any details |
| 16:26 | | Kindamoody is now known as Kindamoody|out |
| 16:40 | | * McMartin reads about DirectX 9 and in particular its Most Annoying Quirk |
| 16:40 | <&McMartin> | This... doesn't actually look that hard to work around, but it does seem like the kind of thing you'd need to build into your design from the very start |
| 16:40 | <&McMartin> | And on any other system you probably would not do this |
| 16:41 | <&McMartin> | (Which is to say, it is allowed to move your rendering device into the "device lost" state at any time, which requires you to destroy and recreate all your GPU-level data structures before rendering may continue, and a great many games would crash if this happened) |
| 16:42 | <&McMartin> | (And it was very common for it to happen when a full-screen application lost focus, say, because Acrobat Reader popped up a notification regarding your third update available today) |
| 16:42 | <~Vornicus> | that sounds like an incredible pain in the ass |
| 16:45 | <&McMartin> | Surely you are old enough to remember the era when games invariably crashed whenever you alt-tabbed out of them |
| 16:46 | <&McMartin> | (And yes, it was, which is why Vista's total non-backwards-compatible rewrite of the graphics architecture moved management of this to the OS... but that does technically keep things further from the hardware) |
| 16:46 | <~Vornicus> | I don't remember that at all. But, uh |
| 16:46 | <&McMartin> | OK, that era was about 2003-2015~ |
| 16:47 | <~Vornicus> | for the first half of that I was on a mac~ |
| 16:50 | <@gnolam> | Are you saying that the later DirectXs stopped doing this? |
| 16:51 | <&McMartin> | I am in fact informed that this specific failure mode does not happen in D3D 10, 11, or 12. |
| 16:51 | <@gnolam> | Huh. |
| 16:51 | <&McMartin> | This does not mean that such applications never crash, but my understanding is that they no longer return "Device Lost" after a call to Present, followed by returning garbage from any attempt to read out of the GPU memory that the OS just reported that it stole back from you. |
| 16:52 | <&McMartin> | I have an extremely vague recollection of being told around when DX10 first came out that a lot of stuff in DX7-9 was kept system-wide in, essentially, kernel level memory that the DirectX libraries asked the OS to arbitrate for them |
| 16:52 | <&McMartin> | And that DX10 moved a bunch of that stuff into the application's userspace and recopied it over as needed. |
| 16:53 | <@gnolam> | Because this was a major reason why everything hobby and indie, even if Windows-exclusive, used OpenGL. |
| 16:53 | <@gnolam> | Because handling those switches was just too much of a hassle. |
| 16:53 | <&McMartin> | Yeah, I can believe it |
| 16:53 | <&McMartin> | If you don't need alpha blending, DX9 appears to be way easier |
| 16:53 | <&McMartin> | Because StretchRect is not really subject to this nonsense |
| 16:54 | <&McMartin> | And starting in OpenGL 3 in the core profile, you can't actually do StretchRect without writing at least two shaders. =P |
| 16:54 | <&McMartin> | Nobody really used DX10 because using it restricted you to Vista at the time |
| 16:54 | <~Vornicus> | I skipped vista entirely |
| 16:54 | <&McMartin> | And by the time people had upgraded to 7, DX11 was there and the thing people wanted to use. |
| 16:55 | <&McMartin> | Most people did. |
| 16:55 | <&McMartin> | I have gotten the general sense that DX11 is "harder to use" at the "get things to appear on the screen at all" level than DX9, in ways that sound very similar to the complications in using OpenGL in the core profile instead of in compatibility mode. |
| 16:56 | <&McMartin> | And DX12 is something MS itself says not to bother with unless you want to go hard-core into getting as much control over what commands are sent to the GPU as possible |
| 16:56 | <&McMartin> | I've sort of put DX12 in the same conceptual bin as Vulkan, there. It exists; if you need its power, you're happy to have it; you probably don't, and thus won't want to put up with its bullshit |
| 17:01 | <&McMartin> | Also "used OpenGL even if Windows-exclusive"... there was a fairly long period where Windows had the best OpenGL performance on consumer PC operating systems by an extremely wide margin |
| 17:02 | <&McMartin> | Pretty much from the time Windows 7 came out -- by which time Apple had already shifted their OpenGL support into "benign neglect" mode even in the absence of their own proprietary alternatives -- through the point where the Linux drivers finally caught up |
| 17:02 | <&McMartin> | Which I think of as being reasonably recently |
| 17:04 | <&McMartin> | Scanning over the DX9 stuff, though, it is interesting to see how close it is to the final form of OpenGL 2.x... except that a lot of things that are easy in one are a royal pain in the other, and vice versa. |
| 17:05 | <&McMartin> | DX9 seems more tightly integrated with its viewport, and has a stronger sense of 2D things existing as a result. |
| 17:05 | <&McMartin> | I haven't actually *tried* it yet, but rendering to offscreen targets looks more straightforward in D3D. |
| 17:07 | <&McMartin> | ... and yes, since nobody asked, I *am* looking at DX9 in part as a retrocoding artifact now |
| 17:47 | | Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has joined #code |
| 18:37 | <@celticminstrel> | Isn't Haskell a language where you can define arbitrary operators? |
| 18:39 | <@celticminstrel> | That seems like it would be one of the worst candidates for programmer ligatures. |
| 18:59 | <&jerith> | celticminstrel: Yes, but in practice there are only a few families of operators in common use. |
| 19:01 | <&jerith> | It's also pretty common (as far as I've seen) to not bother with symbolic operators and just `infixify` a function with backticks. |
| 19:08 | | Pinkhair [user1@Nightstar-g7hdo5.dyn.optonline.net] has joined #code |
| 19:09 | | Pink [user1@Nightstar-g7hdo5.dyn.optonline.net] has quit [Ping timeout: 121 seconds] |
| 20:02 | | Kindamoody|out is now known as Kindamoody |
| 20:14 | | Alek [Alek@Nightstar-kaiguq.il.comcast.net] has quit [Ping timeout: 121 seconds] |
| 20:17 | | Alek [Alek@Nightstar-kaiguq.il.comcast.net] has joined #code |
| 20:17 | | mode/#code [+o Alek] by ChanServ |
| 23:00 | | Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Ping timeout: 121 seconds] |
| --- Log closed Thu Jun 25 00:00:21 2020 |