They haven't paid for it. They've paid for what they've used in the past, and nobody is suggesting charging them again for it. They haven't paid for the generation of future electricity, and there's every right to increase the cost of it for that electricity, or to limit the amount they're able to buy.
Have you ever tried to do that? Have fun waiting on hold, then being told that they'll send a cab right there. Then wait 40 minutes, because they didn't have a free cab in the area (there isn't a single cab network in a city, or even 2 or 3. There's dozens of companies with a few cars each, and either the one you called has to have one free or they have to farm out the request).
Then they'll send a car (probably, but I've been stood up by cab companies), but you won't know any real estimate on when it arrives. And you have no way of checking. If you call back, they won't have an actual answer for you. And good luck finding them if they get a little lost at the end, or if they don't know where your exact address is- they have no way to contact you, and you have no way to know where the car is.
Uber was a quantum leap forward with its ability to directly contact a driver, show car locations on a map, have a single network (or now a few large networks) of drivers rather than dozens of small ones, and far greater ability to match you to the closest driver. It was light years ahead when it came out, which is why it blew up the way it did.
No, it isn't. If you want efficiency, write in a language that targets bare metal. Especially if you're talking about binary layouts, which depend on a dozen factors like padding and endianness which are supposed to be abstracted away in a language like Java.
In the US that works in 1 city- New York. And even then only really in Manhattan. If you live in a suburb, or in Queens, and you're trying to flag a cab down I hope you have a few hours. Even in Chicago there isn't a sufficient mass of cabs anywhere other than downtown to make that work.
Court cases are not, and never have been, considered legislation. Legislation comes from a legislative body, for example Congress. Legislation does not and in the US cannot come from the courts. Especially in the case of this point, putting Citizen's United in the list of actual legislation and complaining about legislation having opposite names is facetious at best, as the name of a court case is not the name of legislation, and is fixed by convention to be the name of the two parties.
In addition, a synonym is not a definition. It is a *similar* word. It is not a replacement, and does not mean the same thing. You can't say because something sounds sort of like a synonym.
Not to mention- the word ruling has multiple meanings. The meaning of the word in the above list is in the sense of a ruling by an executive authority. Not the same thing as a court ruling. So even if it wasn't not how you use a synonym it would be wrong.
Citizen's United is a court case, not legislation. Its named after the organization who sued (Citizen's United vs the United States was the court case)
So I have to have a physical key, magically have copies of it on all my devices, and I'm screwed if I want to log into my account on another computer for some reason. No thanks, I'll keep my passwords.
Yes- there isn't enough room. The problem isn't that there's no affordable housing int he state- go out to central valley or Bakersfield. The problem is that there's no affordable housing in San Francisco (LA and San Diego to a lesser extent) because there's no more land to build on and they won't allow them to build up to higher density.
You don't need to audit every change. You freeze a version, and use that until you need to update. You know, like we've been doing for 50 years.
You also employ layered trust. Is it likely a major open source library, or a library from a major company is safe? Yes. Is some random thing off some guy on github? No. You avoid the second type, trust the first, and audit those in between.
First off- whoever posted that put no evidence in at all. Secondly- the vast majority of people at those companies are not IT. They're programmers. Totally different payscale. The actual IT people are probably paid well, but not anything like the numbers above.
As someone who's written a lot of C professionally- no we wouldn't. Not as an error. As a warning, fine. Preferably one that can be pragma-ed out. But not as an error.
As for formatting- no there really isn't anything good to be said about a consistent style. Especially not to that degree. All you're doing is costing time on meaningless triviality. The time spent to fix it the first time it happens will be an order of magnitude greater than the practical benefits of using the same style for something so trivial for the next 100 years.
But repayment time was 1 movie. I bet there always 1 movie per month you'd be willing to see some evening when bored. If you live in some areas (Silicon Valley, NYC) a ticket is closer to 20 and one movie a month was a 100% gain. If they had been say $50 a month for up to 1 a day it would have possibly made money. At $10 it was too cheap.
There were right outside Chicago. The result was sometimes multi-hour traffic jams caused by the tollbooths and everyone being forced to stop and pay. Automated tolling helped, but they're still a starting point for traffic jams.
Why would a company trying to maximize profits even offer the 1 time cure at any price, when they don't have to and can charge as much as you can afford for the rest of your life instead?
If you privatize profits at all, that's what you get. How you pay for it makes no difference. Which is why only one country in the developed world does it that way, and why they have the worst health outcomes in the developed world.
Or maybe my definition has less to do with knowing every trick of the language, and more with getting tasks done. There's two major things here:
1)Actual coding is only 10-20% of programming. Architecture, debugging, organizational skills, etc are far more important, and are almost completely language agnostic. There were definitely subtle you would have trouble finding because they had to do with language tricks/oddities, but most bugs are logical bugs.
2) You can be reasonably efficient and not do everything the best way. I don't care if you use a for loop where a foreach would be slightly better, both do the job. Spending 1 minute to write trim() instead of using the library version would still be reasonably efficient (although for such a common function I would probably google to see if it exists first, this is just an example).
Last time I did a major language change, I was finding root cause and fixing bugs in the codebase within a day, because I could find where they'd have to be by logic alone. I'd consider that being reasonably efficient.
No, you don't. I've done it multiple times in my career- you learn the syntax and jump in, picking up the library as you go along. It just means you sometimes write a bit of extra code. I wouldn't put it at expert level on my resume, but you can be reasonably efficient and get tasks done. Remember we used to program with minimal libraries and still make progress in new languages. You just might write a bit of redundant code that gets cleaned up (or not) later.
And according to them, anything that's machine independent is high level language. If you want a term for something more than that, come up with a new term and a new definition. Until then, stop muddying the existing ones.
C is a high level language. A high level language is anything that's not a 1:1 mapping of instructions. Stop trying to redefine terms.
As for python being the scientific language of choice- that's just wrong. Its still C and Fortran. Serious scientific computing requires performance, nobody would dream of doing that shit in python.
You don't need to. Nobody knows the whole standard library of any language now. Not even a simple one like C. You learn the parts you use, and google for more stuff as you need it. Occasionally it means you'll write an algorithm instead of using a built in, but the time lost is generally minimal. If it isn't, you'll probably think "I wonder if this already exists" before you finish.
They haven't paid for it. They've paid for what they've used in the past, and nobody is suggesting charging them again for it. They haven't paid for the generation of future electricity, and there's every right to increase the cost of it for that electricity, or to limit the amount they're able to buy.
Have you ever tried to do that? Have fun waiting on hold, then being told that they'll send a cab right there. Then wait 40 minutes, because they didn't have a free cab in the area (there isn't a single cab network in a city, or even 2 or 3. There's dozens of companies with a few cars each, and either the one you called has to have one free or they have to farm out the request).
Then they'll send a car (probably, but I've been stood up by cab companies), but you won't know any real estimate on when it arrives. And you have no way of checking. If you call back, they won't have an actual answer for you. And good luck finding them if they get a little lost at the end, or if they don't know where your exact address is- they have no way to contact you, and you have no way to know where the car is.
Uber was a quantum leap forward with its ability to directly contact a driver, show car locations on a map, have a single network (or now a few large networks) of drivers rather than dozens of small ones, and far greater ability to match you to the closest driver. It was light years ahead when it came out, which is why it blew up the way it did.
No, it isn't. If you want efficiency, write in a language that targets bare metal. Especially if you're talking about binary layouts, which depend on a dozen factors like padding and endianness which are supposed to be abstracted away in a language like Java.
Oh I can answer it. But all it will do is cause him to ask another dozen questions about it, because he's ignorant. Kind of like this response to you.
In the US that works in 1 city- New York. And even then only really in Manhattan. If you live in a suburb, or in Queens, and you're trying to flag a cab down I hope you have a few hours. Even in Chicago there isn't a sufficient mass of cabs anywhere other than downtown to make that work.
Court cases are not, and never have been, considered legislation. Legislation comes from a legislative body, for example Congress. Legislation does not and in the US cannot come from the courts. Especially in the case of this point, putting Citizen's United in the list of actual legislation and complaining about legislation having opposite names is facetious at best, as the name of a court case is not the name of legislation, and is fixed by convention to be the name of the two parties.
In addition, a synonym is not a definition. It is a *similar* word. It is not a replacement, and does not mean the same thing. You can't say because something sounds sort of like a synonym.
Not to mention- the word ruling has multiple meanings. The meaning of the word in the above list is in the sense of a ruling by an executive authority. Not the same thing as a court ruling. So even if it wasn't not how you use a synonym it would be wrong.
If you have to ask that, you don't belong in this conversation. Its a well defined term.
If you need that, write C. Its neither a goal nor a use case Java should support. Not every language needs to do everything.
Citizen's United is a court case, not legislation. Its named after the organization who sued (Citizen's United vs the United States was the court case)
So I have to have a physical key, magically have copies of it on all my devices, and I'm screwed if I want to log into my account on another computer for some reason. No thanks, I'll keep my passwords.
Yes- there isn't enough room. The problem isn't that there's no affordable housing int he state- go out to central valley or Bakersfield. The problem is that there's no affordable housing in San Francisco (LA and San Diego to a lesser extent) because there's no more land to build on and they won't allow them to build up to higher density.
You don't need to audit every change. You freeze a version, and use that until you need to update. You know, like we've been doing for 50 years.
You also employ layered trust. Is it likely a major open source library, or a library from a major company is safe? Yes. Is some random thing off some guy on github? No. You avoid the second type, trust the first, and audit those in between.
First off- whoever posted that put no evidence in at all. Secondly- the vast majority of people at those companies are not IT. They're programmers. Totally different payscale. The actual IT people are probably paid well, but not anything like the numbers above.
As someone who's written a lot of C professionally- no we wouldn't. Not as an error. As a warning, fine. Preferably one that can be pragma-ed out. But not as an error.
As for formatting- no there really isn't anything good to be said about a consistent style. Especially not to that degree. All you're doing is costing time on meaningless triviality. The time spent to fix it the first time it happens will be an order of magnitude greater than the practical benefits of using the same style for something so trivial for the next 100 years.
But repayment time was 1 movie. I bet there always 1 movie per month you'd be willing to see some evening when bored. If you live in some areas (Silicon Valley, NYC) a ticket is closer to 20 and one movie a month was a 100% gain. If they had been say $50 a month for up to 1 a day it would have possibly made money. At $10 it was too cheap.
The theaters have little ability to reprice their tickets, due to deals with the studios for ticket sales.
There were right outside Chicago. The result was sometimes multi-hour traffic jams caused by the tollbooths and everyone being forced to stop and pay. Automated tolling helped, but they're still a starting point for traffic jams.
The phrase "SJW" means "I'm an idiot and everything I say should be ignored". I find treating it that way works perfectly.
Most likely Asperger or autistic. He just gets hyper focused on details.
Why would a company trying to maximize profits even offer the 1 time cure at any price, when they don't have to and can charge as much as you can afford for the rest of your life instead?
If you privatize profits at all, that's what you get. How you pay for it makes no difference. Which is why only one country in the developed world does it that way, and why they have the worst health outcomes in the developed world.
Or maybe my definition has less to do with knowing every trick of the language, and more with getting tasks done. There's two major things here:
1)Actual coding is only 10-20% of programming. Architecture, debugging, organizational skills, etc are far more important, and are almost completely language agnostic. There were definitely subtle you would have trouble finding because they had to do with language tricks/oddities, but most bugs are logical bugs.
2) You can be reasonably efficient and not do everything the best way. I don't care if you use a for loop where a foreach would be slightly better, both do the job. Spending 1 minute to write trim() instead of using the library version would still be reasonably efficient (although for such a common function I would probably google to see if it exists first, this is just an example).
Last time I did a major language change, I was finding root cause and fixing bugs in the codebase within a day, because I could find where they'd have to be by logic alone. I'd consider that being reasonably efficient.
No, you don't. I've done it multiple times in my career- you learn the syntax and jump in, picking up the library as you go along. It just means you sometimes write a bit of extra code. I wouldn't put it at expert level on my resume, but you can be reasonably efficient and get tasks done. Remember we used to program with minimal libraries and still make progress in new languages. You just might write a bit of redundant code that gets cleaned up (or not) later.
And according to them, anything that's machine independent is high level language. If you want a term for something more than that, come up with a new term and a new definition. Until then, stop muddying the existing ones.
C is a high level language. A high level language is anything that's not a 1:1 mapping of instructions. Stop trying to redefine terms.
As for python being the scientific language of choice- that's just wrong. Its still C and Fortran. Serious scientific computing requires performance, nobody would dream of doing that shit in python.
You don't need to. Nobody knows the whole standard library of any language now. Not even a simple one like C. You learn the parts you use, and google for more stuff as you need it. Occasionally it means you'll write an algorithm instead of using a built in, but the time lost is generally minimal. If it isn't, you'll probably think "I wonder if this already exists" before you finish.