mradmin

14 ms·

31.
by mradmin 13y ago
You'll also get major specificity issues when using element selectors with other class/id type selectors. My rule of thumb is classes and only classes for styling, it really makes life a lot easier. (Even if you have a unique el
32.
by mradmin 13y ago
I have no idea what's going on. First time I viewed the link, it took me to nice laundry (after skipping the ad). The second time I viewed the link, it took me to the correct article. :/
33.
by mradmin 13y ago
I'm logged in but still get the error, although my account has very little activity (i only use it for dev purposes).
34.
by mradmin 13y ago
> Grunt in particular doesn't bring anything to the table that bash scripts don't One thing that comes to mind is cross-platform builds, which in some scenarios is very useful.
35.
by mradmin 13y ago
55 external scripts with a plethora of jquery plugins just to show some text content :(
36.
by mradmin 13y ago
Hmm, I've read reasons why you could code like this, but personally I would never make my code more complicated to read just to prevent errors that I can prevent with other methods, like having tests, for example. I would assume after
37.
by mradmin 13y ago
Agreed, I follow this styleguide: https://github.com/felixge/node-style-guide
38.
by mradmin 13y ago
Yup, for example: https://github.com/koajs/koa/blob/master/lib/application.js#...
39.
by mradmin 13y ago
I have utmost respect for TJ and his work but I am not a fan of his yoda style programming :(
40.
by mradmin 13y ago
Ironic that I struggle to read the text on this page due to the horrendous colour contrast. I give you the middle finger, fuckthissite.com.
41.
by mradmin 13y ago
So you can now enforce vagrant versions in your Vagrantfile, which is great, but this is a new feature thus older versions of vagrant won't honour it...so this feature is useless for me, at least for a while. I will continue to do this
42.
by mradmin 13y ago
Weird, I get a scrollbar showing I can clearly scroll. Are you an OSX by any chance?
43.
by mradmin 13y ago
Are you planning on creating the sass-convert utility?
44.
by mradmin 13y ago
Exactly. There shouldn't be a markup structure to style dependency. Personally I would never use an element selector because it makes life really difficult when you need to refactor the markup, which happens fairly often in my experien
45.
by mradmin 13y ago
Agreed, consistency matters most. Regarding whether it matters whether tabs or spaces are used, I've come to realise that I cannot control the tab length when viewing code outside of my editor (obviously!). So, let's say we have a
46.
by mradmin 13y ago
I would recommend splitting out the monolithic Gruntfile.js into individual config and task files. It makes it easier to read, in my opinion. I've put together an example here: https://github.com/badsyntax/gruntfil
47.
by mradmin 13y ago
What's up with the line-length limit on these comments? https://raw.github.com/gravityonmars/nodejs-starter/master/i...
48.
by mradmin 13y ago
It's cut off on my 13" MacBook Air on chrome.
49.
by mradmin 13y ago
What do you mean by "CoffeScript is JS"? CoffeeScript is not JavaScript. CoffeeScript compiles to JavaScript.
50.
by mradmin 13y ago
I would probably only use labels for breaking out of nested loops, for example: https://gist.github.com/badsyntax/5317545
51.
by mradmin 13y ago
It's hipster because it goes against the accepted standard way of writing Javascript. See https://news.ycombinator.com/item?id=1547647&utm_source=twit...
52.
by mradmin 13y ago
I'm just say that the colour contrast is atrocious. I've got pretty good eye sight and the text on that screenshot looks blurry. Both the unvisited and visited link states fail at AA colour contrast accessibility levels. [edit] -
53.
TinyMCE 4 Beta 1 released(tinymce.com)
2 points by mradmin 13y ago|0 comments
54.
by mradmin 15y ago
This solves all issues but unfortunately is not well supported in the older browsers :(
55.
by mradmin 15y ago
I agree with your points. Polling is not the right approach IMO. A much simpler approach would be to use the following script as a bookmark, and hit the bookmark when you want to see the changes: javascript:(function(){var%20s,i,x;x=documen