They call it a feature to create unique, random email addresses.... Email Addresses are for two-way communication.
If I tell you here is a device you use for instant messages. And you ask me, hey how do I send someone a message using this device? I tell you, you can't. That's because you are holding a PAGER.
There are limitations to sending email itself when using HME. You need to be using an iCloud Mail account only (i.e. email with @icloud.com). This is like saying if you want to be using HME, abandon your current mail provider and come into the Apple ecosystem.
Even after doing that, if you try to add another recipient, it complains that HME can be used only with 1 recipient. I tested this out on icloud.com/mail
Another case is lets say if we don't have forwarding email set to an @icloud.com email, which is the normal usecase everybody probably uses this feature. Their primary email address is either Gmail or Hotmail or whatever. In this, if i set another recipient, the mail contents will probably reach [email protected] but I am not sure if it will reach [email protected] because the iCloud MAILER would probably complain the same 1 recipient thing and cause email failure.
Just look at all this complexity & for what? I assume you asked this like a hack to get it working. Even if the email worked, now I have to convince business.com that I am the same user that you have registered as [email protected]. What business out there is going to entertain such kind of thing?
And the thing talks back to you, hello Bob, please tell me where do you want to go?
Now you are not mad at it. You will happily tell it to take you to the nearest AMC to catch your film. Because its a robotic, self driving car. No car salesman is selling you a futuristic self driving car by calling it a car.
Apple clearly sold this feature by saying its creating a unique email addresses for every use. Email addresses allow you to send and receive emails. You can't do that, you don't call it that, you call it something else. Simple.
This post is a shocking realisation of a simple bug in Apple's Hide My Email(HME) feature. You simply cannot send an email.Since Apple has done the marketing as such that with a click of a button, it will create a unique email address for any business you want to sign up with, I doubt many would think twice because its all so simple and Apple way of a solution, sure, why not, let's use HME...
If you don't have a lot of experience, you will learn it with time. Check out 48 Laws of Power. Your work also is not everything you have. It doesn't define you.
Criticisms are also not easy to hear because people don't know to give it well. Many times it could be personal. You can differentiate it by how its being framed, is it a comment on you or your work.
Hey Joe, your have become really lazy with your PRs vs Hey Joe, you have repeatedly submitted change requests that don't have good test coverage and have not been able to meet deadlines and it has been slowing down team velocity.
Maybe also consider a change of workplace if you want to start fresh. Going to gym and staying healthy helps too.
I doubt if majority of people would sit down to say "The pleasure of Busby's company is what I most enjoy. He put a tack on Miss Yancy's chair, when she called him a horrible boy." to even try out this feature
Understand all that and create an app for me that does the work X.
here is where one gets into trouble, reading functional code. while it may look better when you write it, try reading your own code after a few weeks. you will appreciate it much more when your control flow in a significantly large enterprise application is through bunch of ifs and imperative loops than scattered across various functions and operators.
another problem, debugging. when your inputs cross various function boundaries, no matter how smart IDEs you have, you end up messing around adding impurities to your pure functions and adding watches with conditions all over the place.
lastly, all that lux code does hide a significant problem. Performance. I don't know about javascript but all those temporary objects one keeps creating for the pursuit of statelessness is maddening. i don't know if there is anything characteristically different about a language like Haskell which handles this problem. Does it end up creating new objects every time for e.g. a map is called like in this example to update all the attributes?
sorry, I couldn't read the article without solving the question of energy cycle in my mind. renewable sources like solar, wind are kind of taking energy from outside, so in case of geo-thermal, if we keep using that, there is nothing thats balancing the equation.