mikecomstock

I've thought about this before, and I'm betting that a large portion of the developers on HN have too. For me it always comes back to the fact that any new language, framework, or SDK on top of an old one simply fragments the industry even more. When 10 developers come up with 10 different abstractions of 3 frameworks, you get the exact opposite of what you are trying to accomplish.

If you want everyone to use the same framework, then my advice - though somewhat impractical - is to use it, advocate for it, and contribute to the community.

I ran into this issue a few days ago too. Border-radius can also cause it. There are multiple bug reports on this already:

http://bit.ly/vbeCPM http://bit.ly/rSH6sV

Hopefully this gets fixed soon.

A good take-away from this might be "don't do two-level ACL until you have user traction".

DavicMcLaughlin says, "we were getting absolutely ridiculous user engagement..." When you are starting a site, you want as little resistance to usage as possible, and this helps with that. It makes it one step easier for people to use your site. It helps reduce the typical chicken/egg problem, or any other "it's hard to get users" problem.

Once you have the users, and security becomes more of a concern ("But security should always be a concern", yeah I know.) then you should start to think about something more secure. Until then, do all you can, within reason, to get users.

Since this post made it to the front page of HN, I'd say it's got to infuriate at least some people. That, or a large HN demographic likes the report that .NET developers are infuriated? This seems much more likely to me.

Very cool idea. I've been wanting something like this for a while, but for my own memories.

I have a pretty horrible memory, and I'd like a simple site what I can email or SMS or enter posts about things I do, or random memories from my childhood. When I get older, I'll wish I had entered them all somewhere.

Privacy would be my main concern - I'd want to permission it only to my wife and children, and maybe a few others. I'd want my data encrypted, so admins can't even see it.

Something like this would also be great for couples - documenting relationships over time and being able to look back on them later. Emails could automatically go out on a certain date every year to remind you of something that happened on that date.

Also important would be getting my memories out. If the system ever went defunct, I'd want my data emailed to me or something.

I will definitely use this if you can generalize it. I don't normally get migraines, but it would be great to correlate things like sore throats, stomach aches, fingernail ridges, skin breakouts, etc. to external factors like food, weather, and pollution.

Here's what I do:

- Almost all CSS goes in 1 big file. One line per selector to keep thinks clean and easy to find. Styles from external sources (like jQuery UI) go in separate files.

- Reset lines go at the top, if you use them, in a / RESET / section.

- Styles for individual HTML tags are next in the / HTML TAGS / section.

- Then a / UTILITY CLASSES / section for clearing floats, etc.

- Next comes site layout. Headers, footers, page width, etc. all go here. Just the layout though - think the grid. No real content styling yet.

- Now sections for each piece in the layout. Content styles go here. First a section for the / HEADER CONTENT /, then a big section for the / PAGE CONTENT / (vast majority of styles go here), then the / FOOTER CONTENT / styles.

Great post, but how do you structure a press package in the first place? Is a great landing page, and a good 'about' page enough, or do you look for something more?