61–70 of 152 posts
On one hand, a user base wants the old product with minimal twists and they are known to balk at anything more than that.
On the other, project survival likely depends on getting new users on board, in which case an old design and UI are probably going to be detriments.
Oh, cool. I can finally fix the bug/feature that whenever someone replied to an email from me they got warned about profanity because of my last name :-)
An architect in the Netherlands had 'Rothuizen' as his last name, which translates to 'Rotten houses', not the best name for an architect so he changed it to 'Rotshuizen', which translates as 'Houses built like rocks'. Much better :)
In your case I wouldn't change a thing.
It would be fun to port the Mac version to x86.
Wonder why they chose not to host on GitHub...
Earlier quoted context omitted.
As long as works…
What does it do?
I applaud Qualcomm for donating all trademarks and copyrights too, which means literally anyone can recompile it and still call it "Eudora". Unfortunately Eudora is basically three completely different codebases (Windows, Mac, and a rebranded Thunderbird for Linux). I guess only the Windows one is likely to ever be revived.
The difference in code bases is striking [0]: > The Windows version of Eudora is written in C++. The source tree consists of 8,651 files in 565 folders, taking up 458 MB. There are both production (“Eudora71”) and test (“Sandbox”) versions of the code. > The Macintosh version of Eudora is an entirely different code base and is written in C. The source tree consists of 1,433 files in 47 folders, taking up 69.9 MB. [0]…
Earlier quoted context omitted.
Tell that to Gmail people... Edit: https://news.ycombinator.com/item?id=16830156
Not sure how message expiry is a standards compliance issue. SMTP, MIME and RFC822 et. al. don't say anything about where, how or if the message gets stored once transmitted.
using market-influence to build massive scale expectation for a feature which can't actually be supported by the underlying protocol in an effort to 'embrace and extend' is exactly a standards compliance issue, and precisely what led to microsoft's internet explorer being labeled as an antitrust violation.
Damn. The "bad" words have been sanitized. Seeing the programmers' frustrations as they appear in the comments enhances the experience when viewing old code like this.
It's funny how in most corporate/commercial code past 2005 or 2010, you'll rarely ever see profanity in comments. I've never put profanity, or even any jokes, in comments. I really try to keep my professional code professional. Even on my own OSS projects I tend not to do that anymore.
something like "// this is fucked" is pretty darn common, even in corporate code. It gets stripped by minifiers anyhow