HNHacker News
TopNewBestAskShowJobs

anonyfuss

159 karma · joined April 27, 2013

submissionscomments
anonyfuss··on Results of the Debian systemd survey
That's the way Mac OS X is written. They certainly haven't bundled the entire universe into a single master "system daemon" project.

A few, off the top of my head:

configd: A configuration store that handles storing (and monitoring changes to) configuration. It supports arbitrary plugins, such that other dependent systems can inject their own implementation code if necessary. It depends on kernel notification APIs and network notification APIs that are implemented at a different level.

launchd: Starting/stopping/restarting services, on-demand and on a schedule, per-user and system-wide.

diskarbitrationd: Handles mounting/unmounting of file systems, and notifies clients of changes to mounted file systems.

opendirectoryd: Handles namespacing of local and remote user/data directories. This includes LDAP, local user accounts, etc.

mDNSResponder: Used to be just the mdns daemon, now handles all name resolution and local caching.

All of these things have been iterated on independently over time, are loosely coupled with each other, and do not create tight bindings between Mac OS X and open source software, nor do they require huge non-portable changes to open-source software.

The precursor to opendirectoryd was netinfo, which also used to handle name resolution and caching. Later releases of Mac OS X moved name resolution into directory services, and then eventually into mDNSResponder. launchd replaced system starter (similar to initd/rc), cron, and a number of other services, but maintained 'perfect' backwards compatibility with the standard configuration file formats (eg, crontab(5)).

These are just a few of the (independently maintained, internally) projects/daemons that Mac OS X layers together to produce the desktop. You don't need a huge monolthic project to tackle all these problem domains, as evidenced by the fact that Mac OS X works.

You also benefit from laying these projects cleanly, as it allows them to tackle what they're good at, provide a stable interface, or even be swapped out entirely later.

anonyfuss··on Principles of Flat Design
> I disagree, people say my flat designs look great.

Lots of people would also say otherwise, simply by virtue of them being flat. They look like stunted half designs, lacking the the visual cues and polish that make application UX intuitive and understandable.

anonyfuss··on Results of the Debian systemd survey
D-bus isn't a software architecture and doesn't somehow magically make systemd more maintainable.
anonyfuss··on Results of the Debian systemd survey
> The opposite is true: Abundant use of #ifdefs makes for unmaintainable and brittle software.

False dichotomy; simply don't make abundant use of #ifdefs.

Most large, portable projects don't use #ifdefs across the codebase. They abstract the core concepts out into interfaces that can be implemented atop different APIs, and then maintain distinct implementations where necessary.

The advantage is that this also insulates you from changes to the underlying system APIs, creates testable code, and provides clean well-defined points of interaction between subsystems.

anonyfuss··on Results of the Debian systemd survey
footnote: because the maintainer (Lennart Poettering) is religiously anti-portability.

This is a shame, because it makes for brittle software, even when targeting the same platform where APIs do shift and improve over time.

To quote:

> In fact, the way I see things the Linux API has been taking the role of the POSIX API and Linux is the focal point of all Free Software development. Due to that I can only recommend developers to try to hack with only Linux in mind and experience the freedom and the opportunities this offers you. So, get yourself a copy of The Linux Programming Interface, ignore everything it says about POSIX compatibility and hack away your amazing Linux software. It's quite relieving!

I find this to be extremely cringe-worthy; I can only hope that a Linux monoculture isn't the future of open source development.

anonyfuss··on Bike Share Program Opens in New York City After Long Delay
> I actually prefer biking fast in NYC.

I've found this to be very dangerous, because other bicyclists simply do not obey traffic laws.

For example: they regularly run red lights, which makes approaching intersections at-speed dangerous for both parties. I was nearly hit on one occasion (the other cyclist skidded out and set his bike down) while I had a clear green light.

After that (and a few other incidents), I stopped riding fast in Manhattan. I'd love to see strict and brutal enforcement of traffic laws to curb people's antisocial bicycle behavior, but I doubt we will.

anonyfuss··on Principles of Flat Design
As far as I can tell, this is the real argument behind flat design -- that developers who aren't designers can produce something they think looks good and works well.

It doesn't. You still need a designer.

anonyfuss··on The Mozilla Manifesto
There's a reason even 'God' wouldn't dare -- pdf.js is slow, buggy, and incomplete.
anonyfuss··on What's the difference between 'git pull' and 'git fetch'?
> Four, basic concepts. Why is this difficult?

Because it's 3 more concepts than most people need.

A simple remote repository, coupled with a working copy, is easy to understand (and also all that most people really need).

You commit, you update. The only local divergences are the changes you haven't committed yet. In my experience, almost anyone can understand this semi-intuitively, and they only start getting confused when they hit merge conflicts.

Git, however, introduces considerable more state that a user must understand. There is local working copy state. There is local repository state. There is remote repository state. There is other people's remote repository state. Those states can become in conflict with one another, which means that there are quite a few more places to hit conflicts, and lots of sharp edges in the tool (git) with which you'd resolve them.

That's a lot of state, and it's state that most people don't actually need; it incurs a lot of mental overhead, even for people that understand how it works -- as evidenced by the fact that we're even having this conversation and two of you are debating how the index works.

The fact that this is git's default operating mode means that git is a bit like using a thermonuclear weapon to cook your breakfast, when most of the time, a simple gas stove would do. The tool was built for Linux, where it was designed to handle competing, divergent organizations, all of whom maintain long-term ongoing forks, with existing political and technical disagreements, divergent code bases and divergent ideas of stability and support requirements, all of whom are independently and concurrently maintaining, sharing, and rejecting patch sets across the graph of organizations participating in Linux development.

It's a huge, complicated, expensive, and messy development process, and it's nothing like what most organizations and projects need to support as their default mode of operation.

The problem isn't the people, the problem is that the tool is too damn complicated.

anonyfuss··on The terrifying rise of the political entrepreneur
Losing 1-3 years of career development by working at a failed startup with other 20-somethings from whom you have nothing to learn is a very expensive career choice -- unless we do actually live in a bubble of vapid startups in which actually being good at your job (whether it's programming, business development, or otherwise) doesn't actually matter.

That's not even factoring in the broader opportunity costs, actual cash outlay, etc.

anonyfuss··on Stop Validating Email Addresses With Your Complex Regex
In that case, I wouldn't say it's a particularly useful anecdote for anyone else.
anonyfuss··on Stop Validating Email Addresses With Your Complex Regex
At which point the legit sender does what -- replace their MtA? More likely they just contact thir receipient out-of-band (eg; gmail) and avoid your over-zealous mta.

Whether you think you're 'Throwing away' is just semantics. From a user's perspective that's exactly what you're doing.

anonyfuss··on Stop Validating Email Addresses With Your Complex Regex
I got a response in 55ms. We must have different definitions of 'slow'.
anonyfuss··on The terrifying rise of the political entrepreneur
> The failed founders are adults who walk into the project with risks understood.

Most of the YC founders are barely out of college.

> However the ones who fail wind up with invaluable experience, an excellent item on the resume, and a network of connections to help them either try again or get a job.

I'm curious, have you looked into "where are they now" for YC startups? eg, http://venturebeat.com/2012/03/27/y-combinator-demo-day-marc...

You're really just pushing the startup religion; that somehow inexperienced people who failed at getting traction now have a resume bullet point and a great network?

If that's true, then it just lends credence to the original article's point that we've replaced quantifiable quality with politics.

anonyfuss··on Stop Validating Email Addresses With Your Complex Regex
> It's still a good sign of a badly written bulk mail engine, and worth rejecting for.

No, it might be worth scoring the e-mail with a spam filter, but the MTA shouldn't be overzealously throwing away e-mail.

anonyfuss··on Stop Validating Email Addresses With Your Complex Regex
> The time you spend doing it the right way will reduce your conversion rate because people will view your site as slow.

During all those new account registrations they're constantly making?

Does this feel slow to you? https://www.emailitin.com/email_validator

> In this case worse is better.

No, it's not. Every time you exclude a valid e-mail address, you lose or annoy a customer for no reason other than your own lack of understanding of the RFCs.

There are a number of steps that can be taken that don't involve broken regexps that filter out valid addresses. Please stop trying to justify doing it completely incorrectly.

anonyfuss··on Stop Validating Email Addresses With Your Complex Regex
> Yes! Great Comic Book Guy impression.

In that case, great junior engineer impression on your part.

Pedantry matters in complex interoperable systems, because otherwise they're not interoperable. This is why we have detailed standards documents on e-mail address formats.

> I would certainly agree with the idea that you not force people, but a nudge is probably going to save you money in increased user retention and fewer support hassles.

A 'nudge' isn't going to come from yet-another-broken-email-validation regexp. There's no need for an 80/20 solution; this just isn't that hard.

> † - I once had a person ask why their emails to http://somesite.com were failing.

That's not a valid e-mail address (as per RFC822).

anonyfuss··on Stop Validating Email Addresses With Your Complex Regex
> Hopefully that's not the SMTP syntax you're actually using.

I typed it out live. I'm not an SMTP client and I don't have the RFCs memorized.

> I'd reject (give you a 5xx) that from my mail server for those reasons alone.

Postfix accepts it. I haven't checked the RFC to verify your concerns, but assuming they're correct, then my expectation is that postfix is liberal in what it accepts because A) it's a good idea, and B) a real mail transfer agent probably ignored those two minimal rules at some point in the past.

anonyfuss··on Stop Validating Email Addresses With Your Complex Regex
Again, what material difference does it make to you?

Overzealously rejecting valid addresses is an application of subjective and inaccurate ideas about what addresses 'should' look like, and ignores the simple fact we've already mutually and formally defined valid address formats via the IETF RFCs.

anonyfuss··on Stop Validating Email Addresses With Your Complex Regex
So in addition, 'spell check' for likely domains. People probably don't mean to type 'gmale.com' -- but don't prevent them from doing so, if that's what they really meant.
anonyfuss··on Stop Validating Email Addresses With Your Complex Regex
Why does it matter? If I managed to acquire the 8.8.8.0/24 netblock, I might very well want to use 'user@8.8.8.8' as my e-mail address.

I don't see why it has any material affect on someone requesting e-mail addresses: if it's valid, then it's valid.

This seems to be an example of the misplaced sense of propriety with which people approach validating e-mail addresses -- that somehow, your job isn't just to help the user enter an address, but also to define what is and is not 'reasonable'.

Imagine if companies refused to accept "1 Infinite Loop" as a street address because it's clearly ridiculous. Except that it's Apple's actual street address.

anonyfuss··on Stop Validating Email Addresses With Your Complex Regex
I think it's great advice; remember, the advice is: Stop Validating Email Addresses __With Your Complex Regex__. Remember that new TLDs are added, and that john@tld can actually be entirely valid.

If you want to prevent "john@gmail", then use a real RFC-compliant e-mail address parser, and attempt to resolve the domain component MX/A records (and remember, it might be an IP address).

If that fails (or your regex fails, or whatever validation you use), ____SUGGEST____ to the user that the address appears to be invalid. There's no reason for an overzealous registration form to refuse to accept the user's actual e-mail address.

anonyfuss··on Stop Validating Email Addresses With Your Complex Regex
1) Because the solutions actually prevent some users from typing their actual e-mail address.

2) There are so many ways to get the e-mail address wrong that it's almost not worth bothering validating the few things that you can validate.

Now, here's what would be an interesting validation method that doesn't actually require sending an e-mail. It requires an RFC-compliant e-mail parser, not a regexp:

- Perform A/MX lookups on the domain part. The domain part can be an IP address, so those get a free pass.

- Connect to the returned MX, issue a MAIL FROM+RCPT TO:

  c> MAIL FROM: test@example.org
  s> 250 2.1.0 Ok
  c> RCPT TO: is_address_valid@example.com
  s> 554 5.7.1 <is_address_valid@example.com>: Relay access denied
  c> RSET [reset the transaction, no e-mail is sent]
- If you get back a permanent 5xx error, the address is invalid. If you get back a 250 Ok, the address is probably valid (it could still be a relay that allows backscatter, in which case it will allow any address on one of its configured domains). If you receive a 4xx, the address may or may not be valid -- graylisters will send 4xx, as will servers that can't currently accept e-mail, etc.

This gives you definitive failure (5xx) and almost-definitive success (250 Ok). It's a cheap DNS lookup + TCP connection that you can begin performing immediately and asynchronously when a user enters their address in a form.

... or just send the user an activation e-mail.

anonyfuss··on Stop Validating Email Addresses With Your Complex Regex
> What is so special about parsing email addresses that makes everyone invent their own solution - regex or otherwise?

A valid email address can contain almost anything; this makes validation via a standard parser mostly useless. As such, devlopers reach for stricter parsers out of a combination of a not comprehending the standards, feeling vague discomfort about letting 'just anything' past data validation, and misplaced concern for users that they believe can't type their own e-mail address.

Add to that the occasional business complaint from the marketing arm about bogus e-mail addresses, and you have people repeatedly solving the problem in slightly different ways, justifying their own divergences from the standard by applying the justification that nobody will use a 'weird' address anyway, and they're actually being helpful.

anonyfuss··on The terrifying rise of the political entrepreneur
You've bought into the startup porn a little too much. YC is a startup mill -- they make a TINY investment, and it doesn't matter if most of them fail. The failed founders make a HUGE investment, and its on their head that the majority of the cost of failure sits.

YC floats on a bubble of spit and polish and politics. They want people like you to buy into it, because they need to take advantage of people like you.

anonyfuss··on A Change to Google Code Download Service
People do publish open-source developer tools -- for developers. They even publish binaries for those developers.
anonyfuss··on A Change to Google Code Download Service
Not everything belongs in a distribution. You have a short-sighted view of what open source is and how people consume it.
anonyfuss··on Instant Messaging for Teams
Non-installable remotely hosted web services aren't usually considered 'enterprise grade'.
anonyfuss··on Show HN: FlatUIKit - Flat UI components for iOS
So your suggestion for propagating 35 years of community norms that have made Mac OS, Mac OS X and iOS successful is to not say anything when newcomers ignore those norms?
anonyfuss··on Show HN: FlatUIKit - Flat UI components for iOS
> The project only makes it easy to generate and integrate flat images into these controls. You make it sound like he is rewriting UIKit.

What does 'native UI element' mean if you're swapping out all the bitmaps and completely changing the visual language, and ALL UIKit elements must be significantly modified to fit into your new language?

← PreviousPage 2 of 3Next →