The presentation is an overview of Node.js on how to use it in developing web apps. It also describes the pros and cons it has along with why it got so much adaption in quick time.
1. The document discusses asynchronous programming in PHP using ReactPHP and compares it to Node.js. It covers non-blocking I/O, event loops, and the reactor pattern.
2. Examples of when to use ReactPHP/Node.js include for chat applications, APIs, queued input, data streaming, proxies, and monitoring. Relational databases and CPU-intensive tasks are given as examples of when not to use them.
3. Differences between Node.js and ReactPHP mentioned include Node.js having more packages/libraries while PHP is more compatible with existing backend code. Node.js is also described as more mature while PHP has better OOP support.
Text Editors (Atom / Sublime)
Apache Server (sftp/ssh/php) – Todd's Server!
CPanel / Wordpress (server side details)
Working with any Web API (Mapping Example)
(facebook, linkedin, twitter, maps, d3.js, jquary)
JSON and HTML <img>
GIT http://www.github.com
Introduction to performance tuning perl web applicationsPerrin Harkins
This document provides an introduction to performance tuning Perl web applications. It discusses identifying performance bottlenecks, benchmarking tools like ab and httperf to measure performance, profiling tools like Devel::NYTProf to find where time is spent, common causes of slowness like inefficient database queries and lack of caching, and approaches for improvement like query optimization, caching, and infrastructure changes. The key messages are that performance issues are best identified through measurement and profiling, database queries are often the main culprit, and caching can help but adds complexity.
ServiceWorker: New game changer is coming!Chang W. Doh
I believe ServiceWorker is one of most important specifications for the next web world. Offline and its technologies are very friendly concepts to native application developers. But, now I think front-end developers have to know that for stepping into new paradigm. With ServiceWorker, you can make your web application can run offline, and it also means you can make your web application load extremely fast.
I've told about ServiceWorker very briefly in this slide. But you can understand how ServiceWorker runs on. If you want to know its usage, I highly recommend Topeka, which is a polymer demo application at google I/O 2014, that also includes material design and ServiceWorker in inside of it.
If you want to know ServiceWorker some more or in detail, I'd like to recommend to read the following, written by Jungkee Song, one of authors of this spec.
http://www.slideshare.net/jungkees/service-workers
EISA is a new programming language targeted towards JavaScript that is designed for asynchronous and interactive development. It addresses key problems with asynchronous programming in JavaScript like nested callbacks and broken code locality. In EISA, asynchronous tasks can be defined sequentially using async/await rather than nested callbacks. This was demonstrated with a 3D scene loading example where the entire workflow was defined asynchronously without nested functions. EISA originated from game development needs but can now be used for general purposes. It focuses on providing an optimized syntax for domain-specific languages while remaining compatible with JavaScript.
Node.js is a JavaScript runtime environment for building fast and scalable network applications. It uses non-blocking I/O and event-driven architecture, allowing it to handle multiple connections simultaneously without blocking. This makes Node.js suitable for real-time web applications with many simultaneous connections. Node.js has a small core but is extensible through modules. Common modules include Express for building web servers and Socket.IO for real-time web functionality. While Node.js is well-suited for I/O-intensive applications, it is less suitable for CPU-intensive or memory-intensive applications due to its single-threaded nature.
This document provides an introduction to Node.js. It discusses that Node.js is an event-driven, non-blocking I/O platform for building scalable network applications using JavaScript. It was created to address issues with traditional blocking I/O by using asynchronous programming. The document outlines benefits of Node.js like using JavaScript for server-side applications, non-blocking I/O, a large module ecosystem, and an active community. It also provides examples of core modules, writing simple modules, and creating an HTTP server in Node.js.
The SPDY Protocol is likely going to be the successor of http. This short talk summarizes the most important points and includes a demo on how to migrate a Wordpress blog on httpd.
This document summarizes configuration management tools and introduces Ansible. It notes that Puppet and bcfg2 are pull-based with custom authentication and performance issues, while Ansible is push-based using SSH keys, fast with no daemons. Ansible can be installed with pip and used immediately in one-shot mode or with playbooks for complete configuration management. Playbooks allow defining collections of actions like one-shot mode with notifications. The document concludes that Ansible can go from zero to production in minutes with no custom setup or dependencies.
The document introduces CouchApp, a tool that helps organize CouchDB applications. CouchApp generates application skeletons and provides libraries for frontend development. It also helps manage design documents through its deployment process. However, CouchApp may not be suitable for all applications and is better suited for smaller single-page applications where business logic is not massive. Larger sites can become hard to maintain with only CouchApp's rudimentary tool support.
This document discusses various tools for rapidly provisioning development environments including Packer, Vagrant, Puppet, Chef, Ansible, Salt, and Docker. It compares the tools and highlights features like infrastructure as code, declarative configuration, provisioning, and ready-to-go images. It also discusses using these tools together in a continuous integration/deployment pipeline with tools like Jenkins.
The document discusses Concurrency-oriented Programming (COP) using Erlang. It explains how Erlang programs work using lightweight processes that communicate asynchronously via message passing. This allows for high performance, reliability, and scalability. It provides examples of stateless server processes and using CouchDB for schema-free document storage accessible via REST APIs. Ruby libraries for interacting with CouchDB are also mentioned.
The document discusses the technology stack used at skypicker.com, including their use of uWSGI to serve Python applications for features like booking flights. It describes how uWSGI provides benefits like high performance, flexibility to run on multiple web servers, and abilities like shared memory and managing worker processes. It also compares uWSGI's performance to alternatives like using the Python dictionary or Redis for shared memory.
This document provides an overview of ExpressJS, a web application framework for Node.js. It discusses using Connect as a middleware framework to build HTTP servers, and how Express builds on Connect by adding functionality like routing, views, and content negotiation. It then covers basic Express app architecture, creating routes, using views with different template engines like Jade, passing data to views, and some advanced topics like cookies, sessions, and authentication.
The document provides an overview of Node.js, a JavaScript runtime environment for building scalable network applications. Some key points covered include:
- Node.js is built on Google's V8 JavaScript engine and is event-driven and non-blocking.
- It is well-suited for data-intensive real-time applications due to its lightweight and efficient nature.
- Node.js differs from other scripting languages by being non-blocking, single-threaded, and having an event-based approach built-in.
This document discusses techniques for improving frontend performance. It recommends making fewer HTTP requests, using a content delivery network, adding expiration headers, gzipping components, optimizing stylesheet and script placement, avoiding redirects and duplicate scripts, and more. It also covers techniques for loading scripts asynchronously without blocking page rendering, such as using script elements, XHR, and iframes. Faster page loads can improve user experience and increase revenue.
JavaScript performance patterns focuses on optimizing JavaScript loading and execution for better performance. Some key points include reducing the number of script files, leveraging caching, minification and compression. Asynchronous loading helps prevent blocking. DOM operations are expensive so it's important to cache references, batch operations and avoid reflows. Data attributes provide a convenient way to store data on elements. Shims and polyfills should be used judiciously, loading conditionally where native support is limited. Benchmarking is crucial to identify real bottlenecks and measure impact of optimizations.
Web Development Environments: Choose the best or go with the restgeorge.james
The document discusses various web development environments and frameworks for choosing the right one. It covers popular options like ASP.NET, Java/JSP, PHP, Python and Ruby as well as databases. For each, it provides an overview and examples of sorting data to demonstrate capabilities. It emphasizes evaluating options based on requirements rather than following trends and notes the impact that open source movements and companies can have on technologies.
This document summarizes best practices for optimizing JavaScript performance. It discusses loading JavaScript asynchronously or lazily to avoid blocking page loads. It also recommends minimizing DOM manipulation, batching style changes, and caching references to reduce reflows and repaints. The document emphasizes measuring performance through tools like Benchmark.js and jsperf.com to avoid premature optimization. It cautions against unnecessary shims and polyfills and stresses optimizing for mobile environments.
This document provides an overview of HTML5, Backbone.js, and web development. It introduces key concepts like client-server architecture, APIs, databases, markup languages, and frameworks like jQuery, Bootstrap, and Backbone. It discusses modern front-end development practices and server-side programming. Mobile web development options like native, hybrid, and PhoneGap are also covered. The document emphasizes learning resources and stresses attention to details, user experience, and adaptability to new technologies in the field.
Node.js is an exciting new platform developed by Ryan Dahl that allows JavaScript developers to create extremely high performance servers by leveraging Google's V8 JavaScript engine and asynchronous I/O. It uses a non-blocking I/O model that makes it lightweight and efficient, as well as features like CommonJS modules and the npm package manager. The document provides examples of building simple HTTP servers and modules in Node.js to demonstrate its capabilities.
Intro to mobile web application developmentzonathen
Learn all the basics of web app development including bootstrap, handlebars templates, jquery and angularjs, as well as using hybrid app deployment on a phone.
It is not HTML5. but ... / HTML5ではないサイトからHTML5を考えるSadaaki HIRAI
This document provides an overview of HTML5 technologies including HTML5 markup, microdata/RDFa, WebFonts, Canvas, MediaQueries, performance optimizations like SPDY and HTTP 2.0. It discusses specifications from the W3C and implementations by companies. Tools for testing responsive design, fonts and browser compatibility are also mentioned. The document is written in Japanese and references the author's blog for code samples.
Sooner or later we all have to work with HTML, despite its verbosity. Those of us who claim to love HTML may just be victims of Stockholm Syndrome, both praising yet secretly loathing it.
Basho designer John Newman is making the trek from the swamps of Florida to show us the way. In the modern world of markup preprocessors, these alternative syntaxes allow you to write simpler, cleaner, more concise code in a shorter amount of time. Certain techniques can even allow your team members who may be less-tech-savvy to contribute content directly without forcing you to wire up a WYSIWYG style CMS.
This talk explores great alternatives to plain HTML and CSS, and covers how Basho put these tools together to facilitate a painless, team-oriented approach to building sites and web apps.
The document provides guidelines and techniques for optimizing web page performance, including recommendations for CSS and JavaScript best practices, optimization of resources, and use of the Firebug tool to inspect pages and identify issues. It discusses strategies like minimizing HTTP requests, optimizing CSS and JavaScript, using JSON over XML, image sprites, caching, and more. The Firebug tool is highlighted as a way to analyze pages and debug JavaScript, CSS, and performance issues.
This document summarizes JavaScript support on Google App Engine including frameworks like Rhino, Narwhal, Ringo, and JSGI/Jack that allow running JavaScript applications on App Engine. It also describes the AppengineJS stack which provides APIs for the App Engine datastore, memcache, and other services via CommonJS packages. Key features of AppengineJS include support for templating, HTML parsing, and the Nitro framework.
The document discusses JavaScript and the Spry framework in Adobe Dreamweaver CS4. It provides an overview of JavaScript development, how Dreamweaver is helping with tools like code hinting, debugging and live preview. It then focuses on explaining the Spry framework, how it provides widgets, effects, datasets and integration with Dreamweaver.
The document discusses the Grails web application framework. It begins with an overview of Grails, describing it as a convention-over-configuration MVC framework built on proven Java technologies like Spring and Hibernate. It then addresses common pain points in web development like complex ORM configuration and numerous XML files. The document outlines how Grails streamlines areas like persistence with GORM, controllers, services, and templating with Groovy Server Pages (GSP). It also covers additional Grails features such as custom tag libraries, URL mappings, conversations, and its plugin system.
Lift is a Scala web framework that makes building highly interactive real-time web applications simple. It leverages Scala language features and takes the best ideas from other frameworks, such as Seaside's granular sessions and security and Rails' convention over configuration. Lift has a unique "view first" architecture and offers unparalleled security and comet support out of the box. It is already used by major companies like Foursquare and has been proven at scale.
Zend Framework is an open source PHP framework that follows the model-view-controller (MVC) pattern to promote best practices. It has many features like simplicity, extensibility, and full documentation. Google Gears is a browser plugin that allows web applications to work offline and store data locally. It includes a database, caching, and background processing to improve performance and responsiveness even without internet access. Google Gears aims to bridge the gap between desktop and web applications and its components are simple to use.
Cross Domain Web Mashups with JQuery and Google App EngineAndy McKay
This document discusses cross-domain mashups using jQuery and Google App Engine. It describes common techniques for dealing with the same-origin policy, including proxies, JSONP, and building sample applications that mashup Twitter data, geotagged tweets, and maps. Examples include parsing RSS feeds from Twitter into JSONP and displaying tweets on a map based on their geotagged locations. The document concludes by noting issues with trust, failures, and limitations for enterprise use.
The document provides an introduction to Node.js, a JavaScript runtime environment for server-side development. It discusses how Node.js uses non-blocking I/O and event loops to handle concurrent connections efficiently. Examples are given demonstrating how to build basic HTTP and TCP servers in just a few lines of JavaScript code. Common use cases for Node.js include real-time applications and static file serving.
Go.cd is a tool for continuous delivery that allows software to be delivered incrementally with reduced cost, time, and risk. It features continuous integration by providing feedback at the build, deployment, and feature stages. Go.cd's core includes a Go Server, REST API, and Go Agents that run on tags in controlled environments. Pipelines define the workflow with stages for logical steps and jobs that run tasks in parallel. Pipelines have run histories that allow re-running and manual triggering at the pipeline, stage, and job levels.
Impact of CD, Clean Code, ... on Team PerformanceFredrik Wendt
The document discusses trends in software development for 2014, including clean code and software craftsmanship, DevOps, continuous delivery, Docker and Vagrant, scaling agile, and microservices. For each trend, it provides a brief description and discusses possible impacts and how teams can implement the trend to improve team performance and deliver value through shorter cycles, faster learning, and lower risk development.
En introduktion till arkitektur och arkitekturrollens plats i en agil miljö.
Presentation gavs under NFIs konferens Systemförvaltning 2013, onsdag 4 december.
This document discusses coding dojos, which are sessions where developers practice and learn coding skills together. The document outlines several key points about coding dojos, including that they provide a safe learning environment where developers can practice skills important for their work in a production-like setting. Coding dojos emphasize learning by doing through repetition of exercises or "katas". Different styles of conducting dojos are discussed, such as presentations, random pairing of developers, and breaking into groups. The document also covers potential skills developers may gain from dojos and how dojos can positively impact company culture.
The document discusses clean code principles such as writing code for readability by other programmers, using meaningful names, following the DRY principle of not repeating yourself, and focusing on writing code that is maintainable and changeable. It provides examples of clean code versus less clean code and emphasizes that code is written primarily for human consumption by other programmers, not for computers. The document also discusses principles like the Single Responsibility Principle and the Boy Scout Rule of leaving the code cleaner than how you found it. It questions how to measure clean code and emphasizes the importance of writing tests for code and refactoring legacy code without tests.
This document discusses test-driven development (TDD) and its benefits. It notes that TDD can find bugs earlier and reduce costs, though traditional testing is still needed. TDD involves writing a test first, then code to pass the test, and refactoring code while ensuring all tests remain passing. Practicing TDD through coding "katas" or exercises in a "dojo" setting can improve skills over time through repetition. While TDD takes more initial time, the benefits are more confidence, productivity, reliability and agility in the long run.
The document discusses several agile concepts including the Agile Manifesto, Scrum, Extreme Programming (XP), Test-Driven Development (TDD), and coding dojos. It outlines the values and principles of the Agile Manifesto which emphasize individuals, interactions, working software, customer collaboration, and responding to change. It then provides brief descriptions of Scrum roles, ceremonies, and artifacts as well as XP practices like pair programming, writing unit tests first, and integrating often.
The document discusses principles and best practices for writing clean code, including writing small, focused functions; writing code according to the "red, green, refactor" process; using intention-revealing names; following the DRY principle to avoid duplicated code; applying the single responsibility principle and Law of Demeter for loose coupling; and writing tests. It also references concepts like the Boy Scout Rule and emphasizes code quality through maintainability and readability.
This document provides an overview of how to use Mockito to create mock objects and define their behavior in tests.
It explains how to create mocks with mock(ClassToMock.class), define return values and exceptions with when(method()).thenReturn()/thenThrow(), and verify mock interactions with verify(mock).method(). It also covers using @Mock annotation and initMocks() to initialize mocks, and matchers like eq() to verify argument matching. The document concludes with some Eclipse IDE tips to help with Mockito development.
The Rise of Supernetwork Data Intensive ComputingLarry Smarr
Invited Remote Lecture to SC21
The International Conference for High Performance Computing, Networking, Storage, and Analysis
St. Louis, Missouri
November 18, 2021
Understanding Insider Security Threats: Types, Examples, Effects, and Mitigat...Bert Blevins
Today’s digitally connected world presents a wide range of security challenges for enterprises. Insider security threats are particularly noteworthy because they have the potential to cause significant harm. Unlike external threats, insider risks originate from within the company, making them more subtle and challenging to identify. This blog aims to provide a comprehensive understanding of insider security threats, including their types, examples, effects, and mitigation techniques.
Mitigating the Impact of State Management in Cloud Stream Processing SystemsScyllaDB
Stream processing is a crucial component of modern data infrastructure, but constructing an efficient and scalable stream processing system can be challenging. Decoupling compute and storage architecture has emerged as an effective solution to these challenges, but it can introduce high latency issues, especially when dealing with complex continuous queries that necessitate managing extra-large internal states.
In this talk, we focus on addressing the high latency issues associated with S3 storage in stream processing systems that employ a decoupled compute and storage architecture. We delve into the root causes of latency in this context and explore various techniques to minimize the impact of S3 latency on stream processing performance. Our proposed approach is to implement a tiered storage mechanism that leverages a blend of high-performance and low-cost storage tiers to reduce data movement between the compute and storage layers while maintaining efficient processing.
Throughout the talk, we will present experimental results that demonstrate the effectiveness of our approach in mitigating the impact of S3 latency on stream processing. By the end of the talk, attendees will have gained insights into how to optimize their stream processing systems for reduced latency and improved cost-efficiency.
Details of description part II: Describing images in practice - Tech Forum 2024BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and transcript: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.
Advanced Techniques for Cyber Security Analysis and Anomaly DetectionBert Blevins
Cybersecurity is a major concern in today's connected digital world. Threats to organizations are constantly evolving and have the potential to compromise sensitive information, disrupt operations, and lead to significant financial losses. Traditional cybersecurity techniques often fall short against modern attackers. Therefore, advanced techniques for cyber security analysis and anomaly detection are essential for protecting digital assets. This blog explores these cutting-edge methods, providing a comprehensive overview of their application and importance.
7 Most Powerful Solar Storms in the History of Earth.pdfEnterprise Wired
Solar Storms (Geo Magnetic Storms) are the motion of accelerated charged particles in the solar environment with high velocities due to the coronal mass ejection (CME).
YOUR RELIABLE WEB DESIGN & DEVELOPMENT TEAM — FOR LASTING SUCCESS
WPRiders is a web development company specialized in WordPress and WooCommerce websites and plugins for customers around the world. The company is headquartered in Bucharest, Romania, but our team members are located all over the world. Our customers are primarily from the US and Western Europe, but we have clients from Australia, Canada and other areas as well.
Some facts about WPRiders and why we are one of the best firms around:
More than 700 five-star reviews! You can check them here.
1500 WordPress projects delivered.
We respond 80% faster than other firms! Data provided by Freshdesk.
We’ve been in business since 2015.
We are located in 7 countries and have 22 team members.
With so many projects delivered, our team knows what works and what doesn’t when it comes to WordPress and WooCommerce.
Our team members are:
- highly experienced developers (employees & contractors with 5 -10+ years of experience),
- great designers with an eye for UX/UI with 10+ years of experience
- project managers with development background who speak both tech and non-tech
- QA specialists
- Conversion Rate Optimisation - CRO experts
They are all working together to provide you with the best possible service. We are passionate about WordPress, and we love creating custom solutions that help our clients achieve their goals.
At WPRiders, we are committed to building long-term relationships with our clients. We believe in accountability, in doing the right thing, as well as in transparency and open communication. You can read more about WPRiders on the About us page.
RPA In Healthcare Benefits, Use Case, Trend And Challenges 2024.pptxSynapseIndia
Your comprehensive guide to RPA in healthcare for 2024. Explore the benefits, use cases, and emerging trends of robotic process automation. Understand the challenges and prepare for the future of healthcare automation
Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Em...Erasmo Purificato
Slide of the tutorial entitled "Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Emerging Trends" held at UMAP'24: 32nd ACM Conference on User Modeling, Adaptation and Personalization (July 1, 2024 | Cagliari, Italy)
TrustArc Webinar - 2024 Data Privacy Trends: A Mid-Year Check-InTrustArc
Six months into 2024, and it is clear the privacy ecosystem takes no days off!! Regulators continue to implement and enforce new regulations, businesses strive to meet requirements, and technology advances like AI have privacy professionals scratching their heads about managing risk.
What can we learn about the first six months of data privacy trends and events in 2024? How should this inform your privacy program management for the rest of the year?
Join TrustArc, Goodwin, and Snyk privacy experts as they discuss the changes we’ve seen in the first half of 2024 and gain insight into the concrete, actionable steps you can take to up-level your privacy program in the second half of the year.
This webinar will review:
- Key changes to privacy regulations in 2024
- Key themes in privacy and data governance in 2024
- How to maximize your privacy program in the second half of 2024
Transcript: Details of description part II: Describing images in practice - T...BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and slides: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.
45. node.js - DNS example var dns = require("dns"); var resolution = dns.resolve4("www.google.com"); resolution.addCallback( function(addresses, ttl, cname) { puts("addresses: "); puts(JSON.stringify(addresses)); } );
46. JS - from birth to closure Genomgång av JavaScript
47. Conditionals, Comparison, Data Types, Functions, Function Arguments, Objects, Inheritance, Scope, Function Scope, Closure, Namespacing, Syntax
Hur många kan CSS? Hur många kan JavaScript? Hur många har läst High Performance Web Sites? Hur många har läst Even Faster Web Sites? Någon som jobbat med webbplats-optimering? Föredrar publiken CSS eller JavaScript? Hur många har haft problem med att läsa ned javascript parallellt? eller känner till problemet? Är JavaScript bra async eller sync?
Jag jobbar på Iptor konsult ab. Tre ben inom konsultingen Jag bloggar på jsolutions.se
150 deltagare över en helg (2 dagar) i centrala Berlin, från 9-18 ett huvudspår 19 förannonserade - hölls i huvudlokalen med runda bord ett basement-spår, 12-13 annonserades sista veckan/allt eftersom Alltså sprängfyllt, första dagen lite sämre, andra bättre
Steve Souders Performance expert, Yahoo. Nu på Google. Anordnar O'Reilly Velocity-konferensen. Lack of progressive rendering makes sites feel slow Learn how to load scripts in parallel Load only scripts needed to render Use YSlow and Google's Page Speed http://developer.yahoo.com/performance/rules.html
Jobbade med att optimera serversidan. Lyckades ibland få bort 10-15 %. Tog ett steg tillbaka, och tittade på vad en browser gör - trappstegsbilden visar detta. 10-15 % serverside = bråkdel av hela upplevelsen We've been doing it wrong! FIXME: Hur mycket förlorar Ebay/Amazon på långsamma sidor?
September 2007 Amazon, AOL, CNN, eBay, Google, MSN, MySpace, Wikipedia, Yahoo! YouTube Efter hur många sekunder tappar man kunder?
June 2009 Mer fokus på web2.0 och JavaScript. Mer om vad som skall in i HTML och inte. 5-12 % är HTML-väntande. En nyckelfaktor är parallella nedladdningar. Browsern skall rita så tidigt som möjligt.
OK - vi vet hur man kan göra, men det är alldeles för svårt - för få gör det.
När börjar browsern rita? När tappar man kunden?
Nicole Sullivan Jobbade på Yahoo, nu Facebook. Klagade lite på CSS. Drömde lite om framtiden.
Går att göra redan nu med preprocessing-steg. Lättare att underhålla!
Ryan Dahl I'm just a programmer.
Robert Nyman http://www.slideshare.net/robnyman/javascript-from-birth-to-closure Geek Meet, JavaScript test JSLint Crockford: Embrace JS Don't try to make it into Java, C or any other language Learn to love it and it's dynamic, loose and prototypical nature
Peter Svensson Scandinavian Web Developer Conference 2009 Google Technology User Group Learning Dojo - ISBN 978-1847192684
Nokia stod för hela notan!
Douglas Crockford JavaScript the good parts, JSON Bejublat om JS nutid och framtid variadic functions - arguments-array är problematisk lägga till class (syntaktiskt socker) *Nu i december röstar man - IBM står på tvären *Kommer till SDC ---------QUOTE!!!---------- http://developer.yahoo.com/yui/theater/video.php?v=crockford-yuiconf2009-state ISBN 978-0596517748
Remy Sharp aktiv inom jQuery Sammanfattade HTML 5 som det ser ut just nu.
Dion Almaer Google, Mozilla, och nu Palm WebOS Sometimes we have to use some weird version of C Louise CK: Klippet från Conan OBrian SACRED: restore session/document - firefox, word, ... Jacob Nielsen 0.1 the system is reacting instantaneously 1.0 limit for the user's flow of thought to stay uninterrupted 10 limit for keeping the user's attention on the dialogue http://www.useit.com/papers/responsetime.html