Regulation is a necessary part of a free market. Without it then you have thugs, whoever is the biggest pushes everyone else around, which is not freedom.
Irrelevant. You do not need 365 days of sunlight to make solar power useful. What is your proposed alternative here, to double down on coal? Perhaps mandating is not a great idea, but the idea of solar is good.
I am surprised at how many people instantly like to disparage solar power based upon temperature or amount of direct sunlight. If solar can pay for itself for even 3 months out of the year then it shouldn't matter much. Also, for alternate or traditional forms of electricity, having storage capability greatly increases the benefit.
The solar in California makes great sense because the peak electrical usage corresponds to hot days where the sun is out in full. Back in 2000-ish when we had rolling blackouts because of lack of capacity, the problems were the afternoons and not in the middle of the night.
Naw, it's pretty sunny everywhere except San Francisco. The fog mysteriously vanishes at the city's borders on some days, and this is most often during mornings and evenings. But you do not need direct sunlight to generate electricity with solar panels. The days with the most electricity consumption are inevitably hot sunny days when the air conditioners are on.
And it's always "call to check for availability", because they won't tell you what speeds you will likely get until you're on the hook with a heavy hitting sales person.
I don't even get 25mbs down. I pay for 20Mbps but get 24. I used to have 12Mbps and I could stream HD TV just fine with that. I don't really see the need to go faster for the large increase in cost this would entail.
My mother gets 1Mbit on her u-verse DSL, and lives in a town. That's still better than the standard DSL I had that was 768kbit, but still a whole lot less than my u-verse. She doesn't stream anything and just uses the web so that's fast enough. I wouldn't call it broadband though. She could get broadband, but it means having the cable company run a cable from the closest box and the final monthly price would be far outside of her budget.
Not sure if mobile phones help here, the monthly cost on them for a data plan is outrageous everywhere, and most don't let you use it as a internet source without paying extra. (and mobile coverage is amazingly spotty if you're not in a big city)
Maybe they could program the robot to run around in circles screaming when this happens? It would let the other workers empathize with it and realize that they're not the only with with burning red eyes.
You need to think this through and not fall into a partisan trap. The left wants more power for a leftist government, and the right wants more power for a rightist government. Any candidate with enough integrity to be for the people won't get elected for the reason of avoiding gutter politics.
At the time, the PC wasn't dominant except in homes. The corporate world was still using a lot of workstations, especially in technical areas which was where the web was more popular originally. When workstations started being replaced by lower powered PCs a lot of technical users still stuck to Netscape (and it's honory child, Mozilla). Many corporations had policies against using Internet Explorer, but other corporations had IT support groups that just did whatever Micrososft asked and they'd go and create services that required ActiveX. So it really was the migration to the PC in the workplace that killed Netscape the most. Still, IE was just barely in the "serviceable browser" category.
I don't understand not gaining "mindshare" from developers. Does this matter still? Are developers still reluctant to make browser independent pages? It's one thing to worry that users don't like it but it should be irrelevant if web developers like it or not. The days of coding only for IE should be relegated to ancient history.
All the more reason that you should never give any personal financial data to your phone. It can't charge you if it doesn't know your credit or bank card number.
Even native English speakers in voice mail have hilarious Microsoft transcriptions. Even though it's out there, I don't think this service is really ready and was rolled out to customers by mistake. It's not getting better over time, I had a Skype voice mail last week that was nearly gibberish.
I have U-verse, but it's not DSL it's VDSL (fiber to near neighborhood). It's not as fast as cable but cheaper more than enough for streaming if you don't have kids. Ie, started at 12Mbps but am at 24 now (while only paying for 20). It's not 4K but who cares about that hipster stuff. If you don't need HD then you can get away with even less.
You almost do need a DVR with it. I haven't tried it because when I got rid of my satellite it meant that the DVR went with it. I was watching so little television on broadcast channels that it wasn't worth buying a brand new DVR just for that purpose.
The problem with broadcast is that you just don't get a lot of stuff, and what you do get is on fixed times and without repeats at alternate times. So if you get stuck in traffic then you miss your show. Even back in the 90s I was using a VHS to automatically record stuff. Ie, if you want to see the Big Bang Theory, example only, then tbhe new episodes are only on for one hour on one day of the week. Even the extremely crappy CBS now, the worst streaming service ever, is better than that for watching TBBT. (well almost, since it won't play on my computer at all anymore, even with all filters blocked and privacy disabled)
I liked my DirecTV when I had it. It was digital and so much better than the crappy analog cable I could get by default, and half the price of the digital cable option. Then after a couple years it integrated with Tivo and was awesome, vastly better to any other set top box DVR I've seen. I only got rid of it because over time I was watching less and less television while the price had slowly been creeping up.
But we have essentially exhausted all IP addresses already. We got around it with a hack called NAT. There are some unassigned addresses still but you can't assign them out to just anyone because they belong to particular companies (Ie, IBM).
Remember too, IPv4 was designed when the internet only had thousands of nodes and was meant to support millions of nodes. Today we need support for billions of nodes or more. The IPv4 style just won't cut it. You can't just add a couple more bytes and think that the problem is solved.
Seeing someone object about going from IPv4 to IPv6 is like freeing someone from a cage who then complains that standing up straight is unnatural.
If you're a regular user then even IPv4 can be complicated... I think you mean as a regular sysadmin, or regular network support guy.
IPv6 is in hex because in the dotted style of IPv4 you'd have 16 numbers. Not just 2 extra octets. So your address might be 1.2.3.4.5.6.7.8.9.10.11.12.13.14.15.16. Do you really need to know all those numbers? A colon is the same as a dot, so that's easy. Hex is easy for anyone who knows about IPv4 anyway, so no worries there. The only snag is the double colon '::', which is pretty easy to learn, and you can suppress leading zeros in groups (ie,:;1 is your localhost loopback, same as 127.0.0.1). The only hard part is that there are more numbers.
The only slight advantage you get with IPv4 is that *some* people can readily recognize prefixes for their local subnets and such. Sure, in your building that you are an IT goon for you can recognize addresses by visual inspection, but if you have 20 million nodes you have to deal with then you need a different way of working.
A lot of things don't change too much - you will probably have only a handful of 64 bit prefixes that you ever need to worry about in practice and you learn to recognize them. FE80:: is the link-local prefix, which is often used in the same context that you will see ipv4 private addresses (192.168.0.0/16, etc).
So as a company you can get a unique 48 bits for network address, you have 16 bits to do whatever you want with subnetting, and combine with the 64 bits of the interface address of the device. There's a huge amount of stuff you can do with that that you could never do with IPv4.
Slashdot Mirror
Regulation is a necessary part of a free market. Without it then you have thugs, whoever is the biggest pushes everyone else around, which is not freedom.
Irrelevant. You do not need 365 days of sunlight to make solar power useful. What is your proposed alternative here, to double down on coal? Perhaps mandating is not a great idea, but the idea of solar is good.
I am surprised at how many people instantly like to disparage solar power based upon temperature or amount of direct sunlight. If solar can pay for itself for even 3 months out of the year then it shouldn't matter much. Also, for alternate or traditional forms of electricity, having storage capability greatly increases the benefit.
The solar in California makes great sense because the peak electrical usage corresponds to hot days where the sun is out in full. Back in 2000-ish when we had rolling blackouts because of lack of capacity, the problems were the afternoons and not in the middle of the night.
Naw, it's pretty sunny everywhere except San Francisco. The fog mysteriously vanishes at the city's borders on some days, and this is most often during mornings and evenings. But you do not need direct sunlight to generate electricity with solar panels. The days with the most electricity consumption are inevitably hot sunny days when the air conditioners are on.
There's always a violent group willing and able to join any available protest.
And it's always "call to check for availability", because they won't tell you what speeds you will likely get until you're on the hook with a heavy hitting sales person.
I don't even get 25mbs down. I pay for 20Mbps but get 24. I used to have 12Mbps and I could stream HD TV just fine with that. I don't really see the need to go faster for the large increase in cost this would entail.
My mother gets 1Mbit on her u-verse DSL, and lives in a town. That's still better than the standard DSL I had that was 768kbit, but still a whole lot less than my u-verse. She doesn't stream anything and just uses the web so that's fast enough. I wouldn't call it broadband though. She could get broadband, but it means having the cable company run a cable from the closest box and the final monthly price would be far outside of her budget.
Not sure if mobile phones help here, the monthly cost on them for a data plan is outrageous everywhere, and most don't let you use it as a internet source without paying extra. (and mobile coverage is amazingly spotty if you're not in a big city)
Can you remember the jingle?
Maybe they could program the robot to run around in circles screaming when this happens? It would let the other workers empathize with it and realize that they're not the only with with burning red eyes.
You need to think this through and not fall into a partisan trap. The left wants more power for a leftist government, and the right wants more power for a rightist government. Any candidate with enough integrity to be for the people won't get elected for the reason of avoiding gutter politics.
I'm waiting for the first honest advertisement. "An adequate product for adequate people."
At the time, the PC wasn't dominant except in homes. The corporate world was still using a lot of workstations, especially in technical areas which was where the web was more popular originally. When workstations started being replaced by lower powered PCs a lot of technical users still stuck to Netscape (and it's honory child, Mozilla). Many corporations had policies against using Internet Explorer, but other corporations had IT support groups that just did whatever Micrososft asked and they'd go and create services that required ActiveX. So it really was the migration to the PC in the workplace that killed Netscape the most. Still, IE was just barely in the "serviceable browser" category.
I don't understand not gaining "mindshare" from developers. Does this matter still? Are developers still reluctant to make browser independent pages? It's one thing to worry that users don't like it but it should be irrelevant if web developers like it or not. The days of coding only for IE should be relegated to ancient history.
But it's a city court. Should a ruling from just a city court affect an entire country this way?
All the more reason that you should never give any personal financial data to your phone. It can't charge you if it doesn't know your credit or bank card number.
Even native English speakers in voice mail have hilarious Microsoft transcriptions. Even though it's out there, I don't think this service is really ready and was rolled out to customers by mistake. It's not getting better over time, I had a Skype voice mail last week that was nearly gibberish.
I have U-verse, but it's not DSL it's VDSL (fiber to near neighborhood). It's not as fast as cable but cheaper more than enough for streaming if you don't have kids. Ie, started at 12Mbps but am at 24 now (while only paying for 20). It's not 4K but who cares about that hipster stuff. If you don't need HD then you can get away with even less.
Well, the shitty VDSL service is the only option I have other than selling my soul to the devil and going with Comcast.
You almost do need a DVR with it. I haven't tried it because when I got rid of my satellite it meant that the DVR went with it. I was watching so little television on broadcast channels that it wasn't worth buying a brand new DVR just for that purpose.
The problem with broadcast is that you just don't get a lot of stuff, and what you do get is on fixed times and without repeats at alternate times. So if you get stuck in traffic then you miss your show. Even back in the 90s I was using a VHS to automatically record stuff. Ie, if you want to see the Big Bang Theory, example only, then tbhe new episodes are only on for one hour on one day of the week. Even the extremely crappy CBS now, the worst streaming service ever, is better than that for watching TBBT. (well almost, since it won't play on my computer at all anymore, even with all filters blocked and privacy disabled)
I liked my DirecTV when I had it. It was digital and so much better than the crappy analog cable I could get by default, and half the price of the digital cable option. Then after a couple years it integrated with Tivo and was awesome, vastly better to any other set top box DVR I've seen. I only got rid of it because over time I was watching less and less television while the price had slowly been creeping up.
But we have essentially exhausted all IP addresses already. We got around it with a hack called NAT. There are some unassigned addresses still but you can't assign them out to just anyone because they belong to particular companies (Ie, IBM).
Great, then they'll know how to cut and past an IPv6 address into their Minecraft settings.
Remember too, IPv4 was designed when the internet only had thousands of nodes and was meant to support millions of nodes. Today we need support for billions of nodes or more. The IPv4 style just won't cut it. You can't just add a couple more bytes and think that the problem is solved.
Seeing someone object about going from IPv4 to IPv6 is like freeing someone from a cage who then complains that standing up straight is unnatural.
If you're a regular user then even IPv4 can be complicated... I think you mean as a regular sysadmin, or regular network support guy.
IPv6 is in hex because in the dotted style of IPv4 you'd have 16 numbers. Not just 2 extra octets. So your address might be 1.2.3.4.5.6.7.8.9.10.11.12.13.14.15.16. Do you really need to know all those numbers? A colon is the same as a dot, so that's easy. Hex is easy for anyone who knows about IPv4 anyway, so no worries there. The only snag is the double colon '::', which is pretty easy to learn, and you can suppress leading zeros in groups (ie, :;1 is your localhost loopback, same as 127.0.0.1). The only hard part is that there are more numbers.
The only slight advantage you get with IPv4 is that *some* people can readily recognize prefixes for their local subnets and such. Sure, in your building that you are an IT goon for you can recognize addresses by visual inspection, but if you have 20 million nodes you have to deal with then you need a different way of working.
A lot of things don't change too much - you will probably have only a handful of 64 bit prefixes that you ever need to worry about in practice and you learn to recognize them. FE80:: is the link-local prefix, which is often used in the same context that you will see ipv4 private addresses (192.168.0.0/16, etc).
So as a company you can get a unique 48 bits for network address, you have 16 bits to do whatever you want with subnetting, and combine with the 64 bits of the interface address of the device. There's a huge amount of stuff you can do with that that you could never do with IPv4.