01:11:08  * akirosejoined
01:12:05  * aki_quit (Ping timeout: 244 seconds)
02:14:41  * AtumT_quit (Remote host closed the connection)
02:53:34  * gibson042joined
03:17:48  * aki_joined
03:19:14  * akirosequit (Ping timeout: 260 seconds)
04:11:06  * jmdyckquit (Remote host closed the connection)
05:24:15  * akirosejoined
05:25:51  * aki_quit (Ping timeout: 268 seconds)
07:30:47  * aki_joined
07:31:27  * akirosequit (Ping timeout: 240 seconds)
09:37:27  * akirosejoined
09:38:41  * aki_quit (Ping timeout: 248 seconds)
09:38:54  * keith_millerjoined
10:07:46  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
10:25:11  * mylesborinsquit (Quit: farewell for now)
10:25:19  * mylesborinsjoined
10:41:31  * jmdyckjoined
10:44:55  * gibson042quit (Quit: Leaving.)
11:44:08  * aki_joined
11:45:21  * akirosequit (Ping timeout: 264 seconds)
13:25:13  * emilianobovetti[joined
13:49:46  * akirosejoined
13:51:20  * aki_quit (Ping timeout: 276 seconds)
14:19:53  * AtumTjoined
14:34:00  * gibson042joined
15:56:04  * aki_joined
15:57:19  * akirosequit (Ping timeout: 268 seconds)
16:29:36  * keith_millerjoined
16:31:30  * keith_millerquit (Client Quit)
16:33:26  * AtumTquit (Remote host closed the connection)
16:40:37  * keith_millerjoined
16:43:43  * keith_millerquit (Client Quit)
16:51:56  * keith_millerjoined
17:34:26  * AtumTjoined
17:36:22  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
17:40:48  * keith_millerjoined
18:02:16  * akirosejoined
18:03:12  * aki_quit (Ping timeout: 244 seconds)
18:55:12  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
18:58:10  * keith_millerjoined
19:33:11  * gibson042quit (Quit: Leaving.)
19:40:48  * towcjoined
19:41:30  <towc>so, I came across a really annoying thing about proxies, and I couldn't find much information about it online, other than a post that links to what I'd consider a bug in the spec, but maybe someone can tell me otherwise
19:41:36  <towc>http://jsbin.com/xafeluziqa/edit?js,console
19:42:07  <towc>or to save some clicks:
19:42:08  <towc>/ from a framework. Modifying this would be a horrible unmaintainable hack
19:42:09  <towc>const session = {};
19:42:09  <towc>Object.defineProperty(session, 'id', {
19:42:09  <towc> writable: false,
19:42:09  <towc> value: 123,
19:42:10  <towc>});
19:42:12  <towc>/ simplification of code I'm using
19:42:14  <towc>const modSession = new Proxy(session, {
19:42:16  <towc> get(obj, prop) {
19:42:20  <towc> return obj[`mod${prop}`];
19:42:22  <towc> },
19:42:24  <towc> set(obj, prop, value) {
19:42:26  <towc> console.log(obj);
19:42:28  <towc> obj[`mod${prop}`] = value;
19:42:30  <towc> return true; // bad practice, but it proves a point
19:42:32  <towc> }
19:42:34  <towc>});
19:42:36  <towc>modSession.xyz = 'abc'; // {...}
19:42:38  <towc>modSession.abc = 123; // {..., modxyz}
19:42:40  <towc>modSession.id = 456; // {..., modxyz, modabc}
19:42:42  <towc>/ TypeError, it was looking at writable in session.id
19:42:44  <towc>/ instead of session.modid
19:43:20  <towc>I find the Q here fairly confusing, but the answer seems to make sense for my problem too: https://stackoverflow.com/questions/46227721/typeerror-with-proxy-class-typeerror-set-on-proxy-trap-returned-truish-for
19:43:50  <towc>is this something that is going to get fixed? Or because it's already a standard, it can't be changed? Where can I read more about it?
19:46:46  <towc>I think this will easily lead to so many bugs that will hit developers down the line, but maybe I should just use a better data structure and this is considered proxy abuse
20:08:58  * aki_joined
20:10:05  * akirosequit (Ping timeout: 240 seconds)
21:32:16  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
21:39:53  * keith_millerjoined
22:00:32  * ryzokukenquit (Ping timeout: 268 seconds)
22:15:40  * akirosejoined
22:16:44  * aki_quit (Ping timeout: 260 seconds)
22:43:17  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)