He's not talking about "exacting specifications", he's talking about the standard fucking 4- or 5-wire connection that most normal thermostats have been using for decades. (The one that somehow operates relays off of 24VAC.) It's a weird spec, but it's a well known one. Even then, there are still home HVAC manufacturers out there that insist on their own special snowflake wiring.
It is also completely impossible to make a smart thermostat that doesn't expose itself to inbound connections from everywhere. I have one that connects out to the cloud service every 3-5 minutes. (It also doesn't have a fancy color display for those l33t pwnz0r screens.) So when you make a change from their web page it may take a few minutes before it happens, but it it's not being a port slut to every kiddie scan out there.
They were the first company to drop PS2 ports in favor of USB.
They never used PS2, they used their own ADB. And even after they stopped putting ADB ports on the back of computers, they still used ADB for their laptop keyboards until they went with Intel.
Late-2011 17" here, bought it in 2012 when they were discontinued, 16GB RAM and a 480GB SSD (from about two years ago). The trackpad has worn out, but I have a replacement on order. I immediately downgraded it to 10.6.8 (it shipped with 10.7), and only recently upgraded to 10.9. I also recently purchased a used Core i7 Mac Mini (6,2) which I haven't upgraded from 8GB RAM yet.
I had one PPC and two Intel Aluminum era Powerbooks, and that case was flimsy crap (for instance, CDs wouldn't eject because the case frame went out of alignment). The Unibody is a lot more sturdy, and mine has been through more than its share of abuse and is still ticking, aside from the trackpad.
Current Apple hardware isn't as good as it was back in 2011 before they became obsessed with Retina displays and gluing shit together, but it still isn't quite as bad as the 4-digit PowerPC era.
There are 365 days in a year (sometimes 366), and many places in the world have only had proper temperature records kept for only 100-150 years. Thus the chance of any random day having a record temperature (among recorded temperatures) is not bad at all.
It didn't matter, really, the company that built MF went out of business due to the economic crash due to the destruction of the second death star. Any government run by people who can force-choke you certainly doesn't have to pay outstanding bills for in-progress projects that were destroyed by rebel terrorists.
If only there were a way to get television without paying money to some company, maybe some kind of wireless television? But it would have to be unencrypted, and you would have to be able to get equipment for it at regular retail stores.
Seriously, I cut the cord 15 years ago, and have been antenna-only since then. (No Netflix because most of the stuff coming out of Hollywood is garbage, especially the newer stuff. And I already have two free channels that run old garbage movies 7/24.) The digital switch-over has made things a lot better, now I have a MythTV with 4 tuner cards dumping the raw MPEG onto a hard drive where I can do whatever the fuck I want with it. Like, say, keep it.
The only good reason to pay for cable or satellite TV is if you like to watch live sports. Over the past 20 years or so (in the USA), sports have been slowly migrating away from broadcast, though not so much that I still don't regularly get DVR recordings fucked up from weekend games going into overtime.
This was a 4-lane divided US Highway with a grass median. Those tend to be 70 MPH here in Texas. Even 2-lane undivided rural highways are often 70 here. Just because your state wants to be wimpy about it doesn't mean they have actual scientific reasons to do so.
...yes, because of the possibility that someone may cross in front of you when they don't have right of way, like this truck. It was a typical rural US Highway grade crossing intersection, and the truck was turning left onto a side road. The road was long and straight, and as I remember from looking at it on street view, it wasn't hilly, either, and it was daylight, so the truck driver should have had a good view of the oncoming car.
I don't know why the truck driver's part is ignored so much. Well, I know, really, it's because that's so boring that it's not news. If the oncoming car hadn't been a Tesla, but had instead been an ordinary tired driver, none of this would have gone beyond local news.
If braces aren't put on single-line if or else conditions, that leaves the possibility of a bad code merge causing a goto fail situation. In the worst case, if you keep open braces on the same line (1TBS like "} else {"), you add one line over naked statements, which is still better than putting open braces alone on a line.
So basically, it ensures that if a merge or patch slips in an extra line, it doesn't silently cause a change in code flow. It also keeps the unchanged if() expression out of the diffs when the sub-blocks are changed, which makes merges more reliable.
I think you missed his implied meaning of "helpfully pre-deduct". As in it's not a line item on the paycheck or in any accounting system. Nor is it optional.
Well maybe you should try working somewhere other than Silly Valley? I'm sure you could find work as an embedded systems guy (which is basically what you have described) in Austin or Dallas.
It depends on where you live. In Texas, a single guy (fresh grads don't have a family to care for) can do quite okay on 60K. In Silicon Valley you would have a big problem on even 100K.
Far northwest Austin here (just south of Cedar Park), the only thing I've gotten from them is a T-shirt (1XL with no option for a 2XL). The original map made me feel like I was in the boonies. Hell, a freaking Tesla service or showroom place (not sure which yet) even opened nearby in the past few weeks! And I'm moving back to San Antonio, which has at least been chosen as a GF city, so who knows, it might not even set my wait back by much.
If you don't live between, say, Ben White and 2222, you will probably be waiting for a while. If your neighborhood doesn't have above-ground comm wires on poles, you might be waiting even longer. For what it's worth, many years ago TW ran some kind of hammer mole thingy down the back yards in my neighborhood (digging a hole in only one of every 4 yards) to run a soda-can sized pipe though the ground. (They used an actual soda can bottom to cover the end of the pipe when pushing it through the hole!) Who knows if Google would even be able to use that hole.
They also supported a client for Xbox 360 which they dropped support for at the same time as PS2. Rumors I had heard were that MS wasn't happy (at the time) that it supported cross-platform play, but somehow it happened. Both clients could be easily overloaded with lots of players and effects nearby, and good luck finding a working fat PS2 with a hard drive. You could use a first gen PS3 in emulation mode, but it had the same poor performance.
As for just stop updating the PS2 version, they had sort of already done that (the final expansion only had a Japan version), but I get the idea that they were dependent upon their PS2 development systems for creating 3D assets, and that they were using the last working PS2 development systems left in the whole world. They are still releasing updates, but only for things that re-use existing 3D models. The most recent update even listed a bug that sounds like they found a wall hole somewhere in a zone (and a clone of it) that lets you go outside the normal area, and that they can't fix it any time soon.
I just watched them both, and while I think he overdoes it for effect, and some people may dismiss it because it's full of camel memes, he's got some basic points that can't be ignored.
The language and some of its libraries have implicit unexpected behavior (as opposed to the "nasal demons" explicitly undefined behaviors in C), that just isn't something even a well-experienced programmer would expect from a typical programming language, and even with workarounds, there is still unexpected behavior. Arrays being flattened when creating a new hash or put into parameter lists, CGI modules returning a different basic type of variable when a parameter name is repeated (a concept most people wouldn't think of with CGI in any language), and the intersection of both of those problems. Then trying to work around the problems by writing code that makes an assumption that because it didn't come from CGI, well gosh, the data must be okay! That's a recipe for fail.
If cgi.pm simply hadn't gone out of its way to do something weird (by default, and I don't know if you can even turn it off) in an unusual condition that most people don't care about, none of this might even have happened. The hash and parameter splicing problems could still be there, but without the chain of fail leading to them, the remote vulnerabilities wouldn't have happened.
Slashdot Mirror
He's not talking about "exacting specifications", he's talking about the standard fucking 4- or 5-wire connection that most normal thermostats have been using for decades. (The one that somehow operates relays off of 24VAC.) It's a weird spec, but it's a well known one. Even then, there are still home HVAC manufacturers out there that insist on their own special snowflake wiring.
It is also completely impossible to make a smart thermostat that doesn't expose itself to inbound connections from everywhere. I have one that connects out to the cloud service every 3-5 minutes. (It also doesn't have a fancy color display for those l33t pwnz0r screens.) So when you make a change from their web page it may take a few minutes before it happens, but it it's not being a port slut to every kiddie scan out there.
They were the first company to drop PS2 ports in favor of USB.
They never used PS2, they used their own ADB. And even after they stopped putting ADB ports on the back of computers, they still used ADB for their laptop keyboards until they went with Intel.
Late-2011 17" here, bought it in 2012 when they were discontinued, 16GB RAM and a 480GB SSD (from about two years ago). The trackpad has worn out, but I have a replacement on order. I immediately downgraded it to 10.6.8 (it shipped with 10.7), and only recently upgraded to 10.9. I also recently purchased a used Core i7 Mac Mini (6,2) which I haven't upgraded from 8GB RAM yet.
I had one PPC and two Intel Aluminum era Powerbooks, and that case was flimsy crap (for instance, CDs wouldn't eject because the case frame went out of alignment). The Unibody is a lot more sturdy, and mine has been through more than its share of abuse and is still ticking, aside from the trackpad.
Current Apple hardware isn't as good as it was back in 2011 before they became obsessed with Retina displays and gluing shit together, but it still isn't quite as bad as the 4-digit PowerPC era.
Is that some Year of Linux on the Desktop going on?
The State of California has determined that Florida may cause cancer.
I call it normal statistics.
There are 365 days in a year (sometimes 366), and many places in the world have only had proper temperature records kept for only 100-150 years. Thus the chance of any random day having a record temperature (among recorded temperatures) is not bad at all.
Nice math there, it's actually 327.15 kelvins.
It didn't matter, really, the company that built MF went out of business due to the economic crash due to the destruction of the second death star. Any government run by people who can force-choke you certainly doesn't have to pay outstanding bills for in-progress projects that were destroyed by rebel terrorists.
Clearly, we must acquit.
You forgot a motto: "It ain't done 'till Lotus won't run!"
If only there were a way to get television without paying money to some company, maybe some kind of wireless television? But it would have to be unencrypted, and you would have to be able to get equipment for it at regular retail stores.
Seriously, I cut the cord 15 years ago, and have been antenna-only since then. (No Netflix because most of the stuff coming out of Hollywood is garbage, especially the newer stuff. And I already have two free channels that run old garbage movies 7/24.) The digital switch-over has made things a lot better, now I have a MythTV with 4 tuner cards dumping the raw MPEG onto a hard drive where I can do whatever the fuck I want with it. Like, say, keep it.
The only good reason to pay for cable or satellite TV is if you like to watch live sports. Over the past 20 years or so (in the USA), sports have been slowly migrating away from broadcast, though not so much that I still don't regularly get DVR recordings fucked up from weekend games going into overtime.
This was a 4-lane divided US Highway with a grass median. Those tend to be 70 MPH here in Texas. Even 2-lane undivided rural highways are often 70 here. Just because your state wants to be wimpy about it doesn't mean they have actual scientific reasons to do so.
...yes, because of the possibility that someone may cross in front of you when they don't have right of way, like this truck. It was a typical rural US Highway grade crossing intersection, and the truck was turning left onto a side road. The road was long and straight, and as I remember from looking at it on street view, it wasn't hilly, either, and it was daylight, so the truck driver should have had a good view of the oncoming car.
I don't know why the truck driver's part is ignored so much. Well, I know, really, it's because that's so boring that it's not news. If the oncoming car hadn't been a Tesla, but had instead been an ordinary tired driver, none of this would have gone beyond local news.
If braces aren't put on single-line if or else conditions, that leaves the possibility of a bad code merge causing a goto fail situation. In the worst case, if you keep open braces on the same line (1TBS like "} else {"), you add one line over naked statements, which is still better than putting open braces alone on a line.
So basically, it ensures that if a merge or patch slips in an extra line, it doesn't silently cause a change in code flow. It also keeps the unchanged if() expression out of the diffs when the sub-blocks are changed, which makes merges more reliable.
I think you missed his implied meaning of "helpfully pre-deduct". As in it's not a line item on the paycheck or in any accounting system. Nor is it optional.
Your generation screwed everyone
Hey, watch that "your generation" thing. Gen X is just now going over 50. If you mean boomers, you're going to have to say boomers.
for silicon valley employers
Well maybe you should try working somewhere other than Silly Valley? I'm sure you could find work as an embedded systems guy (which is basically what you have described) in Austin or Dallas.
It depends on where you live. In Texas, a single guy (fresh grads don't have a family to care for) can do quite okay on 60K. In Silicon Valley you would have a big problem on even 100K.
Far northwest Austin here (just south of Cedar Park), the only thing I've gotten from them is a T-shirt (1XL with no option for a 2XL). The original map made me feel like I was in the boonies. Hell, a freaking Tesla service or showroom place (not sure which yet) even opened nearby in the past few weeks! And I'm moving back to San Antonio, which has at least been chosen as a GF city, so who knows, it might not even set my wait back by much.
If you don't live between, say, Ben White and 2222, you will probably be waiting for a while. If your neighborhood doesn't have above-ground comm wires on poles, you might be waiting even longer. For what it's worth, many years ago TW ran some kind of hammer mole thingy down the back yards in my neighborhood (digging a hole in only one of every 4 yards) to run a soda-can sized pipe though the ground. (They used an actual soda can bottom to cover the end of the pipe when pushing it through the hole!) Who knows if Google would even be able to use that hole.
They also supported a client for Xbox 360 which they dropped support for at the same time as PS2. Rumors I had heard were that MS wasn't happy (at the time) that it supported cross-platform play, but somehow it happened. Both clients could be easily overloaded with lots of players and effects nearby, and good luck finding a working fat PS2 with a hard drive. You could use a first gen PS3 in emulation mode, but it had the same poor performance.
As for just stop updating the PS2 version, they had sort of already done that (the final expansion only had a Japan version), but I get the idea that they were dependent upon their PS2 development systems for creating 3D assets, and that they were using the last working PS2 development systems left in the whole world. They are still releasing updates, but only for things that re-use existing 3D models. The most recent update even listed a bug that sounds like they found a wall hole somewhere in a zone (and a clone of it) that lets you go outside the normal area, and that they can't fix it any time soon.
Sounds more like The Fifth Element to me. I couldn't find the scene where he has to switch the apartment around a lot, but I found this:
https://www.youtube.com/watch?...
I just watched them both, and while I think he overdoes it for effect, and some people may dismiss it because it's full of camel memes, he's got some basic points that can't be ignored.
The language and some of its libraries have implicit unexpected behavior (as opposed to the "nasal demons" explicitly undefined behaviors in C), that just isn't something even a well-experienced programmer would expect from a typical programming language, and even with workarounds, there is still unexpected behavior. Arrays being flattened when creating a new hash or put into parameter lists, CGI modules returning a different basic type of variable when a parameter name is repeated (a concept most people wouldn't think of with CGI in any language), and the intersection of both of those problems. Then trying to work around the problems by writing code that makes an assumption that because it didn't come from CGI, well gosh, the data must be okay! That's a recipe for fail.
If cgi.pm simply hadn't gone out of its way to do something weird (by default, and I don't know if you can even turn it off) in an unusual condition that most people don't care about, none of this might even have happened. The hash and parameter splicing problems could still be there, but without the chain of fail leading to them, the remote vulnerabilities wouldn't have happened.
I don't look forward to the FCC license I'll need to tape an LED to a coin battery.
Actually they all wind up on the front page. I think you mean where we wish they would go.