My talk at the January 21, 2009 Mountain View JavaScript Meetup about the performance of JavaScript variables relative to their position in the scope chain.
Nicholas C. Zakas discusses common JavaScript performance issues and recommendations to address them. He covers scope management, data access, loops, and DOM manipulation. The key points are to minimize scope chain lookups, store frequently accessed data in local variables, optimize loops, avoid reflows from DOM changes, and leverage modern browser optimizations. Overall, the talk provides practical tips to speed up JavaScript code by addressing issues related to scope, data access patterns, loops, and DOM interactions.
Writing Efficient JavaScript discusses common issues that can slow down JavaScript performance and provides recommendations to address them. It covers scope management, data access, loops, DOM manipulation, and avoiding browser limits. The document recommends minimizing scope chain lookups, storing frequently accessed properties in local variables, optimizing loops, performing DOM changes off-document to reduce reflows, and using setTimeout() to avoid locking up the browser thread.
Progressive Enhancement 2.0 (jQuery Conference SF Bay Area 2011)Nicholas Zakas
In the beginning, progressive enhancement was simple: HTML layered with CSS layered with JavaScript. That worked fine when there were two browsers, but in today's world of multiple devices and multiple browsers, it's time for a progressive enhancement reboot. At the core is the understanding that the web is not print - the same rules don't apply. As developers and consumers we've been fooled into thinking about print paradigms for too long. In this talk, you'll learn just how different the web is and how the evolution of progressive enhancement can lead to better user experiences as well as happier developers and users.
The document discusses optimizing JavaScript performance for Yahoo's homepage. It describes techniques used such as:
1. Loading non-critical JavaScript asynchronously and lazily to improve time to interactivity.
2. Splitting long-running JavaScript tasks into smaller chunks with timers to maintain responsiveness.
3. Using Web Workers to offload CPU-intensive tasks without blocking the UI thread.
4. Caching and preloading resources to reduce roundtrip times for Ajax requests.
The techniques helped optimize performance by reducing JavaScript parsing time and improving responsiveness.
High Performance JavaScript (Amazon DevCon 2011)Nicholas Zakas
The document summarizes techniques for improving JavaScript performance in web applications. It discusses how JavaScript execution blocks the browser UI thread, leading to unresponsive user experiences if scripts run for too long. It then provides recommendations to limit JavaScript execution times to under 50ms and describes load time techniques like placing scripts at the bottom of the page, combining files, and loading scripts dynamically or deferring their execution to improve page load performance.
The document discusses responsive interfaces and how to keep the user interface responsive when executing JavaScript. It explains that the UI thread is used for both drawing updates and running JavaScript, so no updates can happen while JavaScript runs. It recommends keeping JavaScript execution under 50ms to avoid unresponsiveness, and describes using timers and web workers to split processing over multiple ticks to keep the UI responsive.
Test Driven Development With YUI Test (Ajax Experience 2008)Nicholas Zakas
This document discusses test-driven development (TDD) using the YUI Test framework. It introduces TDD principles like writing tests before code and iterating through failing tests, passing tests, and refactoring. It then covers key aspects of YUI Test like writing unit tests, simulating events, handling asynchronous code, and hooking into the test runner. The document provides examples and recommendations for effectively using TDD and YUI Test in web development.
As browsers explode with new capabilities and migrate onto devices users can be left wondering, “what’s taking so long?” Learn how HTML, CSS, JavaScript, and the web itself conspire against a fast-running application and simple tips to create a snappy interface that delight users instead of frustrating them.
In the beginning, progressive enhancement was simple: HTML layered with CSS layered with JavaScript. That worked fine when there were two browsers, but in today's world of multiple devices and multiple browsers, it's time for a progressive enhancement reboot. At the core is the understanding that the web is not print - the same rules don't apply. As developers and consumers we've been fooled into thinking about print paradigms for too long. In this talk, you'll learn just how different the web is and how the evolution of progressive enhancement can lead to better user experiences as well as happier developers and users.
This deck is a conference-agnostic one, suitable to be shown anywhere without site-specific jokes!
This document provides an overview of hybrid mobile application development using HTML5, CSS and JavaScript. It discusses frameworks like PhoneGap and jQuery Mobile that allow building cross-platform apps for iOS, Android and other mobile platforms from a single codebase. Key points include how these frameworks integrate with native SDKs while exposing native device APIs to web technologies, and examples of building demo hybrid apps targeting iPhone and Android.
Firefox 3.5 Overview; Interesting statistics, feature for user and developer.
Thank for http://www.slideshare.net/
tbassetto/firefox-31-in-31-minutes
The document discusses building websites that work for all users regardless of browser, operating system, device or connection. It emphasizes building websites using progressive enhancement and graceful degradation to provide core content and functionality to all while enhancing the experience for newer browsers. It also discusses modern browser support and trends, new web standards like HTML5, and taking a "future friendly" approach to support emerging technologies while degrading gracefully.
The document discusses the history of web browsers and layout engines. It describes how Microsoft's Internet Explorer and Netscape competed in the 1990s/2000s through proprietary features, leading to fragmentation. Now the mobile browser market is dominated by WebKit, with Chrome and Safari using it. The document advocates for standards-compliant development and feature detection to avoid browser sniffing and promote an open web.
Mozilla's mission is to promote choice, innovation and participation on the Internet. Mozilla stands on the shoulders of giants such as open source operating systems, databases, web servers and scripting languages as well as open web standards. Firefox 3.5 provides improved speed, user experience, security and privacy, customization and technical capabilities compared to earlier Firefox versions.
The document provides an overview of Denis Platonov's experience with web technologies from 2008 to 2011 focusing on HTML, CSS, and JavaScript. It then discusses the evolution of the web from HTML 4.01 to HTML5, highlighting new CSS3 features and the introduction of HTML5. The document outlines several HTML5 features including offline storage, web workers, web sockets, geolocation, new form input types, the <canvas> element, and audio/video support. It encourages using feature detection with Modernizr to support HTML5 and CSS3 across browsers.
1. Internet Explorer (IE) is a web browser developed by Microsoft and included in the Microsoft Windows operating system. It was first released in 1995 and became the dominant browser for several years.
2. In the late 2000s, IE lost market share to Google Chrome and Mozilla Firefox. As of 2022, IE's global usage share is less than 10%.
3. IE allows users to view web pages, send and receive email, access social media sites, conduct online shopping, and transfer files using basic functions like a back button, search bar, and home page. It supports technologies like HTML, Java, and FTP.
My preliminary presentation for the report "Client-Side Storage in Web Application". 2012.
by Markku Laine, http://www.tinyurl.com/mplaine
The document discusses several popular web browsers: Opera, Firefox, and Google Chrome. It provides details on their key features such as [1] Opera being cross-platform and having built-in email/address book capabilities. Firefox 2.0 incorporated improvements like quick search links and tabbed browsing. Google Chrome is designed for speed and powered by WebKit with translation, customization, and incognito modes.
Progressive Enhancement is one of the most important and useful software engineering tools in our web development toolbox, but in practice it's largely ignored. We'll dive into the basics of PE, the common pitfalls (think <noscript> and the newer class="no-js"), how to support Blackberry 4.x and IE6 without a ton of extra work, tools to avoid that violate PE best practices, and how to apply PE pragmatically.
1. The document discusses the rise of HTML5 and its adoption in China, noting that older versions of Internet Explorer still dominate the market but that HTML5 support is improving in newer browsers.
2. It provides statistics on browser support for HTML5 features from the HTML5 Test website and global browser usage statistics, showing Internet Explorer 6-8 make up over 80% of the Chinese market.
3. The document advocates for progressive enhancement approaches to support older browsers while taking advantage of new HTML5 features in modern browsers to provide richer experiences.
HTML5 introduces several new elements for embedding multimedia content like audio and video. The <audio> element displays audio content while the <video> element displays video content. The <source> element specifies multiple media resources for media elements and is defined inside <audio> or <video> elements. The <embed> element embeds external content like a plug-in. HTML5 also introduces new form input types for entering dates, numbers, email addresses and other structured data.
The document compares several popular JavaScript libraries and frameworks for building web applications, including jQuery, Prototype, Dojo, Ext JS, MooTools, and others. It evaluates them based on criteria like popularity, features, cross-browser compatibility, and how well they integrate with other libraries and tools. After testing the frameworks, jQuery was selected as the winner for the Kauri project due to its lightweight size, active community, and beautiful, concise syntax.
The document compares several popular JavaScript libraries and frameworks for choosing one to use in a web application project. It evaluates libraries like jQuery, Prototype, Dojo, Ext JS and others based on criteria like popularity, features, browser compatibility, and how well they integrate with other tools needed for the project. After testing the top candidates, jQuery is selected as the winner due to its lightweight size, active community, and ability to meet the project's requirements.
The document compares several popular JavaScript libraries and frameworks for choosing one to use in a web application project. It evaluates libraries like jQuery, Prototype, Dojo, Ext JS and others based on criteria like popularity, features, browser compatibility, and how well they integrate with other tools. After testing the top candidates, jQuery is selected as the winner due to its blooming community, concise language, and lightweight size.
The document compares several popular JavaScript libraries and frameworks for building web applications, including jQuery, Prototype, Dojo, MooTools, Ext JS, qooxdoo, and YUI. It evaluates them based on criteria like popularity, features, cross-browser compatibility, and how well they integrate with other libraries and tools. After testing the frameworks on sample tasks, the document concludes that jQuery will be the best choice for the Kauri project due to its lightweight nature, growing community, and beautiful syntax.
The document provides information about web browsers and market share. It discusses the first web browser created by Tim Berners-Lee and the top browsers as of April 2009, including Internet Explorer 7.0 with 45% market share. Charts show the top browser trends from Q1 2008 to Q2 2009 and reasons why browser market share numbers alone don't tell the full story. Finally, it outlines 10 cool things that will be possible once the outdated Internet Explorer 6 browser is eliminated, such as using new CSS selectors and properties and eliminating most CSS hacks.
The document summarizes the history of Mozilla and Firefox, from the initial open sourcing of the Netscape browser code in 1998 to the present. It discusses key milestones like the releases of Mozilla 1.0 and Firefox 1.0, and how Firefox was developed in response to limitations in Netscape and Internet Explorer. It also outlines Mozilla's vision for an open web and how the non-profit organization and browser development community operates.
Browser Wars Episode 1: The Phantom MenaceNicholas Zakas
This document summarizes the history and evolution of web browsers and internet technologies from the early 1990s to the late 1990s. It traces the development of key browsers like Netscape Navigator and Internet Explorer. It also outlines the introduction of important web standards like HTML, CSS, JavaScript and XML. Major events included the commercialization of the web in the mid-1990s, the browser wars between Netscape and Microsoft in the late 90s, and the consolidation of online services providers toward the end of the decade.
After consulting with several companies on performance related issues, it became clear that one of the biggest performance issues facing websites today is the sheer amount of JavaScript needed to power the page. The demand for more interactive and responsive applications has driven JavaScript usage through the roof. It’s quite common for large sites to end up with over 1 MB of JavaScript code on their page even after minification. But do today’s web applications really need that much JavaScript?
In the beginning, progressive enhancement was simple: HTML layered with CSS layered with JavaScript. That worked fine when there were two browsers, but in today's world of multiple devices and multiple browsers, it's time for a progressive enhancement reboot. At the core is the understanding that the web is not print - the same rules don't apply. As developers and consumers we've been fooled into thinking about print paradigms for too long. In this talk, you'll learn just how different the web is and how the evolution of progressive enhancement can lead to better user experiences as well as happier developers and users.
This deck is a conference-agnostic one, suitable to be shown anywhere without site-specific jokes!
This document provides an overview of hybrid mobile application development using HTML5, CSS and JavaScript. It discusses frameworks like PhoneGap and jQuery Mobile that allow building cross-platform apps for iOS, Android and other mobile platforms from a single codebase. Key points include how these frameworks integrate with native SDKs while exposing native device APIs to web technologies, and examples of building demo hybrid apps targeting iPhone and Android.
Firefox 3.5 Overview; Interesting statistics, feature for user and developer.
Thank for http://www.slideshare.net/
tbassetto/firefox-31-in-31-minutes
The document discusses building websites that work for all users regardless of browser, operating system, device or connection. It emphasizes building websites using progressive enhancement and graceful degradation to provide core content and functionality to all while enhancing the experience for newer browsers. It also discusses modern browser support and trends, new web standards like HTML5, and taking a "future friendly" approach to support emerging technologies while degrading gracefully.
The document discusses the history of web browsers and layout engines. It describes how Microsoft's Internet Explorer and Netscape competed in the 1990s/2000s through proprietary features, leading to fragmentation. Now the mobile browser market is dominated by WebKit, with Chrome and Safari using it. The document advocates for standards-compliant development and feature detection to avoid browser sniffing and promote an open web.
Mozilla's mission is to promote choice, innovation and participation on the Internet. Mozilla stands on the shoulders of giants such as open source operating systems, databases, web servers and scripting languages as well as open web standards. Firefox 3.5 provides improved speed, user experience, security and privacy, customization and technical capabilities compared to earlier Firefox versions.
The document provides an overview of Denis Platonov's experience with web technologies from 2008 to 2011 focusing on HTML, CSS, and JavaScript. It then discusses the evolution of the web from HTML 4.01 to HTML5, highlighting new CSS3 features and the introduction of HTML5. The document outlines several HTML5 features including offline storage, web workers, web sockets, geolocation, new form input types, the <canvas> element, and audio/video support. It encourages using feature detection with Modernizr to support HTML5 and CSS3 across browsers.
1. Internet Explorer (IE) is a web browser developed by Microsoft and included in the Microsoft Windows operating system. It was first released in 1995 and became the dominant browser for several years.
2. In the late 2000s, IE lost market share to Google Chrome and Mozilla Firefox. As of 2022, IE's global usage share is less than 10%.
3. IE allows users to view web pages, send and receive email, access social media sites, conduct online shopping, and transfer files using basic functions like a back button, search bar, and home page. It supports technologies like HTML, Java, and FTP.
My preliminary presentation for the report "Client-Side Storage in Web Application". 2012.
by Markku Laine, http://www.tinyurl.com/mplaine
The document discusses several popular web browsers: Opera, Firefox, and Google Chrome. It provides details on their key features such as [1] Opera being cross-platform and having built-in email/address book capabilities. Firefox 2.0 incorporated improvements like quick search links and tabbed browsing. Google Chrome is designed for speed and powered by WebKit with translation, customization, and incognito modes.
Progressive Enhancement is one of the most important and useful software engineering tools in our web development toolbox, but in practice it's largely ignored. We'll dive into the basics of PE, the common pitfalls (think <noscript> and the newer class="no-js"), how to support Blackberry 4.x and IE6 without a ton of extra work, tools to avoid that violate PE best practices, and how to apply PE pragmatically.
1. The document discusses the rise of HTML5 and its adoption in China, noting that older versions of Internet Explorer still dominate the market but that HTML5 support is improving in newer browsers.
2. It provides statistics on browser support for HTML5 features from the HTML5 Test website and global browser usage statistics, showing Internet Explorer 6-8 make up over 80% of the Chinese market.
3. The document advocates for progressive enhancement approaches to support older browsers while taking advantage of new HTML5 features in modern browsers to provide richer experiences.
HTML5 introduces several new elements for embedding multimedia content like audio and video. The <audio> element displays audio content while the <video> element displays video content. The <source> element specifies multiple media resources for media elements and is defined inside <audio> or <video> elements. The <embed> element embeds external content like a plug-in. HTML5 also introduces new form input types for entering dates, numbers, email addresses and other structured data.
The document compares several popular JavaScript libraries and frameworks for building web applications, including jQuery, Prototype, Dojo, Ext JS, MooTools, and others. It evaluates them based on criteria like popularity, features, cross-browser compatibility, and how well they integrate with other libraries and tools. After testing the frameworks, jQuery was selected as the winner for the Kauri project due to its lightweight size, active community, and beautiful, concise syntax.
The document compares several popular JavaScript libraries and frameworks for choosing one to use in a web application project. It evaluates libraries like jQuery, Prototype, Dojo, Ext JS and others based on criteria like popularity, features, browser compatibility, and how well they integrate with other tools needed for the project. After testing the top candidates, jQuery is selected as the winner due to its lightweight size, active community, and ability to meet the project's requirements.
The document compares several popular JavaScript libraries and frameworks for choosing one to use in a web application project. It evaluates libraries like jQuery, Prototype, Dojo, Ext JS and others based on criteria like popularity, features, browser compatibility, and how well they integrate with other tools. After testing the top candidates, jQuery is selected as the winner due to its blooming community, concise language, and lightweight size.
The document compares several popular JavaScript libraries and frameworks for building web applications, including jQuery, Prototype, Dojo, MooTools, Ext JS, qooxdoo, and YUI. It evaluates them based on criteria like popularity, features, cross-browser compatibility, and how well they integrate with other libraries and tools. After testing the frameworks on sample tasks, the document concludes that jQuery will be the best choice for the Kauri project due to its lightweight nature, growing community, and beautiful syntax.
The document provides information about web browsers and market share. It discusses the first web browser created by Tim Berners-Lee and the top browsers as of April 2009, including Internet Explorer 7.0 with 45% market share. Charts show the top browser trends from Q1 2008 to Q2 2009 and reasons why browser market share numbers alone don't tell the full story. Finally, it outlines 10 cool things that will be possible once the outdated Internet Explorer 6 browser is eliminated, such as using new CSS selectors and properties and eliminating most CSS hacks.
The document summarizes the history of Mozilla and Firefox, from the initial open sourcing of the Netscape browser code in 1998 to the present. It discusses key milestones like the releases of Mozilla 1.0 and Firefox 1.0, and how Firefox was developed in response to limitations in Netscape and Internet Explorer. It also outlines Mozilla's vision for an open web and how the non-profit organization and browser development community operates.
Browser Wars Episode 1: The Phantom MenaceNicholas Zakas
This document summarizes the history and evolution of web browsers and internet technologies from the early 1990s to the late 1990s. It traces the development of key browsers like Netscape Navigator and Internet Explorer. It also outlines the introduction of important web standards like HTML, CSS, JavaScript and XML. Major events included the commercialization of the web in the mid-1990s, the browser wars between Netscape and Microsoft in the late 90s, and the consolidation of online services providers toward the end of the decade.
After consulting with several companies on performance related issues, it became clear that one of the biggest performance issues facing websites today is the sheer amount of JavaScript needed to power the page. The demand for more interactive and responsive applications has driven JavaScript usage through the roof. It’s quite common for large sites to end up with over 1 MB of JavaScript code on their page even after minification. But do today’s web applications really need that much JavaScript?
Believe it or not, accessibility is more than just screen readers. There's a whole group of users who only use a keyboard (without a mouse). Learn how to make the web a friendly place for all kinds of people by ensuring keyboard accessibility.
JavaScript APIs you’ve never heard of (and some you have)Nicholas Zakas
The document discusses several JavaScript APIs related to manipulating the DOM and CSS, including some newer APIs that the reader may be unfamiliar with. It describes APIs such as insertAdjacentHTML() and outerHTML for inserting and retrieving HTML, children and firstElementChild/lastElementChild for traversing element nodes, and matches() and getBoundingClientRect() for working with CSS selectors and elements' positions. The document provides examples and explanations of many DOM and CSS-related JavaScript APIs beyond the traditional ones.
JavaScript Timers, Power Consumption, and PerformanceNicholas Zakas
This document discusses how timers, power consumption, and performance are related on web pages. It explains that CPUs can enter low-power sleep states when idle, but timers used in JavaScript can prevent this and increase power usage. The document recommends using higher interval timers (over 15ms) when possible to improve battery life on mobile devices. It also notes that having too many concurrent timers can flood the browser's queue and negatively impact rendering performance.
An update to the Scalable JavaScript presentation of 2009. Describes how to piece together a JavaScript application framework designed for maintainability.
This document summarizes Nicholas C. Zakas's presentation on maintainable JavaScript. The presentation discusses why maintainability is important, as most time is spent maintaining code. It defines maintainable code as code that works for five years without major changes and is intuitive, understandable, adaptable, extendable, debuggable and testable. The presentation covers code style guidelines, programming practices, code organization techniques and automation tools to help write maintainable JavaScript.
High Performance JavaScript (CapitolJS 2011)Nicholas Zakas
High Performance JavaScript provides techniques for optimizing JavaScript performance. It discusses how JavaScript execution blocks the browser UI thread, preventing responsive user experiences. It recommends limiting individual JavaScript jobs to under 50ms to avoid unresponsiveness. The document then provides techniques to improve load time performance such as dynamically loading scripts, and runtime techniques like timers and web workers to avoid blocking the UI thread during long-running processes.
Writing JavaScript as a hobby and writing JavaScript as a job are two very different things. Learn some common practices for making your JavaScript friendly to a team environment.
For much of its existence, JavaScript has been slow. No one complained until developers created complex web applications with thousands of lines of JavaScript code. Although newer JavaScript engines have improved the situation, there’s still a lot to understand about what makes JavaScript slow and what you can do to speed up your code.
YUI Test The Next Generation (YUIConf 2010)Nicholas Zakas
This document summarizes a presentation given by Nicholas C. Zakas on the evolution of YUI Test and introducing the new standalone version. Some key points:
- YUI Test was originally developed as a testing framework for YUI but inconsistencies arose between YUI 2.x and 3.x versions.
- A new standalone version was created to address these issues and allow YUI Test to be used without YUI dependencies. It provides a familiar syntax and API improvements.
- Additional related libraries were introduced, including a Selenium driver for browser automation and code coverage to identify untested code paths.
- Together these provide a complete JavaScript testing solution for continuous integration with features like Hudson integration and reporting
High Performance JavaScript (YUIConf 2010)Nicholas Zakas
Ever wonder why the page appears frozen or why you get a dialog saying, "this script is taking too long"? Inside of the browser, JavaScript and the page's UI are very intertwined, which means they can affect each other and, in turn, affect overall page performance. Ensuring the fastest execution time of JavaScript code isn't about geek cred, it's about ensuring that the user experience is as fast and responsive as possible. In a world where an extra second can cost you a visitor, sluggishness due to poor JavaScript code is a big problem. In this talk, you'll learn what's going on inside the browser that can slow JavaScript down and how that can end up creating a "slow page". You'll also learn how to overcome the conspiracy against your code by eliminating performance bottlenecks.
High Performance JavaScript - Fronteers 2010Nicholas Zakas
For much of its existence, JavaScript has been slow. No one complained until developers created complex web applications with thousands of lines of JavaScript code. Although newer JavaScript engines have improved the situation, there's still a lot to understand about what makes JavaScript slow and what you can do to speed up your code.
High Performance JavaScript - WebDirections USA 2010Nicholas Zakas
This document summarizes Nicholas C. Zakas' presentation on high performance JavaScript. It discusses how the browser UI thread handles both UI updates and JavaScript execution sequentially. Long running JavaScript can cause unresponsive UIs. Techniques to ensure responsive UIs include limiting JavaScript execution time, using timers or web workers to break up processing, reducing repaints and reflows, and grouping style changes. Hardware acceleration and optimizing JavaScript engines have improved performance but responsive UIs still require discipline.
Overhauling one of the most visited web sites in the world is a major task, and add on top of it the pressure of keeping performance the same while adding a ton of new features, and you have quite a task. Learn how the Yahoo! homepage team achieved performance parity with the previous version even while adding a ton of new features.
\n\nThe document discusses scalable JavaScript application architecture. It advocates for a modular approach where each component (module) has a limited, well-defined purpose and interface. Modules are loosely coupled by communicating through a central sandbox interface rather than directly referencing each other. The core application manages modules by registering, starting, and stopping them. It also handles errors and enables extension points. This architecture aims to build flexible, maintainable applications that can evolve over time.
The document summarizes the goals and key features of the new Yahoo! homepage and YUI 3.0 library. YUI 3.0 aimed to eliminate global dependencies, reduce file sizes for faster loading, create version independence between releases, and allow code portability. It achieved these goals by removing the YAHOO global namespace and modularizing the library into smaller independent modules to improve performance and flexibility.
No-Code Workflows for CAD & 3D Data: Scaling AI-Driven InfrastructureSafe Software
When projects depend on fast, reliable spatial data, every minute counts.
AI Clearing needed a faster way to handle complex spatial data from drone surveys, CAD designs and 3D project models across construction sites. With FME Form, they built no-code workflows to clean, convert, integrate, and validate dozens of data formats – cutting analysis time from 5 hours to just 30 minutes.
Join us, our partner Globema, and customer AI Clearing to see how they:
-Automate processing of 2D, 3D, drone, spatial, and non-spatial data
-Analyze construction progress 10x faster and with fewer errors
-Handle diverse formats like DWG, KML, SHP, and PDF with ease
-Scale their workflows for international projects in solar, roads, and pipelines
If you work with complex data, join us to learn how to optimize your own processes and transform your results with FME.
Supporting the NextGen 911 Digital Transformation with FMESafe Software
Next Generation 911 involves the transformation of our 911 system from an old analog one to the new digital internet based architecture. The evolution of NG911 opens up a host of new opportunities to improve the system. This includes everything from device based location, to real time text. This can improve location accuracy dramatically as well as provide live updates from the citizen in need along with real time sensor updates. There is also the opportunity to provide multi-media attachments and medical records if the end user approves. This digital transformation and enhancements all require the support of new NENA and CRTC standards, along with integration across a variety of data streams.
This presentation will focus on how FME has supported NG911 transformations to date, and how we are positioning FME to support the enhanced capabilities to come. This session will be of interest to emergency services, municipalities and anyone who may be interested to know more about how emergency services are being improved to provide more accurate, localized information in order to improve the speed and relevance of emergency response and ultimately save more lives and provide better outcomes for those in need.
Enabling BIM / GIS integrations with Other Systems with FMESafe Software
Jacobs has successfully utilized FME to tackle the complexities of integrating diverse data sources in a confidential $1 billion campus improvement project. The project aimed to create a comprehensive digital twin by merging Building Information Modeling (BIM) data, Construction Operations Building Information Exchange (COBie) data, and various other data sources into a unified Geographic Information System (GIS) platform. The challenge lay in the disparate nature of these data sources, which were siloed and incompatible with each other, hindering efficient data management and decision-making processes.
To address this, Jacobs leveraged FME to automate the extraction, transformation, and loading (ETL) of data between ArcGIS Indoors and IBM Maximo. This process ensured accurate transfer of maintainable asset and work order data, creating a comprehensive 2D and 3D representation of the campus for Facility Management. FME's server capabilities enabled real-time updates and synchronization between ArcGIS Indoors and Maximo, facilitating automatic updates of asset information and work orders. Additionally, Survey123 forms allowed field personnel to capture and submit data directly from their mobile devices, triggering FME workflows via webhooks for real-time data updates. This seamless integration has significantly enhanced data management, improved decision-making processes, and ensured data consistency across the project lifecycle.
FME for Good: Integrating Multiple Data Sources with APIs to Support Local Ch...Safe Software
Have-a-skate-with-Bob (HASB-KC) is a local charity that holds two Hockey Tournaments every year to raise money in the fight against Pancreatic Cancer. The FME Form software is used to integrate and exchange data via API, between Google Forms, Google Sheets, Stripe payments, SmartWaiver, and the GoDaddy email marketing tools to build a grass-roots Customer Relationship Management (CRM) system for the charity. The CRM is used to communicate effectively and readily with the participants of the hockey events and most importantly the local area sponsors of the event. Communication consists of a BLOG used to inform participants of event details including, the ever-important team rosters. Funds raised by these events are used to support families in the local area to fight cancer and support PanCan research efforts to find a cure against this insidious disease. FME Form removes the tedium and error-prone manual ETL processes against these systems into 1 or 2 workbenches that put the data needed at the fingertips of the event organizers daily freeing them to work on outreach and marketing of the events in the community.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2025/06/why-its-critical-to-have-an-integrated-development-methodology-for-edge-ai-a-presentation-from-lattice-semiconductor/
Sreepada Hegade, Director of ML Systems and Software at Lattice Semiconductor, presents the “Why It’s Critical to Have an Integrated Development Methodology for Edge AI” tutorial at the May 2025 Embedded Vision Summit.
The deployment of neural networks near sensors brings well-known advantages such as lower latency, privacy and reduced overall system cost—but also brings significant challenges that complicate development. These challenges can be addressed effectively by choosing the right solution and design methodology. The low-power FPGAs from Lattice are well poised to enable efficient edge implementation of models, while Lattice’s proven development methodology helps to mitigate the challenges and risks associated with edge model deployment.
In this presentation, Hegade explains the importance of an integrated framework that tightly consolidates different aspects of edge AI development, including training, quantization of networks for edge deployment, integration with sensors and inferencing. He also illustrates how Lattice’s simplified tool flow helps to achieve the best trade-off between power, performance and efficiency using low-power FPGAs for edge deployment of various AI workloads.
מכונות CNC קידוח אנכיות הן הבחירה הנכונה והטובה ביותר לקידוח ארונות וארגזים לייצור רהיטים. החלק נוסע לאורך ציר ה-x באמצעות ציר דיגיטלי מדויק, ותפוס ע"י צבת מכנית, כך שאין צורך לבצע setup (התאמות) לגדלים שונים של חלקים.
Russia is one of the most aggressive nations when it comes to state coordinated cyberattacks — and Ukraine has been at the center of their crosshairs for 3 years. This report, provided the State Service of Special Communications and Information Protection of Ukraine contains an incredible amount of cybersecurity insights, showcasing the coordinated aggressive cyberwarfare campaigns of Russia against Ukraine.
It brings to the forefront that understanding your adversary, especially an aggressive nation state, is important for cyber defense. Knowing their motivations, capabilities, and tactics becomes an advantage when allocating resources for maximum impact.
Intelligence shows Russia is on a cyber rampage, leveraging FSB, SVR, and GRU resources to professionally target Ukraine’s critical infrastructures, military, and international diplomacy support efforts.
The number of total incidents against Ukraine, originating from Russia, has steadily increased from 1350 in 2021 to 4315 in 2024, but the number of actual critical incidents has been managed down from a high of 1048 in 2022 to a mere 59 in 2024 — showcasing how the rapid detection and response to cyberattacks has been impacted by Ukraine’s improved cyber resilience.
Even against a much larger adversary, Ukraine is showcasing outstanding cybersecurity, enabled by strong strategies and sound tactics. There are lessons to learn for any enterprise that could potentially be targeted by aggressive nation states.
Definitely worth the read!
FME for Distribution & Transmission Integrity Management Program (DIMP & TIMP)Safe Software
Peoples Gas in Chicago, IL has changed to a new Distribution & Transmission Integrity Management Program (DIMP & TIMP) software provider in recent years. In order to successfully deploy the new software we have created a series of ETL processes using FME Form to transform our gas facility data to meet the required DIMP & TIMP data specifications. This presentation will provide an overview of how we used FME to transform data from ESRI’s Utility Network and several other internal and external sources to meet the strict data specifications for the DIMP and TIMP software solutions.
Artificial Intelligence in the Nonprofit Boardroom.pdfOnBoard
OnBoard recently partnered with Microsoft Tech for Social Impact on the AI in the Nonprofit Boardroom Survey, an initiative designed to uncover the current and future role of artificial intelligence in nonprofit governance.
AudGram Review: Build Visually Appealing, AI-Enhanced Audiograms to Engage Yo...SOFTTECHHUB
AudGram changes everything by bridging the gap between your audio content and the visual engagement your audience craves. This cloud-based platform transforms your existing audio into scroll-stopping visual content that performs across all social media platforms.
Integration of Utility Data into 3D BIM Models Using a 3D Solids Modeling Wor...Safe Software
Jacobs has developed a 3D utility solids modelling workflow to improve the integration of utility data into 3D Building Information Modeling (BIM) environments. This workflow, a collaborative effort between the New Zealand Geospatial Team and the Australian Data Capture Team, employs FME to convert 2D utility data into detailed 3D representations, supporting enhanced spatial analysis and clash detection.
To enable the automation of this process, Jacobs has also developed a survey data standard that standardizes the capture of existing utilities. This standard ensures consistency in data collection, forming the foundation for the subsequent automated validation and modelling steps. The workflow begins with the acquisition of utility survey data, including attributes such as location, depth, diameter, and material of utility assets like pipes and manholes. This data is validated through a custom-built tool that ensures completeness and logical consistency, including checks for proper connectivity between network components. Following validation, the data is processed using an automated modelling tool to generate 3D solids from 2D geometric representations. These solids are then integrated into BIM models to facilitate compatibility with 3D workflows and enable detailed spatial analyses.
The workflow contributes to improved spatial understanding by visualizing the relationships between utilities and other infrastructure elements. The automation of validation and modeling processes ensures consistent and accurate outputs, minimizing errors and increasing workflow efficiency.
This methodology highlights the application of FME in addressing challenges associated with geospatial data transformation and demonstrates its utility in enhancing data integration within BIM frameworks. By enabling accurate 3D representation of utility networks, the workflow supports improved design collaboration and decision-making in complex infrastructure projects
TrustArc Webinar - 2025 Global Privacy SurveyTrustArc
How does your privacy program compare to your peers? What challenges are privacy teams tackling and prioritizing in 2025?
In the sixth annual Global Privacy Benchmarks Survey, we asked global privacy professionals and business executives to share their perspectives on privacy inside and outside their organizations. The annual report provides a 360-degree view of various industries' priorities, attitudes, and trends. See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar features an expert panel discussion and data-driven insights to help you navigate the shifting privacy landscape. Whether you are a privacy officer, legal professional, compliance specialist, or security expert, this session will provide actionable takeaways to strengthen your privacy strategy.
This webinar will review:
- The emerging trends in data protection, compliance, and risk
- The top challenges for privacy leaders, practitioners, and organizations in 2025
- The impact of evolving regulations and the crossroads with new technology, like AI
Predictions for the future of privacy in 2025 and beyond
Down the Rabbit Hole – Solving 5 Training RoadblocksRustici Software
Feeling stuck in the Matrix of your training technologies? You’re not alone. Managing your training catalog, wrangling LMSs and delivering content across different tools and audiences can feel like dodging digital bullets. At some point, you hit a fork in the road: Keep patching things up as issues pop up… or follow the rabbit hole to the root of the problems.
Good news, we’ve already been down that rabbit hole. Peter Overton and Cameron Gray of Rustici Software are here to share what we found. In this webinar, we’ll break down 5 training roadblocks in delivery and management and show you how they’re easier to fix than you might think.
The State of Web3 Industry- Industry ReportLiveplex
Web3 is poised for mainstream integration by 2030, with decentralized applications potentially reaching billions of users through improved scalability, user-friendly wallets, and regulatory clarity. Many forecasts project trillions of dollars in tokenized assets by 2030 , integration of AI, IoT, and Web3 (e.g. autonomous agents and decentralized physical infrastructure), and the possible emergence of global interoperability standards. Key challenges going forward include ensuring security at scale, preserving decentralization principles under regulatory oversight, and demonstrating tangible consumer value to sustain adoption beyond speculative cycles.
Kubernetes Security Act Now Before It’s Too LateMichael Furman
In today's cloud-native landscape, Kubernetes has become the de facto standard for orchestrating containerized applications, but its inherent complexity introduces unique security challenges. Are you one YAML away from disaster?
This presentation, "Kubernetes Security: Act Now Before It’s Too Late," is your essential guide to understanding and mitigating the critical security risks within your Kubernetes environments. This presentation dives deep into the OWASP Kubernetes Top Ten, providing actionable insights to harden your clusters.
We will cover:
The fundamental architecture of Kubernetes and why its security is paramount.
In-depth strategies for protecting your Kubernetes Control Plane, including kube-apiserver and etcd.
Crucial best practices for securing your workloads and nodes, covering topics like privileged containers, root filesystem security, and the essential role of Pod Security Admission.
Don't wait for a breach. Learn how to identify, prevent, and respond to Kubernetes security threats effectively.
It's time to act now before it's too late!