RDF, Typescript and Deno Part 1: motivation

So a few things I’ve been mulling over recently have come together into a, doubtless not very sensible, idea to play with some new tech. Well, new to me anyway.

First off, there’s an ongoing buzz around Vue 3, which has now reached the 3.1 release. I think some of the ideas and goals for Vue 3 are interesting, and worth exploring. I’m not yet fully conviced about the composition API (which I should write about) one day, but to be fair I’ve not really tried to build a composition-API app yet.

Then there was Ryan Dahl, the founder of Deno on the ChangeLog. I knew of Deno, but didn’t know much about it. The flaws in NodeJS that Deno wants to address are valid concerns, and the approach sounds solid.

Deno is written in TypeScript, something else I’ve been meaning to get to grips with. So I played with the first few exercise from Exercism’s TypeScript track. Exercism has long been one of my favourite ways of just getting a feel for a new language. Each problem only takes a short while, you know definitely when you’ve solved the problem (because the tests pass), and solving allows you to look at the other community solutions, which is often the most instructive part.

And finally, arising from thinking about a new project at work, I’ve wanted for a while to have a play with the RDF libs for JavaScript. While the range of libraries available for RDF-Js look reasonable, the “getting started” docs are basically MIA.

So, to the doubtless not very sensible plan: to spend some time looking at an app in the intersection of the above technologies, and blog about what I learn along the way.

Rougly speaking, my plan of attack is to start small, with just the core elements, and build outwards from there. Step 1 will be to read and write some basic RDF with a simple Typescript program.

 newer · index · older