Having said that, I would not blame you when you would "pirate" XP after having bought a new system with a forced inclusion of the latest MS OS version which you do not want (the So-called MS tax).
Microsoft has a long history of creating "lock-in" products then dumping support for them. If you need XP because of something Microsoft did in the past and they're not selling XP any more then I think you have a right to cheat on them.
Plus there the whole business of them making newer products which stink and/or won't fit on old machines due to lack of RAM/disk space/drivers.
I've seen the kids taught to develop powerpoint presentations, where the emphasis was on the visual aspects of the presentation, rather than on the soundness or validity of their arguments.
Realistically you use what your PHB decides and that is usually ado.net or some Oracle api. My info might be outdated by this sql_safe_string stuff is not part of SQL Server or Oracle and therefore doesn't exist in the eyes of the business world.
My bad. The "SQL" example required you to follow a link and read something.
It's not about SQL, it's about how weak languages lead to problems like (for example) SQL injection vulnerabilities. Read the page and weep over the method being proposed to "solve" this program.
Please be specific. We already know you don't like them. The question is: why?
Because they trade away everything good computer science strives for in exchange for being easy to type and so that uneducated people can call themselves programmers without having to educate themselves. It's Visual Basic and Excel Macros all over again.
you can easily have sql injections in your c or c++ code if you are lazy.
Not if your SQL API only accepts parameters of type "sql_safe_string" (or whatever you want to call them)
sql_safe_string would be like std::string but all assignment to it will run the string through a sanitizer.
Passing any other type of string to the API would give an error when you compile the program. The compiler doesn't have a bad hair day or need you to be constantly alert in case a std::string slips though.
(PS: None of this applies to C, obviously, and your continued grouping of C with C++ is revealing...)
It's not just the hipsters, it's also people like Joel Spolsky - the god of hipster programmers.
eg. I've lost count of the number of times I've seen this article referenced on the web and every time I see it I want to bash his head against something solid.
"Making Wrong Code Look Wrong"? Really? How about making wrong code *be* wrong? How about not having it compile at all? How about an SQL library that doesn't accept unsafe strings as parameters?
If you really want to, you could get the compiler to convert unsafe strings to safe strings on the fly ("implicit type conversion") to avoid having to educate the junior programmers.
All SQL injection problems could be eliminated at a stroke, now and forever. How is possible that people aren't doing it?
They're not though, because that would require a strongly typed language...and that's not fashionable.
Joel also rants endlessly against languages with exceptions (there's some of in that article), fails to grok very basic C++ concepts every time they're mentioned (eg. stack unwinding), but the hipsters worship him as some sort of a guru./rant over
Sure, but gold has been used as an exchange medium since before the beginning of civilization. Everybody knows what gold is and everybody thinks it has value. The wearing of gold is a symbol of wealth almost anywhere in the world. Part of the US reserve is a big pile of gold in Fort Knox.
Slashdot Mirror
If you double the number of batteries, you don't double the range, you get something like 25% more range.
Citation needed.
Sure, some of it.
You've calculated that precisely, have you?
An ICE car can make the trip in 32 hours 7 minutes.
Average 108mph?
I assume Tesla wanted this test to be legal...
When I saw the words "Perfect Boss" I imagined something totally opposite to the rest of the description (which describes the boss from hell...)
Why doesn't Tesla rent little trailers with extra batteries for long trips?
(or some sort of thing you can clip on the back of the car, or on the roof, whatever it takes...use your imagination)
Extend the range to as far as you're ever likely to drive in a single day.
That way you can drive down to Vegas for a weekend, drive to Grandma's place for thanksgiving, etc., no problem.
No, we need to go back to separating out the dumbest kids and putting them in rooms with other kids who learn at the same pace.
Having said that, I would not blame you when you would "pirate" XP after having bought a new system with a forced inclusion of the latest MS OS version which you do not want (the So-called MS tax).
Microsoft has a long history of creating "lock-in" products then dumping support for them. If you need XP because of something Microsoft did in the past and they're not selling XP any more then I think you have a right to cheat on them.
Plus there the whole business of them making newer products which stink and/or won't fit on old machines due to lack of RAM/disk space/drivers.
Some people are still actively supporting/updating Windows XP: https://thepiratebay.se/torren...
"Dredge waste" is more commonly called "sand". It is not exactly toxic industrial sludge that they are dumping.
Even so, can't they just drive a bit further out to sea before pressing the "dump" button?
I've seen the kids taught to develop powerpoint presentations, where the emphasis was on the visual aspects of the presentation, rather than on the soundness or validity of their arguments.
And that emphasis is incorrect because...?
Red crucifix? Skewed carbon dating results?
Does this mean the Turin Shroud is real...?
Correct. We should start with learning to read/write before we move on to the advanced stuff.
Experienced engineers wil indeed be able to properly use thread-shared state.
True, but we're talking about Javascript programmers.
Realistically you use what your PHB decides and that is usually ado.net or some Oracle api. My info might be outdated by this sql_safe_string stuff is not part of SQL Server or Oracle and therefore doesn't exist in the eyes of the business world.
My bad. The "SQL" example required you to follow a link and read something.
It's not about SQL, it's about how weak languages lead to problems like (for example) SQL injection vulnerabilities. Read the page and weep over the method being proposed to "solve" this program.
Please be specific. We already know you don't like them. The question is: why?
Because they trade away everything good computer science strives for in exchange for being easy to type and so that uneducated people can call themselves programmers without having to educate themselves. It's Visual Basic and Excel Macros all over again.
Do they know what denormalizing is?
Chrome's Javascript blocking is a joke. It's almost as if Google doesn't want you to block it....
OK, *some* of it applies to C.
C can't do it as anywhere near as neatly or safely as C++ though because it has no concept of privacy or encapsulation.
You also couldn't do things like implicit conversions to sql_safe_string to make it more friendly (assuming you want that).
(And Joel is still wrong and Javascript still rubbish, which is more important than starting a C vs. C++ thread...)
you can easily have sql injections in your c or c++ code if you are lazy.
Not if your SQL API only accepts parameters of type "sql_safe_string" (or whatever you want to call them)
sql_safe_string would be like std::string but all assignment to it will run the string through a sanitizer.
Passing any other type of string to the API would give an error when you compile the program. The compiler doesn't have a bad hair day or need you to be constantly alert in case a std::string slips though.
(PS: None of this applies to C, obviously, and your continued grouping of C with C++ is revealing...)
It's not just the hipsters, it's also people like Joel Spolsky - the god of hipster programmers.
eg. I've lost count of the number of times I've seen this article referenced on the web and every time I see it I want to bash his head against something solid.
"Making Wrong Code Look Wrong"? Really? How about making wrong code *be* wrong? How about not having it compile at all? How about an SQL library that doesn't accept unsafe strings as parameters?
If you really want to, you could get the compiler to convert unsafe strings to safe strings on the fly ("implicit type conversion") to avoid having to educate the junior programmers.
All SQL injection problems could be eliminated at a stroke, now and forever. How is possible that people aren't doing it?
They're not though, because that would require a strongly typed language...and that's not fashionable.
Joel also rants endlessly against languages with exceptions (there's some of in that article), fails to grok very basic C++ concepts every time they're mentioned (eg. stack unwinding), but the hipsters worship him as some sort of a guru. /rant over
One way to improve the situation is to lower the time spent watching TV since that's a giant information feed.
Depends on what you're watching....
People are going to be hurling left and right for no apparent reason.
Let's hope the youtube servers can handle the extra load.
Sure, but gold has been used as an exchange medium since before the beginning of civilization. Everybody knows what gold is and everybody thinks it has value. The wearing of gold is a symbol of wealth almost anywhere in the world. Part of the US reserve is a big pile of gold in Fort Knox.
Bitcoin? Not so much.
Sure ... if it was just one person handing it to you in person then it would be rude to turn it down. It might be all they can afford.
But it isn't.