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

推荐订阅源

Microsoft Azure Blog
Microsoft Azure Blog
Engineering at Meta
Engineering at Meta
A
About on SuperTechFans
T
The Blog of Author Tim Ferriss
I
InfoQ
博客园_首页
G
Google Developers Blog
爱范儿
爱范儿
Last Week in AI
Last Week in AI
量子位
阮一峰的网络日志
阮一峰的网络日志
雷峰网
雷峰网
酷 壳 – CoolShell
酷 壳 – CoolShell
Vercel News
Vercel News
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
GbyAI
GbyAI
月光博客
月光博客
The GitHub Blog
The GitHub Blog
V
Visual Studio Blog
N
Netflix TechBlog - Medium
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园 - 司徒正美
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 聂微东

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
Every learning app is designed to addict you. I built the...
Stilyan Stoy · 2026-05-10 · via DEV Community

Every learning platform I have ever used was built to need me back.

Duolingo needs me to maintain a streak. Coursera needs me to stay enrolled. Khan Academy needs me to keep clicking. The product only works if I keep returning. That is not education. That is retention engineering acting as education.

Aether is built on the opposite premise. Open it. Study. Close it. Come back when you want to, not when an algorithm decides you should.

What it is

Aether is a free, open-source learning platform. Fully static React/Vite. No backend. No accounts. No streaks. No notifications. Progress lives in IndexedDB -- on your machine, not a server. Drop the dist/ behind any web server and it runs. A Raspberry Pi, a $5 VPS, Cloudflare Pages. No database to configure. No auth to set up. No container stack unless you want one.

It currently has:

  • Classical Mechanics in full -- Newtonian through Hamiltonian, LaTeX throughout, problem sets, FSRS-scheduled review
  • Arithmetic with interactive manipulatives
  • German A1
  • FSRS spaced repetition running entirely in the browser
  • KaTeX for math rendering

Why the architecture matters

The backend is where dark patterns live. Streaks require a server to track them. Push notifications require a server to schedule them. Engagement metrics require a server to collect them. Remove the server and you remove the mechanism for all of it -- not as a policy, but structurally.

This cannot be walked back by a future contributor adding "just one feature." There is no server to add it to.


What is missing - and why that is the point

Three subjects exist. The architecture handles any subject in any language.

The subject you know best is not in it yet. The feature you would want is not in it yet. Both belong here, and neither requires a product manager to approve them.

Content is Markdown with LaTeX. If you can write about a subject, you can add it. No React required. No build tooling knowledge required. Open a file, write, submit a PR.

If you are a developer: the codebase is solo-built. Someone better at React than me will see things I missed. The architecture is intentional but not infallible. Issues and PRs are open.

If you care about what does NOT get added -- streaks, accounts, notifications, social features -- that line is written into the contribution guide. If you want to be one of the people who holds it, you can be.


The only ask

Use it. If something feels wrong, name it. If a subject is missing, add it. If the code has a problem, open an issue.

The version of this platform that is actually useful to most people does not exist yet. It gets built by the people who know what is missing.

Link of the repo