While the code you write is running single threaded, that's only the programming model; the program you create with that code is decidedly multi-threaded. The truth is it's easier to write properly multi-threaded code in Node.js for the vast majority of real world use cases, and for everything else, you can write multi-process code with good language support built right in.
If you can't be bothered to use professional tools which glaringly highlight misspelled variables, then perhaps you should stick with something with more hand holding. I've never really felt compelled to "use strict", because I - as a developer - have discipline, and don't need it.
The concept of East and West doesn't map to the poles. All directions are some combination of North/South and up/down. At the South Pole, the sun rises and sets in the North, and moves clockwise; at the North Pole, the sun rises and sets in the South, and moves counter-clockwise.
I think the issue is that "clean" is in the eye of the beholder. It looks very different in OOP than it does in FP, both of which are pretty well supported paradigms in JS. Seems like the real argument is that JS doesn't make these decisions for you, so you don't get much guidance. That's certainly a speedbump, but it's also a feature, in that it is eminently flexible in the face of new paradigms.
Also, I've never once felt any need for namespaces in JS. Whether you're using ES6, CommonJS, or require.js, you can name anything whatever you want, so there are no naming conflicts which require namespaces to address.
Also, this is one example of how JS deters you from globals, and pushes you into DI.
I will defend Javascript to pretty much anyone. All languages suck in various ways. Javascript at least has the sense to keep the language small, backwards compatible, and well defined. New language features are almost always targeted, useful improvements, with clear use cases. And it's fast as fuck (not really because of anything related to the language, of course, but still).
Quickest way to kill my loyalty is treating loyalty like a currency. I pay you for good service everytime. Not just for the times I present a magic "gimme decent service" card.
Here in the US, I get paid a competitive salary, have unlimited vacation, work about 35 hours a week, have on demand telecommuting, and free health care.
Sorry, foreigner, you can tell yourself you've got a good deal, but it sounds like unsubstantiated nationalism.
Police put child pornographers in prison after asking them for photos. That's how the law works. It's a dumb law, but THINK OF THE CHILDREN!!!!!!!!!!!!!!!
No. The requirement is that the software do something useful for the company and provide ongoing value. The feature list and documentation are what comes out at the end, after you have figured out how to meet the requirement.
Doubtful. Ubuntu phone is designed around various side swipes. This is probably a case of Apple designers not wanting anything spoiling their pretty mockups. Apple: fuck usability, it's fucking pretty.
Which are exactly the types of jobs that Americans can be trained for and for which there is a glut of underemployed workers looking for an American salary.
For a lot of things, 32 bit is overkill, but you don't see people storing 24 bit numbers. This is a fundamental problem with premature optimization. You should always use the largest precise integer available unless you have a compelling, evidence-based reason not to. The onus should be on the 32bit users to demonstrate their choice is better.
Slashdot Mirror
While the code you write is running single threaded, that's only the programming model; the program you create with that code is decidedly multi-threaded. The truth is it's easier to write properly multi-threaded code in Node.js for the vast majority of real world use cases, and for everything else, you can write multi-process code with good language support built right in.
If you can't be bothered to use professional tools which glaringly highlight misspelled variables, then perhaps you should stick with something with more hand holding. I've never really felt compelled to "use strict", because I - as a developer - have discipline, and don't need it.
The concept of East and West doesn't map to the poles. All directions are some combination of North/South and up/down. At the South Pole, the sun rises and sets in the North, and moves clockwise; at the North Pole, the sun rises and sets in the South, and moves counter-clockwise.
I think the issue is that "clean" is in the eye of the beholder. It looks very different in OOP than it does in FP, both of which are pretty well supported paradigms in JS. Seems like the real argument is that JS doesn't make these decisions for you, so you don't get much guidance. That's certainly a speedbump, but it's also a feature, in that it is eminently flexible in the face of new paradigms.
Also, I've never once felt any need for namespaces in JS. Whether you're using ES6, CommonJS, or require.js, you can name anything whatever you want, so there are no naming conflicts which require namespaces to address.
Also, this is one example of how JS deters you from globals, and pushes you into DI.
Weak scoping rules? How do you differentiat between strong and weak scoping? Either an identifier is in scope or it's not.
I will defend Javascript to pretty much anyone. All languages suck in various ways. Javascript at least has the sense to keep the language small, backwards compatible, and well defined. New language features are almost always targeted, useful improvements, with clear use cases. And it's fast as fuck (not really because of anything related to the language, of course, but still).
Or named so because St. Jude is the patron saint of desperate causes and that concept applies to medicine in general.
Do you really think it will not be possible to drag and drop onto another tab?
There's no guarantee an AI will be auditable. Lots of AIs are too complicated to understand how they work.
Some of us actually thrive doing this sort of work. Rewriting working code is such a lazy cop-out.
Pretty sure the driver can take any route they (or the passenger) like. Which is probably why Uber is padding the up front cost.
In what way is that answer still correct? The sun rises in the South at the North Pole.
Quickest way to kill my loyalty is treating loyalty like a currency. I pay you for good service everytime. Not just for the times I present a magic "gimme decent service" card.
Here in the US, I get paid a competitive salary, have unlimited vacation, work about 35 hours a week, have on demand telecommuting, and free health care.
Sorry, foreigner, you can tell yourself you've got a good deal, but it sounds like unsubstantiated nationalism.
Police put child pornographers in prison after asking them for photos. That's how the law works. It's a dumb law, but THINK OF THE CHILDREN!!!!!!!!!!!!!!!
No. The requirement is that the software do something useful for the company and provide ongoing value. The feature list and documentation are what comes out at the end, after you have figured out how to meet the requirement.
Many studies have been done on anthropic climate change, but almost no experiments.
Doubtful. Ubuntu phone is designed around various side swipes. This is probably a case of Apple designers not wanting anything spoiling their pretty mockups. Apple: fuck usability, it's fucking pretty.
Blame the anti-intellectual Europeans who forget how everything worked in their quest for a Catholic idiocracy.
http://www.history.com/news/th...
Opera started it. Other browser makers had to follow suit to keep up with Opera's speed.
It means 4 concat 4. This is typical notation. PostgreSQL even supports it for text concatenation.
Management functions primarily as a distributed buffer for blame. It will continue to serve that purpose for the foreseeable future.
Which are exactly the types of jobs that Americans can be trained for and for which there is a glut of underemployed workers looking for an American salary.
For a lot of things, 32 bit is overkill, but you don't see people storing 24 bit numbers. This is a fundamental problem with premature optimization. You should always use the largest precise integer available unless you have a compelling, evidence-based reason not to. The onus should be on the 32bit users to demonstrate their choice is better.