惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

N
News | PayPal Newsroom
云风的 BLOG
云风的 BLOG
GbyAI
GbyAI
Engineering at Meta
Engineering at Meta
B
Blog RSS Feed
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
The Register - Security
The Register - Security
L
LangChain Blog
A
About on SuperTechFans
S
Schneier on Security
博客园 - 三生石上(FineUI控件)
Stack Overflow Blog
Stack Overflow Blog
The Hacker News
The Hacker News
AWS News Blog
AWS News Blog
博客园 - 司徒正美
Scott Helme
Scott Helme
K
Kaspersky official blog
Cyberwarzone
Cyberwarzone
T
Tenable Blog
腾讯CDC
Recorded Future
Recorded Future
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
G
GRAHAM CLULEY
Security Latest
Security Latest
S
Securelist
D
Darknet – Hacking Tools, Hacker News & Cyber Security
aimingoo的专栏
aimingoo的专栏
Google DeepMind News
Google DeepMind News
V
Vulnerabilities – Threatpost
雷峰网
雷峰网
T
The Exploit Database - CXSecurity.com
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
V
V2EX
T
The Blog of Author Tim Ferriss
D
Docker
S
Security Affairs
F
Full Disclosure
Know Your Adversary
Know Your Adversary
N
News and Events Feed by Topic
N
News and Events Feed by Topic
T
Tor Project blog
Hugging Face - Blog
Hugging Face - Blog
www.infosecurity-magazine.com
www.infosecurity-magazine.com
Microsoft Security Blog
Microsoft Security Blog
Simon Willison's Weblog
Simon Willison's Weblog
Recent Announcements
Recent Announcements
博客园_首页
博客园 - 聂微东
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
S
Security @ Cisco Blogs

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Without google's transformers, there is no GPT-ishs
Paulo Victor · 2026-04-25 · via DEV Community

Yes, remember back there in 2020/2021 when OpenAI created the gpt2? How about we really focus on what enable them to do that? google transformers.

The modern generative AI industry was built on one of the most consequential papers in the history of software: Google’s 2017 paper, Attention Is All You Need.

That paper introduced the Transformer architecture.
And without that architecture, GPT-2 does not happen in the way we know it.
Honestly, most of today’s AI industry does not happen in the same way either.

This is one of those moments where the industry narrative got flattened.
People remember products, brand names, launches, demos, APIs, and valuation charts.
But under all of that sits a technical shift that changed what was economically and architecturally possible.

That shift was the Transformer.


The pre-Transformer world was not useless, but it was narrower

Before Transformers took over, the field was already making real progress with recurrent neural networks, LSTMs, GRUs, sequence-to-sequence models, and attention layers added on top of those systems.
This mattered.
It was not fake progress.

But it had limits.

Those older architectures were much more painful to scale for long-range dependencies, much harder to parallelize efficiently, and generally less well-suited to the kind of giant training runs that would later define modern language models.

That matters more than people think.

A lot of AI history is really compute history wearing a research costume.
If an architecture is elegant but does not map well onto large-scale training infrastructure, it can hit a ceiling even if the ideas are good.

The brilliance of the Transformer was not only that it worked.
It was that it worked in a way the industry could scale.


What Google actually changed

The key claim in Attention Is All You Need was radical for its time: sequence modeling did not need recurrence or convolution at the center.
The model could rely entirely on attention mechanisms.

That is the line that changed everything.

Google’s authors proposed a model architecture that:

  • removed recurrence from the core sequence model
  • relied on self-attention to model relationships across tokens
  • made training far more parallelizable than RNN-heavy approaches
  • created a cleaner path toward scaling with more data, more parameters, and more compute

This is why the paper mattered so much.
It did not just improve benchmark performance.
It changed the operating assumptions of the field.

Once that door opened, the industry got a new answer to a bigger question:

what if language modeling could be treated as a scaling problem instead of a carefully hand-managed sequence bottleneck problem?

That is the real pivot.


GPT-2 is not just “an OpenAI breakthrough”

GPT-2 absolutely mattered.
It helped prove that large-scale generative language modeling could produce outputs with a level of fluency that forced the industry to pay attention.
It made a lot of people understand, maybe for the first time, that language models were not just autocomplete toys.

But GPT-2 was not born in a vacuum.

GPT-2 stands on the Transformer architecture.
Not metaphorically.
Directly.

Even the name GPT says it:
Generative Pre-trained Transformer.

That last word is doing a lot of work.

Without Google’s Transformer paper, there is no straightforward architectural foundation for GPT-2 as we know it.
Maybe OpenAI would have built some other path eventually.
Maybe the field would have discovered a similar breakthrough through a different line of work.
But the GPT-2 that actually happened, when it happened, and how it happened, is inseparable from the Transformer.

That is just the technical truth.


The Transformer did something more important than improve models

The biggest thing Google gave the industry was not merely a better model block.
It gave the industry a scaling primitive.

That sounds dry, but it is the whole story.

The AI industry today is defined by a few recurring ideas:

  • pretraining at large scale
  • transfer of general capability into downstream tasks
  • parameter growth
  • context-window expansion
  • foundation models as platform assets
  • model families with derivative products, tools, and APIs

All of that became much more viable because the Transformer architecture matched the industrial reality of training large systems on serious hardware.

That is why its influence extends so far beyond NLP papers.

The Transformer did not merely improve one subfield.
It helped create the modern operating model for AI companies.


Why this shaped the industry so deeply

The reason the Transformer shaped the entire industry is simple:

it connected research progress to economic scale.

That is what wins.
Not just cleverness.
Not just novelty.
Not just benchmark gains.

The winning architecture is usually the one that makes the next order of magnitude possible.

Transformers made it easier to imagine:

  • larger language models
  • broader pretraining corpora
  • reusable model backbones
  • generalized text generation
  • eventually multimodal systems built on related scaling logic

Once that happened, the center of gravity changed.
The industry stopped thinking in terms of narrow task-specific systems and started thinking in terms of large trainable model families.

That shift is still the water we are swimming in.

You can argue about whether the current generation of AI products is overhyped, overcapitalized, or overmarketed.
I make that argument all the time.
But the architectural break itself was real.

And Google triggered it.


This is one of the great ironies of AI history

One of the funniest parts of the whole story is that Google created one of the most important technical foundations of the generative AI boom, and then for a while let the market narrative get captured by everyone else.

That is an extraordinary industrial fumble.

Researchers at Google helped create the architecture that underlies the most important AI platform shift in years.
Then OpenAI became the popular face of the revolution.
Then the rest of the industry ran around trying to catch up in public, even while depending on the same architectural lineage.

That is not a criticism of the Transformer.
If anything, it proves how foundational it was.
Once an idea is that powerful, it stops belonging to one company in the practical sense.
It becomes infrastructure for an era.

That is exactly what happened.


GPT-2 was one of the first public proofs of what the architecture unlocked

GPT-2 matters because it was one of the first large public demonstrations of what a Transformer-based generative system could look like when pushed hard enough.

It was not the final form.
It was not the most advanced model by today’s standards.
But it was one of the moments when the broader industry could no longer pretend this line of research was marginal.

People saw coherent text generation at a level that changed expectations.
Developers, founders, investors, media, and eventually platform teams all started recalibrating.

That is why saying “GPT-2 would not be possible without Transformers” is not rhetorical exaggeration.
It is just a concise summary of the dependency chain.

Google created the architectural breakthrough.
OpenAI used that breakthrough to push generative language modeling into a new public phase.
Then the rest of the industry reorganized around the consequences.


My take

If you want to understand why the AI industry looks the way it does now, you have to stop treating products as the primary story and start treating architectures as the primary story.

ChatGPT was a product event.
GPT-2 was an early capability event.
The Transformer was the deeper industry event.

That is the layer that changed the shape of the map.

Without Google’s Transformer paper, there is no clean path to GPT-2 as we know it.
Without that path, there is no similar acceleration in large-scale generative language modeling.
And without that acceleration, the current AI industry probably looks slower, messier, and far less unified around the same technical backbone.

So yes, OpenAI deserves credit for what it built.
But the underlying architecture that made that path real came from Google research.

The industry loves to celebrate whoever ships the loudest product.
It is worse at remembering who changed the underlying physics.

In this case, the underlying physics changed in 2017.
And the rest of the AI industry has been compounding that decision ever since.