Re:Give HN: *.til.io resolves to 127.0.0.1
by sk5t on Friday November 21, 2014 @02:34PM
(#8642914)
Relying on a magical domain "just for development" is extremely careless behavior. Even assuming that these addresses always resolved to 127.0.0.1 with no interruption, slowdown, or redirection ever, do you really want to be leaking private hostnames etc. over the internet? Simply run a local DNS with forwarding, create a zone or two for your internal machines, all done. And you can even have other record types besides A and PTR...
[ Parent
| on HN ]
This kind of reminds me of "A monad is just a monoid in the category of endofunctors, what's the problem?"
Do you mean that I am understating the difficulty of running DNS on a development workstation or home network? Running secure DNS at huge scale is challenging, but a puny server to mess around with is 1/10 the challenge of almost any development chore. (Apologies if I misunderstand the comparison to monad-speak.)
I'm basically saying you're overestimating the average developer's understanding of the running of a private DNS server at all. Monoids and endofunctors aren't actually difficult either, but they're arcane knowledge that most people don't have, so any statement that relies on average developers having that knowledge is a bit unrealistic.
Basically, I'm pretty sure I could apt-get install bind, but then I would have no clue what I was doing and I'm not entirely sure what setting up a zone entails. These problems are probably all quite solvable, but without the foundational knowledge, it's not 1/10.
Re:Give HN: *.til.io resolves to 127.0.0.1
by mercer on Friday November 21, 2014 @03:13PM
(#8643156)
Oh lord, you made me read those fake histories again. They consistently tickle my funny-bone in an unusually strong way and I'm not entirely sure why exactly. Can anyone recommend more of this kind of stuff?
Re:Give HN: *.til.io resolves to 127.0.0.1
by 0942v8653 on Friday November 21, 2014 @03:42PM
(#8643272)
For anyone not getting the reference, here's the link: http://james-iry.blogspot.com/2009/05/brief-incomplete-and-m...
I thought "The C Programming Language by Brian W Kernighan & Dennis M Ritchie & HP Lovecraft" was kinda similar in flavor.
Re:Give HN: *.til.io resolves to 127.0.0.1
by troels on Friday November 21, 2014 @02:43PM
(#8642975)
Editing /etc/hosts isn't exactly rocket science. If you're a developer anyway.
Re:Give HN: *.til.io resolves to 127.0.0.1
by coolsunglasses on Friday November 21, 2014 @02:52PM
(#8643037)
> isn't exactly rocket science. If you're a developer anyway.
This applies to monads too.
sk5t was talking about setting up a private DNS server, not editing /etc/hosts.
Re:Give HN: *.til.io resolves to 127.0.0.1
by saidajigumi on Friday November 21, 2014 @09:45PM
(#8644526)
Or, as I posted elsewhere in this thread, just setup dnsmasq for a very straightforward way to wildcard an entire TLD to 127.0.0.1. See [1] for setup details on OS X, which should be easily adaptable to other *nixen.
It's significantly easier just to add a 127.0.0.1 record to your hosts file.
Re:Give HN: *.til.io resolves to 127.0.0.1
by rikkus on Friday November 21, 2014 @02:45PM
(#8642993)
AFAIK /etc/hosts doesn't support wildcards, which means you have to edit it every time you want a new virtual host.
Now, that is a serious pet peeve of mine, especially when things break later because people forgot they modified their hosts file.