So you just selectebly ignored that I was only talking about noobs creating GUI apps quickly and the applications that those produced. In no way did I ever talk about the quality of applications that can be produced with VS. I'm only commenting on the argument that VS is great for creating GUI quickly. Skilled developers can create GUI apps quickly regardless of platform.
Visual Studio? The only version that Microsoft made that was any good was 6.0, all the others are crap. Yeah some noobs might make GUI applications a lot faster using VS but who wants to run the applications that these produce?
Hope plays no part, there is a substantial amount of software running on servers that have hiigher risks of faults than RAM. And that includes all those fancy database engines of yours. And running a server is not equal to running only databases;). In Upstart you can tell it to stop respawning after X attempts.
What is quite puzzling is that you take an argument against Upstart by attacking a functionality of it that has been severely lacking on Linux for years.
They only risk loosing it if they don't defend the trademark when there is something that looks like a violation, it doesn't mean that one has to chase down everyone using Apple in the name. This is just silly.
And what is the ratio of bad RAM vs segfault in program due to bug which is fixed by restarting the service now;-) And of course if say mysql would segfault, then what percentage of admins wouldn't just type "/etc/init.d/mysql restart" ?
I myself love it for servers, now our sql dependent applications automatically start at the correct time when the sql server starts etc and also the service monitoring that Upstart has is very essential on a server restarting services who crash or exit on failure. What I don't like is that the logs are less informant though.
So configure your services to not fork, with Upstart there is no need to fork anyway so there is no benefit what so ever to fork in a Upstart enviornment.
Well, imho it doesn't make any sense for backward compatibility either since the old software is the 32-bit one and that path is changed while the new 64-bit software that has to be recompiled and changed anyway is the one who gets to use the old path:-)
Whats annoying with Upstart? The only annoying thing that I've encountered is that not all scripts are ported yet so if one for example have an application that needs to be started after a sql-server then one have to install either a Upstart script (to support MySQL) or a init.d script (to support PostgreSQL)...
Actually it's funny that the anti meat people always bring up cows as the big methane producers as a threat to the environment, like 7 billion people didn't produce any methane...
Your state problems with paper ballots is only valid for situations where there is no monitoring. And that should come as no surprise since paper ballots by itself is not secure. I.e here in Sweden anyone who likes are allowed to take part of the whole process, i.e you can stay in the voting area and supervise that no mischief is going on, you are allowed to follow the box as it is sealed and stored, and you are allowed to stay and watch the counting take place. And this right is used, especially by the political parties who have members sent to all voting facilities, i.e each vote is counted by members of different parties so the risk of fraud is very very slim. It still happens that some votes gets lots or people are trying to commit fraud, but to date all attempts have been spotted and reported and in no way could the problem ballots account for any impact of the end result.
Compare this with an all electronic system where no one, and as a programmer and systems architect I mean no one, has any ability what so ever to conduct supervision of the calculation of the votes.
And why is it a problem that the counting may take a few hours when the new elected party/president etc doesn't come to office until a few months later anyways and stays in office for 4 years. A few hours in that context is insignificant.
Problem is that Scientific doesn't try to be compatible with Red Hat at all times so software that is ceritified for Red Hat that works with CentOS might not work with Scientific.
No, because that is not what GP claimed, he claimed that each process had an INCREASE of 2%. If you have 10 processes that each increase by 2% then you still have a total increase of 2%.
Actually the whole world is broken in this way since usage was the intended target of patents since day one. And we will probably never see them surrendering the cover for usage, they would probably give up software patents long before even considering that.
You do have to remember that both HTC and Samsung sells hardware that runs Windows Mobile OS so they might not think it wise to litigate with a partner that they depend upon!
Yeah because MS was making a shitload of software and hardware back in the 60:s when Samsung ventured into the electronics market... Or would the foundation of Microsoft full 15 years later in 1975 do something with that idea of yours?
Because they employ a significant amount of the people usually developing MySQL and getting the community to grow from what-ever-level-it-might-be might take a while?
Slashdot Mirror
So you just selectebly ignored that I was only talking about noobs creating GUI apps quickly and the applications that those produced. In no way did I ever talk about the quality of applications that can be produced with VS. I'm only commenting on the argument that VS is great for creating GUI quickly. Skilled developers can create GUI apps quickly regardless of platform.
So you say that everyone who uses websites wants to run GUI applications done be noobs using VS, does that even make sense :) ?
Could be, 6 was the first one I tried so :-)
Visual Studio? The only version that Microsoft made that was any good was 6.0, all the others are crap. Yeah some noobs might make GUI applications a lot faster using VS but who wants to run the applications that these produce?
Actually no, there is a huge group of people who like Unity and a probably even bigger group who don't care.
Hope plays no part, there is a substantial amount of software running on servers that have hiigher risks of faults than RAM. And that includes all those fancy database engines of yours. And running a server is not equal to running only databases ;). In Upstart you can tell it to stop respawning after X attempts.
What is quite puzzling is that you take an argument against Upstart by attacking a functionality of it that has been severely lacking on Linux for years.
They only risk loosing it if they don't defend the trademark when there is something that looks like a violation, it doesn't mean that one has to chase down everyone using Apple in the name. This is just silly.
And what is the ratio of bad RAM vs segfault in program due to bug which is fixed by restarting the service now ;-) And of course if say mysql would segfault, then what percentage of admins wouldn't just type "/etc/init.d/mysql restart" ?
I myself love it for servers, now our sql dependent applications automatically start at the correct time when the sql server starts etc and also the service monitoring that Upstart has is very essential on a server restarting services who crash or exit on failure. What I don't like is that the logs are less informant though.
So configure your services to not fork, with Upstart there is no need to fork anyway so there is no benefit what so ever to fork in a Upstart enviornment.
Well, imho it doesn't make any sense for backward compatibility either since the old software is the 32-bit one and that path is changed while the new 64-bit software that has to be recompiled and changed anyway is the one who gets to use the old path :-)
Whats annoying with Upstart? The only annoying thing that I've encountered is that not all scripts are ported yet so if one for example have an application that needs to be started after a sql-server then one have to install either a Upstart script (to support MySQL) or a init.d script (to support PostgreSQL)...
Na, it's far better to put all the 64-bit dll:s into C:\Windows\system32\ and the 32-bit dll:s into C:\Windows\syswow64\. Makes perfect sense :-)
Actually it's funny that the anti meat people always bring up cows as the big methane producers as a threat to the environment, like 7 billion people didn't produce any methane...
And eating lots of greens causes buildup of gas, something that might impact on your social skills!
Your state problems with paper ballots is only valid for situations where there is no monitoring. And that should come as no surprise since paper ballots by itself is not secure. I.e here in Sweden anyone who likes are allowed to take part of the whole process, i.e you can stay in the voting area and supervise that no mischief is going on, you are allowed to follow the box as it is sealed and stored, and you are allowed to stay and watch the counting take place. And this right is used, especially by the political parties who have members sent to all voting facilities, i.e each vote is counted by members of different parties so the risk of fraud is very very slim. It still happens that some votes gets lots or people are trying to commit fraud, but to date all attempts have been spotted and reported and in no way could the problem ballots account for any impact of the end result.
Compare this with an all electronic system where no one, and as a programmer and systems architect I mean no one, has any ability what so ever to conduct supervision of the calculation of the votes.
And why is it a problem that the counting may take a few hours when the new elected party/president etc doesn't come to office until a few months later anyways and stays in office for 4 years. A few hours in that context is insignificant.
Problem is that Scientific doesn't try to be compatible with Red Hat at all times so software that is ceritified for Red Hat that works with CentOS might not work with Scientific.
No, because that is not what GP claimed, he claimed that each process had an INCREASE of 2%. If you have 10 processes that each increase by 2% then you still have a total increase of 2%.
Learn math, 2% per session is the same as 2% total.
Yeah, nobody stole the Windows 2000 source code now did they?
Actually the whole world is broken in this way since usage was the intended target of patents since day one. And we will probably never see them surrendering the cover for usage, they would probably give up software patents long before even considering that.
You do have to remember that both HTC and Samsung sells hardware that runs Windows Mobile OS so they might not think it wise to litigate with a partner that they depend upon!
Yeah because MS was making a shitload of software and hardware back in the 60:s when Samsung ventured into the electronics market... Or would the foundation of Microsoft full 15 years later in 1975 do something with that idea of yours?
Because SMBFS was an IBM invention perhaps?
Because they employ a significant amount of the people usually developing MySQL and getting the community to grow from what-ever-level-it-might-be might take a while?