Hacker News new | past | comments | ask | show | jobs | submit | lowboy's comments login

I’ve been Colemak for 11 years.

For quick things (<5 min) I can still type decently on QWERTY.

For longer I just set the OS to Colemak and then back again when I’m done. Win/Mac has Colemak and Dvorak built in. I hope most linux distros do as well.

Assuming you don’t need to look at the keys.


This has great discoverability for other eng teams ime. Duplication of components across multiple product teams is a drag on velocity and a major pain when you want to update brand/design across the board. In a previous role, we spun up a Storybook with the few dozen atomic React + pure HTML components, shopped it around the relevant teams. Saw great uptake for centralizing components, and a few teams did storybook-driven development for their more complex UIs. Can recommend.

Also very useful for non technical stakeholders (design, product, etc) to test UIs in isolation.


Can you expand on how it was hijacked?


The checkbox label is often my thumb’s target. A pox on the house of any dev who doesn’t properly use a _for_ attribute.


When they first got started, booking a cab was:

1. Pick a cab company, look up phone number. 2. Phone, usually get a dispatcher but sometimes busy signal. 3. Tell them where you are. 4. Get very loose estimate on pickup time. 5. Wait with no updates. 6. Most of the time cab comes, if it doesn’t, GOTO step 1 by phoning back or trying another company.

Compared to 1. Open app. 2. Hit button. 3. “Real time” updates on car location and estimated time

I don’t like the gig economy model and I don’t use Uber and still use cabs, but I can see the appeal.


Yeah, where I grew up it was even worse. The main nearby company constantly had multiple cabs parked and people idling for huge amounts of time, but they demanded at least 24 hour notice and a 3 hour pickup window regardless of the time. For trips taking ~10 minutes.

I'm honestly surprised they still exist. I have no idea whose money is keeping them in business.


if you're of certain minority groups, the cab experience was:

1. Go outside

2. Put your hand up

3. Never get a taxi

> Most of the time cab come

This got really bad in many cities because of a cycle: If the rate of dispatched cabs get low enough, people make multiple requests to the dispatchers, so more than one cab would go to the spot, and you take whichever cab gets there first and the rest are "dropped". So the other cabs can't service dispatch requests, the servicing rate drops, so that further incentivises multiple request...


I'm sure it's worse for minorities, but "cab supposedly dispatched but never shows" is definitely not a rare experience even with maximum privilege in play.


I didn't mean to suggest that the two phenomena were connected, sorry!


Not in NYC where the article takes place


Out of interest, which bit of the flow they described is different in NYC?

It was similar to that in London 10 years ago - the most 'fun' thing used to be booking a cab for an airport drop - would they turn up at 3am as planned? If not, what will you do - as their office may now be closed... I ended up nearly stuck at the airport one night after my booked cab (pre paid!) didn't turn up, so had to get a black cab at twice the cost, and only after I convinced him I had the cash at home, as I didn't have any on my and my card had been cancelled while I was on holiday (for using the card abroad). Fun


I'm not from new york, but I think you just hail the cab down in the street, no? The described flow is what I'd have to do in atlanta to go basically anywhere.


Yeah, anyway outside of the centre of London and even there outside of peak hours, and waiting in the street for a cab can be a long wait.


6. Most of the time cab comes

It does? That's not how I remember it.


HATEOAS have always sounded like a delicious part of a healthy breakfast


My brain drops the A, so I always read it HATEOS which makes me thinks it is a joke Linux distro of some kind.


On my machine the clone has more padding and line height, which makes it easier on the eyes


This is not a good experience on a mobile device. It could likely be fixed with a few dozen bytes of inline css.

https://i.imgur.com/T5ntV2A.png


Or.

<meta name="viewport" content="width=device-width, initial-scale=1">


This looks to me like the browser failing to include a reasonable default stylesheet.


Mobile browsers have, since at least the first iPhone, defaulted to showing websites zoomed way out, on the theory that the site might not have been designed for a screen that narrow. Sites that are designed to support a phone screen are supposed to say so, using the meta tag given elsewhere in the thread.


Point of Contact


Ah, thanks (both of you). Yeah, I'd seen that before, recognise it now that you mention it. But it had completely slipped my mind, so I really couldn't fathom what skin colour had to do with this.


Audio quality is only one of the metrics for comparison, including:

- form factor (my powerbeats pro case is huge compared to airpods) - handoff between different Apple devices - BT reliability/connection strength (mostly down to BT 4 vs 5) - fit and finish - noise cancellation

People weigh all of these things differently to arrive at what is "best". If a broad range of wireless buds all meet someone's threshold for acceptable audio quality, the other factors will be deciding.


Form factor is largely a fashion parameter which is what OP is saying , it is not purely technical superiority driving buying decisions


Usability is by far the biggest factor for me when it comes to AirPods.

3 years ago, they were the first seamlessly and reliably working product to free me of the cabled ear buds mess.

Were there other bluetooth ear buds before? Yes. Were they complete and utter shit to use? Also yes.

Now, 3 years later, a few competitors arise and some are better in some ways than AirPods - but again none are better than AirPods Pro. Active noise cancellation always has a markup of around $100 no matter the brand or product. So still, these AirPods Pro are fairly priced in my opinion (AirPods + $100).

You have to actively hate on Apple for even claiming any bluetooth in-ear buds are better than AirPods Pro as of today.

Samsung etc. caught on to AirPods after 3 years - but certainly not to AirPods Pro.


Audio quality may be only one metric, but it is by far the most important. When shopping for headphones/iems you first listen to them and find the ones that sound how you like, then you compare on all other factors. I think most people who buy them do so because the marketing, not due to the experience. They know the brand and know they won't suck. Not that they are the best.


I doubt anyone I know cares about audio quality better than what airpods provide. What they care about is a device that works (I.e. pairs and has long battery life). Plus it has some neat features integrated with other Apple hardware, such as being able to listen to the audio from an Apple TV.


It isn’t by far the most important. I have numerous audiophile headphones which provide a better listening experience than AirPods, but I use AirPods almost all the time because they are with me when I need them.


"The best camera is the one you have with you" is a saying among photographers, and the same goes for headphones. Apple realised this a long time ago, and they sell both.


I, and I expect many others, mostly use them walking down the road, or around the house. And mostly for voice, not music, in my case. Audio quality certainly isn’t my main priority; comfort, battery life, and reliability are all far more important.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: