I used to feel annoyed when I'd see an e-bike while I was out riding. I'm not sure which bastion of my ego that irritation came from, but eventually I decided that more bikes (of any kind) is better than more cars, or folks just sitting at home.
I would get annoyed out of jealousy when they effortlessly accelerated from a stop, easily clearing dangerous intersections. In contrast I was using a muscle-powered bike which takes much more effort to start up from a standstill.
+1 I really do like my new Moonlander, which I purchased in November. However, as a former Kinesis Advantage user, I miss the contoured shape, I think it helped a lot with carpal pain.
That said, I'm not sure I can justify another keyboard.
Yeah, the bowl shape is absolutely the missing piece on my Moonlander. It is otherwise perfect in nearly every other way, and the flexibility from QMK is unmatched. But I don't know how you can reconcile it with its low profile; the Moonlander looks a lot nicer to throw in my bag than the 360 when you pull the wings in...
I agree; I can't justify yet another keyboard. But there's the continuous itch to go ham and design my own split contour keyboard with QMK...
(For anyone reading this, you literally can't go wrong with either of these keyboards and they'll last 10+ years, so get one if you can.)
I got a extra set of legs from ZSA (was cheaper in the Ergodox store than the Moonlander store) which allows putting the thumb pads on the desk, plus MT3 profile caps, both of which add to a somewhat a finger helping curve;
ok, could you expand on your experiences with both? i’m a longtime kinesis user (like, LONG time—i got rid of one with an AT connector a few years ago) and i’ve been really toying with the idea of switching. what are the pros and cons you’ve experienced?
Not OP but the issue for me moving from a scooped keyboard (Kinesis) to a flat one (Ergodox) was reaching the top/bottom row comfortably.
On a flat keyboard, hitting that top row (especially edge keys like the 5 and 6) required either moving my entire hand or doing some weird reaching motion. And I wear a 4XL glove so I don't even know how other people deal with the top row at all. Being able to not move your hands as much doesn't sound like a big thing but it helped a lot with my wrist issues because I can find a comfortable position when I get started and never leave it until I stand up.
I'm currently on a scooped and fully split KB from bastardkb.com which is kind of the best of both worlds (scooped for reach, split for my shoulders, and custom firmware so I can use less keys overall). But if Kinesis offers that out-of-the-box it's a pretty easy choice for my next keyboard.
I’ve used both extensively and fully switched from the Kinesis Adv2 to the Moonlander. I believe what gp is referring to is the (obvious) structural difference between the two. With the Advantage 2, your hands are largely resting on the frame of the keyboard. With the Moonlander your wrists are either poised above whatever surface you have the Moonlander on or resting directly on it. For me, and I suspect most people, that’s simply my desk. At that point the height of your arm with respect to your desk becomes very critical to avoid your wrists getting too far from a neutral position.
- QMK is second to none. With the moonlander specifically I can flash my keyboard from any OS with nothing but a browser and a paperclip.
- Tenting is easy, adjustable, and feels good to use. I liked the thumb cluster tenting (over the ergodox) because it felt more natural.
- Excellent build quality, wrist rests are comfy, and it's pretty portable (it's in my carryon bag right now).
- High quality switch and cap choices (mostly, the custom thumb buttons are obviously nonstandard. But I strongly disliked the rubber function key row of the advantage 2)
- I occasionally play FPS games, and like that I can disconnect the right half of the keyboard and gain more mousepad real estate.
Kinesis pros:
- Mainly the shape. I think the kinesis is probably the most natural device to type on. The moonlander is comfy, but I think the kinesis is still more natural overall. The sculpted key-well is ideal, IMHO.
Both keyboards have eliminated my carpal tunnel symptoms, so I don't have any issues recommending either. If you're going to travel with a keyboard, definitely get the moonlander. But I think from a pure ergonomic standpoint - the kinesis wins.
If I ever switch jobs and have a keyboard stipend, I'll purchase the Advantage 360 and write a full review. But I'm very happy with my present position :)
Recognizing that employment is a marketplace, and thus the value I can provide might be worth 5x (or more) to Company A vs Company B (even if it's a similar title or role).
A couple thoughts occurred to me as I read the post:
- Lambda functions deployed using Docker images can be up to 10GB.[1] Would that change your math here? I'm curious what the tradeoff would be vs parallelizing more function executions searching smaller datasets on both cost and performance.
- Great notes on the anti-competitive nature of the current market. If there was an open standard on crawling, maybe we'd see more innovation here.
Maybe. Based on my experiments with lambda I doubt they have enough CPU to deal with the additional space. At the current size it's bumping against the limits of lambda as is. Might be possible to switch to something like C++/Rust/C/Zig however to help with this.
Strongly agree, I've experienced this myself from both sides of the table.
The concept of "the market" for engineering talent is far more nuanced and multifaceted than the nice x/y plots used to correlate compensation and experience (not meant as a criticism to the author at all).
Plenty of people find value in things like better ads or more connectivity across sites. Tracking can imrpove some services (I let maps keep my location history) and while I always use adblocks on PC, I admit to have found interesting relevant to me stores on instagram presumably because they keep data about me.
I really nearly fainted when I saw my location history on google and now that I have a firewalled Huawei with Google forbidden on it, I finally feel a bit location-safe :D And it's not that I care that americans know where I am, it's that people can just get my phone/account, people close to me, and track me, eww.
I really am impressed you found relevant stuff on instagram, but I found that desiring less things is usually just as rewarding as getting an add for the right flavor of yoghurt.
>I really am impressed you found relevant stuff on instagram
It's mostly been small alternative-type stores, typically for clothes which I'd have never even found out about otherwise but match my aesthetic presumably because they just advertise to a niche audience like me based on the data.
I’m surprised it’s so low. These sites are used mostly for indulging in narcissism, and people who tend that direction generally prefer to have their lives be less private.
For AWS specifically, I prefer to have an AWS account specifically dedicated to each service + stage. For example, if I have an image service that handles s3 uploads (say Lambda, S3, Cloudfront and API Gateway), then I'd deploy a "test" environment to a dedicated AWS account and run tests against that. Since it's fully serverless, it only costs a few pennies to test (or free).
That means that every person who runs the tests needs credentials for that AWS account. That obviously won’t work for an open source project. Even for a company project, how do you distribute those secrets? It adds friction for developers getting their local dev environment setup.
Not only that, but you now need network access to run tests. A network blip or a third party service outage now makes your tests fail.
There is also the possibility that an aborted test run might leave state in s3 that you are now paying for. Someone hits Ctrl-c during a test run and now you have a huge AWS bill.
> That obviously won’t work for an open source project
On the contrary - I was an employee at Serverless Inc, working on the Serverless Framework for the last two years, we used this pattern extensively (and very successfully) in our open source repos.
We used part of our enterprise SaaS product to provision temporary credentials via STS and an assumable role, and it works great. You could do the same thing with something like HC Vault.
For Lambda, S3, DynamoDB, the perpetual free tier means we've never paid to run our own tests. API Gateway isn't free (after 1 year), but it's still pennies per month. We've had several cases where tests stuck around a long time, but a billing alert and occasionally some CloudFormation stack cleanup takes care of that.
We still have offline unit tests which test business logic, but everything else runs against the cloud - even our development environments ship code straight to lambda.
Speaking from personal experience, our team wasted far more money tinkering with local dev environments and trying to replicate the cloud than we ever did simply using it to develop.
The blog post in the parent comment lays out our experience and my thoughts, but because of the pretty generous free tier, I don't think we've ever paid a penny for a build/dev/test AWS account.
