.NET MeetUp Brno - Challenges of Managing CoreFX repo -- Karel Zikmund

•Download as PPTX, PDF•

1 like•102 views

This document summarizes the challenges of managing the .NET CoreFX repository. It discusses that the repo contains the base class libraries for .NET Core, is maintained by around 40 Microsoft engineers, and receives hundreds of issues and pull requests monthly. It outlines strategies for organizing the large repo, prioritizing work, adding new APIs, and involving external contributors through community outreach efforts.

Challenges of
Managing CoreFX repo
.NET MeetUp in Brno, CZ (2017/8/1)
Karel Zikmund ( @ziki_cz)

CoreFX repo
https://github.com/dotnet/corefx
• Core Framework of .NET Core
• BCL (Base class libraries) – 50 namespaces:
• System.Collections
• System.IO
• System.Linq
• System.Data
• System.Net
• System.Reflection
• System.Runtime
• System.Xml
• and more …
• Not included:
• ASP.NET Core
• WCF, EF
• Namespaces, which are not part of .NET Core (e.g. UI / System.Xaml)

People behind CoreFX repo
• ~40 active Microsoft engineers
https://github.com/dotnet/corefx/graphs/contributors
• Ownership/expertise per technology
• Beyond .NET Core:
• .NET Framework
• .NET Native (UWP)
• More teams part of end-to-end:
• Runtime/JIT, infrastructure, CLI, SDK, project system, NuGet, VS, etc.

Issues and PRs
• Incoming monthly: 500-600 issues, 700 PRs
• Notifications: 400-500 per day

Slicing large repo
• Area labels
• Tooling – incoming / outgoing
• Per area / query
• Limitations (no replies, user-configuration, etc.)
• Similar problem for community:
• New issues/PRs into Twitter feeds @corefxissues

Next gen tooling
https://github.com/karelz/GitHubIssues

Triage rules
1. One area-* label
2. Empty Assignee
3. Use up-for-grabs with next steps & complexity description
4. Set Milestone as 95% commitment
5. One issue type label
• bug / enhancement / api-needs-work / documentation, etc.
6. Don't be afraid to say no, or close issues – just explain why and be polite
7. Don't be afraid to be wrong – just be flexible when new information
appears

Adding new APIs
• ~100 unique APIs in .NET Core now
• Dictionary.GetValueOrDefault
• Decision tree:
• Is it existing BCL type?
• Will it be used by CoreFX itself?
• Can it live somewhere else? (PowerCollections)
• API approval process is slow by design
• APIs are forever

Which code change to take?
• Performance changes
• Performance trade-offs
• Code complexity vs. value
• Compatibility breaking changes
• vs. 1.x or .NET Framework / UWP / Mono
• Is the value worth the risk someone will get hurt?
• API usage
• Obsolete APIs
• TreatAsWarnings = breaking change

API Compat tooling – Demo
https://github.com/terrajobst/platform-compat

APIs that
throw PNSE
Platform
Not
Supported
Exception

.NET Standard
2.0 APIs
missing from
.NET
Framework
4.6.1

Team Culture changes & challenges
• Discussions in the open
• Onboarding new contributors (docs, tooling, attitude)
• Communication – being polite, welcoming, patient; making it
constructive
• Unclear language (e.g. ESL = English as Second Language)
• Missing/incomplete/complex repro steps
• Frustration
• Abuse (aggressiveness)
• Having your own opinion vs. driving consensus

Involving Contributors & Community
• CoreFX Contributors standups - https://github.com/dotnet/corefx-standup
• Goals:
• Bi-directional discussion
• Identify blind spots
• 1st
session on 6/26
• Future:
• Monthly cadence
• Live streaming & recordings, open to everyone
• More is coming:
• .NET Technology Q&A sessions
• Monthly alpha versions for close community
• CLR Foundations Talks videos
• More ideas: https://karelz.github.io

Thank you
Seeking
• Feedback
• Alternative / existing solutions
• Ideas (incl. above & beyond CoreFX, Microsoft)
Contacts
@karelz
@ziki_cz
karelz@microsoft.com

This document summarizes the challenges of managing the .NET CoreFX repository. It discusses that the repo contains the base class libraries for .NET Core, is maintained by around 40 Microsoft engineers, and receives hundreds of issues and pull requests monthly. It outlines tools used to manage the large repo and process for evaluating new APIs and code changes. It also discusses efforts to improve communication and involvement with external contributors on issues like onboarding, unclear issues, and driving consensus.

.NET Fringe 2017 - Challenges of Managing CoreFX repo -- Karel Zikmund

Karel Zikmund

.NET MeetUp Prague 2017 - .NET Standard -- Karel Zikmund

Karel Zikmund

The document discusses .NET Standard, which is a specification that defines a set of APIs that all .NET platforms must implement. This allows code written for one platform using those APIs to work seamlessly across all other platforms that support the same .NET Standard version. The document outlines the different versions of .NET Standard and shows which platforms support each version. It emphasizes that .NET Standard is for libraries, while applications should target specific platforms like .NET Core or Xamarin. The document also provides an overview of .NET Core and its key advantages like being cross-platform, unified, fast, modern, open source and lightweight.

.NET MeetUp Amsterdam 2017 - Challenges of Managing CoreFX repo -- Karel Zikmund

Karel Zikmund

This document summarizes the challenges of managing the .NET CoreFX repository. It discusses that the CoreFX repo contains the base class libraries for .NET Core, is maintained by around 40 engineers, and receives 500-600 new issues and 700 pull requests monthly. It outlines techniques for slicing the large repo, setting guidelines for triaging issues, processes for adding new APIs, and approaches for involving external contributors and community. The document aims to gather feedback on managing the repo and improving collaboration.

DotNext 2017 in Moscow - Challenges of Managing CoreFX repo -- Karel Zikmund

Karel Zikmund

C# code sharing across the platforms

Andrei Marukovich

Portable, shared, net-standard libraries – so many options to choose when you need to share some code between the platforms. During this talk we will explore all the options and differences between the library types. After the session you will have a solid understanding of the modern .NET library types and code sharing strategies which you can apply for your next .NET Core, desktop or Xamarin project.

Evalution about programming language part 1

Synapseindiappsdevelopment

Entity Framework for Cross platform apps

Swaminathan Vetri

This document discusses Entity Framework Core, an object-relational mapper that enables .NET developers to work with databases using .NET objects. It offers cross-platform support, is lightweight and composable, supports multiple data stores and providers, and is optimized for simple ORM usage. Key features covered include modeling, change tracking, querying, schema management, and support for .NET Core, ASP.NET Core, and platforms like UWP. Differences from EF 6.x are also outlined, such as additional provider and platform support in Core. The presentation concludes with links for further information and a request for questions.

This document summarizes the challenges of managing the .NET CoreFX repository. It discusses that the repo contains the base class libraries for .NET Core, is maintained by around 40 Microsoft engineers, and receives hundreds of issues and pull requests monthly. It outlines tools used to manage the large repo and process for evaluating new APIs and code changes. It also discusses efforts to improve communication and involvement with external contributors on issues like onboarding, unclear issues, and driving consensus.

.NET Fringe 2017 - Challenges of Managing CoreFX repo -- Karel Zikmund

Karel Zikmund

.NET MeetUp Prague 2017 - .NET Standard -- Karel Zikmund

Karel Zikmund

.NET MeetUp Amsterdam 2017 - Challenges of Managing CoreFX repo -- Karel Zikmund

Karel Zikmund

DotNext 2017 in Moscow - Challenges of Managing CoreFX repo -- Karel Zikmund

Karel Zikmund

C# code sharing across the platforms

Andrei Marukovich

Evalution about programming language part 1

Synapseindiappsdevelopment

Entity Framework for Cross platform apps

Swaminathan Vetri

.NET Standard - Introduction

Immo Landwerth

.NET Standard is a specification that defines a set of APIs that all .NET platforms must implement. It represents a common language infrastructure that allows code to be shared across platforms. Unlike Portable Class Libraries (PCL) which targeted specific platform combinations, .NET Standard provides a versioned set of APIs that can be targeted by any project or library and ensures compatibility with platforms that implement that version or higher. Higher versions of the .NET Standard incorporate all APIs from previous versions, allowing projects and libraries targeting a given version to be used on any platform implementing an equal or higher version.

Java Persistence API (JPA) - A Brief Overview

Craig Dickson

Why Kotlin?

Yongqiang Li

Kotlin is a statically typed programming language that runs on the JVM and is fully interoperable with Java. It aims to combine object-oriented and functional programming in a concise syntax that reduces boilerplate code. Kotlin was developed by JetBrains in 2010 and became an officially supported language for Android development by Google in 2017. It features improvements like type inference, data classes, default function parameters, null safety checks, and higher-order functions that allow developers to write safer, more concise code compared to Java.

Plug-ins & Third-Party SDKs in UE4

Gerke Max Preussner

Overview of Java EE

Kohei Nozaki

Java EE is a set of API specifications for enterprise application development on the Java platform that focuses on server-side development. It includes APIs like JAX-RS for RESTful web services, JPA for object-relational mapping, and JBatch for batch processing. Java EE applications can be run on various application servers like GlassFish, WildFly, WebSphere, and WebLogic. Java EE offers a rich set of APIs for server-side development that are built and maintained by experts in the community.

Adf-fusion-architecture_manage-modular-approach_4581

Berry Clemens

The document discusses modularizing ADF applications for manageability. It recommends: - Organizing workspaces by functional "units" and common components into separate libraries. - Ensuring each module can run independently with full debugging. - Automating the build, test, deployment process to make it consistent, less error-prone, and faster. - Managing dependencies, versions, sources, and documentation across modules requires care. Modularization allows applications to scale while remaining understandable when implemented correctly through library management, versioning, and automated processes.

A Tour of EF Core's (1.1) Most Interesting & Important Features

Julie Lerman

This document summarizes key features and the evolution of Entity Framework Core. It notes that EF Core is a lightweight and extensible version of EF that works across platforms with .NET Core. It highlights composable APIs, cross-platform functionality, and modern software practices as themes of EF Core. The document reviews EF Core versions and features, differences between EF6 and EF Core, the roadmap for future EF Core releases, and resources for learning more.

Welcome to New Swift: Library Evolution & LSP Support

G ABHISEK

Onion Architecture and the Blog

barryosull

2014 01-21-mpi-community-feedback

Jeff Squyres

This document summarizes feedback from the MPI community on requirements for the network layer. It discusses what MPI needs from the network layer including messages, efficient APIs, asynchronous progress, and scalability to millions of peers. It outlines features the MPI community likes in verbs, such as different communication modes, RDMA, and atomic operations. It also describes additional features wanted, such as non-blocking operations, buffer specifications as parameters, and standalone send/receive channels. The document was presented to the OpenFabrics libfabric working group to inform the design.

Neevo - database abstraction layer for PHP

smasty

Neevo is a database abstraction layer for PHP that aims to solve problems with inconsistencies between database systems, lack of abstraction between PHP and SQL, and hand-written SQL queries. It provides an easy to use interface, supports multiple database systems, automatically prevents SQL injection attacks, and includes diagnostic tools for developers. The architecture uses reusable code and unit tests to make queries scalable and the library easily extensible via a custom database driver.

Modern .NET Ecosystem

Andrei Marukovich

Joe Damato

Ontico

The document discusses best practices for building and packaging compiled applications across different platforms. It recommends setting up a build server like Jenkins to enable reproducible builds. Built artifacts should be backed up, such as copying to S3. The document also discusses using tools like chroot, mock, and pbuilder to build in clean environments. It recommends static linking of dependencies where possible and capturing debug symbols to aid in debugging. Automated testing of install/uninstall and correctness is also recommended to catch errors on supported platforms.

Domain Specific Development using T4

Joubin Najmaie

The document discusses domain specific development using T4 templates. It provides an overview of T4, describing it as a text generation engine in Visual Studio used to create domain specific languages. Key points include that T4 can generate code from domain models, capturing business knowledge and making it accessible. The document also outlines the anatomy of T4 templates and how they are processed.

.Net programming with C#

NguynSang29

This document provides an overview of the .NET framework and common type system. It discusses key concepts like value types, reference types, inheritance, polymorphism, interfaces, boxing and unboxing. It also covers working with types in .NET like type operators, conversions, casting and managing external types. The document is divided into multiple modules that cover topics such as the .NET framework architecture, common language runtime, deployment, and common type system fundamentals.

Intro

tutorialsruby

Perl is a powerful general-purpose scripting language that is popular for processing and formatting text files. It is easy to learn and has strong support from developers. Programmers like Perl because it gets the job done quickly - one story describes a programmer writing 12 lines of Perl code in minutes to process thousands of files when it would have taken much longer in other languages. While not suited for low-level or compute-intensive tasks, Perl supports high-level data types, regular expressions, automatic memory management, and is extensible through modules.

Methodologies and flows for chip design

Derek Pappas

This document discusses the benefits of using a Chip Specification Language (CSL) to automatically generate shared infrastructure elements across hardware, software, simulation, and verification domains for chip design. Key points include: - CSL allows for a single specification of infrastructure that can be compiled to generate equivalent code for all domains, avoiding errors from manual generation and maintenance. - Automatically generating infrastructure can reduce engineering time spent on repetitive tasks by 10-100x, allowing teams to focus on design. - Shared infrastructure specified in CSL maintains consistency when changes are made, rather than requiring updates across different files and teams manually. - CSL can generate test benches, vectors, and other elements to dramatically increase verification points

Pitch open plant_fund_dokubricks_v8

docubricks

DocuBricks is a documentation tool for open plant technology projects that aims to address issues with replicating existing open hardware projects. It will create an open source, universal standard for open hardware documentation with features like a modular archive format, bill of materials, assembly instructions, and more. The tool will include desktop and mobile apps to allow consistent documentation in the field or lab. It aims to make documentation inherently modular, verifiable, and useful for benefiting all open hardware projects.

Deep Dive into Entity Framework 6.0

Microsoft Developer Network (MSDN) - Belgium and Luxembourg

This document provides an overview and agenda for a deep dive into Entity Framework 6 (EF6). It discusses EF6 being released as open source, with a Git repository and nightly builds available. It outlines new EF6 runtime features like async query/save, code-based configuration, and performance improvements. The document also discusses EF6 tooling unification and releasing timeline, with alpha versions available now and a tools preview coming in a few months. It concludes by listing potential post-EF6 features for voting on and resources for learning more about EF6.

.Net standard 2.0

Scott Golightly

.NET Standard 2.0 is a specification that defines common .NET APIs that can be used across .NET implementations like .NET Framework and .NET Core. It reduces conditional compilation by offering a common set of APIs and is more resilient to changes in platforms compared to the Portable Class Library (PCL) it replaces. .NET Standard 2.0 significantly increases the number of common APIs to over 32,000, growing 142% from the previous version, and targets a broader range of .NET implementations than PCL.

.Net Core Blimey! (16/07/2015)

citizenmatt

.NET Core is a new open source, cross-platform version of .NET that is optimized for cloud scenarios. It consists of a modular runtime (CoreCLR) and class libraries (CoreFX) that are distributed as NuGet packages. .NET Core is a subset of the .NET Framework and aims to be compatible, though some APIs may have platform-specific implementations or fallbacks. It uses a new app model and runtime called CoreCLR that allows it to run cross-platform on Linux, MacOS and Windows.

.NET Core Blimey! (dotnetsheff Jan 2016)

citizenmatt

.NET Core is a new open source, cross-platform version of .NET that is optimized for cloud-based development scenarios. It consists of a modular runtime (CoreCLR), class libraries (CoreFX), and tools (CLI). .NET Core is not a new version of the .NET Framework, but rather a fork that is being merged back. It aims to provide a consistent development experience across platforms via NuGet packages and the .NET Standard platform specification.

What's hot

.NET Standard - Introduction

Immo Landwerth

Java Persistence API (JPA) - A Brief Overview

Craig Dickson

Why Kotlin?

Yongqiang Li

Plug-ins & Third-Party SDKs in UE4

Gerke Max Preussner

Overview of Java EE

Kohei Nozaki

Adf-fusion-architecture_manage-modular-approach_4581

Berry Clemens

A Tour of EF Core's (1.1) Most Interesting & Important Features

Julie Lerman

Welcome to New Swift: Library Evolution & LSP Support

G ABHISEK

Onion Architecture and the Blog

barryosull

2014 01-21-mpi-community-feedback

Jeff Squyres

Neevo - database abstraction layer for PHP

smasty

Modern .NET Ecosystem

Andrei Marukovich

Joe Damato

Ontico

Domain Specific Development using T4

Joubin Najmaie

.Net programming with C#

NguynSang29

Intro

tutorialsruby

Methodologies and flows for chip design

Derek Pappas

Pitch open plant_fund_dokubricks_v8

docubricks

What's hot (18)

.NET Standard - Introduction

Java Persistence API (JPA) - A Brief Overview

Why Kotlin?

Plug-ins & Third-Party SDKs in UE4

Overview of Java EE

Adf-fusion-architecture_manage-modular-approach_4581

A Tour of EF Core's (1.1) Most Interesting & Important Features

Welcome to New Swift: Library Evolution & LSP Support

Onion Architecture and the Blog

2014 01-21-mpi-community-feedback

Neevo - database abstraction layer for PHP

Modern .NET Ecosystem

Joe Damato

Domain Specific Development using T4

.Net programming with C#

Intro

Methodologies and flows for chip design

Pitch open plant_fund_dokubricks_v8

Similar to .NET MeetUp Brno - Challenges of Managing CoreFX repo -- Karel Zikmund

Deep Dive into Entity Framework 6.0

Microsoft Developer Network (MSDN) - Belgium and Luxembourg

.Net standard 2.0

Scott Golightly

.Net Core Blimey! (16/07/2015)

citizenmatt

.NET Core Blimey! (dotnetsheff Jan 2016)

citizenmatt

Eric ShangKuan

This document provides an agenda for a presentation on .NET Core and open source. It introduces .NET Core as addressing fragmentation issues with previous .NET frameworks by having a single, portable runtime (Core CLR) and unified class libraries. It lists resources for .NET Core open source projects, including the Core CLR, CoreFX foundational libraries, Roslyn compiler, and MSBuild, and demonstrates a "Hello World" console app.

C#: Past, Present and Future

Rodolfo Finochietti

C# has evolved significantly over time, from version 1 through the latest version 8. Some key developments include the addition of generics, LINQ, asynchronous programming, and dynamic features. C# continues to focus on productivity and safe, efficient code with recent versions adding capabilities like nullable reference types, async streams, and ranges/indices. .NET has also evolved with improvements to performance and new functionality in versions like .NET Core 2.1. Looking ahead, .NET Core 3 will add support for desktop frameworks like WinForms and WPF.

NDC London 2020 - Challenges of Managing CoreFx Repo -- Karel Zikmund

Karel Zikmund

.net Core Blimey - Smart Devs UG

citizenmatt

.NET Core is a new open source, cross-platform version of .NET that is optimized for cloud scenarios. It consists of a new runtime called CoreCLR and a new base class library called CoreFX that are modular and package-based. .NET Core is a subset of the .NET Framework and aims to provide independent release cycles for the runtime, base class libraries, and applications. It uses NuGet packages and reference assemblies to provide compatibility while allowing platform-specific implementations.

.NET Core Blimey! (Shropshire Devs Mar 2016)

citizenmatt

This document discusses .NET Core, a new open source, cross-platform version of .NET. It is not a new version of the .NET Framework, but rather a fork that is being merged back. .NET Core includes CoreCLR (the runtime), CoreFX (the base class library), and tools like the .NET CLI. It uses NuGet for distribution and targets the new .NET Standard platform for cross-platform compatibility. Key goals are running on Linux and Mac as well as Windows, and being optimized for cloud-based applications.

Entity Framework 7: What's New?

Ricardo Peres

The document summarizes the new features of Entity Framework 7, the next version of Microsoft's Entity Framework data access API. Key points include: - EF7 is built on .NET Core and runs on multiple platforms like Windows, Linux and Mac. It supports both relational and non-relational data stores. - The codebase has been completely rewritten and uses a provider model for different data stores. It is available on GitHub and supports providers like SQL Server, SQLite, PostgreSQL, and Azure Table Storage. - Many existing features have been removed, like ObjectContext API, Entity SQL, and model-first approach. New features include support for additional platforms/providers and batching of CRUD operations.

.NET Core Blimey! Windows Platform User Group, Manchester

citizenmatt

This document discusses .NET Core, a new open source, cross-platform version of .NET. It is not a new version of the .NET Framework, but rather a fork intended to be modular and optimized for cloud deployments. Key aspects include using NuGet for distribution, targeting multiple platforms like Linux and Mac, and using .NET Standard to define a common set of APIs across platforms. It aims to improve on Portable Class Libraries and make .NET more cross-platform.

Introducing .NET Core Open Source

Eric ShangKuan

This document provides an agenda for introducing .NET Core, an open source and cross-platform version of .NET. It discusses issues with past .NET frameworks being fragmented with too many runtimes and lack of portable libraries. .NET Core aims to solve these issues by having a single runtime (Core CLR) and unified class libraries that can be shipped with applications. It also provides demos and links to .NET Core open source projects on GitHub for the CLR, foundational libraries, compiler and build tools.

Raffaele Rialdi

CodeFest

This document introduces .NET Core and its advantages over the .NET Framework. It discusses how .NET Core is cross-platform, uses the .NET Standard library, and can create self-contained applications. It also highlights how .NET Core applications are smaller, faster, and container-friendly. The document demonstrates how to use the dotnet CLI and publish .NET Core applications to reduce their deployment size. Overall, it promotes adopting .NET Core for its performance, portability, and familiar .NET APIs.

Introduction to dot net

QIANG XU

This document provides an overview of .NET (Core), including its components, frameworks, and implementations. It discusses .NET, .NET Standard, .NET Framework, .NET Core, Xamarin/Mono, packages, metapackages, SDK, CLI, target frameworks, and introduces ASP.NET Core. Key points include that .NET Core is a cross-platform implementation of .NET built on NuGet packages, it implements the .NET Standard, and ASP.NET Core is a modern web framework that can be hosted in Kestrel or IIS.

.Net Framework & Languages Supported by .Net Frmaework

Pranil Dukare

Introduction_to_NET.ppt

Darwin Terraza

This document provides an introduction to .NET technology. It discusses how .NET provides a unified development model across languages, platforms and operating systems using common class libraries and tools. It describes how .NET improves productivity and code quality. Technical advantages of .NET include its robust class library, new languages like C# and VB.NET, and strong interoperability features that allow integration with existing systems and platforms. .NET also enables powerful web and database application development. The future of .NET is aligned with new Microsoft technologies in Windows Vista and beyond.

Entity Framework Core 1.0

Senthil Kumar

- Entity Framework 7.0 is a lean and composable framework distributed via NuGet packages that does not require the full .NET Framework. It supports additional data stores and is designed to be cross-platform. - Some missing features in EF Core 1.0 include stored procedures, table valued functions, and complex types. The speaker will demonstrate EF Core. - The presentation discusses the past, present, and future of Entity Framework and .NET data access frameworks. It provides an overview of Entity Framework 7 and some of its new capabilities.

Dot Net Core

Amir Barylko

.NET Core is a cross-platform version of .NET that allows developers to build applications that run on Windows, Linux and Mac. It features a modular design that only includes necessary components, is lightweight and fast. It also introduces a new model for hosting applications, dependency injection, configuration and logging. ASP.NET Core unifies the web frameworks like MVC, Web API and Web Pages on a single shared framework.

SyPy IronPython

Nick Hodge

Future of Kotlin - How agile can language development be?

Andrey Breslav

A successful project usually grows, and Kotlin is no exception. We are adding new targets (JavaScript and Native) and new computation models (coroutines). This talk is about our vision of the future of Kotlin as a language and a ecosystem. We'll talk strategy: what we think our industry needs at large and how we are going to fit Kotlin into this picture. We'll talk tactics: how we deal with legacy and compatibility issues, and whether there will ever be Kotlin 2.0. We'll talk operations: can we do “continuous delivery” for language features? Or, more generally, how agile can language development be? https://mixitconf.org/en/2017/the-future-of-kotlin-how-agile-can-language-development-be-

Similar to .NET MeetUp Brno - Challenges of Managing CoreFX repo -- Karel Zikmund (20)

Deep Dive into Entity Framework 6.0

.Net standard 2.0

.Net Core Blimey! (16/07/2015)

.NET Core Blimey! (dotnetsheff Jan 2016)

C#: Past, Present and Future

NDC London 2020 - Challenges of Managing CoreFx Repo -- Karel Zikmund

.net Core Blimey - Smart Devs UG

.NET Core Blimey! (Shropshire Devs Mar 2016)

Entity Framework 7: What's New?

.NET Core Blimey! Windows Platform User Group, Manchester

Introducing .NET Core Open Source

Raffaele Rialdi

Introduction to dot net

.Net Framework & Languages Supported by .Net Frmaework

Introduction_to_NET.ppt

Entity Framework Core 1.0

Dot Net Core

SyPy IronPython

Future of Kotlin - How agile can language development be?

More from Karel Zikmund

.NET Conf 2022 - Networking in .NET 7

Karel Zikmund

NDC Sydney 2019 - Async Demystified -- Karel Zikmund

Karel Zikmund

WUG Days 2022 Brno - Networking in .NET 7.0 and YARP -- Karel Zikmund

Karel Zikmund

The document discusses HTTP/3 and QUIC support in .NET 7.0, with HTTP/3 providing benefits for unreliable networks and mobile scenarios. It also covers HTTP/2 WebSockets, which allow reusing the HTTP/2 connection at the client level but require an API change. Additionally, it introduces YARP as an open source reverse proxy library built on .NET, highlighting how reverse proxies are useful for load balancing and other scenarios in microservices architectures.

.NET Core Summer event 2019 in Vienna, AT - .NET 5 - Future of .NET on Mobile...

Karel Zikmund

.NET Core Summer event 2019 in Linz, AT - War stories from .NET team -- Karel...

Karel Zikmund

.NET Core Summer event 2019 in Brno, CZ - Async demystified -- Karel Zikmund

Karel Zikmund

.NET Core Summer event 2019 in Brno, CZ - .NET Core Networking stack and perf...

Karel Zikmund

.NET Core Summer event 2019 in Brno, CZ - War stories from .NET team -- Karel...

Karel Zikmund

.NET Core Summer event 2019 in Prague, CZ - War stories from .NET team -- Kar...

Karel Zikmund

Karel shared several stories from investigating issues on the .NET team, highlighting lessons learned: 1) His first serious investigation involved tracking down a hardware error that only reproduced on one machine, teaching him to always ask if an issue reproduces on multiple machines. 2) Another story showed that not all bugs need to be fixed, like a metadata format bug found after 17 years. 3) Breaking changes are a risk with any fix, as innocent changes can trigger latent bugs, especially around sensitive dates like tax deadlines. 4) Tracing techniques like TTD are invaluable for reproducing flaky, high-impact issues like a networking security bug.

.NET Core Summer event 2019 in Vienna, AT - War stories from .NET team -- Kar...

Karel Zikmund

Karel Zikmund shared lessons learned from investigating bugs on the .NET team. Some key investigations included finding the root cause of a build lab failure was a hardware error, fixing an issue where metadata indexes could exceed the maximum allowed size, and resolving a security vulnerability caused by improper buffer lifetime management. Common lessons included the importance of reproducing issues on multiple machines, considering breaking changes carefully, and utilizing trace tools to aid in debugging mysterious problems.

.NET Core Summer event 2019 in NL - War stories from .NET team -- Karel Zikmund

Karel Zikmund

NDC Oslo 2019 - War stories from .NET team -- Karel Zikmund

Karel Zikmund

Karel Zikmund shared lessons learned from investigating bugs on the .NET team. Some key investigations included: 1. Tracking down a hardware error that was corrupting the stack and only reproducing on some machines. 2. Discovering an issue with the metadata format allowing more methods to be defined than the limit. 3. Finding latent bugs triggered by unrelated changes, like a performance improvement breaking an application. The overall lessons were around the challenges of debugging obscure or intermittent bugs, avoiding breaking changes, and appreciating that anything could potentially cause issues.

DotNext 2017 in Moscow - .NET Core Networking stack and Performance -- Karel ...

Karel Zikmund

.NET MeetUp Brno 2017 - Microsoft Engineering teams in Europe -- Karel Zikmund

Karel Zikmund

Microsoft has a development center in Norway that focuses on developing people experiences, Office Graph, and tenant-wide search within Microsoft Office 365. While the roles are located in Norway, relocation assistance is provided for remote candidates. Programming skills and passion for technology are prioritized over specific experience. Flexible working hours and the ability to work from home are offered. Visa sponsorship is also available to qualified candidates. English is the primary language used, and failing an interview does not prevent reapplying.

.NET MeetUp Brno 2017 - Xamarin .NET internals -- Marek Safar

Karel Zikmund

.NET MeetUp Amsterdam 2017 - .NET Standard -- Karel Zikmund

Karel Zikmund

.NET Standard is a specification that defines a set of APIs that .NET platforms need to implement. It aims to improve code reuse across .NET platforms by providing a common language for developers. Higher versions of .NET Standard contain more APIs and allow projects to run on more platforms. The .NET Portability Analyzer helps developers determine which version of .NET Standard a project supports. Major .NET platforms like .NET Framework, .NET Core and Xamarin are implementing .NET Standard 2.0 to improve cross-platform compatibility and code sharing.

More from Karel Zikmund (16)