amavisca

The link is similarly a white screen on Android Chrome for me.

I was just going off what the MDN page said about it being removed in the HTML5 standard. It looks like WHATWG just has a "living standard" and W3C still uses the versioning, so it's probably removed from W3C standards. I'm not too familiar with the reality of these standards.

This site uses the xmp tag (deprecated in HTML 3.2, removed in HTML5) which I found interesting and had never seen!

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/xm...

It's similar to the pre tag but doesn't require the escaping. I guess you just have to make sure you don't have a closing xmp tag :)

Can you add some clarity to your complaints about WebPack?

What are the similarities with Grunt that aren't worth the mess and what are some of the awful habits that WebPack breeds?

What are your preferred ways to handle modules and build steps in general?

I think Redux and React-Router are very opinionated and distract people new to React from React itself.

My workflow for ramping someone up on React and eventually Redux looked like:

- A single React component with React.createClass

- ES6 class React components

- Add a component hierarchy and treat the top level component's state as the entire app state - pass down callbacks to update state. Look how this becomes harder to scale as we get more depth in our component hierarchy!

- Redux without the redux-react bindings. Also stateless function components.

As someone not new to React, I'm seeing this tool as a solid replacement to the old JSX Transformer script they used to provide. Let me get up and running just a bit more quickly.

Under the hood this is Webpack + Babel + ESLint with sane initial configuration. Love it.

I prefer this style of component test and tend to bring in jQuery as a test dependency to remove some of the complexity of the assertions (I'm not always up to date on the current DOM APIs).

I find the instance method unit test a bit unsatisfying. I'm not going to call an instance method of a component from outside of that component (maybe someone else is doing this - I'm just not sure what the use case is), so why would I do that in my test? I want to integrate through the instance method by poking at the DOM rather than calling the method directly.

If you're trying to test client side javascript with phantom + jasmine through gulp there are a few options.

I googled "gulp jasmine phantom" and found 3 options at the top, one of them being under the jasmine org on github. The other 2 seem to have similar APIs to the one under the jasmine org.

My argument would be the fact that it is "just a blogging platform."

He recommended books in his response.

You should be reading JavaScript: The Good Parts.

My opinion would not change as far as "which looks nicer."

You need to consider the context of the icon though.

It was just posted on reddit for the 100th time (r/webdev)

That logo makes me so uncomfortable the more I look at it.

I think Odesk is probably decent for certain businesses, but I can't imagine using it for a startup. You get tacky, inconsistent results.

Both of these companies process through First Data.

1 - Yes

2 - Front End Development, maybe

3 - Ruby/Python/JS/PHP. JS necessary for (2)

Handing my information to Stripe defeats the entire purpose of your application.

You provided a single example and then skipped the alternatives.