That's a big part of why it is insanely expensive to build anything. It would already be a challenge because of New York's density, geographical constraints, and cost of living, but the mob and the politicians make an already bad situation drastically worse.
We heavily invested in roads and bridges instead. It made sense in most places, even most cities except the very largest, because in the U.S. even most cities are not densely populated enough to support cost-effective transit. But now those, too, are falling apart. We spend tons on infrastructure but get very, very little in return for it apart from what was already built generations ago. Mainly just upkeep, and just bare minimum upkeep at that.
Most folks in most urban parts of the U.S. do recognize that our infrastructure is sorely lacking. It's hard not to notice when city streets (e.g., in Cleveland, Ohio) have potholes that have been known to swallow entire cars. Or when old bridges decide to collapse and fall into rivers (e.g., Minneapolis, MN, a few years back). Or 3 significant NJ Transit crashes in the space of a single year. We are very, very good at some things, but infrastructure just isn't one of them.
IIRC: More than 50% of Manhattanites carless. But fewer in the outer boroughs and especially Staten Island, much of which is very suburban in character.
Huge problem in NYC for sure. It is part of why the cost of living is so high. You pay off the unions as well as the government, and good, if you want to get anything done. They justify it because of the cost of living, asking for more, pushing that cost higher; lather, rinse, repeat. Huge death spiral creating bubbles of all kinds that will burst sooner or later. Among several reasons why, though I love visiting NYC, I would never want to live there.
I don't know. Anything that wants to survive our winters needs to be coated or painted anyway, as do lane markings, etc., so I'm guessing it's just a question of reformulating the paint so as to be more easily detectable by sensors. Keep in mind that over time autonomous vehicles are expected to replace manually driven ones, so I likewise expect the street and road infrastructure to adapt over time.
I've had near-misses involving obstacles that were the same color as the road, including road barriers in unexpected/odd places. But they were near-misses, rather than wrecks, because I had the experience to drive more slowly and cautiously when I could not be assured that the road is entirely clear, including when I'm driving in an area I haven't been before, or when there is construction nearby. Perhaps that kind of judgment can be improved on in the future? Also as mentioned by others, barriers in unexpected places might be painted so as to be maximally noticeable by humans and perhaps even by radar. The bar today is that a self-driving vehicle needs to work with unmodified roads, but I would recommend that future road design and maintenance take self-driving vehicles into account and to make it as easy as possible for them to know if they are at risk of driving into something they shouldn't.
A pic exists somewhere with me sitting next to Clippy in Microsoft's Cleveland area office. Had to be there for a work conference (I do use MS products in my day job), and they all knew I was a Linux geek, so they thought that would be hilarious. In hindsight I suppose it sort of is. Wish I'd gotten a copy. BTW . . . isn't every Windows version the "YTFE"??
The advent of laptops, thumb drives and mobile devices long ago rendered life inside the firewall or DMZ just as scary as life outside it. Yes, my experience is that servers are left running as long as they can be, and they are often very vulnerable. Companies typically value stability over security; in their view, a security upgrade is as likely to cause them inconvenience as would an overt security breach. And not to turn this into a yet another Windows versus Linux debate, but Windows servers are typically administered through the GUI, which increases their attack surface, one which you don't need to use necessarily, but most people do, because it's more convenient than to learn how to do Powershell or other command-line scripting. While many Linux servers do have GUIs (contrary to what I would consider best practice), they are strictly optional, and in my experience, Linux admins are not afraid of the command line as are some (not all) of their Windows counterparts.
I'll admit a certain amount of distrust of Intel right now. They did not behave as I expected them to. AMD may one day prove to be just as bad, or even worse, but, as of right now, I consider them as having by far the better track record, and I will give them the benefit of the doubt for as long as there is doubt to give them the benefit of.
Still waiting for Spectre patches to hit stable gentoo-sources. Meltdown wasn't a concern for AMD. Also, don't the retpoline patches depend on patched CPU microcode?
I evaluate desktop CPUs based on performance per unit cost, and laptops based on that *plus* power usage, battery life, etc. Usually, that favored AMD on the desktop but Intel on the laptop. But, now, I have to consider the large possibility that security concerns will obsolete a laptop before anything else does. So, now, I keep using AMD on desktops, but now favor AMD on laptops as well, which, previously, I did not.
Exactly. If I expected to upgrade every 2-3 years, I'd be less irritated. But today I hope to keep even a mid-range laptop or desktop around for at least 5 and hopefully longer. And I've had plenty of much older machines retired from their main use but still doing other useful work. I now have to factor into my purchasing decisions that if Intel commits another abomination like this, it won't replace bubkes, and thus my options are (a) crap (replace it outright, long before I'd have done otherwise); or (b) crappier (risk a potentially life-changing security breach).
Yeah. Shame on them too for that. But then I haven't needed to have an AMD chip re-microcoded, much less replaced. The Honda I drive has a much shorter factory warranty than the Hyundai I don't, but that doesn't bother me so much because I know from much experience (mine plus that of countless others) that a well-maintained Honda will typically last a very long time and the warranty won't likely be needed.
Nah. That was a long time ago. I don't work with my muscles anymore. Just with my apparently undersized but still bigger than Intel troll's brain, and other stuff.
Yeah, that could be taken several different ways, but let's just say that even though I'm well past the prime of my youth, I rarely get complaints about either one.
There is no such thing as the Mafia. Pure fiction. So that is NOT my Mafia name. No such thing. But let's just say that long ago, I used to work in debt collection, and back in those days, it was a very bad idea to not pay my boss whatever money he was owed. Or to try to troll me on Slashdot.:)
None of this makes me feel any more inclined to favor Intel over AMD. This isn't their first "brown paper bag" bug and I doubt it will be their last. If only a 3 year warranty is even offered on some of the highest-end chips they made at the time, when some new cars are warrantied for 10, I think that says something really awful about even Intel's own assessment of whether its products can be supported in the long term. AMD may or may not be drastically better, but Intel has set a very low bar, and it is going to take them serious time to earn back my business, assuming they ever do.
I'm sorry, but if I'm investing in a high-end, server-class CPU, I expect it to be supported for as long as is reasonably possible. If they said they weren't updating 10 year old Celerons or Atoms, that might be understandable. But Xeons? Let's just say I don't plan to every buy one again, at least so long as AMD represents a reasonable alternative. In fact, I will always stick with AMD (as I long have, for other reasons) until and unless Intel makes some kind of definite, enforceable support commitment.
There are multiple Gentoo and Slackware derivatives as well. I've used and loved Gentoo for over a decade now. AFAIK, systemd is optional on both (though I don't think Gnome will run properly without it).
It never quite reaches 220F. It only feels that way. The -50F however is theoretically possible. (I'm in Cleveland, just over 2 hours away, but much closer to Lake Erie, and thus much snowier and more humid on average. The Cleveland economy really sucks compared to Pittsburgh, but there are tech jobs nonetheless, and a surprising amount of culture, and one of the nation's lowest costs of living.)
Unfortunately, in the past 10-15 years, rent has skyrocketed in the outer boroughs, such that Brooklyn rents rival those in Manhattan, the other boroughs aren't far behind, and even really rough areas like Bushwyck and East New York are starting to see extreme increases in rents.
That *BSD* style licenses are or are not "more free" is a matter of perspective. My view is that non-copylefted licenses may do too much to preserve the freedom of those who would embrace/extend/extinguish Free Software, while copylefted licenses encourage the protection of the users' freedoms instead. This distinction would be moot if there were not evil, rent-seeking organizations and individuals who wish to extort the users of formerly free software, plus "laws" that empower and embolden them. Free would simply mean Free. However, there are, and, for as long as there are, I do view copyleft as an vital mechanism to ensure that the most important pieces of software remain free.
Slashdot Mirror
That's a big part of why it is insanely expensive to build anything. It would already be a challenge because of New York's density, geographical constraints, and cost of living, but the mob and the politicians make an already bad situation drastically worse.
We heavily invested in roads and bridges instead. It made sense in most places, even most cities except the very largest, because in the U.S. even most cities are not densely populated enough to support cost-effective transit. But now those, too, are falling apart. We spend tons on infrastructure but get very, very little in return for it apart from what was already built generations ago. Mainly just upkeep, and just bare minimum upkeep at that.
Most folks in most urban parts of the U.S. do recognize that our infrastructure is sorely lacking. It's hard not to notice when city streets (e.g., in Cleveland, Ohio) have potholes that have been known to swallow entire cars. Or when old bridges decide to collapse and fall into rivers (e.g., Minneapolis, MN, a few years back). Or 3 significant NJ Transit crashes in the space of a single year. We are very, very good at some things, but infrastructure just isn't one of them.
IIRC: More than 50% of Manhattanites carless. But fewer in the outer boroughs and especially Staten Island, much of which is very suburban in character.
Huge problem in NYC for sure. It is part of why the cost of living is so high. You pay off the unions as well as the government, and good, if you want to get anything done. They justify it because of the cost of living, asking for more, pushing that cost higher; lather, rinse, repeat. Huge death spiral creating bubbles of all kinds that will burst sooner or later. Among several reasons why, though I love visiting NYC, I would never want to live there.
I don't know. Anything that wants to survive our winters needs to be coated or painted anyway, as do lane markings, etc., so I'm guessing it's just a question of reformulating the paint so as to be more easily detectable by sensors. Keep in mind that over time autonomous vehicles are expected to replace manually driven ones, so I likewise expect the street and road infrastructure to adapt over time.
I've had near-misses involving obstacles that were the same color as the road, including road barriers in unexpected/odd places. But they were near-misses, rather than wrecks, because I had the experience to drive more slowly and cautiously when I could not be assured that the road is entirely clear, including when I'm driving in an area I haven't been before, or when there is construction nearby. Perhaps that kind of judgment can be improved on in the future? Also as mentioned by others, barriers in unexpected places might be painted so as to be maximally noticeable by humans and perhaps even by radar. The bar today is that a self-driving vehicle needs to work with unmodified roads, but I would recommend that future road design and maintenance take self-driving vehicles into account and to make it as easy as possible for them to know if they are at risk of driving into something they shouldn't.
A pic exists somewhere with me sitting next to Clippy in Microsoft's Cleveland area office. Had to be there for a work conference (I do use MS products in my day job), and they all knew I was a Linux geek, so they thought that would be hilarious. In hindsight I suppose it sort of is. Wish I'd gotten a copy. BTW . . . isn't every Windows version the "YTFE"??
The advent of laptops, thumb drives and mobile devices long ago rendered life inside the firewall or DMZ just as scary as life outside it. Yes, my experience is that servers are left running as long as they can be, and they are often very vulnerable. Companies typically value stability over security; in their view, a security upgrade is as likely to cause them inconvenience as would an overt security breach. And not to turn this into a yet another Windows versus Linux debate, but Windows servers are typically administered through the GUI, which increases their attack surface, one which you don't need to use necessarily, but most people do, because it's more convenient than to learn how to do Powershell or other command-line scripting. While many Linux servers do have GUIs (contrary to what I would consider best practice), they are strictly optional, and in my experience, Linux admins are not afraid of the command line as are some (not all) of their Windows counterparts.
I'll admit a certain amount of distrust of Intel right now. They did not behave as I expected them to. AMD may one day prove to be just as bad, or even worse, but, as of right now, I consider them as having by far the better track record, and I will give them the benefit of the doubt for as long as there is doubt to give them the benefit of.
Still waiting for Spectre patches to hit stable gentoo-sources. Meltdown wasn't a concern for AMD. Also, don't the retpoline patches depend on patched CPU microcode?
I evaluate desktop CPUs based on performance per unit cost, and laptops based on that *plus* power usage, battery life, etc. Usually, that favored AMD on the desktop but Intel on the laptop. But, now, I have to consider the large possibility that security concerns will obsolete a laptop before anything else does. So, now, I keep using AMD on desktops, but now favor AMD on laptops as well, which, previously, I did not.
Exactly. If I expected to upgrade every 2-3 years, I'd be less irritated. But today I hope to keep even a mid-range laptop or desktop around for at least 5 and hopefully longer. And I've had plenty of much older machines retired from their main use but still doing other useful work. I now have to factor into my purchasing decisions that if Intel commits another abomination like this, it won't replace bubkes, and thus my options are (a) crap (replace it outright, long before I'd have done otherwise); or (b) crappier (risk a potentially life-changing security breach).
Yeah. Shame on them too for that. But then I haven't needed to have an AMD chip re-microcoded, much less replaced. The Honda I drive has a much shorter factory warranty than the Hyundai I don't, but that doesn't bother me so much because I know from much experience (mine plus that of countless others) that a well-maintained Honda will typically last a very long time and the warranty won't likely be needed.
Nah. That was a long time ago. I don't work with my muscles anymore. Just with my apparently undersized but still bigger than Intel troll's brain, and other stuff.
Yeah, that could be taken several different ways, but let's just say that even though I'm well past the prime of my youth, I rarely get complaints about either one.
There is no such thing as the Mafia. Pure fiction. So that is NOT my Mafia name. No such thing. But let's just say that long ago, I used to work in debt collection, and back in those days, it was a very bad idea to not pay my boss whatever money he was owed. Or to try to troll me on Slashdot. :)
None of this makes me feel any more inclined to favor Intel over AMD. This isn't their first "brown paper bag" bug and I doubt it will be their last. If only a 3 year warranty is even offered on some of the highest-end chips they made at the time, when some new cars are warrantied for 10, I think that says something really awful about even Intel's own assessment of whether its products can be supported in the long term. AMD may or may not be drastically better, but Intel has set a very low bar, and it is going to take them serious time to earn back my business, assuming they ever do.
Hello Intel troll. Sorry you're feeling even more inadequate today than usual. Given the news, I can't say I blame you.
I'm sorry, but if I'm investing in a high-end, server-class CPU, I expect it to be supported for as long as is reasonably possible. If they said they weren't updating 10 year old Celerons or Atoms, that might be understandable. But Xeons? Let's just say I don't plan to every buy one again, at least so long as AMD represents a reasonable alternative. In fact, I will always stick with AMD (as I long have, for other reasons) until and unless Intel makes some kind of definite, enforceable support commitment.
There are multiple Gentoo and Slackware derivatives as well. I've used and loved Gentoo for over a decade now. AFAIK, systemd is optional on both (though I don't think Gnome will run properly without it).
It never quite reaches 220F. It only feels that way. The -50F however is theoretically possible. (I'm in Cleveland, just over 2 hours away, but much closer to Lake Erie, and thus much snowier and more humid on average. The Cleveland economy really sucks compared to Pittsburgh, but there are tech jobs nonetheless, and a surprising amount of culture, and one of the nation's lowest costs of living.)
Unfortunately, in the past 10-15 years, rent has skyrocketed in the outer boroughs, such that Brooklyn rents rival those in Manhattan, the other boroughs aren't far behind, and even really rough areas like Bushwyck and East New York are starting to see extreme increases in rents.
That *BSD* style licenses are or are not "more free" is a matter of perspective. My view is that non-copylefted licenses may do too much to preserve the freedom of those who would embrace/extend/extinguish Free Software, while copylefted licenses encourage the protection of the users' freedoms instead. This distinction would be moot if there were not evil, rent-seeking organizations and individuals who wish to extort the users of formerly free software, plus "laws" that empower and embolden them. Free would simply mean Free. However, there are, and, for as long as there are, I do view copyleft as an vital mechanism to ensure that the most important pieces of software remain free.
Excluded middle fallacy here. That initd needs replacement does not imply that systemd should be that replacement.