puppybeard's comments

Argument which apparently led to the post: http://news.ycombinator.com/item?id=2082965

I love how oslic describes a dev who maintains their right to say how their work is used as a "protestor". Surely putting in the hard work, and being entitled to do with it as you please, is a cornerstone of free enterprise?

In a funny way, the Open Source and related movements are rocket fuel for idealised capitalism.

The first money I made on the web after college was made using Notepad++ to build sites on a LAMP stack. I'd guess most of us have similar stories. I'm happy to give away my knowledge for free, because it's not 1% of what I've received. And it doesn't mean I do everything for free either.

I don't think anyone can seriously claim that people making free software haven't changed EVERYTHING in software, especially on the web.

That one really bewildered me too. Suddenly there's no motive for having a unique element on a page, and styling it's children accordingly? Nonsense.

Don't consumer operating systems always offer a virtual tour of how to use them?

The "teeth itch" thing: It feels too much like over-ornamentation. It just wouldn't suit my style of work. I find it much faster to scan css when everything is vertically aligned. If I have to scan left and right as well as up and down, it takes me longer, and comparisons are slower.

Some nice ideas, but not many new ones. And the new ones don't always make sense:

"For each level of markup nesting, try and indent your CSS to match" <= that made my teeth itch. Mostly just down to personal taste, but I really find it quicker to read css if only the values are indented. It's easier to compare nested classes that way, as repeated values would occupy more similar space.

"Also write vendor prefixed CSS so that colons all line up" <= not all vendor css3 values have the same structure, so this can't be a standard (eg: gradients, mixed border-radius)

I suppose whether or not you add conditional support for IE is a matter of taste. I prefer to handle IE the boilerplate way, with conditionals determining what class the html element has, and including appropriate styles in the main css. Why sacrifice good, standards-compliant css for dirty IE?

I agree with you, and MG Siegler, by extension, that most tech writing is crap. The best writing I've seen is always by technical professionals, rather than journalists assigned to write about technology. However I count Siegler as in the latter camp. He's a fanboy and he's never built anything.

With his article above he's saying "this criticism of a company I'm involved with isn't valid, because these people aren't technically expert". That's wrong because you don't need to be a technical expert to value and appreciate personal privacy, which is the key issue. It's also hypocritical, because he's not a technical expert himself. Like the people he complains about, he makes his money from hype generated around products, without being capable of making his own product.

tl;dr = "Company Not That Bad, says man working for Investment Fund with stake in the First Company" Let's not question that source!

TechCrunch has the most punchable "journalists" I've ever seen, not including tabloids. As for one of their people accusing others of writing shit just for the pageviews, that's staggeringly hypocritical.

Also CrunchFund is a scam. Hire a popular hack, pay him to talk up a new venture, guaranteed business. It's as ethical as insider trading. Bad shit. Leads to lots of crappy "me-too" startups doing better than they deserve.

Remember this rule: design and coding are two separate processes, each of which needs it's own workflow.

If you style a site by adding bits of css now and again while you build the backend of a site, it will look like crap. I know, because I used to do it, and the work I did then embarrasses me now.

You obviously know what a good design looks like, so do your design away from your project, in Photoshop or whatever, and don't turn it into css until you're happy with it.

Solicit criticism of your design. Ask people who know design to give you feedback, whether you know them personally or online. They'll stop you from repeating mistakes they may have learned from themselves.

Everything the user, heretohelp is saying sounds right to me.

I've never made a startup, so I'm talking as a consumer, but here's my honest opinion.

I don't want to use your service, I have no need for it. I have four other services I can use to vent, and I only use 2 of them.

Are you addressing a need that isn't provided elsewhere? What research did you do?

If I was you, I think I'd be researching until I identified something people actually need or want, and I'd re-use some of the code from this project for connectivity.

Also, I'd allow people to use more than just Facebook. Maybe I'd rather have a unique account on your service that's associated with my email, but not discoverable by absolutely everybody.

This could be handy for something like starting a template from scratch for a CMS.

However it needs more work. Multiple classes are broken.

.post-5 post type-post status-publish format-standard hentry category-products post {

}

Also, it misses a trick by not using heierarchy for definitions the way anybody who writes css as part of their job would.

I'd like to see it as a tool that gives you every definition you need, and then you can strip out what you don't want afterwards.

I can't see myself using it on a bespoke project, as I tend to write html and css simultaneously.

Sadly, I have to agree with you. It's not ready yet at all.