Microsoft has become more open in recent years by open sourcing many products, making products cross-platform, and making training materials openly available. This open approach makes business sense for Microsoft as it attracts developers, allows employees flexibility, and taps into outside skills. Examples of Microsoft's success with open source include the Edge browser, Visual Studio Code editor, TypeScript transpiler, and ChakraCore JavaScript engine. The presenter encourages attendees to help promote Microsoft's open products and projects through conference talks, writing, and contributing translations and code.
The document discusses the current state of web development and identifies several issues, including slow page loading times, large file sizes, reliance on outdated libraries and browser hacks, and an emphasis on flashy innovations over foundational web standards. It argues that as an industry, web development has gotten too complex and focuses too much on impressing other developers rather than meeting users' needs. It calls for simplifying solutions, supporting baseline functionality for all browsers, and prioritizing education and collaboration over quick fixes.
This document discusses progressing web development and applications. It talks about some common criticisms of the web, including that browsers differ too much and the web is too flexible. However, it argues that browser differences allow for innovation and flexibility is one of the web's strengths. It promotes an approach of focusing on capabilities rather than browsers. The document also discusses progressing technologies like service workers and progressive web apps that can make applications work offline and feel more like native apps while still being web-based. It concludes by arguing the web is not going away and is a great platform to build upon.
Moore vs. May - everything is faster and better: we can fix thatChristian Heilmann
This document summarizes a presentation about improving efficiency and performance on the web. It discusses Moore's Law, which states that computers get faster every two years, and May's Law, which says software efficiency halves every 18 months to compensate. However, web development has focused too much on innovation and new technologies rather than optimization. As a result, median page load times are over 5 seconds. The document calls for developers to focus on fixing existing issues, improving efficiency, and testing new standards like ES6 before adopting them widely. It argues for less hype and more focus on users, technical limitations, and fixing broken aspects of the current web.
The document discusses the evolution of the web from progressive web apps to native mobile apps and back again to progressive web apps. It notes that early mobile web faced issues like small screens, poor connectivity and unreliable browsers, leading to the rise of native apps. However, app distribution issues like slow updates and the "walled garden" approach of app stores have led to a renewed interest in progressive web apps that work offline but do not require app stores, allowing for more open distribution like the original web.
The document discusses the problem of websites using large, unoptimized images that slow down loading times. It provides solutions like responsive images, automated image optimization tools, extracting metadata from images, intelligent resizing with cloud services, and machine learning for tasks like facial recognition and tagging to improve the image experience on the web. The key is for browsers, tools, and developers to work together to make images lightweight and adaptive while still high quality.
This document discusses challenges facing the open web in a mobile-dominated world. It describes how mobile native platforms are stacked against the mobile web, providing better monetization and a perception that everything must work offline. It discusses the five stages of mourning for the open web, from denial to acceptance. It argues for focusing on simplicity, understanding other perspectives, and promoting the web through love instead of criticism.
The document discusses how developers have become disconnected from users as technology has advanced. It argues that developers should focus on building interfaces that are simple, human-centered, and empower users rather than just improving tools. Machine learning and AI can be used to build helpful interfaces, but developers must focus on the human experience and inclusive design. The talk aims to inspire developers to use their skills to improve people's lives rather than just profit or automation.
Overboard.js - where are we going with with jsconfasia / devfestasiaChristian Heilmann
This document summarizes a talk given by Chris Heilmann on the current state and future of JavaScript. It notes that while JavaScript has become incredibly versatile, developers have a tendency to over-engineer solutions and add unnecessary complexity. This bloat slows down sites and hurts users. The document advocates taking a step back to focus on fundamentals and cleanup. It highlights upcoming ES6 features that provide a cleaner baseline and encourages using them responsibly while also fixing existing broken code.
In the last year or so things changed drastically. Everybody uses an iPhone6, is connected 24/7 at high-speed without data caps, is healthy, has shiny teeth and loves spending money on your products. All you need to do is constantly innovate and you'll be a major success. The term for this is "the modern web". Another word for it is nonsense. There is a web people want and there is one that people use. We should start thinking about upgrading the one people use and stop chasing our own tail trying to mimick other environments.
Advancing JavaScript without breaking the web - MunichJSChristian Heilmann
ES6 and other extensions to JavaScript are exciting, but they have the problem that they are not backwards compatible. How can we deal with that issue? Or is it really one?
Upgrading JavaScript to ES6 and using TypeScript as a shortcutChristian Heilmann
This document discusses upgrading JavaScript to ES6 and using TypeScript as an alternative. It covers some of the old issues with JavaScript, the learning process, tooling challenges, and dependency on libraries/frameworks. ES6 promises to address many of these with new features, but browser support is still evolving so transpilation is needed. TypeScript is presented as a shortcut that provides type safety and class-based syntax without transpilation overhead. The document also mentions the ChakraCore JavaScript engine as a promising new development.
NodeConfLondon - Making ES6 happen with ChakraCore and NodeChristian Heilmann
The document discusses the history and future of JavaScript and Node.js. It covers the promises and problems of JavaScript, how Node.js helped address some issues but created new ones like monoculture. It then discusses how ES6 and the ChakraCore engine can help modernize JavaScript and break the Node monoculture by providing an additional engine option. The author hopes for less drama, embracing change, simplicity, inclusiveness, and prioritizing users over developers.
Let’s learn how to use JavaScript responsibly and stay up-to-date. Christian Heilmann
This document discusses responsible and up-to-date use of JavaScript. It recommends directly learning JavaScript instead of relying on libraries without understanding. Browser tools and editors have improved, removing the need for user agent sniffing or outdated polyfills. New JavaScript features like ES6 are supported in modern browsers through transpilation or superset languages. The overall message is that JavaScript has matured and developers should embrace new capabilities instead of clinging to past workarounds.
No more excuses! Let's build beautiful things. #codemotion Rome Christian Heilmann
A quick reminder of how we make it too complex for ourselves as web developers these days, and how changes in the browser world mean mainly one thing: build to standards.
- The web development community needs to focus more on quality, accessibility, and standards compliance rather than constant innovation and new techniques. Browsers have come a long way but still struggle to balance implementing new features while maintaining compatibility.
- Web pages have gotten slower and larger over time due to an emphasis on appearance over performance and a reluctance to drop legacy techniques. Many modern solutions make the web more complex without real benefits.
- Developers should provide better feedback to browsers, demand stronger support for baseline functionality, and stop catering to outdated browsers to encourage continued progress toward an interoperable web. Simpler, more sustainable approaches would benefit all.
The document discusses strategies for responsibly using JavaScript. It recommends:
1. Learning JavaScript fundamentals directly rather than relying on copying code.
2. Stop supporting outdated browsers like Internet Explorer and instead focus on modern standards.
3. Avoid browser detection and stop introducing non-standard code that breaks websites.
4. Leverage powerful developer tools and modern frameworks rather than workarounds.
5. Evolve use of JavaScript by adopting modern standards like ES2015 using compilers rather than blaming language shortcomings.
The document discusses the pros and cons of using JavaScript on websites. It argues that while JavaScript reliability can be an issue, it also enables many useful features and experiences. JavaScript allows websites to take advantage of user device capabilities in ways that aren't possible without client-side scripting. The document urges moving past arguments against JavaScript and embracing new paradigms like components and functional programming to build higher quality web experiences.
Boilerplates: Step up your Web Development ProcessFibonalabs
The document discusses boilerplates for web development projects. It introduces boilerplates as pre-built code libraries that allow setting up a web application quickly. It then summarizes some React boilerplates from Fibonalabs, highlighting features like TypeScript support, linting, and support for NextJS and Create React App frameworks. UI libraries like Material UI, Ant Design, and Tailwind CSS are also mentioned. The boilerplates aim to help developers speed up project setup through a GUI selection process.
This document discusses the use of open source tools for entrepreneurship and software development. It begins by stating that the talk is intended for newcomers to open source, startups, and those interested in software projects or careers. It then provides background on the speaker and their experience before defining open source as promoting universal access and redistribution of designs. The document lists many popular open source databases, frameworks, servers and other tools that can be used for projects. It emphasizes asking the right questions about goals, users, and requirements before choosing tools. It also stresses system design, testing features with users, and ongoing maintenance like security, backups and monitoring.
Web Velocity is a tool for developing web applications entirely within a web browser. It uses VisualWorks Smalltalk, the Seaside framework, and object-relational mapping to allow users to build, test, and debug dynamic Ajax-enabled web applications directly in the browser. The document discusses where Cincom's Smalltalk products are currently and outlines priorities for future development, including internationalization support, 64-bit virtual machines, improved graphics capabilities, and leveraging multi-core processors. It also emphasizes the importance of advocacy for the Smalltalk language and community.
How Open Source / Open Technology Could Help On Your ProjectWan Leung Wong
ITFest 2014, Seminar on Free & OSS in HK
How Open Source / Open Technology Could Help On Your Project?
A talk brief to talk about how to use open source or open technology to help on start a new project. How to choose technology, and what should people to concern on.
This document summarizes Microsoft's efforts to support and contribute to open source software and PHP development. It discusses tools Microsoft has created to help PHP work well on Windows, such as FastCGI, IIS 7, PHP Manager, and a SQL Server driver for PHP. It also introduces WebMatrix, a new web development tool from Microsoft for creating and publishing PHP websites. The document aims to show Microsoft's desire to work with the open source community and provide positive contributions.
Presentations from our osAccelerate event in London UK by Mark Brincat, CTO of The Economist and Steve Tanner, Systems Analyst at the World Trade Organisation.
These are the slides I've prepared for presenting at CampSmalltalkVI2014 flow, a full-stack smalltalk framework for doing Single Page Applications.
tl;dr: it's Smalltalk for startups.
In a nutshell: flow is Amber frontend, Pharo backend and Mapless for networking objects in JSON and uncomplicated MongoDB persistence.
MIT license
SPS Monaco 2017 - The Lay of the Land of Client-Side Development circa 2017Marc D Anderson
Are you dazzled by all the noises you hear about client-side development? Do the grunts and gulps leave you a little confused? In this session, we’ll talk about the types of things you can do with client-side development, how SharePoint can be used as a service (SPaaS?) and what the popular tool sets are. This are moving fast, so it's guaranteed that between writing this abstract and doing the session, things will have changed.
Whether you’re a server-side developer who wants to catch up with the new trends, a power user wanting to flex your muscles in new ways, or an end user who would like to speak more intelligently with IT, this session will provide useful foundation information as well as a guide to where your learning should progress to work with "modern" SharePoint.
I gave this talk on IEEE Day (October 7, 2014). I covered Introduction to Open Source, Various Projects and Products in Open Source, What students can get from Open Source and various different aspects of Open Source during this talk.
Please feel free to download, modify and use the slides for your talks. Lets keep rocking the Free Web ! :)
The Art Of Documentation for Open Source ProjectsBen Hall
Delivered at Kubecon US 2018 by Ben Hall. Watch the recording at https://www.youtube.com/embed/Yjxupg-NKnA
In this talk, Ben uses his expertise of building an Interactive Learning Platform to highlight The Art of Documentation. The aim of the talk is to help open source contributors understand how small changes to their documentation approach can have an enormous impact on how users get started.
The State of Frontend was presented at Vadodara Frontend Developer's meetup on 4th Apr, 2016. It covers the past, present and the future trends in the frontend development.
DSC UTeM DevOps Session#1: Intro to DevOps Presentation SlidesDSC UTeM
DevOps has been such a buzzword in the IT field nowadays. If you look into job postings, you might be surprised to find terms like "work with DevOps team", "work in an agile team" etc.
What is DevOps? What is agile? And why all these? 樂
Join us on 24 May 2021, where we have a short session to explore on the events that led to the trend nowadays
We will be exploring on the current trends, tech stacks and the existence of DevOps itself! 朗
Mark this date on your calendar and we'll see you there!
* Note: This is an introductory "brief overview" session that gives you context on our upcoming events.
Slides by KwongTN.
Open World Forum - The Agile and Open Source WayAlexis Monville
Slides from Open World Forum 2013 (#OWF13)
The Agile and Open Source Way is the book for everyone who wants to scale agile in multiple distributed teams. This book will also help you to collaborate upstream with Open Source projects.
Whether you want to improve interactions with other teams inside or outside your company, or just interested in scaling from more than one team, you will find in this publication the information you need, illustrated by a real case.
http://www.the-agile-and-open-source-way.com/
The document discusses the state of JavaScript and opportunities for its responsible use. It encourages learning JavaScript properly rather than copying code without understanding. It argues against workarounds for browser issues and urges focusing on standards compliance. Updating tools and libraries, removing legacy code, and embracing modern JavaScript features like those in ES6 can help address past issues and enable further innovation on the web.
Stapling and patching the web of now - ForwardJS3, San FranciscoChristian Heilmann
This document summarizes a talk given by Chris Heilmann at ForwardJS in 2015. Heilmann discusses the state of web development technologies and how developers have focused too much on experimental features that are not ready for production use. This has led to a fragmented web where browsers implement features differently. He argues developers should focus on standardizing and improving existing web standards rather than constantly introducing new technologies. ES6 is highlighted as a priority for improving existing JavaScript.
BelTech 2017 - Building Quality in the BrowserEamonn Boyle
The document provides recommendations for building quality JavaScript applications. It recommends adopting a single page architecture with a front-end JavaScript application communicating with backend services via RESTful APIs. It suggests using modern frameworks like Angular and React that are supported by large companies. It also recommends using static typing with TypeScript to catch errors earlier. Finally, it emphasizes applying software best practices like separation of concerns, modular design, and testing to JavaScript development.
The document discusses lesser known tools that can help with computer science and engineering assignments. It describes tools for website development and testing like Bounce and CodePen. General tools mentioned include Coderwall for coding tips and LastPass for password management. Learning resources highlighted are dictionaries of data structures and algorithms, cheat sheets, open online courses, and Stack Overflow for coding help. The document encourages students to make use of these free and paid tools and online sources for assignments.
Similar to Turning huge ships - Open Source and Microsoft (20)
We are obsessed with coding and creating automated workflows and optimisations. And yet our final products aren't making it easy for people to use them. Somewhere, we lost empathy for our end users and other developers. Maybe it is time to change that. Here are some ideas.
This document discusses ways to improve how web developers learn best practices through browser and tooling improvements. It suggests that linting and inline insights directly in code editors could help prevent mistakes by flagging issues early. A tool called webhint is highlighted that provides one-stop checking and explanations of hints related to performance, accessibility, security and more. The document advocates for customizing hints based on a project's specific needs and environment. Overall, it argues for accelerated learning through context-sensitive, customizable best practices integrated into development workflows.
This document discusses privilege in the context of social media and the internet. It acknowledges privileges like internet access, the ability to communicate, and supportive online communities. It warns that machine learning and algorithms risk creating echo chambers and guided messaging if they are not kept in check by human curation. The document advocates taking back the web for decent, thinking and loving humans and using privileges to help others gain access to learning, communication, and communities.
This document discusses artificial intelligence and how it can help humans. It covers that AI is not new, having originated in the 1950s, and is now more advanced due to increased computing power. It also discusses how AI utilizes pattern recognition and machine learning. The document then covers several applications of AI including computer vision, natural language processing, sentiment analysis, speech recognition/conversion and moderation. It notes both the benefits of AI in automating tasks and preventing errors, as well as the responsibilities of ensuring transparency and allowing people to opt-in to algorithms.
Killing the golden calf of coding - We are Developers keynoteChristian Heilmann
The document discusses concerns about the perception and realities of coding careers. It expresses worry that coding is seen solely as a way to get a job rather than as a means of problem-solving. While coding can provide fulfilling work, the document cautions that the need for coders may decrease with automation and that the role may evolve from coding to engineering. It suggests a future where machines assist with repetitive coding tasks and people focus on delivering maintainable, secure products with attention to privacy and user experience.
PWA are a hot topic and it is important to understand that they are a different approach to apps than the traditional way of packaging something and letting the user install it. In this keynote you'll see some of the differences.
This document discusses privilege in technology and perceptions of technology workers. It acknowledges the privileges that tech workers enjoy, such as access to resources and high demand in the job market. However, it also notes problems like peer pressure, lack of work-life balance, and imposter syndrome. Both tech workers and the public have skewed perceptions of each other - tech workers feel others do not appreciate or understand their work, while the public sees tech workers as antisocial or caring only about profit. The document encourages taking small steps to improve the situation, such as being kind to oneself, considering others, sharing knowledge, and focusing on quality over quantity of work.
The document provides five ways for JavaScript developers to be happier:
1) Concentrate on the present and focus on creating rather than worrying about the past or future.
2) Limit distractions by streamlining your development environment and using an editor like VS Code that consolidates features.
3) Make mistakes less likely by using linters to catch errors as you code.
4) Get to know your tools better like debuggers to avoid console.log and gain insights to build better solutions.
5) Give back to others in the community by being helpful rather than causing drama.
The document discusses progressive web apps (PWAs) and provides suggestions for improving them. It notes that while PWAs aim to have engaging, fast, integrated, and reliable experiences like native apps, they still have room for improvement in areas like speed, integration, and reliability. It emphasizes that PWAs should adhere to web best practices and provide actually useful experiences rather than just focusing on technical features. The document encourages helping the PWA effort by providing feedback, using and contributing to tools, keeping messaging up-to-date, and promoting high-quality examples.
Chris Heilmann gave a talk at BTConf in Munich in January 2018 about machine learning, automation worries, and coding. He discussed how coding used to refer to creative programming within technical limitations but now often refers to programming for work. He addressed common worries about new technologies and dependencies, and argued that abstractions are not inherently bad and help more people build products together through consensus. The talk focused on using tools to be more productive and enabling rather than seeing them as dangers, and creating solutions for users rather than fighting old approaches.
The document provides advice and encouragement for someone starting out with JavaScript development. It discusses how JavaScript can be used in many environments like browsers, apps, and servers. It recommends resources like MDN and tools like linting to help avoid mistakes. It emphasizes that this is an exciting time for JavaScript and advises setting priorities and standards, being involved in the community, and bringing new voices and perspectives.
Keynote at halfstackconf 2017 discussing the falsehood of the idea that in order to survive the automation evolution everybody needs to learn how to code. Machines can code, too.
Progressive Web Apps - Covering the best of both worlds - DevReachChristian Heilmann
Progressive Web Apps (PWAs) can provide app-like experiences through the web by making web content fast, reliable and engaging. While PWAs may not be necessary for all projects, they can help clean up and speed up current web-based projects. PWAs leverage new web capabilities like service workers to work offline, load fast, and improve the user experience without having to meet all the requirements of native apps.
Progressive Web Apps - Covering the best of both worldsChristian Heilmann
This document discusses progressive web applications (PWAs) and their advantages over traditional native mobile applications. PWAs use modern web capabilities like Service Workers to deliver native-like experiences to users. Some key benefits of PWAs include their ability to work across platforms, have smaller file sizes for faster loading, support offline use, and provide simple update mechanisms compared to native apps. While PWAs do not have full access to device capabilities like native apps, they allow delivering app-like web content to users in a more accessible and reliable manner than traditional web pages.
Progressive Web Apps - Bringing the web front and center Christian Heilmann
This document discusses progressive web apps (PWAs). It notes that PWAs aim to make web apps feel like native mobile apps by being discoverable, installable, linkable, safe, responsive and progressive. The document outlines some key characteristics of PWAs, including that they need to be served from secure origins and have app manifests. It also discusses some common misconceptions around PWAs and notes that as PWAs improve, they will continue to blur the line between web apps and native mobile apps.
This document discusses the differences between CSS and JavaScript and when each is most appropriate to use. It argues that CSS is often underestimated in favor of JavaScript solutions. CSS has advanced significantly with features like calc(), media queries, animations/transitions, flexbox, grid, variables and more. These powerful features allow many tasks to be accomplished with CSS alone without needing JavaScript. The document encourages embracing the "squishiness" of the web and considering CSS more when building interfaces.
This document provides tips for becoming an effective conference presenter. It discusses finding a topic to present on, writing a proposal to submit to conferences, creating presentation materials, writing the presentation, and delivering the presentation. The key steps covered are finding an exciting topic, researching it, crafting a compelling proposal, developing slides and other visual aids to enhance the story and message, writing the presentation to have a clear structure and narrative arc, and practicing delivery techniques to engage the audience. The overall goal is to give attendees a memorable experience that leaves them feeling they learned something valuable.
Suit up, bring extra oxygen Internet space explorers needed.Christian Heilmann
The document discusses the future of computing and artificial intelligence. It notes that people are both excited and fearful about technological progress, and outlines things that are going right (e.g. advances in machine learning and computer vision) as well as things that are going wrong (e.g. lack of transparency, data privacy issues). It argues that the future of computing needs people who are not afraid of technology and who will create interfaces that are simple, human, and help people communicate better. The role of technologists is to use their skills to give people a sense of data ownership and ensure technological progress improves lives rather than just making money.
Ardra Nakshatra (आर्द्रा): Understanding its Effects and RemediesAstro Pathshala
Ardra Nakshatra, the sixth Nakshatra in Vedic astrology, spans from 6°40' to 20° in the Gemini zodiac sign. Governed by Rahu, the north lunar node, Ardra translates to "the moist one" or "the star of sorrow." Symbolized by a teardrop, it represents the transformational power of storms, bringing both destruction and renewal.
About Astro Pathshala
Astro Pathshala is a renowned astrology institute offering comprehensive astrology courses and personalized astrological consultations for over 20 years. Founded by Gurudev Sunil Vashist ji, Astro Pathshala has been a beacon of knowledge and guidance in the field of Vedic astrology. With a team of experienced astrologers, the institute provides in-depth courses that cover various aspects of astrology, including Nakshatras, planetary influences, and remedies. Whether you are a beginner seeking to learn astrology or someone looking for expert astrological advice, Astro Pathshala is dedicated to helping you navigate life's challenges and unlock your full potential through the ancient wisdom of Vedic astrology.
For more information about their courses and consultations, visit Astro Pathshala.
Integrated Marketing Communications (IMC)- Concept, Features, Elements, Role of advertising in IMC
Advertising: Concept, Features, Evolution of Advertising, Active Participants, Benefits of advertising to Business firms and consumers.
Classification of advertising: Geographic, Media, Target audience and Functions.
Join educators from the US and worldwide at this year’s conference, themed “Strategies for Proficiency & Acquisition,” to learn from top experts in world language teaching.
Webinar Innovative assessments for SOcial Emotional SkillsEduSkills OECD
Presentations by Adriano Linzarini and Daniel Catarino da Silva of the OECD Rethinking Assessment of Social and Emotional Skills project from the OECD webinar "Innovations in measuring social and emotional skills and what AI will bring next" on 5 July 2024
Understanding and Interpreting Teachers’ TPACK for Teaching Multimodalities i...Neny Isharyanti
Presented as a plenary session in iTELL 2024 in Salatiga on 4 July 2024.
The plenary focuses on understanding and intepreting relevant TPACK competence for teachers to be adept in teaching multimodality in the digital age. It juxtaposes the results of research on multimodality with its contextual implementation in the teaching of English subject in the Indonesian Emancipated Curriculum.
Front Desk Management in the Odoo 17 ERPCeline George
Front desk officers are responsible for taking care of guests and customers. Their work mainly involves interacting with customers and business partners, either in person or through phone calls.
6. What now?
A lot!
What? Why? Who?
• Last year a lot of Microsoft products
went open source or started as open
source
• Many products are cross-platform,
moving Microsoft away from the
“Windows only company” stigma.
• Azure supports multiple OS
• Our training and research papers are
openly available.
8. What now?What? Why? Who?
IT makes sense
• We live in a post-product world -
paying for software in a fixed state feels
wrong.
• Developers don’t want to concentrate
on one environment, but have choices
• People having already worked with your
products are easier to hire and cheaper
to on-board.
9. It makes sense • Open Source and Creative Commons
projects turn a company from someone
you buy from into a source of
information.
• Employees love the option to keep
working on a project, even when they
left the company for something else.
• It is easier to contribute to a project and
tap into other people’s skills than doing
everything yourself.
What now?What? Why? Who?
10. It makes for a great
example for others.
http://www.businessinsider.de/apple-is-finally-going-to-start-publishing-its-artificial-intelligence-research-2016-12?op=1&r=US&IR=T
What now?What? Why? Who?
11. What now?
Who does what in
Microsoft and what are
examples of success?
What? Why? Who?
12. Web-friendly browser with
open information channels
and a responsive team.
https://developer.microsoft.com/microsoft-edge/
Microsoft Edge
What now?What? Why? Who?
19. Microsoft Edge - Visibility
• The Edge team takes part in
conferences and competition events
• They are quick to answer requests on
Stack Overflow, Twitter and other social
media
• Many team members have their own
blogs and maintain a social media
presence outside of their daily work
What now?What? Why? Who?
21. Web Devrel Team / Interop Team
• We help developers to build standards-
based solutions and remove old,
outdated code.
• We stopped advertising our platform as
the best, but let people decide.
• We deliver facts, data and insights into
which technologies are used on the web
by publishing Bing crawler information.
What now?What? Why? Who?
26. http://code.visualstudio.com/
Visual Studio
Code • Lightweight editor for all kind of
developers
• Based on Open Source technologies of
GitHub, Google and our own
• Written in TypeScript
• Extensible and compatible with other
editors
What now?What? Why? Who?
27. http://code.visualstudio.com/
Visual Studio
Code • Git integration
• JavaScript debugging in the editor
• Source Code on GitHub
• Cross-Platform
• “Monaco” editor version embeddable
into own web products
What now?What? Why? Who?
29. Open Source JavaScript
engine; Monopoly
disruptor
https://github.com/Microsoft/ChakraCore
ChakraCore
What now?What? Why? Who?
30. ChakraCore • Open Source variant of Chakra, Edge’s
JavaScript engine
• Cross-platform
• Quick, small and new
• Node compatible
• Can be integrated into own products
• V8 compatibility with shims
• Exemplary GitHub presence!
What now?What? Why? Who?
32. A way to write JavaScript
for those who don’t like it;
JS that scales; Transpiler
http://typescriptlang.org
TypeScript
What now?What? Why? Who?
33. TypeScript
http://typescriptlang.org
• “JavaScript that scales” - JavaScript with
all the features Java/C# developers
always wanted to have
• High adoption by third parties
(Angular/Dojo)
• Allows to transpile into older
ECMAScript versions for interop
• Open Source from the get-go.
What now?What? Why? Who?
34. TypeScript
http://typescriptlang.org
What now?What? Why? Who?
https://slack.engineering/typescript-at-slack-a81307fa288d
A smart static type checker increases our
confidence in our code, catches easily made
mistakes before they are committed, and makes
the code base more self-documenting.
35. TypeScript
What now?What? Why? Who?
https://medium.com/@tomdale/glimmer-js-whats-the-deal-with-typescript-f666d1a3aad0
Most transpiled languages exist because they want
to correct some perceived deficiencies in
JavaScript. It’s hard to quantify, but you can feel the
respect that the TypeScript team has for JavaScript.
They’re not trying to rescue an inherently flawed
language; instead, they’re trying to help a language
they love reach new heights.
37. Presence! • We need Microsoft-knowledgable
presenters outside our own events -
send in CFPs.
• Many online magazines are looking for
guest authors - even for pay - and we
have a team to connect you to them
• Our evangelism team is often forced to
decline conferences and need people to
offer as an alternative
What now?What? Why? Who?
38. Presence! • Take active part in Stackoverflow
discussions
• Help with debunking false accusations
on Twitter by providing facts and links
• Report bugs in the open bug trackers
and as GitHub issues
• Send around our materials in your
circles of influence
What now?What? Why? Who?
39. Information • Windows changed a lot and by adding
Bash we have a lot of things Mac and
*nix users needed to consider switching.
It is important to be up to speed on
that.
• The Surface Book is an exciting piece of
hardware for developers
• Switching from OSX to Windows is
confusing - help people if you can
What now?What? Why? Who?
40. Information
• Many of our newer products are
available independent of our
development chain
• We have to stop starting tutorials with
“Let’s openVisual Studio…”
• There is no lack of prejudice against
Microsoft (EEE)
What now?What? Why? Who?
41. A new
beginning • Help us getting rid of Internet Explorer
dependencies
• Explain customers the benefits of Cloud
First instead of in-house maintenance
and its dangers of stagnation
• Read the blogs of product groups and
follow them on Twitter
• Don’t wait for //build to stay up-to-date
What now?What? Why? Who?
42. Translations
• Many Open Source projects lack
contributors because there are no
materials in other languages than
English
• It helps a lot to write about these
projects in a different language
• Contribute translations to open projects
What now?What? Why? Who?
43. • Open Source is all about taking initiative
and starting to contribute - no sense in
waiting to be asked
• Contribution doesn’t mean to support
and advocate projects
• It can also mean creating something on
your own or take part in other projects
as a Microsoft expert
Dare to take
initiative
What now?What? Why? Who?