Hacker Newsnew | past | comments | ask | show | jobs | submit | tehdely's commentslogin

To be honest, it's disappointing that this lacks calendar and address book integration (for now). There's plenty of prior art in terms of delivering full functionality via EWS, and I'm surprised their first release is this spartan. It's not like they're trying to support MAPI or something else that would need to be reverse-engineered.

My solution 15 years ago, when I needed to support Linux users, was Thunderbird plus a middleware tool called DavMail. Something like that is probably still the best option until Thunderbird is able to deliver more full functionality. Nice to see them working on the thing, at least.


TITCR.

Hit ctrl-f and typed Meego as soon as I saw this thread, hoping I'd be the first. Alas.

The N9 was literally a vision from an alternate timeline where a mobile platform from a major manufacturer was somehow hackable, polished, and secure. Favorite phone I've ever owned and I used it until it started to malfunction.

Had a Jolla for a bit, too. It was nice to see them try to keep the basic ideas going but unfortunately it was a pain in the ass to use thanks to their decision to go with a radio that only supported GSM/EDGE in the US. Had to carry around a MiFi just to give it acceptable data service.

I think the idea with Jolla is that if Nokia ever did an about-face, they were ready to be reabsorbed and get things back on the right track. Unfortunately, though we do once again have a "Nokia", it's just another Android white label with no interest in maintaining its own leading-edge smartphone platform.


My card is die-cut. My card is foil-stamped. My card is embossed.


Is this the relevant reference?

https://x.com/goldman/status/1377437553830203395

(longer quote: "My card is die cut, my card is foil stamped, my card is embossed. It doesn’t fit in a Rolodex because it doesn’t belong in a Rolodex.").


Ex-6aer here. TypePad began as a massively multiuser Movable Type but went through a full architectural transition a few years in that made it much more like a typical, scaled-out web app.

That being said, it still had as much tech debt as any other large application, not to mention being 100% Perl, which would have made sustaining engineering pretty difficult the last few years.

The biggest issue is that people have moved on from the sort of self-publishing that it made possible. Chronological blogs have been out of fashion for over a decade. I'm sad to see this happen but not surprised.


Small nit, I worked on TypePad directly and it was very influenced by Moveable Type (and maybe some copied code) but it wasn't an instance of Moveable Type. E.g. there was never a time where you could patch TypePad with a MoveableType update. The architecture transition was primarily to stop rebuilding pages after every edit, but that also ended up being a good excuse to try to clean up a bunch of other things too.


100% correct, and there's no way I could possibly "well ackshyually" you on this, Garth.

I guess the way I look at it is TypePad began with MT's "publish-then-serve" design, but scaled way up. I agree it wasn't actually directly downstream of MT. Regardless, after Seismic and Phenotype/etc. it looked like a three-tier web app, if a bit idiosyncratic.

I do often wish we were living in 6a's (in retrospect) polly-anna view of a future where everyone self-published and built community, instead of whatever... this world is.


Useless use of cat in their example script.

This is not a serious piece of software.


Maybe the example is intended to be familiar to people who are not script experts?

(rather than an example of how to do things perfectly, according to rabid accolytes of the church of demogification?)


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

Search: