Notices by πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)
-
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Monday, 04-Jun-2018 04:43:29 UTC 
πΎππ½ππππππππΏ
By the way, here's two of probably zillions of gitlab-ce issues about federated merge requests and issues
https://gitlab.com/gitlab-org/gitlab-ce/issues/4013
https://gitlab.com/gitlab-org/gitlab-ce/issues/44486
which are really, really useful to lessen the inevitable impact of GitLab B.V. Has Been Acquired By Someone We Choose to Dislike -
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Friday, 02-Feb-2018 00:03:54 UTC
πΎππ½ππππππππΏ
Oh thanks -
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Thursday, 01-Feb-2018 22:33:47 UTC
πΎππ½ππππππππΏ
"unspecified behavior": "the behavior of this construct may vary across implementations but will conform to at least these guarantees"
"undefined behavior": "idk lol Β―\_(γ)_/Β― rm -rf /" -
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Friday, 26-Jan-2018 04:02:37 UTC
πΎππ½ππππππππΏ
I am willing to entertain the posibility that eating Tide Pods and self-modifying code as part of a calling convention may be a false equivalence -
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Monday, 08-Jan-2018 06:29:06 UTC
πΎππ½ππππππππΏ
Oh hey, C++17 is official
or rather it was official a month or so ago. -std=c++17 works in gcc 7 and clang 5
but tbh this is the only improvement I've been able to do that I couldn't do under -std=c++1z: https://sdfn-01.ninjawedding.org/media/7Eydcaqklh_EfoU9OVc -
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Monday, 25-Dec-2017 00:48:06 UTC
πΎππ½ππππππππΏ
Alan Kay, 1972 -
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Monday, 11-Dec-2017 20:27:48 UTC
πΎππ½ππππππππΏ
I forgot who it was that originally pointed out to me that compilation can be seen as just a fancy form of caching, but ever since then I've viewed compilers through that lens -
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Tuesday, 28-Nov-2017 04:48:53 UTC
πΎππ½ππππππππΏ
@er1n hello my name is 451 Unavailable For Legal Reasons -
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Tuesday, 17-Oct-2017 04:51:18 UTC
πΎππ½ππππππππΏ
@er1n lolol I just found this proposal to the C++ standards committee
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3853.htm
this is evidently a much worse problem than I thought -
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Tuesday, 15-Aug-2017 20:15:36 UTC
πΎππ½ππππππππΏ
(I don't know if this is a common thing globally or even in other parts of the US, but in Chicago these touchscreen-based drink dispenser things are showing up more, and they really are a step back in terms of usability.
It's no longer "push lever, get drink"; now, it's "navigate hierarchical menu system, press touch target, get drink except for the ice dispenser which is still mechanically triggered so we still have the push-lever there just to make it confusing") -
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Tuesday, 15-Aug-2017 20:10:07 UTC
πΎππ½ππππππππΏ
Oh, if you want to know which assholes broke the soda fountain UX by putting a giant touchscreen in it, it looks like these people https://www.firstborn.com/work/featured/282/pepsi-spire -
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Monday, 17-Jul-2017 15:28:45 UTC
πΎππ½ππππππππΏ
"Array Layouts for Comparison-Based Searching": https://arxiv.org/pdf/1509.05053.pdf
One thing that I've had to repeatedly struggle with in gamedev is the importance of keeping the CPU fed with data. This usually means predictable memory access patterns and contiguous data structure layouts.
Unfortunately some very useful data structures -- maps, for instance -- are usually implemented in a way that are non-contiguous and don't have predictable access patterns. What do? Well, the easiest (and often quite sufficient) way is to maintain a array of (key, value) tuples, sorted on key, and binary-search it. There are other methods, though, and this paper is a neat survey of those methods.
Bonus: Section 2, "Processor Architecture Considerations", seems to me to be a pretty good overview of just how badly memory latency will slow your code down and the methods employed by CPUs to overcome that latency. -
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Monday, 17-Jul-2017 02:01:53 UTC
πΎππ½ππππππππΏ
"IBM comment on preparing for a
Trigraph-adverse future in C++17", in which a justification for trigraphs for EBCDIC(!) compatibility is made:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4210.pdf
This is a great reminder that somewhere, someone is dealing with an older software legacy than you. -
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Tuesday, 18-Apr-2017 05:44:45 UTC
πΎππ½ππππππππΏ
A plea for nuance and compromise from Megan Phelps-Roper: https://www.youtube.com/watch?v=bVV2Zk88beY
https://sdfn-01.ninjawedding.org/media/lG2q_OE8k7tLpuC9OkU -
πΎππ½ππππππππΏ (ninjawedding@sdfn-01.ninjawedding.org)'s status on Sunday, 02-Apr-2017 20:44:58 UTC
πΎππ½ππππππππΏ
@maiyannah I think it's something a lot of people will just have to learn on their own by curiosity, clashing with community/admin norms, etc. That's what happened to me, anyway.
I know of at least one new group of arrivals that's eager to begin experimenting with their own instances, and I think it's reasonable to say they aren't the only one. That makes me think it'll work out in the long run.
All Chirp! content and data are available under the