28 min read

Q2 2018 IT Review: GitHub Joins Microsoft, GDPR Goes Live, and ML Frameworks Mature

Q2 2018 IT Review: GitHub Joins Microsoft, GDPR Goes Live, and ML Frameworks Mature

Part of IT Trends & Reviews — what actually shipped, quarter by quarter.

1. Introduction: Three Earthquakes in One Quarter

The Q2 2018 IT review covers a period of unusual density. In the space of twelve weeks, across April, May, and June 2018, three separate shocks hit the industry simultaneously. Each is large enough to define an entire year on its own. As a result, they accelerate timelines and force decisions that practitioners have been deferring. This is the quarter when three long-running tensions reach their boiling points at the same time. One sets open-source idealism against corporate reality. Another sets data monetisation against personal privacy. A third sets research agility against production scalability.

The first and most dramatic shock arrives on June 4, when Microsoft announces its intent to acquire GitHub for US$7.5 billion in stock. In practice, GitHub hosts over 85 million repositories at the time, serving as the shared nervous system of the open-source world. The reaction splits the developer community immediately. Optimists point to Microsoft’s transformation under CEO Satya Nadella. For example, the company is the most-active corporate contributor to open-source software on GitHub itself. It has also shipped Visual Studio Code, a free editor that dominates developer surveys. By contrast, sceptics cite Nokia, Skype, and other acquisitions as cautionary tales, and GitLab reports unprecedented sign-up spikes in the days following the announcement. Overall, the deal is not yet closed, but its announcement alone changes the power geometry of software infrastructure.

1.1 GDPR and the machine-learning shift

The second shock is regulatory and arrives three weeks earlier, on May 25, when the European Union’s General Data Protection Regulation takes full effect. For two years, organisations worldwide have been racing to audit data flows, appoint data protection officers, re-architect consent mechanisms, and rewrite privacy policies. The arrival date produces a flood of consent-request emails, a wave of memes, and immediate legal action. Privacy activist Max Schrems files complaints against Facebook, Instagram, WhatsApp, and Google within hours of midnight. He alleges forced consent violations. In addition, programmatic advertising volume in Europe drops an estimated 25–40 percent on enforcement day itself. Some US-based media sites choose to block EU users entirely rather than comply. Overall, GDPR has instantly become the most consequential data-regulation framework in a generation.

The third shock is technological and unfolds more quietly but with lasting implications. Machine-learning frameworks are reaching an inflection point. For example, PyTorch 0.4.0, released April 24, merges the previously separate Tensor and Variable types into a single abstraction — a change that dramatically simplifies research code and accelerates community adoption. Meanwhile, TensorFlow 1.7 and 1.8 ship in April and May respectively, adding eager-execution improvements that acknowledge PyTorch’s growing influence. In addition, Google’s I/O keynote on May 8 delivers Google Duplex, a phone-call automation system so polished that it triggers an industry-wide debate about AI disclosure and consent. The quarter closes with Kubernetes 1.11 shipping on June 27 and AWS EKS going generally available on June 5. Together they confirm that managed Kubernetes is now standard infrastructure rather than an experiment.

$7.5B
Microsoft acquires GitHub, June 4, 2018
May 25
GDPR enforcement begins, EU-wide
4,300+
Attendees at KubeCon EU, Copenhagen
25–40%
Drop in EU programmatic ad volume on GDPR day
PyTorch 0.4
Tensor/Variable merge, April 24, 2018
June 5
AWS EKS reaches General Availability

2. GitHub Deep Dive: Key Open-Source Releases

Q2 2018 delivers a cohort of open-source releases that collectively define the ML-framework and cloud-native landscape for the next two years. The releases below are not incremental improvements. Rather, they represent deliberate architectural decisions. Those decisions change how practitioners write, train, and deploy machine-learning models, and how they manage containerised workloads at scale.

2.1 pytorch/pytorch — Version 0.4.0

PyTorch 0.4.0 — The Merge That Changes Everything

Released: April 24, 2018 · GitHub: github.com/pytorch/pytorch · License: BSD-3-Clause

PyTorch 0.4.0 is the most consequential release in the project’s short history. It is arguably the moment when PyTorch becomes the dominant framework for academic ML research. Above all, the defining change is the unification of Tensor and Variable into a single type. Prior to 0.4, researchers had to wrap tensors in Variable objects to track gradients, creating friction and confusion. The merge eliminates that distinction: every tensor now has a requires_grad flag, and the autograd engine handles differentiation transparently.

Additionally, 0.4 introduces zero-dimensional tensors (scalar tensors), resolving a longstanding inconsistency with NumPy conventions. The release adds new dtype support, with half, float, double, int, long, and byte types as first-class properties. It brings initial Windows support for the first time. In addition, DataLoader improves for faster multi-process data loading. Notably, the project sits at approximately 14,000 GitHub stars at this point. It is accelerating rapidly in the research community, particularly in natural-language processing. There, papers increasingly prefer PyTorch’s dynamic computational graph over TensorFlow’s static-graph approach.

PyTorch logo representing the 0.4.0 release in April 2018
PyTorch logo. Version 0.4.0, released April 24, 2018, merges Tensor and Variable into a single unified type, dramatically simplifying research code and cementing PyTorch’s dominance in academic ML. Source: pytorch/pytorch on GitHub / BSD-3-Clause license.

2.2 tensorflow/tensorflow — Versions 1.7 and 1.8

TensorFlow 1.7 & 1.8 — Eager Execution Advances and TensorFlow.js Debuts

TF 1.7: April 26, 2018 · TF 1.8: May 2018 · GitHub: github.com/tensorflow/tensorflow · License: Apache 2.0

TensorFlow ships two releases in Q2 2018, both influenced by the competitive pressure from PyTorch. TF 1.7 (April 26) advances eager execution — the define-by-run mode that executes operations immediately rather than building a static computation graph — bringing it closer to the default experience. In addition, TF 1.8 follows in May with further stabilisation and performance improvements to tf.data input pipelines, which are becoming the recommended path for efficient training data ingestion. Importantly, Google announces TensorFlow.js at Google I/O in May 2018: a complete ML library for JavaScript that enables training and inference directly in the browser using WebGL acceleration. TensorFlow.js is not a toy. For example, it ships pre-trained models for pose estimation, toxicity detection, and image classification. Those run at acceptable speed on modern consumer hardware, opening ML to the enormous web-development audience.

At this point TensorFlow commands approximately 85,000 GitHub stars and is the undisputed production ML framework at Google, Amazon, Twitter, and most large enterprises. However, research adoption is visibly shifting. An informal survey of papers at ICML and ICLR 2018 shows PyTorch usage growing sharply among academic submissions, while TensorFlow retains dominance in production deployment.

TensorFlow icon representing the 1.7 and 1.8 releases in Q2 2018
TensorFlow icon. TF 1.7 (April 26, 2018) and TF 1.8 (May 2018) advance eager execution and introduce TensorFlow.js for browser-based ML. Source: Simple Icons project / CC0 license.

2.3 kubernetes/kubernetes — Version 1.11

Kubernetes 1.11 — CoreDNS Graduates, IPVS Mode Stable

Released: June 27, 2018 · GitHub: github.com/kubernetes/kubernetes · License: Apache 2.0

Kubernetes 1.11 is the second release of 2018 and confirms the platform’s steady march toward operational maturity. The headline feature is the graduation of CoreDNS to GA: CoreDNS replaces kube-dns as the default cluster DNS and offers a plugin-based architecture that is far more extensible. Operators can now route DNS queries through custom plugins for logging, caching, health-checking, and advanced service-discovery scenarios. None of that requires patching the core implementation. IPVS mode for kube-proxy moves from beta to stable, delivering better performance at large scale through kernel-level IP virtual-server hash tables rather than iptables chains. In addition, the release ships improved dynamic admission webhooks and further stabilisation of Custom Resource Definitions (CRDs). Those definitions are becoming the foundation for operators and complex application-level automation.

At KubeCon EU 2018 in Copenhagen (May 2–4), the CNCF reports that over 2,700 contributors have touched the Kubernetes codebase. In addition, the project shows no signs of slowing. The conference draws approximately 4,300 registered attendees, more than double the prior year’s equivalent, and spawns a wave of session recordings covering GitOps, Istio integration, operator patterns, and production runbooks.

Kubernetes logo representing version 1.11, released June 27, 2018
Kubernetes logo. Kubernetes 1.11, released June 27, 2018, promotes CoreDNS to GA and stabilises IPVS mode, advancing the platform toward fully production-grade networking. Source: CNCF Artwork repository / Apache 2.0 license.

2.4 istio/istio — Release 0.8

Istio 0.8 — The Last Major Pre-1.0 Milestone

Released: June 1, 2018 · GitHub: github.com/istio/istio · License: Apache 2.0

Istio 0.8 ships on June 1 and is the most significant Istio release since the project’s launch. The release introduces Istio v1alpha3 routing APIs — a complete redesign of the traffic-management configuration model that is more expressive and consistent. The new model introduces the VirtualService and DestinationRule resources that become the standard vocabulary for Istio traffic control, replacing the earlier RouteRule and DestinationPolicy. In addition, Helm-based installation becomes the recommended deployment path, reducing configuration friction significantly. The project also demonstrates production deployments at scale: Lyft, which provides Envoy as Istio’s data-plane proxy, is running Istio in production for portions of its traffic. As a result, the 1.0 release is now clearly within sight. In addition, 0.8 serves as the API-stabilisation milestone that operators need to begin serious production trials.

Istio service mesh icon representing the 0.8 release in June 2018
Istio service mesh icon. Istio 0.8, released June 1, 2018, redesigns the traffic-management API surface with VirtualService and DestinationRule resources, laying the groundwork for the imminent 1.0 release. Source: CNCF Artwork repository / Apache 2.0 license.

2.5 nodejs/node — Node.js 10 (LTS)

Node.js 10.0.0 — V8 6.6, N-API Stability, and npm 6

Released: April 24, 2018 · GitHub: github.com/nodejs/node · License: MIT

Node.js 10 enters Long-Term Support (LTS) in October but ships its first release on April 24, 2018. It bundles V8 JavaScript engine version 6.6, which delivers significant performance improvements for array operations and async/await patterns. Crucially, N-API is promoted to stable. N-API is a C API layer for native addons that abstracts the underlying V8 and Node internals. As a result, native modules compiled against N-API do not need recompiling when the JavaScript engine upgrades.

This resolves one of the most painful recurring friction points in the Node.js ecosystem. The release also bundles npm version 6, which introduces package auditing (npm audit). The command checks installed dependencies against a known-vulnerability database. As a result, CI pipelines everywhere adopt it immediately. In addition, Node.js 10 improves its HTTP/2 implementation and ships the fs.promises API in experimental form, beginning the long-awaited migration away from callback-heavy filesystem APIs toward native Promise-based alternatives.

2.6 helm/helm — Version 2.9

Helm 2.9 — Chart Testing, Tiller TLS, and Improved Stability

Released: May 2018 · GitHub: github.com/helm/helm · License: Apache 2.0

Helm 2.9 arrives alongside the growing KubeCon conversation about production-grade Kubernetes packaging. The release introduces improved chart repository authentication. It also progresses the discussion around Tiller security. Tiller is Helm’s server-side component, and it runs with cluster-admin privileges by default. The community is actively working to address that problem in the upcoming Helm 3 design. Helm 2.9 also improves helm test functionality, enabling chart authors to ship test pods alongside their charts and verify deployments automatically. The project occupies a central position in the Kubernetes packaging ecosystem: virtually every CNCF project that runs on Kubernetes ships a Helm chart. In addition, the Helm Hub (a central chart repository) is under active development this quarter. Overall, Helm’s popularity reflects a broader pattern: as Kubernetes clusters multiply, operators need packaging abstractions that sit above raw YAML manifests.

3. Big Tech & Industry Breakthroughs

Q2 2018 is unusually event-dense for the technology industry’s major players. For example, three flagship developer conferences — Microsoft Build, Google I/O, and Apple WWDC — fire in rapid succession across May and early June, producing hundreds of product announcements. Simultaneously, regulatory pressure and geopolitical dynamics accelerate corporate decision-making across the board. The table below organises the major events by company and significance.

Company / RegionEventDateSignificance
MicrosoftAcquires GitHub for $7.5BJune 4Open Source Largest developer-tool acquisition in history; signals new Microsoft identity
MicrosoftBuild 2018 conferenceMay 7–9Cloud Azure Cognitive Services expansion, VS Live Share launch, Bot Framework 4.0 preview
GoogleGoogle I/O 2018May 8–10AI Google Duplex demo, Android P beta, ML Kit for Firebase, TensorFlow.js launch
AppleWWDC 2018June 4–8Mobile iOS 12, macOS Mojave, ARKit 2, Siri Shortcuts, Swift 4.2 preview
Amazon/AWSEKS General AvailabilityJune 5Cloud Managed Kubernetes on AWS enters GA, completing the big-three managed-K8s landscape
FacebookZuckerberg Senate testimonyApril 10–11Privacy Congressional questioning on Cambridge Analytica; accelerates global privacy-regulation momentum
European UnionGDPR enforcement beginsMay 25Regulation 25–40% EU ad-volume drop on Day 1; $8.8B in GDPR complaints filed immediately
Baidu (China)ERNIE language model and DuerOS 3.0Q2 2018AI ERNIE advances Chinese NLP; DuerOS 3.0 ships for smart-speaker integrations
Alibaba CloudPAI 2.0 ML platform launchQ2 2018AI/Cloud Platform for AI v2 targets enterprise ML; Alibaba extends cloud to 19 global regions
NVIDIAQuadro GV100 GPUApril 2018Hardware Volta-architecture workstation GPU with 32GB HBM2; targets deep-learning researchers
GitLabRapid user-growth spikeJune 4–6Open Source Reports tens of thousands of new repository imports in 48 h following GitHub/Microsoft news
TypeScriptTypeScript 2.9 releasedMay 31Language Tagged template literal type improvements, import.meta support, better JSX namespace handling

3.1 Microsoft Build 2018 and the GitHub Acquisition

Microsoft Build 2018 runs May 7–9 in Seattle and delivers a clear message: Microsoft is now a cloud-and-developer-tools company, not a Windows company. Satya Nadella opens with AI and cloud announcements, demonstrating Azure Cognitive Services capabilities including real-time speech translation and computer vision. Visual Studio Live Share — a collaborative coding extension that lets developers edit the same file simultaneously from different machines, without sharing their environment — reaches general availability. In addition, the Bot Framework v4.0 preview introduces a new dialog system and supports TypeScript natively. Azure adds new AI services including Custom Vision, Content Moderator improvements, and an expanded Language Understanding (LUIS) service.

Free ebook

Free AI Video, Generated Locally

Working scripts and measured benchmarks. Free.

No spam. Unsubscribe at any time.

However, Build is immediately overshadowed one month later when Microsoft confirms the GitHub acquisition on June 4. Notably, the $7.5 billion deal in Microsoft stock is among the largest acquisitions in Microsoft’s history. GitHub’s CEO Chris Wanstrath is leaving, and Nat Friedman — previously CEO of Xamarin — is named as his successor, reporting to executive vice president Scott Guthrie. The stated rationale is developer-centric. Microsoft gains access to GitHub’s 28 million developers and 85 million repositories. It plans to integrate them with Azure DevOps, Visual Studio, and eventually AI coding tooling. Notably, the deal guarantees that GitHub continues to support other cloud platforms and competitors — a commitment Nadella makes explicitly in the press conference.

3.2 Google I/O 2018 and the Duplex Moment

Google I/O 2018 runs May 8–10 at the Shoreline Amphitheatre in Mountain View and is dominated by a single, astonishing product demonstration. Google Duplex makes phone calls autonomously on behalf of Google Assistant users. It books hair appointments and restaurant reservations with natural conversational speech. That speech includes convincing “uhm” and “mm-hmm” fillers. As a result, the demo sparks immediate controversy about AI identity disclosure: should an AI system be required to identify itself as non-human? Google subsequently commits to disclosure, but the Duplex moment crystallises in public consciousness that AI is no longer an abstract future concept.

Beyond Duplex, Google announces Android P beta with adaptive battery features powered by on-device machine learning. It also announces ML Kit for Firebase, a mobile SDK that bundles pre-built ML models. Those cover text recognition, face detection, barcode scanning, and language identification. As a result, on-device inference becomes available to any mobile developer without ML expertise. In addition, Google launches Google Colab to wider audiences, offering free GPU-backed Jupyter notebook environments that immediately become popular in the research community for sharing reproducible ML experiments.

3.3 Apple WWDC 2018 and ARKit 2

Apple’s Worldwide Developers Conference runs June 4–8 in San Jose, the same week as the GitHub acquisition announcement. iOS 12 focuses on performance rather than new features, promising up to 70 percent faster app launches on older devices. Siri Shortcuts introduces a visual automation system built on top of the former Workflow app, bringing power-user automation to mainstream iOS users. ARKit 2 adds persistent and shared AR experiences. Multiple users can view and interact with the same virtual objects in physical space simultaneously. That capability opens new categories of multiplayer AR games and collaborative design tools. Meanwhile, on the macOS side, macOS Mojave introduces a system-wide dark mode and a new Mac App Store. Swift 4.2 reaches beta with improved compile times and new language features including CaseIterable protocol conformance and the @dynamicMemberLookup attribute.

4. AI & Technology Impact

Q2 2018 is a pivotal quarter in the ML framework narrative. The research community is bifurcating between TensorFlow (production, Google-backed) and PyTorch (research, Facebook-backed). In addition, the implications of that split are becoming clear. Additionally, the Duplex announcement forces a broader public discussion about AI capabilities and ethics that shapes policy conversations for the following year.

April 10–11, 2018

Mark Zuckerberg Testifies Before U.S. Congress

Senate and House hearings on Facebook’s data practices following the Cambridge Analytica revelations expose the gap between Silicon Valley’s algorithmic worldview and legislators’ understanding of data flows. The hearings accelerate US interest in comprehensive federal privacy legislation and fuel GDPR’s moral authority in Europe.

April 24, 2018

PyTorch 0.4.0 Released: The Framework War Shifts

The Tensor/Variable unification makes PyTorch dramatically easier to use for research. For example, papers submitted to NeurIPS 2018 show a sharp jump in PyTorch prevalence, with some estimates suggesting over 50 percent of new research papers prefer PyTorch by end of 2018. The research-production split — PyTorch for experiments, TensorFlow for serving — is now visible to the whole industry.

April 26, 2018

TensorFlow 1.7 Released with Eager Execution Improvements

Google advances eager execution in TF 1.7, signalling that the static-graph-only paradigm is no longer the long-term direction. The release ships improved dataset transformation APIs and better GPU memory management, addressing practical pain points in large-model training.

May 2–4, 2018

KubeCon EU 2018 in Copenhagen

With 4,300+ attendees and sold-out sessions, KubeCon EU 2018 is the largest CNCF event to date. Talks on Istio integration, GitOps (popularised by Weaveworks), and ML workloads on Kubernetes confirm that cloud-native infrastructure is mainstream enterprise territory.

4.1 Q2 2018 timeline: May and June

May 8, 2018

Google Duplex Demonstrated at Google I/O

Google’s Duplex system performs convincing phone-call automation in a live demo. The immediate ethical debate forces the AI community to confront disclosure, consent, and transparency. Google subsequently commits to Duplex disclosing its AI nature at the start of calls. The demo is the strongest public evidence yet that conversational AI is approaching human-level fluency in narrow domains.

May 25, 2018

GDPR Day: The Internet’s Privacy Architecture Resets

Enforcement of GDPR begins. Facebook and Google receive immediate complaints from Max Schrems’s NOYB organisation, totalling approximately $8.8 billion in potential fines. As a result, EU programmatic ad volume drops sharply. The GDPR compliance scramble accelerates data-engineering investment across the industry, creating demand for data-discovery tools, consent-management platforms, and privacy-preserving analytics systems.

June 1, 2018

Istio 0.8: Service Mesh API Redesigned

Istio 0.8 ships v1alpha3 traffic-management APIs (VirtualService, DestinationRule) that become the stable vocabulary for Istio configuration. The release is the final major architectural iteration before the 1.0 release expected in Q3 2018.

June 4–5, 2018

Microsoft Acquires GitHub; AWS EKS Goes GA

Two industry-reshaping events land within 24 hours. Microsoft announces the $7.5B GitHub acquisition, triggering mass GitLab migrations. The following day, AWS EKS reaches General Availability, meaning all three hyperscalers (Google GKE, Azure AKS, AWS EKS) now offer production-ready managed Kubernetes. Container orchestration is no longer a competitive differentiator — it is table stakes.

June 27, 2018

Kubernetes 1.11 Released: CoreDNS Graduates

The second 2018 Kubernetes release ships with CoreDNS as the default stable DNS implementation, IPVS mode stable, and further CRD improvements. Overall, the release reflects the project’s mature engineering discipline: each version ships on schedule, with well-documented upgrade paths and thorough release notes.

4.2 The ML Framework War: Research vs. Production

The most structurally important AI development of Q2 2018 is not a single announcement but a gradual shift visible in preprint servers and conference submissions. PyTorch’s dynamic computation graph, now simplified by the 0.4.0 merge, is pulling research practitioners away from TensorFlow in increasing numbers. However, the production deployment story remains dominated by TensorFlow. TF Serving, TFLite, and TensorFlow Extended all contribute. TFX is Google’s ML production pipeline framework, announced at Google I/O. Together they give enterprises a complete, tested, and Google-backed path from training to serving.

This creates a research-production split that will define the ML-engineering talent market for years: researchers think in PyTorch; ML engineers who deploy at scale think in TensorFlow. Furthermore, the announcement of TensorFlow.js opens an entirely new deployment surface: the browser. That has implications for client-side privacy, because inference happens without sending data to a server. It also opens new categories of interactive ML applications.

4.3 Privacy as an Engineering Discipline

GDPR’s enforcement creates immediate engineering demand. The regulation’s requirements translate into concrete engineering challenges. They cover the right to erasure (right to be forgotten), data portability, purpose limitation, and 72-hour breach notification. For example, data lakes that were designed for maximum retention and minimum structure suddenly require cataloguing, lineage tracking, and selective deletion capabilities. Similarly, consent management platforms, which were a niche product category before May 2018, become a required architectural component for any consumer-facing product serving EU users. The term “privacy engineering” enters the mainstream vocabulary of software engineering this quarter, as organisations recognise that compliance is not a legal checkbox but a continuous engineering practice.

5. Key Voices & Thought Leaders

The following practitioners publish the most influential technical content during Q2 2018, shaping how the broader community interprets and responds to the quarter’s events.

5.1 Kelsey Hightower — Google Cloud / Kubernetes

Kelsey Hightower — Developer Advocate, Google Cloud

Platform: @kelseyhightower on Twitter | Conference talks at KubeCon EU 2018

Hightower is the most influential Kubernetes communicator in 2018. At KubeCon EU in Copenhagen he delivers live demonstrations showing production-quality Kubernetes operations from the command line, making complex orchestration concepts immediately tangible. In addition, his GitHub repository kubernetes-the-hard-way continues to be the definitive hands-on introduction to Kubernetes internals, accumulating over 25,000 stars by the end of Q2. His Twitter commentary on the GitHub/Microsoft acquisition — a measured, positive take — is widely shared in the developer community. Hightower’s effectiveness comes from his refusal to lecture and his insistence on showing working code: he tweets working one-liners that solve real operational problems and the community amplifies them immediately.

5.2 Yann LeCun — Facebook AI Research

Yann LeCun — VP and Chief AI Scientist, Facebook

Platform: Facebook and academic lectures

LeCun, one of the pioneers of convolutional neural networks and a future Turing Award co-recipient, is extremely vocal on social media and in conference talks during Q2 2018. His commentary on the Cambridge Analytica scandal is nuanced: he defends the potential of AI while acknowledging the need for responsible data governance. More technically, LeCun is a vocal champion for self-supervised learning. He sees it as the path toward AI that learns efficiently without massive labelled datasets. He articulates that position repeatedly this quarter, and it will prove prescient. LeCun’s public engagement makes him the most prominent AI voice in the ongoing debate between GDPR regulators and technology companies.

5.3 Martin Fowler — ThoughtWorks

Martin Fowler — Chief Scientist, ThoughtWorks

Fowler continues publishing high-impact essays on software architecture this quarter. For example, his bliki entries on serverless patterns and the trade-offs of event-driven architectures are cited widely in conference talks. More significantly, Fowler’s collaborators at ThoughtWorks publish the 2018 Technology Radar. It places service meshes, specifically Istio, in the “Trial” category and GitOps in “Assess”. That positioning shapes how the community evaluates these emerging patterns. Fowler’s writing carries a distinctive combination of practical specificity and architectural humility that makes it trusted by both senior engineers and team leads navigating adoption decisions.

5.4 Andrej Karpathy — Tesla AI

Andrej Karpathy — Director of AI, Tesla

Platform: @karpathy on Twitter and blog

Karpathy is the most prominent practitioner bridging deep-learning research and large-scale production systems. At Tesla, he oversees the Autopilot perception system, which processes video from eight cameras at 36 frames per second across Tesla’s entire fleet. In Q2 2018 the resonance of his earlier GPU Technology Conference (GTC) talk continues. The talk describes Tesla’s approach to building training datasets from the fleet’s real-world driving data. That data-flywheel approach to autonomous driving differs fundamentally from LIDAR-centred strategies. His Twitter thread explaining the engineering behind the Autopilot neural network becomes a viral reference document for the ML community.

5.5 Max Schrems — Privacy Advocate

Max Schrems — Founder, NOYB (None Of Your Business)

Platform: noyb.eu

Schrems is arguably the most impactful non-engineer on the technology industry during Q2 2018. His organisation NOYB files GDPR complaints against Facebook, WhatsApp, Instagram, and Google within hours of enforcement day. He frames the actions as a test. Either GDPR will have real teeth, or it will prove a paper regulation. Schrems’s legal strategy is technically sophisticated: the complaints target “forced consent” mechanisms, arguing that bundling data-processing consent into terms of service violates GDPR’s requirement for freely given, specific consent. His work forces an industry-wide re-examination of consent architecture and drives demand for consent-management engineering across the technology sector. The Google complaint will ultimately result in a €50 million fine from France’s data-protection authority CNIL in January 2019.

6. Trend Synthesis

At the end of Q2 2018, the technology industry stands at a visible inflection point. The events of this quarter are not isolated incidents. They are the convergent outcomes of trends that have been building for several years. To understand where the industry is going, it is necessary to read these events together rather than separately.

The first and most enduring signal is the corporatisation of open source. The GitHub acquisition crystallises what many practitioners have been sensing: open source is no longer a counter-cultural movement operating outside corporate reach. It is the foundational layer of all modern software. In addition, the major technology corporations are competing to own, sponsor, or influence it. Microsoft’s acquisition is the most dramatic example. However, the same dynamic appears elsewhere this quarter: Amazon’s EKS launch commoditises the Kubernetes layer that Google created, and Istio’s growing adoption accelerates Google’s influence over service-mesh architecture. The question is no longer whether corporations will control open-source infrastructure. Rather, it is which corporations will do so and on what terms. Developers are beginning to evaluate not just the technical quality of a project. They also weigh the governance model behind it. That shift in perspective benefits the CNCF’s vendor-neutral foundation model.

6.1 Privacy engineering and the research-production split

The second signal is the emergence of privacy engineering as a discipline. Before GDPR, privacy was treated in most organisations as a legal and compliance concern, handled by a legal team reviewing policies. After GDPR, it becomes an engineering concern requiring data cataloguing, lineage tracking, deletion pipelines, consent-management systems, and privacy-impact assessments as part of the standard software development lifecycle. The €20 million maximum fine for GDPR violations (or 4 percent of global annual turnover, whichever is greater) gives engineering leaders the budget justification they need to invest in privacy infrastructure. This shift accelerates the development of tools for differential privacy, synthetic data generation, federated learning, and on-device inference. That last model processes data without transmitting it to a central server.

The third signal is the research-production split in machine learning. PyTorch’s 0.4.0 release and TensorFlow’s eager-execution advances tell the same story from different angles. The ML community is rejecting the friction of static computation graphs for research work. Meanwhile, it retains production-grade serving infrastructure for deployment. This creates a dual-framework landscape that will persist for years. Furthermore, Google’s introduction of TensorFlow.js and ML Kit for Firebase shows that the ML deployment surface is expanding beyond server-side inference into browsers, mobile devices, and edge environments. The implication for infrastructure is significant: the model pipeline must now accommodate training on GPU clusters, serving on heterogeneous endpoints (server, mobile, browser), and monitoring across all of them.

6.2 Kubernetes maturity and what the signals add up to

The fourth signal is the maturation of the Kubernetes ecosystem. Four events confirm the same diagnosis. AWS EKS goes GA, Kubernetes 1.11 ships CoreDNS, KubeCon EU grows to 4,300 attendees, and Istio 0.8 advances toward 1.0. Container orchestration is no longer an engineering experiment. It is a production-infrastructure layer available from every cloud provider. The competitive focus is now shifting upward in the stack. It moves to service meshes, ML workload scheduling, multi-cluster federation, and developer-experience tooling. The reason is that the base Kubernetes layer is effectively commoditised. Organisations that spent the last two years evaluating whether to adopt Kubernetes are no longer asking that question. They are asking how to run it better.

Taken together, these signals describe an industry undergoing a rapid transition from experimentation to operationalisation. The technologies that were novel in 2016 — containers, ML frameworks, cloud-native networking — are in Q2 2018 becoming engineering requirements rather than engineering choices. The practitioners who thrive in this environment understand more than how to use these tools. They know how to run them reliably at scale and how to govern the data they process. Moreover, they know how to navigate the organisational structures that surround them: corporate acquisitions, regulatory frameworks, and foundation governance.

6.3 Managed Kubernetes everywhere, privacy as architecture

Key Insight: The End of the Kubernetes Adoption Question

With AWS EKS reaching GA in June 2018, all three major cloud providers offer production-grade managed Kubernetes. The question “should we use Kubernetes?” is effectively retired. The new questions are: Which managed offering? How do we manage multi-cluster topologies? How do we run stateful workloads reliably? And how do we secure service-to-service traffic? Istio 0.8 is a direct answer to the last question. In addition, its imminent 1.0 release will make it the default answer for enterprise production environments.

Key Insight: GDPR Creates the Privacy-Engineering Market

The GDPR compliance scramble of Q2 2018 is not merely a regulatory exercise. It is a structural market-creation event. Every organisation that touches EU user data now requires data-cataloguing tools, consent-management platforms, deletion-pipeline infrastructure, and ongoing compliance monitoring. This creates a new engineering sub-discipline — privacy engineering — with its own tools, best practices, and job titles. The market for this infrastructure will grow for years following enforcement day.

7. Summary

Q2 2018 delivers three watershed moments in quick succession. Microsoft’s announcement of the GitHub acquisition on June 4 is the most dramatic consolidation of open-source infrastructure in the industry’s history. It concentrates the world’s largest code-hosting platform inside a single corporate owner. GDPR’s enforcement on May 25 instantly restructures the privacy economics of every consumer-facing product serving European users and establishes a compliance template that shapes global privacy legislation for years. PyTorch 0.4.0’s Tensor/Variable unification completes the framework’s ascent to research dominance, producing a durable research-production split with TensorFlow that fundamentally shapes how ML teams are built and tooled.

Beyond these three headlines, the quarter confirms several quieter but equally significant trends. The Kubernetes ecosystem reaches undeniable maturity. EKS GA, K8s 1.11, KubeCon EU at record attendance, and Istio 0.8 approaching production-readiness all point the same way. Cloud-native infrastructure is now a baseline expectation rather than an advanced capability. Google I/O’s Duplex demonstration and ML Kit launch show that consumer-facing AI is moving from novelty to embedded product feature at Google’s scale. And the NVIDIA Quadro GV100 represents continued acceleration of the hardware available for workstation-scale deep-learning research.

7.1 Open questions and indicators for Q3 2018

The open questions at the end of Q2 2018 are significant. Will the GitHub acquisition genuinely preserve the platform’s developer-neutral character, or will it eventually become an Azure funnel? Similarly, will GDPR enforcement be consistent and consequential, or will it prove toothless against the largest platforms? Will PyTorch’s research dominance eventually translate into production adoption, forcing TensorFlow to either match its developer experience or cede ground? Finally, will Istio 1.0 — clearly imminent — deliver on the service-mesh promise at production scale without the operational complexity overhead that early adopters are already complaining about?

Practitioners entering Q3 2018 should watch four indicators closely. First comes the pace of GitLab migration following the GitHub deal. Next come the first major GDPR enforcement decisions in Europe, where Google is particularly exposed. Third, TensorFlow 2.0’s architectural direction matters, now rumoured to make eager execution the default. Finally, the Istio 1.0 release quality and community reception will tell their own story. The answers to these questions will define the technical landscape through 2019 and beyond.

GitHub Octocat mark representing the Microsoft acquisition announced June 4, 2018
GitHub mark. On June 4, 2018, Microsoft announces its intent to acquire GitHub for US$7.5 billion, the largest developer-tool acquisition in industry history. The deal closes October 26, 2018. Source: GitHub Logos page / GitHub Inc. trademark, used for editorial reference.
PyTorch icon representing the 0.4.0 release in April 2018
PyTorch icon. Version 0.4.0, released April 24, 2018, merges Tensor and Variable types into a single abstraction, cementing PyTorch as the dominant framework for ML research. Source: Simple Icons project / CC0 license.

8. Sources

All factual claims in this article are supported by the following primary and secondary sources, listed in order of first citation.

  1. TechCrunch — “Microsoft has acquired GitHub for $7.5B in Microsoft stock” — June 4, 2018.
  2. Microsoft News — “Microsoft to acquire GitHub for $7.5 billion” — June 4, 2018.
  3. Wikipedia — General Data Protection Regulation — Implementation date May 25, 2018.
  4. The Verge — “Facebook and Google hit with $8.8 billion in lawsuits on day one of GDPR” — May 25, 2018.
  5. Digiday — “GDPR mayhem: Programmatic ad buying plummets in Europe” — May 25, 2018. (25–40% ad volume drop.)
  6. GitHub — pytorch/pytorch release v0.4.0 — April 24, 2018. (Tensor/Variable merge, zero-dimensional tensors, Windows support.)
  7. GitHub — tensorflow/tensorflow release v1.7.0 — April 26, 2018.
  8. Kubernetes Blog — “Kubernetes 1.11: In-Cluster Load Balancing and CoreDNS Plugin are Now Available” — June 27, 2018.
  9. Istio Blog — “Announcing Istio 0.8” — June 1, 2018.
  10. AWS Blog — “Amazon EKS – Now Generally Available” — June 5, 2018.
  11. Node.js Blog — Node.js v10.0.0 release notes — April 24, 2018. (V8 6.6, N-API stable, npm 6.)
  12. Google AI Blog — “Google Duplex: An AI System for Accomplishing Real-World Tasks Over the Phone” — May 8, 2018.
  13. Firebase Documentation — ML Kit for Firebase — Announced Google I/O 2018, May 8, 2018.
  14. TensorFlow.js Official Site — Announced at Google I/O 2018.
  15. Microsoft Blog — “Microsoft Build 2018: Setting the Stage for a Smarter Future” — May 7, 2018.
  16. Apple Developer — WWDC 2018 Session Videos — iOS 12, macOS Mojave, ARKit 2, Siri Shortcuts, Swift 4.2.
  17. CNCF Blog — KubeCon CloudNativeCon Europe 2018 Recap — May 2018. (4,300+ attendees.)
  18. Harvard Business Review — “Why Microsoft Is Willing to Pay So Much for GitHub” — June 6, 2018.
  19. Wikipedia — GitHub: Microsoft acquisition — GitLab migration spikes following announcement.
  20. NOYB — None Of Your Business (Max Schrems’s organisation) — GDPR complaints against Facebook, Google, May 25, 2018.
  21. TypeScript Documentation — TypeScript 2.9 Release Notes — May 31, 2018.
  22. Martin Fowler — “Serverless” bliki entry — ThoughtWorks, updated 2018.
  23. Helm Blog — Helm 2.9 release announcement — May 2018.
  24. ThoughtWorks Technology Radar 2018 — Service meshes (Trial), GitOps (Assess).
  25. GitHub — kelseyhightower/kubernetes-the-hard-way — Hightower’s canonical K8s tutorial repository.

Free ebook

Free AI Video, Generated Locally

Run Wan 2.1 in ComfyUI on your own GPU — the scripts I use, measured times, sample clips. No cloud, no API keys.

No spam. Unsubscribe at any time.

Artur Poniedziałek
Artur Poniedziałek
IT Expert & Project Manager
🤖 AI ⚡ PM 🐍 Python 🖥️ Local AI

IT Expert & Project Manager with 15+ years of experience. Exploring practical AI applications — from local LLMs and RAG systems to workflow automation. Writing to share knowledge and inspire others to experiment with new technologies.

Leave a Reply

Your email address will not be published. Required fields are marked *