Or, you could use a great tool like MailScanner to take care of both for you. It definitly is a good management glue between MTA's, Spam Scanners and Virus Scanners.
Or take away their right to install software and run activex components on their computers. If you already have a license to lock them down, at least do it right.
Most pirates that I know hate it, but I love it:-)
Really, three types of people hate steam:
1. Leeches - They want their free lunch 2. Cheaters - Manditory updates means that you force anti-cheat tech on the game 3. Opposition by prinicple - They hate that Valve is controlling them, or that there's no hard manual, or no cd's with copy check, or whatever.
I've rarely heard valid reasons for hating steam:
1. Inability to play on a LAN without Steam access? 2. Bad patches requires Valve to do something, you can't rollback 3. Hefty re-install
This one little developer has surely made Sierra Fists full of money from the HL+mod franchise. How many other games do you see on store shelves 5 years after it came out?
I'd really like to see Valve dump Vivendi and stick it out themselves. Online distribution IS possible, as steam has shown. Pox and all, it is possible.
Also, I'm not sure of Gabe Newell's motives of saying what he did, but back in the days of 2000 Broadband adoption was nowhere near what it is today (especially in the states). Maybe he actually wasn't lieing at that point?
So, are you telling the poster to abandon JVM's and use the.NET CLR which may or may not break third party tools just to simplify a seemingly small part of their entire development process?
If you REALLY must use.NET based libraries, why not just write a JNI wrapper for the sub-system using operator overloading? Seem rediculous? I do, but its better than changing the entire environment.
the 1.0 syndrome. Is it really that surprising that is this not only EA's first XBox live title, but its also Microsoft's first third party vendor hosted service on XBox live. Typically if you haven't built proceedures and gotchas beforehand, things get forgotten, screwed up, etc...
Mind you, it could be said that this was ultimately the result of bad QA.
As a Canadian in a parlimentatary system, I'll tell you its not all roses.
There have been several minority governments; this happens when the winner doesn't garner 50% of the available seats.
In that case, the leading party usually teams up with another party to reach a majority standing in the house.
Anyways, the main point i'm trying to make is that out of all the monority governments none of them have lasted the four years. Every single one collapsed and forced a re-election.
Right now there's a minority government, so here's hoping everyone gets along!
Think of Mozilla's platform as Java-lite. You can write very small programs that utilize many built-ins that the browser supports. It has a deployment framework through 'extensions', etc..
Not everyone needs a fully library supported language like.NET or Java in order to do their work.
As long as you can learn JavaScript, you can write mozilla extensions. I'm just wish that the Mozilla folks would make it easier to find info on how to develop the platform as a platform. From what I've read on their site, they target the 'Mozilla as-a platform' over 'Mozilla is-a platform'. They might find that free/comercial entities could find use in their platform and help develop it if they think there's more for them to use from it.
Think of thin-apps niche for a moment: Java Runtime ~15MB.NET Runtime ~25MB Mozilla Runtime ~5MB and that includes a browser
If you want to deploy Thin Client App xyz, which one do you choose? You can't assume that your customer has either Java or.NET installed (trust me from experience, they don't). Less means better in this case. The smaller the release, the more likely an admin would choose your solution.
Mozilla has less surface area which means there's less functionality built id but its more simple to develop for. The language is JavaScript which is used by throngs of web developers (the target market of this technology). You can look at the debate over web based Application distribution to see where Mozilla fits into things. (The new MS web services model, Java Web Start, Mozilla)
The poster was saying that once you buy a license for the product (usually flat rate), you will get the source code included with the release.
I've seen quite a few smaller java libraries released like this. It makes sense when you're dealing with small software component developers. If for some reason they go belly up or disappear (which happens often with little guys), you aren't forced to rip out the code and throw it away.
I can't say that this type of distribution would work well for many different software industries, but for some like the example above, it works great. Another idea would be to place code in escrow. If for some reason the developer is unable to fulfill an agreed upon service, the code is given to the buyer of the service.
"Linux now accounts for 15.5 percent of embedded projects"
In other words, more development projects are using Linux over other embedded OS's. So, Symbian may be running on 50% of all embedded devices in the world, but if only a select few comanies are using it, they're just regurgiting the same old thing. There may be 50 seperate symbian projects stemming from Nokia alone, but that wouldn't begin to dent the market share that Linux is forming.
This doesn't surprise me in the least. Symbian was designed for mobile phones, and basically little else. You look at the number of projects in Cell phones vs. the entire Embedded spectrum (which linux more or less competes) and you realize why Linux has such a market share when it comes to who it developing them.
Of course the stats are flawed as usual. You could say Linux has a 15% developer mind-share, but if they only account for 1% of all embedded 'sales', or 'revenue', that's really not that impressive at all.
If you've read ANYTHING about the SCO case, its that you can't hand out API's (erm LSB) and then turn around and sue anyone for using that interface (regardless of the distribution license). Imagine the anti-trust lawsuits of MS sueing a competitor xyz for implementing private API function xyz which makes the program twice as fast while implementing it themselves.
There is also discussion that it may be impossible to enforce copyright's for API's at all. Under fair-use laws, I believe that anyone can have the right to implement the API as long as its been released to the public in one form or the other. I can't remember all the details, but it was something along those lines.
The only cases that I've really seen developers going after vendors is when they take GPL copyrighted code lock stock and barrel and put it in their own systems without credit, source, or some other blatently obvious GPL violation (Netfilter, etc..).
That's good to know! Anyways, how does the card get powered if the system isn't on? Does it need powered ethernet or (more likely) does it use a special motherboard interface thats always powered?
So does SSH, which is actually the preferred method for low-bandwith consumption by some X developers. LBX was a kludge, we all know it.
SSH tunneling solves the authentication and some of the bandwidth issues involved with X transport. Beyond that, Toolkits need to learn to behave with remoting their desktops. KeithP gave a prety good intro on these issues a long time ago: http://keithp.com/~keithp/talks/usenix2003/ AND http://keithp.com/~keithp/talks/lbxpost/inde x.html
I can't say much against RDP. Its got a decent bandwidth usage, I've heard good things about Citrix more-so since they basically invented Remote Windows. The performance could be better, but it is sufficiant for most operations.
Negatives:
Client (TS Server) footprints are heavier which means you need a lot of hardware to support users. Citrix is good in that if you just need an app here and an app there, you can choose to just export the application, and not the entire virtual screen.
Licensing is and will forever doom TS to an obsurity even in windows. The price point is unrealistic for home/small business and even medium sized businesses will likely only use it sparcely. Ditto for ICA, but i'd say only large companies would use ICA. Its a indispensible feature that fillers like VNC and PC Anywhere will likely never be able fill.
PS: XP bans all foreign windowing tools that aren't licensed, aka RDP/ICA. I love that MS doesn't use its monopoly powers for evil:-)
In order to support boot style KVM abilities that hardware KVM's offer, the BIOS has to boot an entire IP stack and daemon to support the integrated KVM functionality, and don't forget the network drivers needed to support the network card. This would be quite heavy. It isn't as simple as the interface between the bios and net boot roms.
I guess this could actually be integrated into network boot roms and add a new differentiator to the innovation stagnent NIC ASIC market. Just to note, the bios would still need to support it, but that interface would be pretty simple.
I know so many people with university education that are incompetent and I know some that are absolutely briliant.
The school doesn't make the man/woman, its their own drive, determination, and their capacity for knowledge.
As for grand-poster: I personally don't relate to the relevence of Calculus or Physics to Programming. I've been in many jobs, and the extent of my math usage has been algebraic. Yes, if your working on weather patterns, then sure it'll help, but look at it this way: If your working on an accounting software package you're better off having a diploma in accounting. If you're working on GUI's you may decide that User Interface Design courses are more applicable than calculus.
Hey, lets be reasonable. I think its perfectly reasonable given the current state of software hedgonomy.
Fact: There are MANY MANY MANY software products on windows that are unavailable on *NIX/Linux. There are also many specialized apps that are only available on *NIX/Linux.
If just one Windows and *NIX program ran client heavy, you'd need two physical PC's to handle them (or else some type of poor man's Virtualization).
I'd be hard pressed to run RemoteX based CAD programs and the like. I don't think I'm alone here either.
Well, I'd like to try, but I wouldn't want to loose my job when it blows up.
1. JDS is a GNOME-centric system. Am I not mistaken in thinking GNNOME takes a back seat to KDE on Suse?
2. JDS server requirements are based on Redhat software. I suppose its possible that they used Suse for the client and Redhat for the servers, but very unlikely.
Spoof integrity will always come down to two factors:
1. Verification of Sender - This will never happen unless systems like cacert.org start to take off. Basically 99% of the internet don't give a damn about certificates, and the ability for anonymity is more limited. A debate about privacy/spam could go on for years if given the chance.
2. SPF-like protocols - This is the ability to discriminate who is and who isn't allowed to send email from a given domain. This will cause a few things:
- a. Every mail sender must be from a domain
- b. Every mail sender has to route through an institutional server (the road warrior problem)
- c. Every institutional mail server must deny relaying from anyone non-authenticated. (Should be done already)
- d. Institution must be regarded positively by the community at large. If they aren't, they're completely eliminated from sending emails.
- e. You have to get DNS servers that you can update.
- f. You must lock down the DNS server from attacks (Have you done this lately?)
Anyways, both solutions are possible, but neither are ideal for everyone. SPF has a real chance of shutting down spoammers, but I imagine the wild west internet we know is pretty much over.
You have to have a working IT economy in those areas before you can outsource anything to them. Its like outsourcing IT operations to Ebonia.
That said, if WVa or TN has a viable IT marketplace with a good set of IT individuals, then great. If you're trying to plant an office in Farmsville USA, then you shouldn't expect much. Just because you live there doesn't mean there are enough of you.
Any attack on click-through licensing means that open source software is more open to the same legal punishments. If someone found a disasterous bug in Linux, would people have a right to sue Linux,OSDL, etc.? I bloody hope not.
Now the problem is that companies buying software don't require full guarantees. If the DOD says this software must be perfect, then its the onus on the Seller to supply that guarantee.
This allows for open source companies to guarantee software without forcing every Linux distributor to get hit with the lawsuits.
Slashdot Mirror
It's called Advanced... or else you could really break them up and call them Registry or gconf-editor
Or, you could use a great tool like MailScanner to take care of both for you. It definitly is a good management glue between MTA's, Spam Scanners and Virus Scanners.
Or take away their right to install software and run activex components on their computers. If you already have a license to lock them down, at least do it right.
Most pirates that I know hate it, but I love it :-)
Really, three types of people hate steam:
1. Leeches - They want their free lunch
2. Cheaters - Manditory updates means that you force anti-cheat tech on the game
3. Opposition by prinicple - They hate that Valve is controlling them, or that there's no hard manual, or no cd's with copy check, or whatever.
I've rarely heard valid reasons for hating steam:
1. Inability to play on a LAN without Steam access?
2. Bad patches requires Valve to do something, you can't rollback
3. Hefty re-install
This one little developer has surely made Sierra Fists full of money from the HL+mod franchise. How many other games do you see on store shelves 5 years after it came out?
I'd really like to see Valve dump Vivendi and stick it out themselves. Online distribution IS possible, as steam has shown. Pox and all, it is possible.
Also, I'm not sure of Gabe Newell's motives of saying what he did, but back in the days of 2000 Broadband adoption was nowhere near what it is today (especially in the states). Maybe he actually wasn't lieing at that point?
So, are you telling the poster to abandon JVM's and use the .NET CLR which may or may not break third party tools just to simplify a seemingly small part of their entire development process?
.NET based libraries, why not just write a JNI wrapper for the sub-system using operator overloading? Seem rediculous? I do, but its better than changing the entire environment.
If you REALLY must use
the 1.0 syndrome. Is it really that surprising that is this not only EA's first XBox live title, but its also Microsoft's first third party vendor hosted service on XBox live. Typically if you haven't built proceedures and gotchas beforehand, things get forgotten, screwed up, etc...
Mind you, it could be said that this was ultimately the result of bad QA.
As a Canadian in a parlimentatary system, I'll tell you its not all roses.
There have been several minority governments; this happens when the winner doesn't garner 50% of the available seats.
In that case, the leading party usually teams up with another party to reach a majority standing in the house.
Anyways, the main point i'm trying to make is that out of all the monority governments none of them have lasted the four years. Every single one collapsed and forced a re-election.
Right now there's a minority government, so here's hoping everyone gets along!
Think of Mozilla's platform as Java-lite. You can write very small programs that utilize many built-ins that the browser supports. It has a deployment framework through 'extensions', etc..
.NET or Java in order to do their work.
.NET Runtime ~25MB
.NET installed (trust me from experience, they don't). Less means better in this case. The smaller the release, the more likely an admin would choose your solution.
Not everyone needs a fully library supported language like
As long as you can learn JavaScript, you can write mozilla extensions. I'm just wish that the Mozilla folks would make it easier to find info on how to develop the platform as a platform. From what I've read on their site, they target the 'Mozilla as-a platform' over 'Mozilla is-a platform'. They might find that free/comercial entities could find use in their platform and help develop it if they think there's more for them to use from it.
Think of thin-apps niche for a moment:
Java Runtime ~15MB
Mozilla Runtime ~5MB and that includes a browser
If you want to deploy Thin Client App xyz, which one do you choose? You can't assume that your customer has either Java or
Mozilla has less surface area which means there's less functionality built id but its more simple to develop for. The language is JavaScript which is used by throngs of web developers (the target market of this technology). You can look at the debate over web based Application distribution to see where Mozilla fits into things. (The new MS web services model, Java Web Start, Mozilla)
The poster was saying that once you buy a license for the product (usually flat rate), you will get the source code included with the release.
I've seen quite a few smaller java libraries released like this. It makes sense when you're dealing with small software component developers. If for some reason they go belly up or disappear (which happens often with little guys), you aren't forced to rip out the code and throw it away.
I can't say that this type of distribution would work well for many different software industries, but for some like the example above, it works great. Another idea would be to place code in escrow. If for some reason the developer is unable to fulfill an agreed upon service, the code is given to the buyer of the service.
"Linux now accounts for 15.5 percent of embedded projects"
In other words, more development projects are using Linux over other embedded OS's. So, Symbian may be running on 50% of all embedded devices in the world, but if only a select few comanies are using it, they're just regurgiting the same old thing. There may be 50 seperate symbian projects stemming from Nokia alone, but that wouldn't begin to dent the market share that Linux is forming.
This doesn't surprise me in the least. Symbian was designed for mobile phones, and basically little else. You look at the number of projects in Cell phones vs. the entire Embedded spectrum (which linux more or less competes) and you realize why Linux has such a market share when it comes to who it developing them.
Of course the stats are flawed as usual. You could say Linux has a 15% developer mind-share, but if they only account for 1% of all embedded 'sales', or 'revenue', that's really not that impressive at all.
If you've read ANYTHING about the SCO case, its that you can't hand out API's (erm LSB) and then turn around and sue anyone for using that interface (regardless of the distribution license). Imagine the anti-trust lawsuits of MS sueing a competitor xyz for implementing private API function xyz which makes the program twice as fast while implementing it themselves.
There is also discussion that it may be impossible to enforce copyright's for API's at all. Under fair-use laws, I believe that anyone can have the right to implement the API as long as its been released to the public in one form or the other. I can't remember all the details, but it was something along those lines.
The only cases that I've really seen developers going after vendors is when they take GPL copyrighted code lock stock and barrel and put it in their own systems without credit, source, or some other blatently obvious GPL violation (Netfilter, etc..).
That's good to know! Anyways, how does the card get powered if the system isn't on? Does it need powered ethernet or (more likely) does it use a special motherboard interface thats always powered?
So does SSH, which is actually the preferred method for low-bandwith consumption by some X developers. LBX was a kludge, we all know it.
e x.html
SSH tunneling solves the authentication and some of the bandwidth issues involved with X transport. Beyond that, Toolkits need to learn to behave with remoting their desktops. KeithP gave a prety good intro on these issues a long time ago:
http://keithp.com/~keithp/talks/usenix2003/
AND
http://keithp.com/~keithp/talks/lbxpost/ind
I can't say much against RDP. Its got a decent bandwidth usage, I've heard good things about Citrix more-so since they basically invented Remote Windows. The performance could be better, but it is sufficiant for most operations.
:-)
Negatives:
Client (TS Server) footprints are heavier which means you need a lot of hardware to support users. Citrix is good in that if you just need an app here and an app there, you can choose to just export the application, and not the entire virtual screen.
Licensing is and will forever doom TS to an obsurity even in windows. The price point is unrealistic for home/small business and even medium sized businesses will likely only use it sparcely. Ditto for ICA, but i'd say only large companies would use ICA. Its a indispensible feature that fillers like VNC and PC Anywhere will likely never be able fill.
PS: XP bans all foreign windowing tools that aren't licensed, aka RDP/ICA. I love that MS doesn't use its monopoly powers for evil
Two words: BIOS Support
In order to support boot style KVM abilities that hardware KVM's offer, the BIOS has to boot an entire IP stack and daemon to support the integrated KVM functionality, and don't forget the network drivers needed to support the network card. This would be quite heavy. It isn't as simple as the interface between the bios and net boot roms.
I guess this could actually be integrated into network boot roms and add a new differentiator to the innovation stagnent NIC ASIC market. Just to note, the bios would still need to support it, but that interface would be pretty simple.
Amen brother!
I know so many people with university education that are incompetent and I know some that are absolutely briliant.
The school doesn't make the man/woman, its their own drive, determination, and their capacity for knowledge.
As for grand-poster: I personally don't relate to the relevence of Calculus or Physics to Programming. I've been in many jobs, and the extent of my math usage has been algebraic. Yes, if your working on weather patterns, then sure it'll help, but look at it this way: If your working on an accounting software package you're better off having a diploma in accounting. If you're working on GUI's you may decide that User Interface Design courses are more applicable than calculus.
Maybe this was a few yesrs ago, but aren't jtag programmers pretty fcking expensive?
Hey, lets be reasonable. I think its perfectly reasonable given the current state of software hedgonomy.
Fact: There are MANY MANY MANY software products on windows that are unavailable on *NIX/Linux. There are also many specialized apps that are only available on *NIX/Linux.
If just one Windows and *NIX program ran client heavy, you'd need two physical PC's to handle them (or else some type of poor man's Virtualization).
I'd be hard pressed to run RemoteX based CAD programs and the like. I don't think I'm alone here either.
Well, I'd like to try, but I wouldn't want to loose my job when it blows up.
Suse? Are you on drugs?
1. JDS is a GNOME-centric system. Am I not mistaken in thinking GNNOME takes a back seat to KDE on Suse?
2. JDS server requirements are based on Redhat software. I suppose its possible that they used Suse for the client and Redhat for the servers, but very unlikely.
Spoof integrity will always come down to two factors:
1. Verification of Sender - This will never happen unless systems like cacert.org start to take off. Basically 99% of the internet don't give a damn about certificates, and the ability for anonymity is more limited. A debate about privacy/spam could go on for years if given the chance.
2. SPF-like protocols - This is the ability to discriminate who is and who isn't allowed to send email from a given domain. This will cause a few things:
- a. Every mail sender must be from a domain
- b. Every mail sender has to route through an institutional server (the road warrior problem)
- c. Every institutional mail server must deny relaying from anyone non-authenticated. (Should be done already)
- d. Institution must be regarded positively by the community at large. If they aren't, they're completely eliminated from sending emails.
- e. You have to get DNS servers that you can update.
- f. You must lock down the DNS server from attacks (Have you done this lately?)
Anyways, both solutions are possible, but neither are ideal for everyone. SPF has a real chance of shutting down spoammers, but I imagine the wild west internet we know is pretty much over.
You have to have a working IT economy in those areas before you can outsource anything to them. Its like outsourcing IT operations to Ebonia.
That said, if WVa or TN has a viable IT marketplace with a good set of IT individuals, then great. If you're trying to plant an office in Farmsville USA, then you shouldn't expect much. Just because you live there doesn't mean there are enough of you.
I'm pretty sure that the Manufacturing and Textiles have NOT come back to America, unless your talking Mexico...
Once the process has been streamlined, there won't be anything but politics and laws to control outsourcing.
Now, we havre to come up with the 'next big industry' to stay above everyone else. I was thinking TV-Blog star!
I have friends in Vancouver that work shifts throughout the night. It Happens.
Any attack on click-through licensing means that open source software is more open to the same legal punishments. If someone found a disasterous bug in Linux, would people have a right to sue Linux,OSDL, etc.? I bloody hope not.
Now the problem is that companies buying software don't require full guarantees. If the DOD says this software must be perfect, then its the onus on the Seller to supply that guarantee.
This allows for open source companies to guarantee software without forcing every Linux distributor to get hit with the lawsuits.