My first thought was that this just looked like a modified ErgoDox. Then I saw that it is made by the same people as the ErgoDox EZ, so it makes sense. I have been using ErgoDox EZ for ~2 years and absolutely love it. It is definitely not for everyone. But if someone is looking for a highly customizable ergonomic keyboard and does not mind the learning curve or price tag, it is great.
This new keyboard looks like it has nice improvements over the ErgoDox EZ, but nothing that I read (on the first pass at leasts) seemed very revolutionary.
It is interesting that they are not offering blank keys or backlighting (as opposed to the keys being lit). I don’t know about their average user, but I have moved all of the non-alphanumeric keys to other locations/layers and therefore prefer blank keycaps.
I had the same thought on this being their own version of the EZ. The thumb cluster looks a little nicer IMO but it seems like it (the full keyboard) maybe has too many keys for my taste. The fact that it’s maybe half the height of the ergodox (by first glance, I could be way off) is really nice, and I was pleasantly surprised to see it priced in the same ballpark. Still feels pricey for a keyboard to me, but having looked at sourcing everything myself to build one I know it’s about right for being pre-built. USB-C is a very nice upgrade over the mini-usb.
I am interested in joining the indieweb community however I am finding it really hard to find a lightweight setup for self-hosting. I feel like I should be able to use a static site generator and a couple of endpoints on nginx to capture webmentions. Am I missing something? I have found it a little difficult to quickly grasp the typical scope of the indieweb.
This site seems to have a lot of resources, this is the page for nginx: https://indieweb.org/Nginx
I find leaving a notes.md or something similar open with some simple todos for the beginning of the week helpful. That way I can sit down, convince myself this one or two hour thing won’t be so bad, and before I know it I’ve loaded what I need back into my brain and can resume what I had been working on previously.
Addressing small bugs, code cleanup and code reviews are typically what I jump back in with. After attempting this enough times you start to set things aside toward the end of the week so you have them for Monday morning (obviously most of these things will be low enough priority they don’t mind the delay)
Additionally I find Monday to be great for meetings. I have to take the time to review what I was working on to talk about it which gives me time to re-assess my approach.
I’ve used Ember for years professionally on an app that I believe is pretty well suited to Embers strengths. I’ve always been happy with it, but also always taking a look at other frameworks to see how the space is evolving. Octane is a breath of fresh air I did not know I needed. I started working in Ember prior to VS Code, so development environments for web applications have come along way and I don’t think I knew what I was missing out on.
Ember pre-octane did not really support things like native classes. Everything you create was an object wrapped by a factory function. This means that IDE support for things like finding references to methods, renaming symbols, etc never worked across files. As I’ve been converting everything to use native classes suddenly I have far better refactoring capabilities (even things like ‘Peek Definition’ seem so advanced!) The Ember Community has built some excellent tooling alongside this release to allow for better syntax highlighting and auto-complete in the handlebars templates. It’s a much different feeling writing an Ember application today than it was when I started years ago.
If you haven’t written an app with Ember, I encourage you to test it out. It’s a very easy framework to write for and it gets better as you add team members and grow the codebase.
Agree here. There’s another thing I love about Ember. As a backend person, I don’t frequently (but sometimes) work in frontend. With Ember, I always roughly know my way around. It’s not like every frontend is a react+100 plugins. I can go away and come back and it’s still by and large the same.