Forgot your password?
typodupeerror

Comment: Re:What 3500$? (Score 2) 280

by narcc (#48218347) Attached to: Tech Firm Fined For Paying Imported Workers $1.21 Per Hour

So you think that it's okay for a company to, for example, hire a number of people from an impoverished country with a lower cost of living at a rate acceptable to them while living in that country and bring them to another country with a dramatically higher cost of living while offering them the same (now clearly unlivable) wage while they're here?

Let me guess "no one forced them!" Sure, they didn't have to come here to work for slave wages under horribly abusive conditions. They could have stayed in their home country and lost one of the few jobs available to them.

If believing that people should not be unfairly exploited so that a socially irresponsible company can save a few bucks means that there's something wrong with me, then that's a label I'll proudly wear.

Comment: Re:Browser Apps are NOT desktop apps (Score 1) 194

by narcc (#48187121) Attached to: JavaScript and the Netflix User Interface

Please don't forget that the whole point of my comment was that threads are broken in JS.

That's new. Here I thought it was this:

The real underlying reason these apps feel flimsy is probably that Javascript is a single-threaded language. [...]
This means that when processing one action of the user (especially if it is a complicated action), the user interface will temporarily freeze.

Which is, of course, total nonsense.

For example, a simple "for" loop turns into a monster of functions calling eachother, in order to break the inside of the for-loop into small chunks that can't lock the UI. Now imagine a doubly-nested for-loop. You'd need special compilers to keep your code clean.

Which is also total nonsense. I'm sorry, but your assumptions simply don't match reality. Where did you come up with this stuff?

Again, I recommend you go do some reading about asynchronous programming and event-driven programming.

Comment: Re:Browser Apps are NOT desktop apps (Score 1) 194

by narcc (#48181465) Attached to: JavaScript and the Netflix User Interface

The problem is that "threads" are supposed to be a solution to dividing work.

Yes, but it's one of many solutions, and certainly not the best in every case. Threads come with their own set of problems, after all. They're no panacea. It's your job to understand the benefits and drawbacks of threads, and alternative solutions, and pick the best approach for your project. As threads are not an option in JS, it's a great opportunity for you to explore various alternative approaches. Tossing up your hands and saying "I must lock the UI!" is silly, particularly when it's clear that other applications don't seem to share that problem.

Lets face it: If your code locks the UI, you have a serious problem with your code! Go do some reading about asynchronous programming and event-driven programming. You'll find it quite helpful. Your users will thank you as well.

The study of non-linear physics is like the study of non-elephant biology.

Working...