git404hub

what is go-at-coreos fr?

kelseyhightower/go-at-coreos — explained in plain English

Analysis updated 2026-07-17 · repo last pushed 2015-01-31

7Audience · developerComplexity · 1/5DormantSetup · easy

tl;dr

A 2015 slide deck, viewable with Go's present tool, from a FOSDEM talk about why CoreOS chose Go to build distributed computing tools.

vibe map

mindmap
  root((go-at-coreos))
    Inputs
      Go present tool
    Outputs
      Browser slide deck
    Use Cases
      Learn Go infra history
      View FOSDEM 2015 talk
    Tech Stack
      Go
      Go present tool

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

View a historical slide deck explaining why CoreOS chose Go for distributed computing tools.

VIBE 2

Learn how Go's design made coordinating work across many servers simpler in CoreOS's tooling.

VIBE 3

Understand the context behind Go's early popularity for infrastructure software.

what's the stack?

Go

how it stacks up fr

kelseyhightower/go-at-coreos0xsv1/ghosttype-bofadguardteam/ruleseditor
Stars777
LanguageCTypeScript
Last pushed2015-01-312026-07-01
MaintenanceDormantActive
Setup difficultyeasyhardeasy
Complexity1/54/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 5min

Requires Go installed locally to run the built-in present tool that serves the slides.

License is not stated in the available content.

in plain english

This repository contains a slide deck for a 2015 talk by Kelsey Hightower about how CoreOS used the Go programming language to build tools for distributed computing. Rather than being a runnable application or library, it's a presentation meant to be viewed in a browser using a specific Go tool. CoreOS was a company focused on making it easier to run software across many servers at once. The talk covers how Go was chosen as the language for their products, which aimed to make distributed computing, the complex task of coordinating work across multiple machines, as straightforward as installing a standard operating system on a single computer. To actually view the slides, you need to have Go installed on your machine. The repository uses Go's built-in "present" tool, which launches a local web server so you can read the slides in your browser. The process involves downloading the repository, navigating into the folder, and running the "present" command, which then gives you a local web address to open. The audience for this talk was developers and engineers attending FOSDEM 2015, a European open source conference. Someone might look at this today to understand the historical context of why Go became popular for infrastructure tools, or to learn how CoreOS thought about building distributed systems at that point in time. The README doesn't go into detail about the specific topics covered in the slides or how much technical depth the presentation reaches. There's no summary of the talk's contents, so you'd need to view the slides directly to see what was discussed.

prompts (copy fr)

prompt 1
Install Go and run the present tool on go-at-coreos to view the FOSDEM 2015 slide deck in my browser.
prompt 2
Summarize the historical significance of CoreOS choosing Go for distributed computing based on this talk's context.
prompt 3
Explain how to clone go-at-coreos and launch its local web server to read the slides.

Frequently asked questions

what is go-at-coreos fr?

A 2015 slide deck, viewable with Go's present tool, from a FOSDEM talk about why CoreOS chose Go to build distributed computing tools.

Is go-at-coreos actively maintained?

Dormant — no commits in 2+ years (last push 2015-01-31).

What license does go-at-coreos use?

License is not stated in the available content.

How hard is go-at-coreos to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is go-at-coreos for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.