Skip to main content


wrote 10 years ago some code to parse some files. I did that in Go.

Now I can't rebuild it because Go broke shit. (think "modules")

I think I ran out of patience and will probably rewrite it in Rust. I mean the first version was in C++ so why not.

in reply to Hubert Figuière

Figured it out (a bit of RTFM) and now I have improved the tool.

tl;dr I used an Android app to replace paper notebooks for my film metadata. (shooting info, subject, location, date)

pro: it did GPS too, with time stamps.

cons: need to parse the format. I almost thought I had been careless and lost them

I still have 20+ year old metadata notebooks.

#believeinfilm

in reply to Hubert Figuière

It'll endure more than silly little trends like Go, Ruby, and Rust.
in reply to Hubert Figuière

Well, I mean, I just offered you a solution to what you were bellyaching about, but go ahead and persist in your inertia, I guess.
in reply to Hubert Figuière

@corruptian also I didn't ask if I should use C++. Because that wasn't even the question.
in reply to Hubert Figuière

It is, in the broader sense. You are upset because some hipster language did something stupid and broke backwards compatibility. Well that ain't the news.

Your solution is to go to the language that is consistent.

in reply to Hubert Figuière

It would be unkind to assume that you were a hipster, don't you think?
in reply to Hubert Figuière

I could never aspire to something so noble as trolling.

But you were bellyaching, and now you have an option, even if your pretense doesn't allow you to take it.