feat: add descriptions

gadomski · Oct 6, 2024 · 1152f45 · 1152f45
1 parent f74ff29
commit 1152f45
Show file tree

Hide file tree

Showing 5 changed files with 10 additions and 0 deletions.
diff --git a/content/posts/2024-09-19-FOSS4G-NA.md b/content/posts/2024-09-19-FOSS4G-NA.md
@@ -2,6 +2,7 @@
 title = "FOSS4G-NA 2024"
 slug = "foss4g-na-2024"
 date = 2024-09-19
+description = "Slides and reflections from FOSS4G-NA 2024 in St. Louis."
 
 [taxonomies]
 tags = ["rust", "stac"]

diff --git a/content/posts/2024-09-19-stac-rs-v0.10.md b/content/posts/2024-09-19-stac-rs-v0.10.md
@@ -2,6 +2,7 @@
 title = "stac-rs v0.10"
 slug = "stac-rs-v0.10.0"
 date = 2024-09-19
+description = "A new release of stac-rs that includes STAC v1.1 and stac-geoparquet support."
 
 [taxonomies]
 tags = ["rust", "stac"]

diff --git a/content/posts/2024-09-20-stacrs-v0.1.md b/content/posts/2024-09-20-stacrs-v0.1.md
@@ -2,6 +2,7 @@
 title = "Python API for stac-rs v0.1"
 slug = "stacrs-python-v0.1"
 date = 2024-09-20
+description = "The first significant release of Python bindings for stac-rs."
 
 [taxonomies]
 tags = ["python", "stac"]

diff --git a/content/posts/2024-09-26-dumb-economics-for-remote-sensing.md b/content/posts/2024-09-26-dumb-economics-for-remote-sensing.md
@@ -2,6 +2,7 @@
 title = "Let's apply dumb economics to the use of remote sensing data"
 slug = "dumb-economics-remote-sensing"
 date = 2024-09-26
+description = "The US government should build searchable indices (e.g. STAC) for their geospatial data, and it should devote resources (aka money) to helping open commercial satellite companies' archives."
 
 [taxonomies]
 tags = ["remote-sensing", "stac", "economics"]

diff --git a/content/posts/2024-10-06-rust-and-geospatial.md b/content/posts/2024-10-06-rust-and-geospatial.md
@@ -2,6 +2,7 @@
 title = "Rust and geospatial"
 slug = "rust-and-geospatial"
 date = 2024-10-06
+description = "Rust can be useful for building geospatial systems, but it's not a silver bullet."
 
 [taxonomies]
 tags = ["rust", "geospatial"]
@@ -17,6 +18,11 @@ The Python geospatial tooling stack is really strong because of mature, well-sup
 If you're doing "geo-native" work where you're opening lots of files, doing analysis, creating visualizations, stick to Python.
 Rust is better at "geo-adjacent" stuff, such as reading and writing formats, building servers, and the like.
 
+## Bindings are great
+
+The tooling to create bindings between Rust and other languages (e.g. Python, Javascript) have come a long way in the last few years.
+It's now pretty trivial to expose parts of your Rust library via functions and data structures in other languages, and this will likely be a place where we'll see significant work in the next few years. 
+
 ## Just because it's written in Rust doesn't mean it's faster
 
 A common trope is that you re-write something in Rust to make it faster.