Sorry K&R first edition was published 1978 -- "70s". Considering most people considered K&R's book the authority on C at the time, and they played a big role in writing C as we know it, I think I'll take their word for it over yours.
The C crowd has been claiming this for awhile, but not since the 70's. It wasn't until the 90's that the C crowd started insisting that C was a low level language. I've been banging keys through all of this period. You are wrong.
Taken from K&R first edition calls C "not a very high level language", while second edition calls C "a relatively low level language" (page 1). I assume they know better than you.
The real problem here isnt(sic) your ignorance about C, its that you have no idea what "low level" means, just like that wave of 1990's C programmers.
I think we know what "low level" means, and it means something other than what you think it does.
Because some people are passionate about all the major browsers being able to use new stuff? Every web dev knows the pain of not being able to use feature X because either it wasn't implemented in browser y or is buggy in browser y. Being able to actually help bring up all 3 browsers so that they can begin using feature X is exactly why the bulk of OSS patches get made.
Express is limited to 4 cores, and you are correct that there is no automatic backup scheduling feature, but most backup software (not a straight file copy) does a shadow copy and should work just fine.
The simple truth is that you need to line up a long term (9-12 month) freelance contract before you quit your day job. Take 50% of your paycheck and sock it away into a savings (or stock market) account. Then you are set. When you are between jobs, draw from that account. When you are working, then deposit into that account 50%. You'll be set with a 9-12 month cushion after your first gig. When you get down to the last 2-3 months, consider looking for a full time job again. Rinse, repeat as necessary (although, I haven't ever had to go back to full-time, yet).
This doesn't happen if your USB device properly supports USB serial numbers. The problem only exists if windows has to generate a semi-unique serial number for the device because it decided not to implement it.
Common carriers are concerned only with the layer responsible for directing the connection from sender to receiver.
Well, sort of, but port addresess are typically considered part of the address, which is in the TCP/UDP header. I don't know many network analysts that consider that part of the "content". Today's "common carriers" do in fact concern themselves with more than just the layer responsible for directing the connection from sender to receiver. They also check the priority (Also in the headers for IP), and they ask for signatures, they can ask for payment, they can redirect, etc etc. Your simplistic view is simply unfounded in the other common carriers as well.
The packet header is quite easy to see, and your analogy is like saying the Post office can't be a common carrier because they read the envelope to get the address, so the are already inspecting the mail. There is a huge difference between reading an IP or TCP/UP header and trying to piece together a stream of packets in order to determine the content.
You may not be a "1%-er", but to the rest of the world, you are probably a "10%-er". Cry more about having to give up some of your stuff so they can raise their standard of living. It's only fair.
I may be confused, but the older Haswell line had 40 PCI lines directly off the CPU and either 4 or 8 off the chipset. The newer architecture drops the CPU to having only 16 lanes directly off of it, and the chipset now has up to 24. 40+8 in the old, and 16+24 in the new is a downgrade, right?
With most motherboards having a SATA controller, USB 3.1 controller, network card (where are the 10GB network ports???), and sound. Then drop in a couple video cards (32 lanes), a M.2 SSD (4 lanes) and you are either out of lanes or real close. I also need 4 lanes for my RAID controller so I'll likely need to find a motherboard that has a PCI-E switch because the CPU/chipset have run out.
Sorry, that should have read prepared statements incur an initial overhead, so for one-off queries they are slower, but actually executing them is faster.
It's not really an issue with prepared statements. Prepared statements are just a form of pre-compilation. You just want parameterized queries, which is sort of related (prepared statements are usually parameterized, but not always).
Prepared statements are usually slower than non-prepared statements (depends on environment, database, etc), so if it is a one-off query that won't be reused then typically you don't want to prepare it. For queries you are calling over and over, or are calling repeatedly, then you want to prepare it.
Facebook has never been a common carrier. Like all websites, they can (and do) remove content when it infringes copyright. Unlike your ISP or phone which they don't monitor the content (and don't have the capabilities to monitor it all in real time -- supposedly).
I don't mind "daily meetings" with people on my own team (2-4 people). We do them, but we don't call them meetings. It's just us sitting and talking.
If the group is larger than that, then there is likely a high noise to signal ratio on them saying anything I would ever need, and it would be more useful to not sit and listen to it because if I ever need the answer, I would likely go to them and ask directly. So overall stuff, like bi-weekly meetings may be useful but anything more common than that is use time wasting.
Well except that only one machine on my network has to download it, and then every other machine on my local network grabs it from the one that has it, which not only helps lower my usage towards the data cap, it also helps ISPs for the same reason (and keeps the transfers on their network as well) which helps alleviate congestion from the ISP to the backbone(s).
I can see the point, but... Comcast hasn't sold "unlimited" internet in years (I think it's been close to 5 years no). They've stated the caps in the fine print, along with the "up to x mbps download/x mbs upload" for a very, very long time. I can't speak for any other cable provider.
No. She didn't eat the food she ordered. Perhaps if she ate it all then you would have a valid argument. It wasn't an all you can pick apart on eat some of what you order place.
Slashdot Mirror
Sorry K&R first edition was published 1978 -- "70s". Considering most people considered K&R's book the authority on C at the time, and they played a big role in writing C as we know it, I think I'll take their word for it over yours.
The C crowd has been claiming this for awhile, but not since the 70's. It wasn't until the 90's that the C crowd started insisting that C was a low level language. I've been banging keys through all of this period. You are wrong.
Taken from K&R first edition calls C "not a very high level language", while second edition calls C "a relatively low level language" (page 1). I assume they know better than you.
The real problem here isnt(sic) your ignorance about C, its that you have no idea what "low level" means, just like that wave of 1990's C programmers.
I think we know what "low level" means, and it means something other than what you think it does.
Yeah, taken from an old three stooges episode. And it worked for the first two, unfortunately, the third had a id labelled PULL.
Because some people are passionate about all the major browsers being able to use new stuff? Every web dev knows the pain of not being able to use feature X because either it wasn't implemented in browser y or is buggy in browser y. Being able to actually help bring up all 3 browsers so that they can begin using feature X is exactly why the bulk of OSS patches get made.
Express is limited to 4 cores, and you are correct that there is no automatic backup scheduling feature, but most backup software (not a straight file copy) does a shadow copy and should work just fine.
The simple truth is that you need to line up a long term (9-12 month) freelance contract before you quit your day job. Take 50% of your paycheck and sock it away into a savings (or stock market) account. Then you are set. When you are between jobs, draw from that account. When you are working, then deposit into that account 50%. You'll be set with a 9-12 month cushion after your first gig. When you get down to the last 2-3 months, consider looking for a full time job again. Rinse, repeat as necessary (although, I haven't ever had to go back to full-time, yet).
This doesn't happen if your USB device properly supports USB serial numbers. The problem only exists if windows has to generate a semi-unique serial number for the device because it decided not to implement it.
Thank you.
Common carriers are concerned only with the layer responsible for directing the connection from sender to receiver.
Well, sort of, but port addresess are typically considered part of the address, which is in the TCP/UDP header. I don't know many network analysts that consider that part of the "content". Today's "common carriers" do in fact concern themselves with more than just the layer responsible for directing the connection from sender to receiver. They also check the priority (Also in the headers for IP), and they ask for signatures, they can ask for payment, they can redirect, etc etc. Your simplistic view is simply unfounded in the other common carriers as well.
The packet header is quite easy to see, and your analogy is like saying the Post office can't be a common carrier because they read the envelope to get the address, so the are already inspecting the mail. There is a huge difference between reading an IP or TCP/UP header and trying to piece together a stream of packets in order to determine the content.
You may not be a "1%-er", but to the rest of the world, you are probably a "10%-er". Cry more about having to give up some of your stuff so they can raise their standard of living. It's only fair.
Do you have an example, ruling, or law that says that, because that does not follow my understanding of how the federal government SHOULD work.
I may be confused, but the older Haswell line had 40 PCI lines directly off the CPU and either 4 or 8 off the chipset. The newer architecture drops the CPU to having only 16 lanes directly off of it, and the chipset now has up to 24. 40+8 in the old, and 16+24 in the new is a downgrade, right?
With most motherboards having a SATA controller, USB 3.1 controller, network card (where are the 10GB network ports???), and sound. Then drop in a couple video cards (32 lanes), a M.2 SSD (4 lanes) and you are either out of lanes or real close. I also need 4 lanes for my RAID controller so I'll likely need to find a motherboard that has a PCI-E switch because the CPU/chipset have run out.
You forgot magic_quotes, lol.
Sorry, that should have read prepared statements incur an initial overhead, so for one-off queries they are slower, but actually executing them is faster.
It's not really an issue with prepared statements. Prepared statements are just a form of pre-compilation. You just want parameterized queries, which is sort of related (prepared statements are usually parameterized, but not always).
Prepared statements are usually slower than non-prepared statements (depends on environment, database, etc), so if it is a one-off query that won't be reused then typically you don't want to prepare it. For queries you are calling over and over, or are calling repeatedly, then you want to prepare it.
Facebook has never been a common carrier. Like all websites, they can (and do) remove content when it infringes copyright. Unlike your ISP or phone which they don't monitor the content (and don't have the capabilities to monitor it all in real time -- supposedly).
I don't mind "daily meetings" with people on my own team (2-4 people). We do them, but we don't call them meetings. It's just us sitting and talking.
If the group is larger than that, then there is likely a high noise to signal ratio on them saying anything I would ever need, and it would be more useful to not sit and listen to it because if I ever need the answer, I would likely go to them and ask directly. So overall stuff, like bi-weekly meetings may be useful but anything more common than that is use time wasting.
And when they convert to IPv6, the problem goes away.
Well except that only one machine on my network has to download it, and then every other machine on my local network grabs it from the one that has it, which not only helps lower my usage towards the data cap, it also helps ISPs for the same reason (and keeps the transfers on their network as well) which helps alleviate congestion from the ISP to the backbone(s).
I forget which exactly, but one (very large) hardware manufacturer distributes driver/manuals through it as well.
I can see the point, but... Comcast hasn't sold "unlimited" internet in years (I think it's been close to 5 years no). They've stated the caps in the fine print, along with the "up to x mbps download/x mbs upload" for a very, very long time. I can't speak for any other cable provider.
Who said anything about illegal video collections? You can download them right off iTunes or Amazon.
Should she have sued them?
No. She didn't eat the food she ordered. Perhaps if she ate it all then you would have a valid argument. It wasn't an all you can pick apart on eat some of what you order place.
SpiderOak seems to charge $25/month for 5TB of storage. I don't see any unlimited options.