Browse 462 talks from our meetups. Covering everything from JavaScript fundamentals to cutting-edge frameworks.
Showing 12 of 462 talks (Page 15 of 39)
JavaScript's native date API is rather weak. Actually, the Date() object has been a long-standing pain point in ECMAScript. It comes from ideas taken from the java.util.Date (sic!) package, which became obsolete back in 1997! It has many limitations - just to name a few: - it only supports UTC and the user’s PC time, - it doesn’t support non-Gregorian calendars, - string to date parsing is error-prone, - Date objects are mutable It is possible to use external libraries, but it's an additional payload which is not always desirable, and is non-standard. But there's good news! New Temporal static global date object, that acts as a top-level namespace (like Math), is at Stage 3 Candidate Proposal in the TC39 standards approval process (the final stage before implementation). The Temporal fixes these above-mentioned Date() problems by: - Providing easy-to-use APIs for date and time computations - First-class support for all time zones, including DST-safe arithmetic - Dealing only with objects representing fixed dates and times - Parsing a strictly specified string format - Supporting non-Gregorian calendars - etc... This makes code more readable and prevents bugs caused by incorrectly assuming 0, UTC, or the local time zone for values that are actually unknown.
Since Node.js came out, a fullstack developer could know just one language - JavaScript and later TypeScript - to write the entire code base. There are many professional software developers today who don't even know any other language. WebAssembly is going to completely disrupt this and it's time to learn low level systems languages, out of which Zig is an interesting choice for many reasons.
I've created a tool to help you customize your apps/news feeds etc. by reducing the effectiveness of dark patterns, and other techniques designed to make you: * spend more money * waste more time * lose your train of thought Built using HTML, JavaScript and Python?
When writing code in BDD way you can write down a more broad test that fails purposefully, and later as soon as it passes it should inform that it can now be marked as not failing anymore. This helps a lot when you stumble upon a hard scenario to implement. This presentation will give a short intro to BDD and TDD and show how to write tests efficiently.
Every frontender knows how to create an SPA and define routes for the app. But do you know how to do it in a SEO friendly way? In this talk, we will take a closer look at routing of an SPA, we will identify common problems that might hurt your SEO, and we will try to find the best solution to overcome those problems.
'New day, new framework' - is this still valid? I follow front-end trends and I want to share my thoughts on them. Both experienced front-end developers and the beginners, expecting a quick summary, should find something valuable for them in my talk. I’m going to start with facts & statistics, then we’ll think about the future of JS & its frameworks, talk through npm problems and we’ll finish up with an open topic: can anyone take over our lovely technologies?
Have you ever thought about simplifying the process of implementing web applications that much, that it would be enough to provide just an image of what would be your expected outcome? Let me show you how this can be done. I will demonstrate how to change a screenshot or a mockup into a real web application. No low-code nor no-code approach, just an old beautiful source code.