Mining my mailbox for top email service providers

Post by akamaozu » Tue, Feb 18, 2020, 9:21 PM UTC

mrweasel wrote: post #84

akamaozu wrote: post #80

Earlier quoted context omitted.

Not all JavaScript devs. Love the language, hate the popularity of anonymous functions and non-descriptive variable names. My production code as a sample. http://designbymobi.us/wp-content/uploads/2020/02/rabbitmq-c...

Your code sort of have the same issue. Why not define a function: function someName(p1, p2) {} and then when you need it for something, like a handler, just say: handler: someName

Post by icedchai » Wed, Feb 19, 2020, 12:13 AM UTC

londons_explore wrote: post #73

I'm wondering the legality of this... The emails in your mailbox aren't yours to do with as you please - they're all still owned by their original sender, who has given you an implicit license to read them, and store them for later re-reading. You don't really have rights to datamine, aggregate, train AI on, post stats about, etc. the data in those emails. Its a violation of the rights of the original sender to do it…

Post by technion » Wed, Feb 19, 2020, 2:01 AM UTC

saagarjha wrote: post #31

Semi-related: emails can often give away more information than you might intend. At one of my previous employers, it was quite easy to get a general idea of how internal development was progressing “from the outside” by keeping track of who was testing which version of a prerelease OS via proxy of the information it would leave in the emails they sent.

Post by Marsymars » Wed, Feb 19, 2020, 2:54 AM UTC

TacticalTable wrote: post #7

It's interesting that this is missing a lot of major enterprise marketing email providers. The author clearly isn't subscribing to things like Best Buy's weekly deal email, or Target cart reminders.

Post by crooked-v » Thu, Feb 20, 2020, 12:41 AM UTC

kerkeslager wrote: post #108

crooked-v wrote: post #97

Earlier quoted context omitted.

({}).foo returning undefined is exactly what I'd expect. That's a basic part of how accessing properties in Javascript works, and wanting it to work differently is like wanting NullPointerException generation in Java to work differently. > Now imagine hundreds of lines of code and a bunch of asynchronous callbacks occur between the last two lines, and imagine what that does for your debugging experience That's what u…

> ({}).foo returning undefined is exactly what I'd expect. That's a basic part of how accessing properties in Javascript works, This is an excellent and succinct explanation of why JavaScript is a badly-designed language, and why I use better designed languages when possible. If the basic properties "work" when it makes no sense for them to work, your language is broken. > That's what using typed signatures for your…

    const a: {propertyA?: true; propertyB?: 'cats';} = {};

    // or

    /**
     * @type {object}
     * @property {true=} propertyA
     * @property {'cats'=} propertyB
     */
    const a = {};