It's still a lot harder to read something like (plus 7 (minus 4 5) (some-function (* my-var 3))) than to read 7 + (4 - 5) + some_function(3 * my_var). It's also easier to read while(x 3) than it is to read the crazy Lisp syntax for do-loops, which appears to be a list of a variety of values, variables, conditions, all compacted into one statement, with no differentiation, syntactically, between the different arguments to the loop structure. Indentation and line breaks only help so much. Having actual syntax helps a lot more.
Visual Studio is a huge project that requires special features from the OS (like debugging ports for the debugger). Porting it to Unix would be a massive undertaking. And what would be the gain? Who would buy it? Maybe some on OS X, but there's already XCode, which I understand to be at least half-way decent, depending on who you ask, and not likely to be unseated by a Windows-style program from the Great Satan. MS won't make any money on the 7 Linux users who would actually buy Visual Studio. It just simply is not worth the cost, not even worth discussing further. MS isn't being evil by not porting it to Unix (which, by the way, is not some singular platform, but a variety of subtly and not-so-subtly different implementations with their own long lists of gotchas and missing features), they are being smart.
The problem with the south really is that people just don't think they can handle it. Well, some people choose not to handle it by being idiots. We've had several decent snow and ice storms in recent years here in North Carolina. Where I live, even after 8-10" of snow and sleet, the roads were plowed by the next morning (not to mention brining a day or two before). I live in a hilly neighborhood and I managed to drive on the ice pack just fine. The key is to not be a fucking idiot and pay fucking attention to what you are doing. There are, of course, legitimately dangerous road sections, but those can be avoided. Unfortunately, a lot of people think they can do 60 on ice because they have 4 wheel drive and that's why you see all the SUVs and sports cars off on the side of the road.
The hype machine, though, runs full force down here as well. I think since we have snowstorms more frequently here than NYC has hurricanes, the result doesn't end up being as big of a deal (the hype, not the storm). It's still really annoying. I especially hate hearing the common folk take a forecast for a 1-3" and turn it into "I heard we were supposed to get a foot!" at which point they flood the grocery stores to perform the ritual buying of bread and milk.
I don't see why vblank information can't be sent over the wire like everything else. Or, as you mention, it can be done outside the wire, just like shared memory images are done. The problem we've had with vblank is that neither the protocol nor the toolkits have any infrastructure for dealing with it. There have been vblank and sync extensions for years, but nobody uses them. Meanwhile, DRI and DRI2 have been used extensively by applications and desktop frameworks/window managers, and DRI and DRI2 are considerably more complicated than a vblank extension.
Once again, the problem isn't really the network transparency, it's the users (not the end users!) and lack of foresight from the 80s (which is understandable, but unfortunate).
You are the retarded one. Their point is that/since/ people sleep at night, having "midnight" (according to GMT) be in the middle of the day or at some other odd time would be ridiculous. It would be evening here in the eastern US when the day goes from Monday to Tuesday. Everyone's still up. People might still be working. It'd be worse on the west coast where going from Monday to Tuesday would happen at 4 PM!
What did he do, specifically, to make it worse? Aside from not really doing anything useful, I haven't seen any policies coming from Obama that ground the economy to a halt. The economy is fucked up and has been fucked up. It was only a matter of time.
Which are the design problems you speak of? It's pretty simple.
Maybe RD doesn't have a lot of use for the average desktop user, but it is used in the corporate world and it is used by power users. Just because *you* don't use it doesn't mean nobody does.
Sometimes that isn't readily available. Also, chances are, if X has crashed, all the programs that you care about are gone too. You might as well power cycle, or use the Magic SysReq key to do a clean-ish reboot. If you can't use the Magic SysReq key, you probably can't SSH in either.
I agree. Nothing can beat Windows 7 at taking 10 minutes to get to a usable desktop. Stupid Linux doesn't even try and gets me there in a piss-poor minute or so. Doesn't even bother reading the entire harddrive for god knows what reason!
It may also be my drivers, but I've found X on my laptop to be damn snappy, and it at least *feels* snappier than Windows 7 on the same machine.
Wayland, but only because it isn't asked to do what a modern windowing system needs to do. Once it goes "live" and all of the same requirements that X had to deal with and foisted upon it, it'll likely quickly become bloated like every other software project that has to do anything useful. Except, instead of having a good architecture, even if it's large and complex, they went for simple for the sake of simple. We'll see how that works out. Already things like network transparency will have to be bolted on the side, and window decoration policy is causing schisms.
Sometimes the drivers can actually leave the keyboard and screen in a state where you can't do anything. The Magic SysReq key comes in handy here. Very occasionally, the kernel-mode portion of the drivers will actually somehow hardlock the kernel. Then the Magic Powerbutton comes in handy.
Or the media, rather. They love this. Hurricane headed for one of the biggest markets in the country. Even if it ends up being a dud, they can still spend a day going after the meteorologists who correctly predicted it, even when the media did not, and get their ratings fill. It's a win-win for them.
New York has nor'easters, which can be gusty and have storm surge and flooding. Granted, they are often worse further north than NYC, but they aren't rare in NYC either.
Flood is a big concern still, as is storm surge. Due to interaction with a trough in SE Canada, a large area of heavy rain will spread out ahead of the storm and keep raining over areas for potentially as long as 24 hours. Many of these areas have already had significant rains during the summer, leading to saturated ground before the storm even gets there. Some gusty winds can thus easily knock down trees and powerlines (for the areas where that's a concern). Flooding is definitely going to be a problem.
Media hype is...well, very disappointing. They focus on the wrong problems in the wrong area and in their zeal for ratings, they completely distort reality.
That's a pretty lame definition of religion. Please don't "vague" your way out of the problem. Christianity is a religion, secular humanism is not. They are only similar in that they have some philosophical underpinnings unique to either. Well, so does everything else in the world. Do you want to count preferences for EMACS and Vi to be religious in nature as well (and I don't mean facetiously)?
The establishment clause. Despite the religious right's attempt to make it appear impotent, the clause is pretty clear about the state's role in religion. It's effectively a separation of church and state clause.
The OP seemed to think that the problem was the existence of the GC, rather than its tuning. To "fix" that would require switching to a non-GC high-level scripting language (an absurd proposition, of course).
It would be fixed by using a non-GC language. Seeing how JavaScript has become the defacto scripting language of the client-side web, I doubt this is going to change any time soon.
Slashdot Mirror
Nobody writes JS like that.
Yes, that's MUCH better /sarcasm.
It's still a lot harder to read something like (plus 7 (minus 4 5) (some-function (* my-var 3))) than to read 7 + (4 - 5) + some_function(3 * my_var). It's also easier to read while(x 3) than it is to read the crazy Lisp syntax for do-loops, which appears to be a list of a variety of values, variables, conditions, all compacted into one statement, with no differentiation, syntactically, between the different arguments to the loop structure. Indentation and line breaks only help so much. Having actual syntax helps a lot more.
Visual Studio is a huge project that requires special features from the OS (like debugging ports for the debugger). Porting it to Unix would be a massive undertaking. And what would be the gain? Who would buy it? Maybe some on OS X, but there's already XCode, which I understand to be at least half-way decent, depending on who you ask, and not likely to be unseated by a Windows-style program from the Great Satan. MS won't make any money on the 7 Linux users who would actually buy Visual Studio. It just simply is not worth the cost, not even worth discussing further. MS isn't being evil by not porting it to Unix (which, by the way, is not some singular platform, but a variety of subtly and not-so-subtly different implementations with their own long lists of gotchas and missing features), they are being smart.
The problem with the south really is that people just don't think they can handle it. Well, some people choose not to handle it by being idiots. We've had several decent snow and ice storms in recent years here in North Carolina. Where I live, even after 8-10" of snow and sleet, the roads were plowed by the next morning (not to mention brining a day or two before). I live in a hilly neighborhood and I managed to drive on the ice pack just fine. The key is to not be a fucking idiot and pay fucking attention to what you are doing. There are, of course, legitimately dangerous road sections, but those can be avoided. Unfortunately, a lot of people think they can do 60 on ice because they have 4 wheel drive and that's why you see all the SUVs and sports cars off on the side of the road.
The hype machine, though, runs full force down here as well. I think since we have snowstorms more frequently here than NYC has hurricanes, the result doesn't end up being as big of a deal (the hype, not the storm). It's still really annoying. I especially hate hearing the common folk take a forecast for a 1-3" and turn it into "I heard we were supposed to get a foot!" at which point they flood the grocery stores to perform the ritual buying of bread and milk.
I don't see why vblank information can't be sent over the wire like everything else. Or, as you mention, it can be done outside the wire, just like shared memory images are done. The problem we've had with vblank is that neither the protocol nor the toolkits have any infrastructure for dealing with it. There have been vblank and sync extensions for years, but nobody uses them. Meanwhile, DRI and DRI2 have been used extensively by applications and desktop frameworks/window managers, and DRI and DRI2 are considerably more complicated than a vblank extension.
Once again, the problem isn't really the network transparency, it's the users (not the end users!) and lack of foresight from the 80s (which is understandable, but unfortunate).
You are the retarded one. Their point is that /since/ people sleep at night, having "midnight" (according to GMT) be in the middle of the day or at some other odd time would be ridiculous. It would be evening here in the eastern US when the day goes from Monday to Tuesday. Everyone's still up. People might still be working. It'd be worse on the west coast where going from Monday to Tuesday would happen at 4 PM!
You know a changeover to metric isn't that simple.
What did he do, specifically, to make it worse? Aside from not really doing anything useful, I haven't seen any policies coming from Obama that ground the economy to a halt. The economy is fucked up and has been fucked up. It was only a matter of time.
Except the myth about AIDS is prevalent, whereas the basement folks are not.
Which are the design problems you speak of? It's pretty simple.
Maybe RD doesn't have a lot of use for the average desktop user, but it is used in the corporate world and it is used by power users. Just because *you* don't use it doesn't mean nobody does.
Sometimes that isn't readily available. Also, chances are, if X has crashed, all the programs that you care about are gone too. You might as well power cycle, or use the Magic SysReq key to do a clean-ish reboot. If you can't use the Magic SysReq key, you probably can't SSH in either.
I agree. Nothing can beat Windows 7 at taking 10 minutes to get to a usable desktop. Stupid Linux doesn't even try and gets me there in a piss-poor minute or so. Doesn't even bother reading the entire harddrive for god knows what reason!
It may also be my drivers, but I've found X on my laptop to be damn snappy, and it at least *feels* snappier than Windows 7 on the same machine.
That's not what they mean here. They are talking about making input scroll events (mouse wheel, presumably) be less jumpy and more smoothed out. See this article: http://www.phoronix.com/scan.php?page=news_item&px=OTUyNw
Wayland, but only because it isn't asked to do what a modern windowing system needs to do. Once it goes "live" and all of the same requirements that X had to deal with and foisted upon it, it'll likely quickly become bloated like every other software project that has to do anything useful. Except, instead of having a good architecture, even if it's large and complex, they went for simple for the sake of simple. We'll see how that works out. Already things like network transparency will have to be bolted on the side, and window decoration policy is causing schisms.
Sometimes the drivers can actually leave the keyboard and screen in a state where you can't do anything. The Magic SysReq key comes in handy here. Very occasionally, the kernel-mode portion of the drivers will actually somehow hardlock the kernel. Then the Magic Powerbutton comes in handy.
Did you forget about Isabel in 2003?
Or the media, rather. They love this. Hurricane headed for one of the biggest markets in the country. Even if it ends up being a dud, they can still spend a day going after the meteorologists who correctly predicted it, even when the media did not, and get their ratings fill. It's a win-win for them.
New York has nor'easters, which can be gusty and have storm surge and flooding. Granted, they are often worse further north than NYC, but they aren't rare in NYC either.
Flood is a big concern still, as is storm surge. Due to interaction with a trough in SE Canada, a large area of heavy rain will spread out ahead of the storm and keep raining over areas for potentially as long as 24 hours. Many of these areas have already had significant rains during the summer, leading to saturated ground before the storm even gets there. Some gusty winds can thus easily knock down trees and powerlines (for the areas where that's a concern). Flooding is definitely going to be a problem.
Media hype is...well, very disappointing. They focus on the wrong problems in the wrong area and in their zeal for ratings, they completely distort reality.
That's a pretty lame definition of religion. Please don't "vague" your way out of the problem. Christianity is a religion, secular humanism is not. They are only similar in that they have some philosophical underpinnings unique to either. Well, so does everything else in the world. Do you want to count preferences for EMACS and Vi to be religious in nature as well (and I don't mean facetiously)?
The establishment clause. Despite the religious right's attempt to make it appear impotent, the clause is pretty clear about the state's role in religion. It's effectively a separation of church and state clause.
I know...
The OP seemed to think that the problem was the existence of the GC, rather than its tuning. To "fix" that would require switching to a non-GC high-level scripting language (an absurd proposition, of course).
It would be fixed by using a non-GC language. Seeing how JavaScript has become the defacto scripting language of the client-side web, I doubt this is going to change any time soon.
He said "virtual machine runtime" not "runtime" by itself.