With the Apple XS tips, which otherwise fit well for me, any yawn means the APP3 fall out.

It's already a pretty degraded experience.

(This is a joke)

I was a huge fan of Apollo and genuinely appreciate your UX design and aesthetic chops. Please make something 100% your own next time! You have the name recognition and development experience to pull it off.

I can’t wait to see what you do next. Just… please not another client for someone else’s service.

I am kicking myself that I couldn't stop at the Museum of Computing, but the family was jetlagged and really tired. Regardless of that, I considered Bletchley Park time well spent and an awesome visit.

PowerBI are their lunch because it was “free” with the rest of our Microsoft stuff, so everyone could make the shiny dashboards no one uses instead of just a few.

In some cases we just wrote our own d3-based visualizations. It was easier than dealing with the constant licensing headaches Tableau brought.

I can afford the lump sum, but it's a lot nicer to smooth out the cash flow using Apple's money instead of mine. As long as you're responsible, what's the harm?

"Even for a technological tour de force, 5K is a lot of dough. If I used it, and loved it, I’d keep it. But for discomfort, actual eye pain, looking through a periscope, and the inevitable resulting gathering-dust-in-a-corner? I’m not insane. It has to go back. I’m an early adopter, but not a throw-away-5-kilodollars early adopter."

Not all problems become evident in a carefully-curated demo at a well-lit store, either.

They're definitely not as good as the cameras on my iPhone, either.

Comments URL: https://news.ycombinator.com/item?id=39384158

Points: 70

# Comments: 204

Vendors can and do get greedy, and if you're deeply integrated with them then untangling those integrations and migrating elsewhere becomes a big job in and of itself. I've had my share of experiences where enterprise SaaS vendors try to squeeze their customers after they effectively become a single source.

I am not at all opposed to SaaS, and use it at my organization quite effectively. But you have to choose carefully. In many cases, the vendor will become a partner, and it can become a pretty abusive partnership.

On the other hand, when you own it, at least you KNOW you own it.

And this isn't even taking into account the quality of the product itself. We have vendors that, like others complain here, just delight in changing UIs and offered functionality left and right, deprecating APIs with two months' notice. We have others who behave like grownups.

Yes, UUIDs are overkill for most applications. But CPUs and hard drives are, relatively speaking, cheap. Using an existing, battle-tested unique ID library implementation has advantages. The 8 bytes per record you're saving over bigserial is, for most use cases, negligible. 1,000,000 rows? You'll save 8 MB by switching away from UUIDs.

Most databases won't be that large. Use a UUID if you want; pretend you'll have Really Big Data some day if it makes you happy. Render it using a special function if the hyphens are too ugly.