jdwissler's comments

I'm also doing Mentzer's workout.

Even though it is only one set per workout, that set tends to be pretty painful. ;)

I see. I don't think we actually disagree on anything, but were just thinking of different semantics.

I should have qualified that I rarely use the table tag and use display:table-cell.

I was thinking of them as effectively the same as using a table for layout.

What qualifies tabular data?

GMail uses a table for laying out emails, is that tabular? (Maybe it is, I don't know, which is why I'm asking.)

What if you have an element which has 5 children that are in a row and you want the one in the middle to take up all the remaining width while the rest just take the width they need? I'm actually curious because I haven't figured it out. (Besides using table cells that is)

It really depends on what you are trying to do, I don't really know how to answer the question, it is too broad.

But like I said, I don't think tables are 'bad'. I think the main stigma against tables was that back in the old days they were used to layout pages that had column layouts, but I didn't program back then so I don't really know.

In my own experience I find them to be very inflexible and unpredictable.

There are still scenarios when you need them though, so I wouldn't call them 'poor practice' so much as something that should only be used if it makes sense.

Ha ha thanks ;)

Kind of a side issue to the article.

CSSLint is useful, at least for me. The only problem is I find myself disabling a lot of rules.

There are certain rules that would be useful if you could easily specify their parameters. For example, there is a rule that says that you can only have 10 font-size declarations in your CSS sheet, which is completely and utterly arbitrary. What if I need 11? Or what if I ONLY want 3? It would be useful if I could specify that. In fact I should be able to do that for any property.

Developers need to be able to enforce standards in their JS, CSS and even HTML. The fact, however, is that certain standards aren't ubiquitous across every webpage, and need to be set by the developer.

If HTML 5/JS is going to become a serious platform for applications I think it is going to have to be able to leverage multiple threads/cores much more easily. I don't use Web Workers simply because they are too limited in scope in my opinion.

Sometimes I just want to search through my local data in my main thread to process 'n' numbers to show some result to the user and I don't want to lock up the DOM for 'n' milliseconds. I also don't want to make an entire new script file just for processing 'n' numbers, what if I need access to data in my main thread? Do I package 'n' numbers up and then send it as JSON? Well that can take more time then actually processing the numbers....and timers...such a hack.

I don't know all the design decisions behind web workers and I understand the safety of communicating with strings and events, but sometimes I really just want to call 'new Thread()' and have access to all my variables and data in my main thread. Yes it can be dangerous, yes you can fuck it up, but we still have that problem when we try to make our servers fast.

However, maybe I just don't understand how Web Workers work.

It thinks I'm 42.

I'm 21. Something must be wrong with me.

"The tallest trees catch the most wind."

I hated the article starting there.

It is cowardly, evasive and deceitful. It completely ignores the issues people have with EA.

Is it possible to have emacs controls in this?

That is one of the only things preventing me from using it.