kyoto VS GoatCounter

the only thing i need to do is port the htmx code to golang and then cross compile to wasm for web and then to mobile and desktop. I am currently seeing that there are other htmx style systems out there that are already written n golang. for example: https://github.com/kyoto-framework/kyoto

But this baby here https://github.com/kyoto-framework/kyoto is in the early development stages, which is a nice approach imho.

htmx requires you to return markup for specific components. So, you’ll need to maintain component template definition in two ways: embed directly into page template, and serve it as an api. IMO htmx is cool, but requires some tooling around it to simplify work. Our team is developing and using kyoto library, focused on server rendering and components approach: https://github.com/kyoto-framework/kyoto

GoatCounter — GoatCounter is an open-source web analytics platform available as a hosted service (free for non-commercial use) or self-hosted app. It aims to offer easy-to-use and meaningful privacy-friendly web analytics as an alternative to Google Analytics or Matomo. The free tier is for non-commercial use and includes unlimited sites, six months of data retention, and 100k pageviews/month.

> Not sure when GoatCounter started

"Hello, world" - arp242 committed on May 28, 2019 - 66a4d7f9b7af8dccacaf3ad8a9fb57a9f9008030 - https://github.com/arp242/goatcounter/commit/66a4d7f9b7af8dc...

Location: Ireland (Galway)

Remote: yes

Willing to relocate: yes

Technologies: Go ("Golang"), Python, Ruby, JavaScript, Linux, Unix, PostgreSQL

Résumé/CV: https://www.arp242.net/cv/cv-martintournoij

Email: [email protected]

I've been using Go as my primary language for the last seven years, although I don't overly care about the specific language and have experience with a wide variety of tools and languages such as Python, Ruby, PHP, C, JavaScript, Lua, and probably some more. While I've mainly focused on backend in the last few years, I also have written plenty of frontend code over the years, from the "pre-jQuery" days to VueJS.

In the last few years I mainly focused on GoatCounter (https://www.goatcounter.com) with the occasional contract job, but I'm keen to start working on something new for the longer term.

I've got quite a bit of code on my GitHub, so you can take a look at that if you want: https://github.com/arp242/

I suggest using analytics that you can self-host, like https://www.goatcounter.com/ and renting a cheap vm to run it on along with your blog. It is way better, you have more control and you can be sure that javascript tracking is working for 100% of people using the site since you have full control over it not getting blocked by adblockers.

I'm self-hosting GoatCounter and using it across all my websites.

Apart from controlling my data, I also have more accurate visitor statistics, as it doesn't get picked up by script blockers, unlike GA.

https://github.com/arp242/goatcounter

https://www.goatcounter.com

I first used basic google analytics but found it too invasive/heavy so I switched over to https://www.goatcounter.com/.

For comments, most solutions were also too heavy, paid or had ads, but I finally found https://giscus.app/.

So while I did add these 2 features, I'm happy with those variants that I managed to find.

Location: Ireland

Remote: yes

Willing to relocate: yes

Technologies: Go ("Golang"), Python, Ruby, JavaScript, Linux, Unix, PostgreSQL

Résumé/CV: https://www.arp242.net/cv/cv-martintournoij

Email: [email protected]

I've been using Go as my primary language for the last seven years, although I don't overly care about the specific language and have experience with a wide variety of tools and languages such as Python, Ruby, PHP, C, JavaScript, Lua, and probably some more. While I've mainly focused on backend in the last few years, I also have written plenty of frontend code over the years, from the "pre-jQuery" days to VueJS.

In the last few years I mainly focused on GoatCounter (https://www.goatcounter.com) with the occasional contract job, but I'm keen to start working on something new for the longer term.

I've got quite a bit of code on my GitHub, so you can take a look at that if you want: https://github.com/arp242/