HNHacker News
TopNewBestAskShowJobs

tuldia

183 karma · joined November 9, 2019

submissionscomments
tuldia··on Benchmarking shell pipelines and the Unix “tools” philosophy
Not explaining, trying to tell that you are comparing apples to oranges and making a conclusion based on that.

Also, you don't need to spawn a subshell nor feed sort via stdin in the first example :)

tuldia··on Benchmarking shell pipelines and the Unix “tools” philosophy
> That’s the theory but frankly the syntax is so cumbersome, irregular and needs so many googling for "easy" things like conditional, substring, etc. that I now use a real programming language if a script needs to be anything more than a list of commands without any logic (besides variables substitution).

You are basically describing modern programming.

Script Language (or scripting) is a programming language.

And about the "real" programming language you can also trap yourself googling and installing yet another library (did you read the code?) and/or reimplementing existing tools from the unix programming environment.

tuldia··on Benchmarking shell pipelines and the Unix “tools” philosophy
sed 's| no | not only |'
tuldia··on Benchmarking shell pipelines and the Unix “tools” philosophy
> [...] but they're just scripts he has on his system. Personally I'd prefer to use the ubiquitous commands that work everywhere than rely on having custom scripts on my system [...]

Is okay for one to have their own tools.

  $ f() { printf "\$%s" "$1"; }
  $ echo a b c | awk '{ print $(f 2) }'
His system is not very different from mine or yours. He just chose to combine the tools in a specific way.
tuldia··on Benchmarking shell pipelines and the Unix “tools” philosophy
This is because in the first example you are invoking two programs. The first one sort the content of the file, the second count how many lines are equal.

While in the awk example it is creating a hash table with all words and incrementing by the key and then printing.

There is no sorting plus printing may be buffered.

tuldia··on Benchmarking shell pipelines and the Unix “tools” philosophy
Thanks for this!

Another nice thing about /usr/bin/time is the --verbose flag which gives:

  Command being timed: "ls"
  User time (seconds): 0.00
  System time (seconds): 0.00
  Percent of CPU this job got: 0%
  Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.00
  Average shared text size (kbytes): 0
  Average unshared data size (kbytes): 0
  Average stack size (kbytes): 0
  Average total size (kbytes): 0
  Maximum resident set size (kbytes): 1912
  Average resident set size (kbytes): 0
  Major (requiring I/O) page faults: 0
  Minor (reclaiming a frame) page faults: 112
  Voluntary context switches: 1
  Involuntary context switches: 1
  Swaps: 0
  File system inputs: 0
  File system outputs: 0
  Socket messages sent: 0
  Socket messages received: 0
  Signals delivered: 0
  Page size (bytes): 4096
  Exit status: 0
:)
tuldia··on A serverless email server on AWS using S3 and SES
> If my name doesn’t give you a clue,I was around and developing way before AWS or hosted solutions was a thing. Being able to provision resources by writing yaml and not having to deal with the infrastructure gatekeepers is a godsend.

Take some time to learn some soft skills, just enough to be able to convince people to do stuff for you, if you are the "throw over the wall ones" I recommend to get out of your sillo and interact well with the rest of your team :)

The problem with "serverless" is this kind of attitude around it.

tuldia··on A serverless email server on AWS using S3 and SES
Thanks for the link!

Seems like a really fun project.

> I only learned about MX record priorities last night haha.

Nice!

> With Postfix, the most straightforward way to run code on receiving an email seems to be through a pipe filter.

True.

Take a look into LMTP, you may be able to "read the email" directly from your rust daemon (via unix socket or tcp) :)

tuldia··on A serverless email server on AWS using S3 and SES
You are missing the point. (the "tired responses")

No, there only very few cases, such as shaving video encoding time (the one that started all this mess around "serverless")

For majority of other cases, using "(human) resource efficient" or "time saved managing servers" to justify the use of "serverless" is a plain bogus argument, since you end up shifting (best case scenario) OR spending more (worst case) time "managing the cloud's alphabet soup".

I will not even start talking about the code base mess.

tuldia··on A serverless email server on AWS using S3 and SES
> I’ve been working on a small side project that involves processing incoming email. In particular, it’s an app that needs to do something for each email it receives from (hopefully paying!) users.

I wish you all the best! Mind if I ask for the link?

> With (1), there is no need to worry about overages, but scaling the mail server might be challenging.

Honestly, quite the opposite.

1. Duplicate your MX box.

2. Duplicate your MX record.

That is it :)

> I am writing the mail processing daemon ... in Rust...

You might like to take a look in https://github.com/mailman/mailman for ideas/inspiration. It's a great tool for processing emails too, but cannot deny I'm now curious to see how one in rust will look like.

tuldia··on A serverless email server on AWS using S3 and SES
Seems that you edit your comment quite a bit, eh?

---

> Not a single post on Hacker News can use the term "serverless" without the exact same replies being posted every time.

Indeed.

> It's as if a certain portion of the HN crowd simply cannot fathom that a new term exists and is in use, and instead resort to the same, tired responses.

If was only "a certain portion/crowd" it will have no responses at all.

I see more like:

"It's as if a certain portion of the HN crowd simply cannot fathom that servers exists and is easy to use, and instead resort to the same, tired responses."

tuldia··on A serverless email server on AWS using S3 and SES
Thanks for sharing!

Your setup seems sane and pretty close to what would be if you want to run the same thing on a single server.

It makes the code base in the original link looks like a proprietary duct tape spaghetti :P

I just recommend setup postscreen[1] and rspamd[2].

1. http://www.postfix.org/POSTSCREEN_README.html

2. https://www.rspamd.com/

tuldia··on A serverless email server on AWS using S3 and SES
> 1. Someone else maintains the software running these services, including OS upgrades, security upgrades and patches, uptime monitoring, etc.

This is the standard marketing phrase echoed to promote serverless. By experience, I don't think is valid. Packages like unattended-upgrades automates all this stuff.

Also, not being able to verify what the software is doing is scary and looks like a 10 steps backwards to me.

> 2. Since every logical component is an independent service, each scaling independently, any one single component is unlikely to become a bottle-neck while scaling. In traditional monolithic servers, you'll have to have contingency plans if you beat storage/network/CPU/RAM limits

Except when it comes with a bottle-neck by default. Running mail servers requires rather little resource.

> 3. The closest thing to this is to break up a monolithic email server into microservices and deploy them as independently scalable containers, which is a considerable engineering effort.

Why in earth? Have you seen the postfix architecture?

> Assuming this works as advertised, you can go from zero to a full blown email service for organizations with thousands of people (assuming the stated AWS limits are lifted), in record time.

I'm pretty sure one can have a up and running mail server while the "cloudformation" thingy will still be running :)

tuldia··on A serverless email server on AWS using S3 and SES
> The emails sent by your $5 VPS wouldn't stand a chance of actually being delivered to people's Gmail or Outlook mailboxes.

The emails sent from my $5 VPS arrives in Gmail's priority box :)

tuldia··on A serverless email server on AWS using S3 and SES
Indeed.

I suspect the "serverless" word was created due to the emotional appeal to a specific (majority) group that is strongly opinionated against having servers at all.

Reading from the README.md file:

  There are two major limitations with SES:

    For security reasons, AWS defaults to 200 emails sent per 24 hour period at a rate of 1 email/second. If you need to send more than that, you'll need to ask AWS to increase your limit.
    By default, you can't send emails to unverified addresses. If you'd like to be able to send (as opposed to just receiving), you'll need to reach out to AWS to remove this limitation from your account.
I see zero benefit in having complete vendor lock-in, non-sense limitations, seriously, with a $5 VPS can send at least 300 emails per minute.
tuldia··on Just Build the Product
Better raw performance, low latency, etc
tuldia··on Just Build the Product
It saddens me to see people growing a business and having to make tradeoffs due to hosting costs or trying to catch up with new tech.

My (opinionated) take on this if you are just starting a new business:

  0. Lay your foundation on something that is battle tested and well supported.
    
    Rent/buy a real computer (dedicated/root server), not cloud.
    Use software that is already included in major/stable GNU/Linux distributions.

  1. Build your stuff.
    Get used to writing things.
    Beware tech news.
tuldia··on The Bastard Operator From Hell (1999)
Indeed!

  $ curl  http://bofh.bjash.com/ -I
  HTTP/1.1 200 OK
  Content-Length: 22100
  Content-Type: text/html
  Last-Modified: Mon, 09 Sep 2019 18:36:39 GMT
  Accept-Ranges: bytes
  ETag: "916293843d67d51:0"
  Server: Microsoft-IIS/10.0
  X-Powered-By: ASP.NET
  Date: Mon, 30 Dec 2019 18:53:47 GMT
tuldia··on The Linux codebase has over 3k TODO comments, many from over a decade ago
> The Linux codebase has over 3k TODO comments, many from over a decade ago

And that is ok.

tuldia··on The Bastard Operator From Hell (1999)
For some reason it become socially acceptable to bash folks who do system administration for a living.

Seems that you are really frustrated because you had a bad experience while working with a sysadmin and I don't think it is fair to despise people who do system administration just because of that.

This is toxic, and is _not_ ok.

Sysadmins are busy people, with their own reponsibilities, tasks, etc. They are always willing to help, assuming that you know how to communicate nicelly, tell about what you want to achieve, being a humble, honest human being.

Assuming that the sysadmin profession entails helping people all the time is plain wrong. Don't abuse.

Though, even if you ask for help several times about a specific subject is very likelly you will receive useful links, docs etc to get you "unblocked".

You still have to read and try to help yourself with the new piece of knowledge that you received.

_Demanding_ to help all the time is _not_ ok.

Peace!

tuldia··on Networking Guides for Linux Sysadmins
Why?

https://www.youtube.com/watch?v=o_AIw9bGogo

tuldia··on Networking Guides for Linux Sysadmins
Here you go: https://www.lartc.org/
tuldia··on You can't just rename your IT Ops team and call it DevOps
The job description of a sysadmin always required knowing at least one interpreted and one compiled programming language.

Programming is a subset of skills within the sysadmin role.

tuldia··on Odyssey: Scalable PostgreSQL Connection Pooler
Scalable in which sense?

Assuming that this is something like pgbouncer or pgpool that sit between the client and the database, and that you have a limit of connections with the database as well as the number of client connections you can keep, what value does this adds compared with those other (more mature, battle tested, included in major distros) projects?

tuldia··on Twitter CEO Endorses DuckDuckGo
Search for:

1. "fix incorrect mayonese".

2. "fix incorrect lazagna"

and compare with:

1. "fix incorrect mayonnaise".

2. "fix incorrect lasagna"

tuldia··on Twitter CEO Endorses DuckDuckGo
Given the amount of M$ ads DDG has showing latelly does not surprises me they might be partnering with bing.
tuldia··on The Configuration Complexity Curse
The thing is, for me, configuration and code feels like two different things. It's like worrying more about the system components and their relationships than the "code" itself.

When you treat configuration as flat files your configuration becomes a 1:1 mapping of the thing you have running.

tuldia··on Debian 10.2
> Starting from www.debian.org, reading from top left to bottom right as the English language is read...

I guess you should start with the first link, the one that says "About Debian". There you can know what Debian is about and align your expectations.

If you think it works for you, then go back to www.debian.org and do a ctrl+f and type "download", there is a big button in the top right corner. It is probably what you need (amd64, netinstall).

tuldia··on Debian 10.2
I guess pretty much any tool that copies files will do that too. I like that!
tuldia··on Debian 10.2
Wifi firmwares are non-free and are not included in the official iso for a reason.

Search for "debian non-free iso" and you probably will find what you are looking for.

> ...nightmare maze of wrong links and secret knowledge.

Please, don't exaggerate.

← PreviousPage 2 of 3Next →