Omeka VS gleam

Omeka

Omeka (https://omeka.org/) is OSS and has a REST API. Usually used by museums/libraries, but primary function is to upload and describe media files.

Adding new features to listmonk (mailing list / newsletter manager), preparing for its next release.

https://github.com/knadh/listmonk

Setting up and playing around with Omeka, a brilliant document publishing system, to help publish an archive of digitised physical books and documents.

https://omeka.org

If you Google "COVID-19 digital archive" you can also find a range of projects with different focuses. A benefit of technology is that now many organizations can create their own Omeka site and build a collection to document events in real time. However, I hope the post above demonstrates that while anyone can, any historian utilizing these various resources need to consider the practices undertaken to gather digital archives. We would never enter a physical archive and look at paper documents without questioning why those survive, what's missing, and thinking about voices specifically left out. A digital collection is the same, however they present an abundance of sources that can distract or distort- approaching the surviving records of the Salem Witch Trials is different from approaching a collection of 40,000 personal accounts. What voices might not volunteer a personal account to a website if it requires identifying information? How many images of people in masks at the grocery store do we need to deliberately save? These are not substantially different questions from what past historians and archivists thought about, but technology does reframe discussion. We'll see how many of these projects were developed with sustainability in mind.

Yes to this and other free, open source solutions such as Omeka.

I have not tried this yet but: https://wordpress.org/plugins/diviner-archive/ Or you might look into a non-Wordpress solution like Omeka https://omeka.org/

There are some great visual archives online that might serve as inspiration. Free tools to create them include Collection Builder, Omeka, and some other free, open source repository software. Most of their sites have links to projects that people have built using their tool, and I find them super inspiring to scroll through and get ideas for projects like yours.

A popular alternative is Omeka, which can't directly be used with WordPress but does have some workarounds to effectively show the digital collection in a frame. Search the Omeka forum for more info.

Omeka (https://omeka.org/)

I haven't had time to really try to write anything in it, but https://gleam.run/ looks really good too. Like Elm for backend + frontend!

Want a friendly language for building safe systems at scale? Gleam is here for you. It features modern and familiar syntax, that's reliable and scalable. Gleam runs on an Erlang virtual machine, and can run plenty of concurrent tasks. It comes with a compiler, build tool, formatter, editor integrations, and package manager all built in so you can get started right away. Congrats to the team on shipping your first major version 🙌.

While I love Clojure, I have to agree about tooling. I recently started using Gleam* and was impressed at how easy it was to get up and running with the CLI tool. I think this is an important part of getting people to adopt a language.

* https://gleam.run/

If you use languages that compile to WASM (such as Gleam https://gleam.run), and can also run Postgres via WASM, then it opens very interesting offline scenarios with codebases which are similar on both the client and the server, for instance.

Recently, Gleam has gained more popularity, and a lot of developers (including me) are learning it. At the time of this writing, it has exceeded 14k stars on GitHub; it grew really fast for the last month.

Oh, strange that github had a date of 2016 on this one: https://github.com/gleam-lang/gleam/issues/2

I was just going by that, though I do remember checking out gleam 5 years ago or so.

Re: macros, I really do think they’re a big deal and all the other newer languages I’ve used, such as Rust have some kind of macros or powerful meta programming features.

For older languages, a few, like Ruby have enough meta programmability to make nice DSLs, but many others don’t. Given the choice, I’d much rather have Elixir/Clojure style macros than other meta-programming facilities I’ve seen so far.

I had been only following this language with some interest, I guess this was born in gitlab not sure if the creator(s) still work there. This is what I'd have wanted golang to be (albeit with GC when you do not have clear lifetimes).

But how would you differentiate yourself from https://gleam.run which can leverage the OTP, I'd be more interested if we can adapt Gleam to graalvm isolates so we can leverage the JVM ecosystem.