text
stringlengths
0
1.36k
**Alex Sexton:** They don't have to...
**Mikeal Rogers:** They don't have to, but if you talk to Slack, for instance... They have ostensibly the exact same thing on the website as they do on the desktop, and the desktop has a lot more engagement. Getting to people initially, asking them to (before they've seen any value) download this thing is a bit of a st...
**Alex Sexton:** I agree.
**Mikeal Rogers:** We still value the desktop, it looks like. There's been some great articles lately... GitHub actually -- they have these GitHub desktop apps that they've built a while back, and they have not actually moved them to Electron yet, so they wrote up their experiences - some C\# and Objective-C developers...
Alright, moving on to our picks... Everybody got their picks locked and loaded?
**Alex Sexton:** \[56:12\] Yeah, but mine's a copout.
**Mikeal Rogers:** Okay... Well, we'll start with your cop-out then, and then we'll go up from there.
**Alex Sexton:** It's create-react-app 1.0, baby.
**Mikeal Rogers:** Oh, shut up... \[laughs\] You can't pick the project of the week. That's like cheating.
**Alex Sexton:** Okay... Webpack 2.
**Mikeal Rogers:** \[laughs\] Tell us about Webpack 2. What's in it?
**Alex Sexton:** Tree shaking.
**Mikeal Rogers:** \[laughs\] Alright, I'm just gonna go on a little bit of a tangent here and you're gonna get mad about it... But I think that if you need tree shaking, you're dependent on some anti-patterns. I don't think that we should have these grab bag modules with a bunch of other properties in them that you sh...
**Alex Sexton:** Maybe...
**Mikeal Rogers:** \[laughs\] Maybe... That's an amazing rebuttal. \[laughter\]
**Rachel White:** Anyway, my pick of the week -- were you gonna say something else? Go ahead, Alex...
**Alex Sexton:** I was gonna say that I agree to an extent that if you write something that has a few too many things, then tree shaking becomes a crutch, but I also think that take a substack or take a set of tools that are only substack and you'll still get some benefit from tree shaking in the end. It won't be massi...
I think tree shaking becomes even more cool when it can -- I guess you guys were gone when we made this the project of the week... What was that thing? Code-something came our recently... Facebook -- it was the project of... Anyways, it tries to code unroll and precompute things that are already available to compute at...
**Mikeal Rogers:** \[laughs\] Alright. Rachel, what's your pick?
**Rachel White:** My pick of the week is a talk from JSConf EU that just happened that I unfortunately did not get to see in person... It's from Anjana Vakil and it's about immutable data structures for functional JS. She explains it in such a really simplified, easy to understand way for people that don't really under...
So yeah, if anybody else was wondering about that kind of thing, there's a link to it and it's pretty great.
**Mikeal Rogers:** Awesome.
**Alex Sexton:** \[01:00:10.11\] Earlier in the episode we talked about features that we don't use... My wish is that there was a way to use Immutable.js as the default in the syntax... Like there could be a Babel plugin for immutable versions of things. And there actually is a spec - I think Sebastian Markbåge propose...
**Rachel White:** Cool.
**Mikeal Rogers:** Cool. Okay, my pick is a book... It's actually a really old book. It came out like in the '80s, I think... '84. Crazy. It's called "Hackers", and it's not...
**Alex Sexton:** I've seen the movie...
**Mikeal Rogers:** It's not -- there's no rollerblading... \[laughs\] Hackers is about the origins of hacker culture, which eventually kind of became early technology and open source culture. You can skip the third part -- the book is in three parts, and the third one does not hold up. The first one is basically from t...
**Alex Sexton:** What's that chapter about...?
**Mikeal Rogers:** So hold on... The second chapter is about the Homebrew Computer Club and early Apple and early computing in the Bay Area, and also how a bunch of really crazy counter-culture political figures also informed that culture and what they were doing, and that's super interesting.
The third section is about the gaming industry, about Sierra and all those companies that were in the early '80s. At the time it was like, "Oh, and then this is what people are doing right now", but it really doesn't connect very well to the other parts and it really doesn't hold up as like "this particular section of ...
One of the appendices is called "The last hacker", and it's about the last person in the MIT AI lab that is kind of the keeper of the flame for hacker culture. It's about Richard Stallman before he started the GNU project and before there was even such a thing as copyleft licenses or a GPL to argue about. It is fascina...
I've been trying to read a lot about early hacker culture and how the counter-culture movement played into all this stuff, and this one of the best books to really dig into it. It's by Steven Levy and it's called Hackers. There you go.
**Alex Sexton:** My pick is the movie Sneakers.
**Mikeal Rogers:** Oh, that's a good movie!
**Rachel White:** Oh my god!
**Mikeal Rogers:** It's really the only tech movie that holds up, really...
**Alex Sexton:** River Phoenix?
**Mikeal Rogers:** Yeah, yeah... Oh man, that's a good one... That's a really good one. Some Robert Redford... Okay, anyway... Great talking with you all. I think that we're just about done now. Rate us on iTunes, check us out at Changelog.com/JSParty, you can get into our Slack, you can catch us live every Friday at n...
• Introduction of JSParty and its hosts
• Discussion of the hosts' recent vacation and being temporarily replaced by others
• Topic for discussion: using ES6 and ES7 features, trade-offs, and specific features rather than "buckets"
• Rachel shares her limited experience with new language features, mentioning arrow functions and template literals
• Alan discusses his disagreement that arrow functions make code more readable, citing issues with implicit returns and patterns
• Discussion of the use of arrow functions and their impact on readability in larger systems
• Semantics of arrow functions and lexical scope
• Complexity reduction by avoiding older syntax
• Debate over defaulting to arrow functions or traditional functions
• Pitfalls of using class syntax with implicit returns
• Ambiguity between lexically bound functions and unbound functions
• Potential gotchas when using class syntax with arrow functions
• Discussion on the new rules and classes in programming
• Lexically bound ambiguity and its elimination
• Use of compilers for legacy browser support
• Babel as a tool for compiling code to ES5 or older versions
• Adoption rates of newer features like object spreads and array spreads
• Debate over whether it's worth using a compiler for modern browsers that support new features
• IoT projects and JavaScript usage
• Common JavaScript features in frameworks like Vue, React, and Ember
• Features not widely used or accepted
• Issues with implementing modules in Node due to conflicting specifications
• Proxies as a feature that is not well-suited for current use cases
• Metaclasses and similar concepts being discouraged in favor of other approaches
• Proposals in the language spec that may not gain traction