If "right to choose" means rolling back legislation on abortion and marriage to take away those choices, then yes. I can just see your presidential race and policies getting bogged down in those issues as Paul tries to take you back to an idealized 1950s where America was insular and everyone was "happy."
Java has been quite successful (not so much at applets, of course, but otherwise) and it is developed and supported by a consortium of major companies (JSRs, JVMs, etc).
Anyway, it's pretty clear that Android is being led by Google and they're using Java as an example to follow.
I think many of the posts here are from programmers who are stroking their own egos. there are fairly well understood types of programmers...
although 'programmer' or 'software developer' are general terms, they may mean the comp sci or otherwise specialized type who focuses on one aspect. they are by far the loudest here, and don't mind insulting other people or ironically insulting other people's way of working while promoting their own. they like to pretend they are the only ones with hard problems.
there are all kinds or hard problems. making an interface work for a blind or novice user. making something work in a complex business environment and can be supported in a coarse grained, heterogeneous environment. usually, performance is the least of worries. visual tools have good applications, but there will always be 'problems' that are just out of the reach of visual tools, that require reaching into systems or framework APIs and writing new code, hopefully with some skill (though well designed base APIs can cover for a lot of ineptness, it will bite you in the end), yet don't require CS type knowledge. for these kinds of problems, a person's care about their end users and the future of their code is more important. you don't need matrix calculations to create a good system that suits the end users, and I doubt most of these macho programmers could be bothered to design a good end user system.
Again, glad it is working out for you, but one would think most sites might benefit from emerging modules, but I guess yours are just fulfilling one static requirement.
You can stick with older versions for a little while, but the whole point is to have modules available, as soon as x.x+1 comes out you no longer have that advantage. And you can't test or support modules because there is no real API or tests. And after a while, your older version starts to have no support so you're better off taking it offline.
Glad it is working out for you, but maybe its just because of your personal investment.
Do you want such a high level framework? To see things always not quite doing what you want, to always have to do complex upgrades at the last minute when a new exploit is found?
Do you want to invest in a framework where there's no real api (just convention, that can't be enforced reliably), no standard practices like unit tests, a language (PHP) that is under constant flux, the developers are always arguing over whether they should actually use things like encapsulation or just keep on with arrays (everything is a string! Of course! or a number)
Do you want to work with a system where the main developers aggressively state that they will pay no attention to backward compatibilty? Everything changes from 4.6 to 4.7. That nice module you're using may not work in a week, if no one can be bothered to upgrade it. A common occurance.
Do you want to use a system where the database isn't even relational?
Just check out the Drupal site, and check out how many "solutions" are scraps of code pasted here and there, kludges and hacks. That's going to be supported and upgraded really easily. Oh, and they have so much scorn when they say how easy it is to "learn php." Yes, way to learn about software development, kludges and hacks.
How about the flammage in the Drupal discussions, and the fact that any criticism is given the silent treatment.
How about a system that bills itself "Community plumbing." This may be the best reason to use Drupal, because clearly the attitude is all about the "wizard" programmers, and the "users" at their mercy.
Then go Drupal! It's working out very well for the core developers.
Otherwise, there are better languages that support better, more tuned libraries for getting things done.
Slashdot Mirror
If "right to choose" means rolling back legislation on abortion and marriage to take away those choices, then yes. I can just see your presidential race and policies getting bogged down in those issues as Paul tries to take you back to an idealized 1950s where America was insular and everyone was "happy."
Java has been quite successful (not so much at applets, of course, but otherwise) and it is developed and supported by a consortium of major companies (JSRs, JVMs, etc). Anyway, it's pretty clear that Android is being led by Google and they're using Java as an example to follow.
Also make sure you keep your messages on topic.
I think many of the posts here are from programmers who are stroking their own egos. there are fairly well understood types of programmers...
although 'programmer' or 'software developer' are general terms, they may mean the comp sci or otherwise specialized type who focuses on one aspect. they are by far the loudest here, and don't mind insulting other people or ironically insulting other people's way of working while promoting their own. they like to pretend they are the only ones with hard problems.
there are all kinds or hard problems. making an interface work for a blind or novice user. making something work in a complex business environment and can be supported in a coarse grained, heterogeneous environment. usually, performance is the least of worries. visual tools have good applications, but there will always be 'problems' that are just out of the reach of visual tools, that require reaching into systems or framework APIs and writing new code, hopefully with some skill (though well designed base APIs can cover for a lot of ineptness, it will bite you in the end), yet don't require CS type knowledge. for these kinds of problems, a person's care about their end users and the future of their code is more important. you don't need matrix calculations to create a good system that suits the end users, and I doubt most of these macho programmers could be bothered to design a good end user system.
Again, glad it is working out for you, but one would think most sites might benefit from emerging modules, but I guess yours are just fulfilling one static requirement.
Disagree with what?
You can stick with older versions for a little while, but the whole point is to have modules available, as soon as x.x+1 comes out you no longer have that advantage. And you can't test or support modules because there is no real API or tests. And after a while, your older version starts to have no support so you're better off taking it offline.
Glad it is working out for you, but maybe its just because of your personal investment.
Do you want such a high level framework? To see things always not quite doing what you want, to always have to do complex upgrades at the last minute when a new exploit is found?
Do you want to invest in a framework where there's no real api (just convention, that can't be enforced reliably), no standard practices like unit tests, a language (PHP) that is under constant flux, the developers are always arguing over whether they should actually use things like encapsulation or just keep on with arrays (everything is a string! Of course! or a number)
Do you want to work with a system where the main developers aggressively state that they will pay no attention to backward compatibilty? Everything changes from 4.6 to 4.7. That nice module you're using may not work in a week, if no one can be bothered to upgrade it. A common occurance.
Do you want to use a system where the database isn't even relational?
Just check out the Drupal site, and check out how many "solutions" are scraps of code pasted here and there, kludges and hacks. That's going to be supported and upgraded really easily. Oh, and they have so much scorn when they say how easy it is to "learn php." Yes, way to learn about software development, kludges and hacks.
How about the flammage in the Drupal discussions, and the fact that any criticism is given the silent treatment.
How about a system that bills itself "Community plumbing." This may be the best reason to use Drupal, because clearly the attitude is all about the "wizard" programmers, and the "users" at their mercy.
Then go Drupal! It's working out very well for the core developers.
Otherwise, there are better languages that support better, more tuned libraries for getting things done.