Datasets:
2017-JS-Party-Transcripts / Web Assembly, Higher Education with JavaScript, JS Standards_summary.txt
| • WebAssembly is a new platform being developed, inspired by asm.js and aimed at compiling languages other than JavaScript to run in web browsers. | |
| • It's designed to improve performance for tasks like encryption and high-performance computing, while maintaining sandboxing and web security features. | |
| • Game developers are likely to be among the first adopters of WebAssembly. | |
| • The technology is still experimental and requires running Node.js with a specific flag or using Chrome/Firefox with flags enabled. | |
| • The current spec is considered stable enough for browser implementations, but it's not yet exposed in most browsers. | |
| • The challenges in implementing WebAssembly include ensuring cross-browser compatibility, maintaining backwards compatibility, and addressing concerns around garbage collection and memory sharing between different languages. | |
| • History of attempts to create alternative JavaScript interpreters and languages (e.g. Dart) | |
| • asm.js limitations and failure to effectively share native resources | |
| • WebAssembly as an attempt to go beyond asm.js limitations by creating a lower-level compile target language that can work inside the same VM as JavaScript | |
| • Concerns about WebAssembly potentially leading to degradation in performance if vendors stop optimizing for JavaScript | |
| • Possibility of alternative languages compiling down to WebAssembly and running in the browser, but with potential performance issues | |
| • Discussion of Node.js and other server-side use cases where JavaScript is still a popular choice despite having alternatives | |
| • WebAssembly as a JavaScript file with an external API | |
| • Stanford University transitioning from Java to JavaScript in their CS106 course | |
| • Ease of use and debugging in JavaScript compared to Java | |
| • Potential benefits of starting programming with dynamic, non-typed languages like JavaScript | |
| • TypeScript or Flow as optional typing for JavaScript projects | |
| • Curriculum revision at Stanford University, including a course on Computer Science and Social Good | |
| • Discussion on the addition of typing to JavaScript at Stanford University | |
| • Comparison of Flow type and TypeScript as optional typed editions to JavaScript | |
| • Benefits of learning types in CS degree programs | |
| • Differences between dynamic languages and statically-typed languages | |
| • Functionality of Flow type and its capabilities for adding types to codebases | |
| • Usage of Flow at Stripe and benefits of having typed definitions for third-party libraries | |
| • Discussion on the effectiveness of types for safety and speed | |
| • Introduction to lesser-known JS Standards: Abstract Blob Store and Abstract Chunk Store | |
| • Explanation of the Dat Project as a toolchain for open scientists to share data and manipulate it | |
| • Comparison between Abstract Blob Store and IndexDB, including persistence and async functionality | |
| • Mention of the LevelUP ecosystem and its role in building abstract standards | |
| • IPFS Abstract Blob Store | |
| • Dat Project | |
| • LevelUP and abstract LevelDOWN stores | |
| • Flow-typed repository for type definitions | |
| • Offline Camp community and events | |
| • JSConf EU conference dates | |
| • Recommendations for Vietnamese noodle places in Berlin (Monsieur Vuong) and dumpling places with Trips of Beef | |
| • Alex Sexton plans to attend JSConf EU with his child. | |
| • Rachel White recommends Data Sketches project for data visualization using D3 and other tools. | |
| • Discussion of visualizing data through interactive means using D3 and its benefits. | |
| • Upcoming conferences mentioned: OpenVis Conf, CSV Conf, and JSConf EU. |