"In all our hearts' command" is kind of weird -- the heart isn't normally associated with command, but whatever. So long as they don't get rid of "The true North, strong and free" -- that part is cool.
You know, it's always nice to see America take a step forward. For all the crying conservatives do about liberalism "destroying" their country, America has progressively become more and more free (in a civil majority sense) with each passing decade. Women can do what they wish, gays aren't persecuted, non-Christians aren't reviled, and so forth. Anachronisms such as state-enforced pledges to God are better removed; keep religion out of institutions.
Now...if only we in Canada could fix our stupid national anthem! "God keep our land/Glorious and free..." Bah...
Try the Archos Jukebox. I believe they offer a variety of hard drive sizes (10 and 20? Can't remember). I'm going to buy the 20GB one, I think -- it makes a handy portable hard drive for data, too.
I agree with your opinion about the split. But it's interesting to think of the consequences of such a move.
Despite your assertion that their software is "light years" ahead, MS have no market leading software except for Windows and Office (and Exchange in the server room). They have hundreds of software titles, yet those are the only market leaders. Office alone accounts for 1/3 of their software revenues. A split into an OS and SW (basically an Office) company would have wide-reaching effects: Office revenues would no longer fund ongoing Windows development, such as it is, and I'm betting they would drop many of their other titles to focus on Office and perhaps rethink any sort of a closed approach to software services.
Anyway, it's obvious to anyone with a brain that controlling the operating system as well as the office suite that forces most people to use it (on commodity PCs) is the source of their ongoing monopoly. Would splitting them up end this? I don't know.
So let's see, Mozilla is faster than IE, has a great email client, is skinnable so it will look nice, has tabs, which the reviewer liked, and on and on...but because the chat client is IRC-based, it only gets 7 out of 10?
If one were paranoid, one would almost suspect a conspiracy...or bias.
Part of it was also filmed in a town called Stewart, in northern B.C.
And it is important to the plot. The movie is a remake of a Norwegian movie also called Insomnia, where a Swedish detective goes to Norway to solve a murder. By setting the whole thing in America, with American characters, part of the nature of the original -- dislocation, being a foreigner, etc. -- was lost.
If BizTalk ignores my custom namespaces, then it's not implemented. I was told, to my face, by someone at Microsoft that full namespace support was coming "in a later version", along with SOAP support (the headers are simply stripped off in 1.0).
And furthermore, it can make them vulnerable when consumers start to associate a company with just that one product. MS has many, many software products, but none are market leaders except Windows, Office, and, on the back end, Exchange. That's it. Office alone accounts for 1/3 of their income. In the minds of consumers, the first two products ARE Microsoft, period.
So throwing money at inferior offerings can harm companies in more ways than just wasting cash: it can cement their image in the eyes of consumers.
Frank Miller did Dark Knight, not, as Katz says, Bob Kane. It was kind of a high-water mark for its time, along with Watchmen, because it really was on a different level artistically. I'd agree that it had a sort of mythical power.
Re:Many programmers do this anyway.
on
Agile Modeling
·
· Score: 1
Yeah, I agree. For me, the UML is more an effective way to visualise object relationships and to provide good documentation for future code maintainers. To be honest, I've never used the code generation bit in Rose. The UML diagramming in Dia works just as well for me. I find that UML helps to make complex inheritance hierarchies a lot more elegant, and it becomes a lot easier to see just what object is using what.
That said, I once worked with a total UML/UP freak who produced sequence diagrams for every public method in our whole project. They were really nice, but it took a reeeeallly long time for him to get anything done. So I guess if you have the time, and that's the way your brain works, it's worth it.
Many programmers do this anyway.
on
Agile Modeling
·
· Score: 2, Interesting
OK, I guess I'm mostly speaking for myself and those programmers I work with, but I think many programmers have, over the years, evolved a personal set of design and modeling techniques that closely resemble what's described here. Using the unified process from the start just doesn't work for me, because it's not the way I think. I do a combination of "loose" modeling with UML, rapid prototyping to work out thorny problems, and then a complete design review to fix up the problem areas. Then repeat. Eventually, what emerges is reasonable for the time spent.
For me, XP techniques come in handy for rapid prototyping, especially the flow of ideas that come with working closely with another programmer. And the UP is good for bringing elegance to the overall design.
Finally, let's not forget the ultimate design tool for every programmer: the whiteboard. Ah, the smell of erasable marker in the morning...
Ford and Daimler both own large shares of Ballard, the world leader in hydrogen cell technology. They are prepared to make the leap. Why? Market advantage. They know there is a large group of consumers who are concerned about fossil fuel use. They want to sell to these people. The relative success of the Toyota Prius (hybrid gas/electric) shows the market exists. There is a lot of marketing advantage when you can say, "Our product is just as fast, just as reliable, and 100% cleaner. Buy Ford and feel good about yourself."
Sorry, I didn't realise that people in the military made no oath to the President, etc. I stand corrected. Still, I question whether a general uprising of the American people would be supported by the military. Sorry, it just seems a bit...romantic (for lack of a better term). I suspect the media would spin it as a Waco type of thing. And another thing: if the American government were to become hopelessly corrupt and harmful to its citizens, how would you know? It's not like they would start mercilessly killing people at random, or ban elections. So how do you know it hasn't happened already? Must you wait for a Germany circa 1933 scenario before you act?
By the way, I'm not European (this is in reply to all the others who responded to the original inflammatory post I made). And no, I don't REALLY think all Americans are idiots -- being Canadian, I've several American friends -- but hey, that is the general worldwide reputation, and it's fun to rile you guys up sometimes:)
However, it must be said that an all-Canadian Stanley Cup would be cool.
If you people (Americans) honestly think that a bunch of suburbanites armed with rifles and handguns can overthrown the government in charge of the most powerful military the world has ever seen, you are even dumber than your reputation allows.
Actually, enterprise Java development is doing rather well. And I'd hardly consider Java an "idiot" language -- I say this as someone with a decade of professional C and C++ programming behind him. Programming is about the design; getting cool points for one's language of implementation won't help ship the product on time.
After reading posts like the parent, I sure wish more actual programmers would post on Slashdot.
Yup. What this guy wants is remote services from a central server, complete with desktop, like VNC, X, etc..NET won't remote your desktop for you.
The other thing that annoys me about the hype machine surrounding.NET is people seem to forget that SOAP is RPC -- that's really it, just RPC. It's been around forever.
Yes, good points. As for the 5 million figure, where did you get it? If you add in the cumulative effects of fossil fuels (even the cleanest burning engines produce unfilterable microparticulate that lodges deep in the lungs), I'd bet it's actually much higher.
Despite these logical facts about nuclear, don't expect public opinion to change any time soon. The fact is, when stuff goes wrong with nuclear power, it freaks out an entire generation who won't go near the stuff. And also, don't lump all environmentalists together; I happen to be one (a wilderness activist, to be specific), but I'm certainly aware of the advantages that nuclear offers.
Here's some other stuff Macromedia needs to do to Flash to make it better:
1. Fix XOR. Currently, it is unreliable, which is amazing, but true. 2. Fix the string handling. It is unbelievably slow. This is a known issue, so hopefully they're on it. 3. Generally be better than Javascript. 4. Introduce native encryption support for XMLSockets.
A fair number of people have been complaining about this stuff, so let's hope it gets fixed.
Example: travel agent says, "Give me current flight status information - only send changes; keep me updated."
Use publish/subscribe; information comes in the form of SOAP; guaranteed delivery doesn't need resends; message-store is implementation-dependant, and anyway, who stores RPCs?
This is better than RPCs because no polling is needed.
As for your other points:
I don't know what you mean by point 3.
Point 5: I agree there is a performance hit with publish-subscribe. Point-to-point is better, but pub-sub has some great advantages.
Final point: message order is not guaranteed, so far as I know. Obviously, if you're doing multi-part transactional updates where ordering is critical, don't use messaging.
Well, we differ on a few things -- I like EJBs. Your "log updates" solution lacks a few things -- like scalability, authentication, security, etc. It's all roll-your-own; expensive and time-consuming. EJBs are around so you don't solve the same problems over and over.
One other thing to consider is messaging, like that provided by JMS (now part of J2EE). It's a good alternative to the purely synchronous world of RPC (embodied by XML-RPC, SOAP, and the like) because it gets around some of the vagaries of making calls over an unpredictable environment (the Internet). Things like publish-and-subscribe, guaranteed delivery, and asynchronous processing are pretty cool, since synchronous RPCs can get waylaid by part of the network going down, etc.
I've only fooled around with it, never used it in a real project, since message-driven beans are pretty new. Does anyone know of a project that makes extensive use of Java messaging, particularly using message-driven beans?
He's primarily referring to the app server (aka web services) market. The implicit assumption is that client machines (your desktop) will do most of their work via web services. These will be implemented on.Net (soon) or J2EE (now). He's not talking about client-side app development so much.
Keep in mind that Java, for example, is very fast as a server-side language.
The real question is: is his assumption correct? Will web services take off to such an extent that the majority of new development is done in these languages?
Slashdot Mirror
"In all our hearts' command" is kind of weird -- the heart isn't normally associated with command, but whatever. So long as they don't get rid of "The true North, strong and free" -- that part is cool.
You know, it's always nice to see America take a step forward. For all the crying conservatives do about liberalism "destroying" their country, America has progressively become more and more free (in a civil majority sense) with each passing decade. Women can do what they wish, gays aren't persecuted, non-Christians aren't reviled, and so forth. Anachronisms such as state-enforced pledges to God are better removed; keep religion out of institutions.
Now...if only we in Canada could fix our stupid national anthem! "God keep our land/Glorious and free..." Bah...
Try the Archos Jukebox. I believe they offer a variety of hard drive sizes (10 and 20? Can't remember). I'm going to buy the 20GB one, I think -- it makes a handy portable hard drive for data, too.
I agree with your opinion about the split. But it's interesting to think of the consequences of such a move.
Despite your assertion that their software is "light years" ahead, MS have no market leading software except for Windows and Office (and Exchange in the server room). They have hundreds of software titles, yet those are the only market leaders. Office alone accounts for 1/3 of their software revenues. A split into an OS and SW (basically an Office) company would have wide-reaching effects: Office revenues would no longer fund ongoing Windows development, such as it is, and I'm betting they would drop many of their other titles to focus on Office and perhaps rethink any sort of a closed approach to software services.
Anyway, it's obvious to anyone with a brain that controlling the operating system as well as the office suite that forces most people to use it (on commodity PCs) is the source of their ongoing monopoly. Would splitting them up end this? I don't know.
So let's see, Mozilla is faster than IE, has a great email client, is skinnable so it will look nice, has tabs, which the reviewer liked, and on and on...but because the chat client is IRC-based, it only gets 7 out of 10?
If one were paranoid, one would almost suspect a conspiracy...or bias.
Part of it was also filmed in a town called Stewart, in northern B.C.
And it is important to the plot. The movie is a remake of a Norwegian movie also called Insomnia, where a Swedish detective goes to Norway to solve a murder. By setting the whole thing in America, with American characters, part of the nature of the original -- dislocation, being a foreigner, etc. -- was lost.
If BizTalk ignores my custom namespaces, then it's not implemented. I was told, to my face, by someone at Microsoft that full namespace support was coming "in a later version", along with SOAP support (the headers are simply stripped off in 1.0).
How come BizTalk 1.0 failed to implement XML namespaces?
And furthermore, it can make them vulnerable when consumers start to associate a company with just that one product. MS has many, many software products, but none are market leaders except Windows, Office, and, on the back end, Exchange. That's it. Office alone accounts for 1/3 of their income. In the minds of consumers, the first two products ARE Microsoft, period.
So throwing money at inferior offerings can harm companies in more ways than just wasting cash: it can cement their image in the eyes of consumers.
Frank Miller did Dark Knight, not, as Katz says, Bob Kane. It was kind of a high-water mark for its time, along with Watchmen, because it really was on a different level artistically. I'd agree that it had a sort of mythical power.
Yeah, I agree. For me, the UML is more an effective way to visualise object relationships and to provide good documentation for future code maintainers. To be honest, I've never used the code generation bit in Rose. The UML diagramming in Dia works just as well for me. I find that UML helps to make complex inheritance hierarchies a lot more elegant, and it becomes a lot easier to see just what object is using what.
That said, I once worked with a total UML/UP freak who produced sequence diagrams for every public method in our whole project. They were really nice, but it took a reeeeallly long time for him to get anything done. So I guess if you have the time, and that's the way your brain works, it's worth it.
OK, I guess I'm mostly speaking for myself and those programmers I work with, but I think many programmers have, over the years, evolved a personal set of design and modeling techniques that closely resemble what's described here. Using the unified process from the start just doesn't work for me, because it's not the way I think. I do a combination of "loose" modeling with UML, rapid prototyping to work out thorny problems, and then a complete design review to fix up the problem areas. Then repeat. Eventually, what emerges is reasonable for the time spent.
For me, XP techniques come in handy for rapid prototyping, especially the flow of ideas that come with working closely with another programmer. And the UP is good for bringing elegance to the overall design.
Finally, let's not forget the ultimate design tool for every programmer: the whiteboard. Ah, the smell of erasable marker in the morning...
Ford and Daimler both own large shares of Ballard, the world leader in hydrogen cell technology. They are prepared to make the leap. Why? Market advantage. They know there is a large group of consumers who are concerned about fossil fuel use. They want to sell to these people. The relative success of the Toyota Prius (hybrid gas/electric) shows the market exists. There is a lot of marketing advantage when you can say, "Our product is just as fast, just as reliable, and 100% cleaner. Buy Ford and feel good about yourself."
Sorry, I didn't realise that people in the military made no oath to the President, etc. I stand corrected. Still, I question whether a general uprising of the American people would be supported by the military. Sorry, it just seems a bit...romantic (for lack of a better term). I suspect the media would spin it as a Waco type of thing. And another thing: if the American government were to become hopelessly corrupt and harmful to its citizens, how would you know? It's not like they would start mercilessly killing people at random, or ban elections. So how do you know it hasn't happened already? Must you wait for a Germany circa 1933 scenario before you act?
:)
By the way, I'm not European (this is in reply to all the others who responded to the original inflammatory post I made). And no, I don't REALLY think all Americans are idiots -- being Canadian, I've several American friends -- but hey, that is the general worldwide reputation, and it's fun to rile you guys up sometimes
However, it must be said that an all-Canadian Stanley Cup would be cool.
If you people (Americans) honestly think that a bunch of suburbanites armed with rifles and handguns can overthrown the government in charge of the most powerful military the world has ever seen, you are even dumber than your reputation allows.
Eating people is bad for your health (kuru, I believe).
Unfortunately, well-meant ethical systems based upon utter claptrap are themselves claptrap. Sorry about that.
Don't you enjoy the noise the rain makes when it bounces off your tinfoil hat?
KDE's DCOP relies on ICE, which is an X protocol. There's more to do than just port Qt.
Actually, enterprise Java development is doing rather well. And I'd hardly consider Java an "idiot" language -- I say this as someone with a decade of professional C and C++ programming behind him. Programming is about the design; getting cool points for one's language of implementation won't help ship the product on time.
After reading posts like the parent, I sure wish more actual programmers would post on Slashdot.
Yup. What this guy wants is remote services from a central server, complete with desktop, like VNC, X, etc. .NET won't remote your desktop for you.
.NET is people seem to forget that SOAP is RPC -- that's really it, just RPC. It's been around forever.
The other thing that annoys me about the hype machine surrounding
Yes, good points. As for the 5 million figure, where did you get it? If you add in the cumulative effects of fossil fuels (even the cleanest burning engines produce unfilterable microparticulate that lodges deep in the lungs), I'd bet it's actually much higher.
Despite these logical facts about nuclear, don't expect public opinion to change any time soon. The fact is, when stuff goes wrong with nuclear power, it freaks out an entire generation who won't go near the stuff. And also, don't lump all environmentalists together; I happen to be one (a wilderness activist, to be specific), but I'm certainly aware of the advantages that nuclear offers.
Here's some other stuff Macromedia needs to do to Flash to make it better:
1. Fix XOR. Currently, it is unreliable, which is amazing, but true.
2. Fix the string handling. It is unbelievably slow. This is a known issue, so hopefully they're on it.
3. Generally be better than Javascript.
4. Introduce native encryption support for XMLSockets.
A fair number of people have been complaining about this stuff, so let's hope it gets fixed.
OK, I'll try :)
Example: travel agent says, "Give me current flight status information - only send changes; keep me updated."
Use publish/subscribe; information comes in the form of SOAP; guaranteed delivery doesn't need resends; message-store is implementation-dependant, and anyway, who stores RPCs?
This is better than RPCs because no polling is needed.
As for your other points:
I don't know what you mean by point 3.
Point 5: I agree there is a performance hit with publish-subscribe. Point-to-point is better, but pub-sub has some great advantages.
Final point: message order is not guaranteed, so far as I know. Obviously, if you're doing multi-part transactional updates where ordering is critical, don't use messaging.
Well, we differ on a few things -- I like EJBs. Your "log updates" solution lacks a few things -- like scalability, authentication, security, etc. It's all roll-your-own; expensive and time-consuming. EJBs are around so you don't solve the same problems over and over.
One other thing to consider is messaging, like that provided by JMS (now part of J2EE). It's a good alternative to the purely synchronous world of RPC (embodied by XML-RPC, SOAP, and the like) because it gets around some of the vagaries of making calls over an unpredictable environment (the Internet). Things like publish-and-subscribe, guaranteed delivery, and asynchronous processing are pretty cool, since synchronous RPCs can get waylaid by part of the network going down, etc.
I've only fooled around with it, never used it in a real project, since message-driven beans are pretty new. Does anyone know of a project that makes extensive use of Java messaging, particularly using message-driven beans?
He's primarily referring to the app server (aka web services) market. The implicit assumption is that client machines (your desktop) will do most of their work via web services. These will be implemented on .Net (soon) or J2EE (now). He's not talking about client-side app development so much.
Keep in mind that Java, for example, is very fast as a server-side language.
The real question is: is his assumption correct? Will web services take off to such an extent that the majority of new development is done in these languages?