loganfsmyth

6 ms·

1.
by loganfsmyth 5y ago
(Replay engineer here): We don't currently support inspecting network requests, but that is something we plan to support in the future.
2.
by loganfsmyth 5y ago
> What's the timeline on Windows support? Work on Windows support in ongoing now and we're hoping to have at least an initial beta Windows release some time in the next month or two ideally, though it certainly depends on if an
3.
by loganfsmyth 5y ago
(Replay engineer here): > What are the limits for the recordings in terms of time and input data size? The best answer right now is that it varies a lot depending on overall CPU usage, the amount of memory used, and the length, so it&#x2
4.
by loganfsmyth 5y ago
(Replay employee here): We have experimental support for some react-specific features using react-devtools since React is such a common framework, but the Replay is a general debugging tool and will work with other frameworks well too.
5.
by loganfsmyth 5y ago
Once a recording is made, you can jump around in it as much as you like. The network requests will only be made during the initial recording process as they would normally, and when debugging it will all be pulling the request/response
6.
by loganfsmyth 5y ago
Very excited to see what folks here think. Replay has been a wonderful project to work on so far.
7.
by loganfsmyth 9y ago
Babel on its own only addresses syntactic functionality and wouldn't cover this, but it is indeed extremely easily to polyfill `classList`.
8.
by loganfsmyth 9y ago
You don't even need the `Array.from` anymore. `.forEach` on `NodeList` is standard https://developer.mozilla.org/en-US/docs/Web/API/NodeList/fo... , so all you need to do is load a polyfill for
9.
by loganfsmyth 9y ago
It's even easier now. `.forEach` on `NodeList` is standard https://developer.mozilla.org/en-US/docs/Web/API/NodeList/fo... , so all you need to do is load a polyfill for that.
10.
by loganfsmyth 10y ago
That doesn't appear to replace variable names with shorter versions, or remove dead code, which Uglify and other minifiers do.
11.
by loganfsmyth 10y ago
I totally agree that the initial user experience for Babel could use some work. We don't tend to do a great job of guiding users through initial setup. It absolutely needs work. I'd be curious to hear the author's thoughts on
12.
by loganfsmyth 11y ago
I've also hit this in the past. However I feel like I remember seeing that the error messaging had been enhaced in whichever version of Chrome came out next. I've forgotten the details now, but I feel like it explicitly said that
13.
by loganfsmyth 11y ago
ES6 imports are declarative, so dependencies are resolved and executed before the body of the module is executed. That means you don't conceptually have to think about whether your dependencies are loading synchronously or asynchronous
14.
by loganfsmyth 11y ago
Just a nit, but that isn't destructuring. Named import syntax has several differences, since name aliasing uses a different format and you cannot nest or provide default values.
15.
by loganfsmyth 11y ago
Both are useful, but I'd hesitate to call it better. What makes you say it is better?
16.
by loganfsmyth 11y ago
I switched to Fi about a month ago and it has served me very well in the Bay area so far, and it made a trip to the east coast with good wifi and bad cell service much easier because I could just use wifi. Also liking the Nexus 6. After pla
17.
by loganfsmyth 11y ago
JSON is a very specific subset of JavaScript, and there is no literal syntax for Symbols, so there is no defined way to represent a symbol at the moment. Unless you wanted to encode them as a function call or something, which sounds terribl
18.
by loganfsmyth 11y ago
To me at least, that's more up to NPM to manage though. As it is, it means you're essentially sidestepping npm. There's also no guarantee that people will install a version of babel-runtime that is compatible with the version
19.
by loganfsmyth 11y ago
Looks cool. Not sure I get why installing `babel-runtime` would be something you'd have as a separate install step though, since there is no guarantee that the user would install the right version.
20.
by loganfsmyth 11y ago
The main other benefit of decorators is that they work on property descriptors, and are automatically passed property names and the target object, so you have a bit more info. Having the descriptor means for instance that you can switch a v
21.
by loganfsmyth 11y ago
Yeah, I wish that were handled better too. Since the parser is expecting a statements, it parses it like { a } = 5 As in, a block with just an "a" in it, followed by an assignment to nothing, which throws a
22.
by loganfsmyth 11y ago
Happy to hear Babel is working well for you. I'm loving it too so far. Just to noet, named imports aren't technically destructuring though, since the syntax is different and doesn't nest. e.g. import { fooFunc as otherF
23.
by loganfsmyth 11y ago
I see an "aliceblue". No idea if there is a history behind it. http://dev.w3.org/csswg/css-color/#named-colors
24.
by loganfsmyth 11y ago
Overall, totally agree, just wanted to mention two things. 2) I've always found passing callbacks by name to be very difficult to read/follow, but this is a case where I think ES6 arrow functions will help readability a lot.
25.
by loganfsmyth 11y ago
The main thing in my mind is that it means your code could have cases where it throws synchronously, and cases where the promise rejects with an error. One place this is mentioned is: https://github.com/petkaantonov/blu
26.
by loganfsmyth 11y ago
That was my first question too. QUIC is all user-land code.
27.
by loganfsmyth 11y ago
Definitely second writing your own as a way to learn. I wrote one that could mostly play pong a while back and it was super satisfying. The PPU was definitely the toughest part.
28.
by loganfsmyth 11y ago
Maybe it's only a hashed version of the characters? :P
29.
by loganfsmyth 12y ago
I save pretty compulsively, so this would annoy the crap out of me...
30.
by loganfsmyth 12y ago
Definitely. Thankfully, ES6 will introduce "🍣".codePointAt(0) and iterators will iterate code points, not code units. for (var c of "🍣"){}

More ›