Earlier quoted context omitted.
I still wear my Pebble every day and am not looking forward to the day when it conks out. The thing that blows me away is no one has really swooped in to replace it. I got a Pebble because I wanted an always-on screen with high battery life (I charge mine roughly once every 5 days), and I have no idea where I'm going to find one when the time comes.
Garmin watches have a week battery life and an always on display!
Ask HN: Which great products didn't succeed?
541–550 of 648 posts
Re: Ask HN: Which great products didn't succeed?
#542I miss not having a new Nexus every year given that Pixel lineup has neither lived up to be a worthy contender for the iPhone nor has it managed to appeal to the Nexus audience. Second to that is probably the void that Sunrise, Carousel and Rdio have left out. I still haven't worthy replacements to all of them.
Not that I think Google's hardware is doing a bang up job. Pixel buds are the worst headphones I've ever owned.
Re: Ask HN: Which great products didn't succeed?
#543Earlier quoted context omitted.
And the Nexus 5 phone. Lightweight, durable plastic body, good hardware, not ridiculously large... I still havent seen a spiritual successor
We had 3 different Nexus 5X phones die via a bootloop. All bought from different vendors. 100% death rate. And yes, I know there was a "fix" released last year. Didn't work for any of them. Great cheap phones other than that. Really good cameras on them.
Re: Ask HN: Which great products didn't succeed?
#544Earlier quoted context omitted.
Xmpp is a disaster, I have otp enabled and all too often messages are delivered to the wrong machine, but encrypted with a different key, so it is pure garbage and lost forever. That is on the off chance that the message is actually delivered. Trying to get omemo up and running, but some clients (pidgin) have next to no support for it, while others only support it, and it seems it is only supported on ejabberd as of…
While I agree with your pain points, I would not say XMPP that the protocol isn't any good. - Pidgin: Just take a look at their bug tracker. You will not have any problems finding tickets requesting essential features which are 6 years and older (e.g. Message Archive Management). So unless the Pidgin devs get some done I would not use their client (Gajim is a much better alternative, especially since the 1.0 release…
Re: Ask HN: Which great products didn't succeed?
#545Swype. It disappeared from my phone this week and I'm in shambles.
If it’s gone that’s one less reason to switch back to Android.
Re: Ask HN: Which great products didn't succeed?
#546Google glass. https://en.wikipedia.org/wiki/Google_Glass A pure ingenious effort to turn humans into cyborg by adding the 4th dimension of computing to their lives in a non intrusive and seamless way. I can never understand why google couldn't make it popular given that wearable tech like watches and fitness band is catching up so quickly.
Re: Ask HN: Which great products didn't succeed?
#547Earlier quoted context omitted.
I wouldn’t call it luck. Sure, the money is good, but their company is now essentially dead and should never be trusted to do anything good (just like every single thing Facebook does ends up having nefarious goals behind it).
Luck only in the sense of how early they were as a company and the premium Facebook put on them.
Re: Ask HN: Which great products didn't succeed?
#548Re: Ask HN: Which great products didn't succeed?
#549BeOS, a modern operating system that supported SMP, preemptive multitasking, and a journaling file system waaaaay before Windows 95 was even released.
BeOS was indeed great, but its first version was released a few months after Win95.
And (again on same hardware) it was if not faster, much more pleasant to the eye than most Linux distros.
Surely it needed less memory and processor power than the competitors or however felt on limited resources very "snappy".
Re: Ask HN: Which great products didn't succeed?
#550Google Wave. At work we use Slack, Email, Google Docs, etc. We’re never quite happy with how things work - what should be email vs Slack, at what point should a a Slack conversation become an email conversation to be visible to more people, when should that turn into a doc for a more formal review process, etc. We’re trialling Notion for some things and it’s good. What should be a Wiki? Whenever we have any of these…
What it would take to built a similar product now? Ten years later, the tooling and ecosystem for such complicated SPAs is much better, so it should be at least a little bit less of an effort, right?