tuldia
I don't understand why so much frustration coming against owning your own stuff.
EDIT:
> When someone decides to run a persistent brute force attack from a botnet, eating up 100% of your CPU and you have no meaningful ways to block it.
postscreen? http://www.postfix.org/POSTSCREEN_README.html
BTW, there is soo much FUD in your comment, check http://www.postfix.org/ before claiming "someone will hack your email"
""" First of all, thank you for your interest in the Postfix project.
What is Postfix? It is Wietse Venema's mail server that started life at IBM research as an alternative to the widely-used Sendmail program. Now at Google, Wietse continues to support Postfix.
Postfix attempts to be fast, easy to administer, and secure. """
EDIT: go check it out :-) https://www.rainloop.net/
EDIT 2: I don't understand why other comments are so agressive against the author for sharing how he runs his own mail server, I'm not sure if it comes from one's frustration, failures, unreasonable expectations about email, but I noticed that everything related to servers or email receives this hate (here on HN, eh?). Come on, let's start a new year where we appreciate someone sharing their experience in running a mail server :-)
Happy Holidays!
That is simple not true, you have to adapt your application to be multi region aware to start with, and if you do that on AWS you are basically locked-in, and one of the most expensive cloud providers out there.
It is naive to assume people bashing AWS are uncapable to running things better, cheaper, faster, across many other vendors, on-prem, colocation or what not.
> Outrage is the easy response.
That is what made AWS get the marketshare it has now in the first place, the easy responses.
The main selling point of AWS in the beginning was "how easy is to sping a virtual machine". After basically every layman started recommending AWS and we flocked there, AWS started making things more complex than it should. Was that to make harder to get out of it? IDK.
> Empathy and learning is the valuable one.
When you run your infrastructure and something fails and you are not transparent, your users will bash you, independently who you are.
And that was another "easy response" used to drive companies towards AWS. We developers were echoing that "having a infrastructure team or person is not necessary", etc.
Now we are stuck in this learned helplessness where every outage is a complete disaster in terms of transparency, multiple services failing, even for multi-region and multi-az customers, we saying "this service here is also not working" and AWS simple states that service was fine, not affected, up and running.
If it was a sysadmin doing that, people will be asking for his/her neck with pitchforks.
Don't miss the point of being able to do something about it instead of multi hours outage and being in the dark regarding what is going on.
Heck, if that was even possible... "everything is green" dashboards... :-)
Not to mention the amount of garbage in the cloud, the constant learned helplessness that we have to endure even knowing that the situation could have been avoided or even mitigated/solved if the access to the box was possible.
The status-quo of the cloud is uninspiring to say the least...
We used to have that, some companies still have the capability and know-how to build and run infrastructure that is reliable, distributed across many hosting providers before "cloud" became the "norm", but it goes along with "use or lose it".
Yes, that is in the context of a giant and very successful team using this approach, believe or not. :)
I get all my dependencies from Debian and they all work, when I need something that is not yet packaged, I use pip.
What are people doing to get all this issues? I don't understand...
Global state is global state.
The enemy is your own mind.
Oh, the classic "There is one administrator" falacy.
> kubernatis if you feel fancy
I hear this mindset about kubernetes very often from people who can do some stuff with, but don't get infrastructure at all.
EDIT: thinking that a regular dev can do what an admin does is simply naive.
Thanks for your hard work, Greg!
This is the regex used in the watch file for Debian to fetch new upstream tarballs: http://www.kernel.org/pub/linux/utils/boot/dracut/dracut-([\...
\time -v ls
to skip the builtin version.Programming is about paying the bare minimum attention to the details.
> [...] two methods of accomplishing the same thing [...]
Absolutelly not.
one prints:
72000000 hello
72000000 world
the other hello 72000000
world 72000000
Now try both examples against a file with more than one column to understand what I'm talking about ;)Heck, forget about RAM, the output of both programs don't even match.
That awk is pretty efficient and fast is no surprise ;)
Now that I saw tingletech comment I got your point :)
Please, "huge waste"? How do you sort something that does not fit in memory?