Hacker Newsnew | past | comments | ask | show | jobs | submit | cauterize's commentslogin

I’m partial to https://gitlab.com/simple-nixos-mailserver/nixos-mailserver

Does require some NixOS knowledge, but is nice for upgrades.


It has IPv6 support

# uname -a OpenBSD xxx 7.1 GENERIC.MP#3 amd64

# ifconfig em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 lladdr x:x:x:x:x description: xxx index 2 priority 0 llprio 3 media: Ethernet autoselect (1000baseT full-duplex) status: active inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x inet6 fe80::x:x:x%em0 prefixlen 64 scopeid 0x2 inet6 2601:x:x:x::1 prefixlen 64 pltime 301996 vltime 301996


I think he meant the website, not the OS.


I meant the website, yeah


Oops :) I was so excited for the release I forgot how to read!


No worries


The SMP improvements look interesting. Anyone know of performance results from 7.1 to 7.2?


i am also wondering about this and happen to be in the middle of testing some L2 tunneling (etherip mostly, might also test vxlan or egre) with ipsec and wireguard in a set of VM's on virtualbox.

the SMP improvements in the networking stack caught my eye and i am in the process of trying to upgrade these vm's and re-test (iperf3). if i find anything interesting i'll report back


Yes, I am most excited about SMP improvements with networking too. I run OBSD on all my edge devices so this could make life a lot cheaper.

I've been a huge fan since v4.7 and I'm glad to see the constant improvements.


I chose it due to the type system. Nearly every piece of data is optional. I need to compose these pieces of data to form a full set and apply that set of rules to a system. Haskell made a lot of things work out really well:

* embedded DSL for describing things with minimal syntax * types to enforce my invariants * immutable data + STM to protect my shared data structures * multithreaded/async code is easy to work with * deterministic outputs given inputs

but it was headaches in a lot of ways:

* exceptions - still not sure I’ve handled all exceptions gracefully * culture - most teammates are intimidated by Haskell (and types) * ecosystem is behind (Rust has exponential usb acceleration vs Haskell’s constant pace)

While I’m proud of the outcome I would have chosen differently now that I’ve seen the other side and have the project done. The inertia I was fighting required far too much energy


We failed to build Linode like things internally. We innovate through acquisition.

[ source: I was a part of those failures ]


If you don't mind sharing, how long ago was this? And do you know if the attitude is, "this is hard and we blew it, let's by an expert and learn from them" or was it, "we only failed because <excuse> let's buy a starter platform and use it as the foundation?"


A different take -- drugs. Especially marijuana and hallucinogens. Helped me better understand how to think about abstract computations vs the nitty gritty details like pointers. Not for everyone, but helped me.


Similar direction but different:

Spirituality, mysticism, religion, "alternate" non-sciency stuff, but also history. When not approached with sceptic mindset but one that tries to understand it can be very enlightening.

I think it trains to think with vague, incomplete and also contradictory thoughts (its bit similar to simulated annealing in contrast to deriving a solution analytical). On a side note, its damn interesting what our heritage has to offer.

Regularly revisit it with some scepticism so you don't get lost.

I suppose.. when logic is located in the left brain hemispere, this other stuff is located in the right hemisphere. Don't fixate on only the one side. Boost it with the help of the other one.


Then you've never been bitten by bugs in the runtime. I wait a few point releases (or when I see the runtime bugs stop being fixed) to start using a major version.


I’ll take a little more pollution over attending a drunk driving funeral


Kubernetes.


Why, if I might ask? What were your use cases? Asking as someone deciding whether or not to use it for certain projects.


Your projects are never big enough to justify kubernets unless they are.

Rule of thumb: If you can manage it alone you can manage without kubernets. If you have kubernets you can manage it alone.


I’ve never used kubernetes and only have the vaguest idea about what it does. But, in another life I used Nomad+Consul for orchestration of Docker containers and thought it was the greatest thing since sliced bread.

These days I’m all in on AWS.


FWIW, I'm keeping your name in the back of my head for when my current company inevitably fails at their big data revolution. Biggest product produces 10-15 PB/day that must be processed. Our existing solution is 20 years old and relies on navigating C code with function line counts on the orders of 10k. Rust would've saved me a lot of time from living in gdb.

Really enjoyed the article. Keep it up!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: