aggronn

>Do they provide any sort of guidelines or rules on how the work is done?

I wonder what constitutes rules on how the work is done. If I use a bike to pick people up and drop them off, and I not doing the work, or am I doing the work in a way that is violates the rules? If I pick people up and then drop them off in the wrong place intentionally, am I not doing the work or am I violating rules on how the work is done?

So is the car a specification for work or is it a guideline on how to do the work? Seems like CA thinks its the latter, but I definitely see the argument for the former. Its more clear cut in freelancing--the end product shouldn't indicate the type of computer that it was developed on. For Uber, the car is definitely part of the experience that you're being paid to provide as a driver.

Anyways, i'm not qualified to speculate about any of this. I'm just going to be unhappy if a decision similar to this somehow prevents me from making a few hundred bucks every now and then for driving drunk people home from bars.

Maybe things are different in CA, but as a driver in FL:

> Taxi drivers get to choose how they do their job (i.e. who to pick up).

I can reject any fare.

> Moreover taxi companies do not forbid customers from tipping nor do they get a percentage of a taxi driver's gratuity.

Uber doesn't forbid me from getting tips, and doesn't take any of the tips that I do get...

Any data-heavy applications that have significant grouping/filtering/etc.. SQL is very powerful, and when you try to work with large datasets in the browser, its kind of disappointing that you have to either transfer a lot of data on every data view change or do SQL's job with lodash collection methods.

I agree--I think that there are problems deeper than special interests. It would take many years and many people in different parts of government, but I think the real solution is a movement to a multi-party system. One person elected as president can't turn the ship around.

Our children will be taught to do all of their homework in git as the 2040 way of showing work! Github for 6th graders!

There is some amount of boilerplate with rolling your own, but I think people might benefit from rolling their own flux implementation when they first try to play with react. The best solution I think for this is to have multiple dispatches in your actions.

Create action -> action[dispatch 'action pending' -> async action -> dispatch 'action complete with data'] -> stores.

Keep your stores completely sync, and the data in a single object, and maybe have them all be pure functions, and suddenly there is no web of anything and theres a single source of truth, and bam. nice.

My observation while looking at his resume: Why so much emphasis on functional programming? Most shops are much more OOP than functional, and making it seem like you care more about the intellectual aspects of programming than actually solving problems is not good. Employers don't care if you like functional programming if they aren't also huge functional programming people. HR managers sure as hell do not know what functional programming is.

If you're interested in Polymer just for its material design, you can use React just the same with something like Materialize. There are also projects like MaterialUI which might be worth looking at.

Forgetting the question about Material design, and just addressing which is better: I don't think its a one or the other deal. For the most atomic, cross-application, least state-full components, Web Components are a good choice. But if you're building an entire application that is component driven, does it make sense to have a Web Compoent <App />? At some point when you get to the point of using application level state across components, you can use React.

My first job was as a Silverlight developer. I used to complain all the time about XAML, and as a huge React fanboy, its been lurking in the back of my mind. Why would I like JSX but not XAML? Especially since early Silverlight projects used 'code-behind', which is essentially just a c# file that is paired with each component. How is this different than React? At all?

I think the biggest difference is that XAML was really terrible to work with in part because of proprietary components and the massive tooling around it. I remember I'd have to use Blend whenever I wanted to change how something looked. And then there wasn't a great application structure that moved along with it. I pushed really hard for us to switch from code-behind to MVVM for our application architecture. It worked great, and made everything much easier, though it was really abstract and styling was difficult still. But that was my first job--maybe if I went back it would seem trivial.

I don't know if this applies to XAML, but once you start thinking of React in a component architecture model (knowing JS helps too!), the declarative style makes so much sense.

From http://thesavvybackpacker.com/long-term-travel-europe/

> The easiest ways to extend your trip past 90 days is to visit both Schengen and non-Schengen countries. Once your 90 days is up, travel to the UK, Ireland or many of the Eastern European countries that aren’t part of the agreement. Once you’ve spent those 90 days there you are free to return to to the Schengen area for another 90 days. You can keep repeating this process until you run out of money. - See more at: http://thesavvybackpacker.com/long-term-travel-europe/#sthas...

You can only be in Schengen zone for 90 days out of 180, so expect to spend some in eastern europe or UK/Ireland. You may also qualify for the german freelance visa:

https://medium.com/@imcatnoone/how-to-get-your-german-freela...

There was a time when React literally just didn't support web components, so I don't think that's really fair. Yes, it would be nice if it worked completely free, but if you're only listening to 2 or 3 events on a component, it is definitely a fair price to pay for being so bleeding edge.

You're wrong about web components and react. As of 0.12, if you register a web component like you normally would, you can reference it in a react component. React no longer has a white list, and instead assumes all lower case tags are HTML tags (standard or custom).

The only drawback is that it doesn't support custom events out of the box. Instead, you have to manually create event listeners on elements on mount. As far as I can tell, there's no reason why it couldn't in the future though; Web component adoption is so low right now that it just hasn't been something people have complained about.

> unless what web devs had before was really that horrible

As a big fan of react, I think that this isn't really a fair thing to say. I feel as though this statement implies that front end dev is not complex and therefore it surprises you that there is room for significant improvement. I'm sure that's not what you were thinking, but really, building complex imperative UIs with state can be very difficult, and react does represent a new step in the paradigm shift away from imperative development. Whether React is the future or not, components and composition are here to stay, and I think a increasingly large portion of the community is interested in writing web applications with immutability--all of which suites flux (and react) very well, and does not suite jquery very well.

React doesn't enable anything that you simply couldn't do with jquery and backbone, but it does make a lot of it way easier and reduces overall complexity by a ton, especially if you're developing with component structure and immutability in mind.

I've had a lot of trouble finding out what people are thinking about the comparison between shadow dom/web components and react.

If web components are finalized and ubiquitous, how does that effect react?

Hopefully you've seen this:

https://networthify.com/calculator/earlyretirement

OP's tool is great, but this tool might address your second bullet point.

This is probably intended to be a joke about how Javascript was originally developed over about 10 days, which has been the root of many of JS's problems.

http://www.computer.org/csdl/mags/co/2012/02/mco2012020007.p...

http://www.wsj.com/articles/greece-expects-primary-budget-su... http://finance.yahoo.com/news/greece-says-eu-imf-lenders-095...

Greece hasn't had a balanced budget in decades, and creditors don't believe that 2015 will be any different. If they can manage to actually not run a deficit in 2015, that would be a great boon for them.

Same, though I don't know if tired is the best word for me. For me, its just like, whats the point? Being able to use a computer without having to move my arms more than an inch or so is kind of...relaxing?

I agree that having this issue dominate discussion is incredibly annoying, however I have to say, Facebook needs to make this more clear. There should not be confusion about this.

How is the assumption that "ending of human life would not be so easy" any better than the opposite? If they're equally valid, then its rather fair to take the opposite view because it is more cautious.

I think reading through Flux framework documentations (marty's for instance) helps a lot. They do some abstracting on top and let you avoid some more in-depth questions about how to implement framework level features. They offer you some classes, and you just implement the classes to model the high level ideas of Flux.

This implies you don't do any research for products other than amazon reviews and official marketing material. I think this is typical for some kinds of products, but not necessarily typical overall.

I think the idea is that you should have grouped projects broken out into organizations?

You could have said the same thing about several of the languages you listed, even within the last 5 years. The difference here is that C# already has a massive userbase.

X dollars go in, x dollars go out. before, average revenue per market participant category was x/n. Now its x/(n+1).

At the end of the day, unless their participation increases x by more than their cut, they're just taking revenue from everyone in the game who actually provides value.

They don't make the market more efficient.

Assuming this doesn't affect advertiser RTB budgets, it hurts all of the players who actually create value (publishers, exchange providers, etc)

I'm interested in knowing how people can even detect this happening. Anyone? The article didn't really go into detail on that point.

In the few hackathons I've participated in, interesting ideas have always trumped technical ambition in terms of winning. If you're only participating for the atmosphere, then I would say go ahead and challenge yourself.

This sounds like a rather uninformed view on how Nazi Germany operated.

> DAF membership was theoretically voluntary, but any workers in any area of German commerce or industry would have found it hard to get a job without being a member

http://en.wikipedia.org/wiki/German_Labour_Front

You could not work unless you joined the Nazi party.

You could investigate the people in charge of the company and their backers. If you think they have more to gain by draining a small number of peoples bank accounts than they have to lose by committing a federal fraud crime then don't use them. Obviously any evaluation would also depend on the credibility of the information presented on the website about those individuals.

I don't make any purchases with my debit card, so I would only link my credit card, which has pretty solid fraud protection. I'd probably be more way about cash accounts.