summaryrefslogtreecommitdiff
path: root/tech
diff options
context:
space:
mode:
authorJJ2024-10-02 03:29:51 +0000
committerJJ2024-10-02 03:29:51 +0000
commit3d6149cfdf4ec1e8cfbcd4d620e75d9398772818 (patch)
treeeb48c58a8402c4fa154c3c7854567742d75c8027 /tech
parentc76437dfdc4a10780a439ed71883637114cb084d (diff)
meow
Diffstat (limited to 'tech')
-rw-r--r--tech/transit.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/tech/transit.md b/tech/transit.md
index ae21bd9..93f1d49 100644
--- a/tech/transit.md
+++ b/tech/transit.md
@@ -5,7 +5,7 @@ title: tech/transit
# Transportation Routing
-The state of transit software, particularly open-source transit software, is *atrocious*. It is a mess of mostly scattered, abandoned, half-completed projects. This is extremely weird, because a lot of people into open source are also into transit: so maybe transit apps are just hard to write and thankless to maintain? In any case, it is a bummer.
+The state of transit software, particularly open-source transit software, is *atrocious*. It is a mess of mostly scattered, abandoned, half-completed projects. This is extremely weird, because a lot of people into open source are also into transit! So maybe transit apps are just hard to write and thankless to maintain? In any case, it is a bummer.
I've collected some notes on transit information sources and transit data, for anyone looking to find a decent transit app, or looking to build one themselves. This does not include projects that I consider dead (no activity in ~2 years: API churn means these will almost certainly not function) or too specific (tooling for making maps, region-specific transit apps, etc). If you're reading this and notice any major omissions - of which there certainly are - feel free to shoot me an email.