Well, we know the components of glycine, and we can synthesize it. It's not unreasonable to imagine that it can form from reaction with other elements: on or off our planet.
Just so happens we found some off.
It's even STILL possible that terristerial glycine is responsible for us, and this is just some other source.
Man I don't get how people are so polarized about this. Look dudes. It's against the law to infringe copyrighted material. It's against the law to aid somebody else breaking the law. File sharing therefor is Against The Law. It is the Proper Decision for these people to be convicted. Anything else would make me think the judges were asleep at the wheel.
If you dislike that so much, don't focus on whether somebody wins or loses these cases. It is Proper that they lose. It would be Wrong if the law bent so much to allow what is clearly outlawed. Instead, seek to CHANGE the law. Donate to lobbyists. Become lobbyists yourself. Civil disobedience is fine, but don't expect to get off the hook for doing it until you change the law.
Wrong. Atheist. a-theist. Negating theist. Anybody who is not a theist is an atheist. Answering "I don't know" to "is there a god?" makes you an atheist.
This is silly. An atheist is somebody who does not believe in God. Period. Atheist. Not a theist. Theist with an a in front of it. It's not that hard.
Is there a God?
A) Yes.
B) I don't know.
C) No.
A) is a theist. B) and C) are both not theists, therefor, atheists.
Agnostic is a seperate and overlaying word. No knowledge. Most people without knowledge answer B). That makes them an atheist and agnostic, at the same time.
I'm just going to throw this out there. I'm evaluating upgrading out existing Office install from 2003 to 2007. The cost for this is around $400 per desktop, $650 if we do software assurance. That's $650 per machine in the office. Some of these machines we bought from dell for $400. That means Office costs more than the entire computer and Windows itself.
But I suspect we're still going to do it.
Why? Because We're talking $650 for basically 3 years of productivity software per individual. That's about a week of salary for an employee. In total it makes back WAY more than a week of an employee's time over 3 years. So it may feel like a huge amount of money up front. And it is. But it *is* worth it.
Because there is a finite amount of sperm. This is about allocation of sperm. Allocate more sperm to attractive females, where attractiveness is established by ability to care for offspring. Strong body. Upright posture. Features which hint at youth, etc. The genes which then cause you to do the allocation are promoted more strongly.
I have worked on far more.Net server-side code bases in the last few years than Java. Far more. I get Java offers too, but the.Net ones come in quite a bit more often..Net web services are super easy to use (basically you just drop a file in a directory and it works)..Net remoting. And now WCF. And of course ASP.Net web sites, which is basically serverside code.
It's been ages since I've had a serious project that used servlets come to light.
Disclaimer: I work in the small business sector, which massively out numbers the large business sector in terms of number of applications. Maybe not size of individual applications, but certainly totals. Java in this realm is essentially disappearing (in the US).
I'd use AD for everything. It works out of the box. Isn't that expensive. Does replication properly. Tracks site locality. Is expandable instantly to huge networks. Has Kerberos set up perfectly by default. There's really no downside to using it in my experience. All of hte other solutions require massive hand holding. Linux can auth against it either as a normal LDAP directory, or using Winbind. Winbind recommended.
I think this stuff is absolutely stupid. If the BIOS were to just get out of the way in 0 seconds and begin booting the OS I'd have a desktop in 4 seconds. My Linux loads that quickly. If they can make Linux in the BIOS load that quickly, they can make Linux from a SSD load that quickly. The problem is the huge post steps. Long pauses. Scanning CD drives when there are no CDs.
Or do what the G1 does... use normal OS security between apps. The G1 just uses a different Unix UID per app. You can already run native code on it (with the caveat that you have to distribute said native code wrapped in Java stuff so the phone can be persuaded to run it.)
G1 apps can actually spawn bash. That's how Terminal.apk works. The Terminal app actually has it's own UID, and it just forks() a copy of bash. Of course, that bash is limited to the Terminal UID: app_XX or something.
The idea of a UID per app should be used on desktops too (though implemented a layer below that)
I don't get it. Can't you do this with Vista? And XP? Wasn't that the point of the Windows Components option in Add/Remove?
I know each of these components on XP can be disabled with an autoanswer file during install... so I only assumed it was some package-like thing.
Pushing printers will not happen automatically. Printers will not be stored in LDAP. You will not have interfaces to 'find users and groups', or to identify computer accounts.
You will not be able to delegate control to certain users to give them permission to join computers to the domain.
You will not be able to store ACLs in the LDAP tree itself, if using OpenLDAP, instead they will be stored in the text configuration file. With RDS you can do this, but there is no UI to edit them. And you have to make them by hand.
When configuring anything, you will have to play with saslauthd. You will have to play with pam. You will have to understand pam like the back of your hand. And NSS.
Desktops and laptops will not do credential caching by default. Disconnect from the network, desktop freezes.
Kerberos creds won't store in LDAP without some Samba patches. DNS won't store in LDAP without Bind patches. There is no such thing as group policy. You cannot have nested groups. You will have to manually unify UIDs. You will not have automatic UID allocation. Your UIDs will not be scoped to the domain.
There is no comparable solution. Choosing anything else is a massive disservice to your users and the people responsible.
AD is set up by default to work properly. It requires minimal maintence. It supports multimaster replication, automatically doing nearly everything required.
It uses Kerberos. It does your DNS for you. Windows works perfectly with it. Linux sort of works with it with Samba.
Your alternatives in the FOSS space are basically seting up FDS or OpenLDAP by hand. THat means making the schema by hand. OpenLDAP does not do multimaster replication.
You will have to hand configure kerberos. You will have to manage most maintence tasks by hand, using tools like some Java LDAP UIs, which expose raw LDAP information to you. You will not have an easy interface to 'create users'. You will have interfaces to edit LDAP databases.
FDS is a better LDAP server: but it is STILL JUST AN LDAP SERVER. It does not take care of DNS. It does not do Kerberos.
Novel's commercial offerings are the closest: but they are woefully hard to get set up compared to AD, and they cost just about the same.
Well, some of this is inevitable, and something you can't change. People are spending time writing free software, and it will undercut commercial software... and you can't stop these people.
The fundamental problem is pretty much exactly as MS says it. A commercial software is written, extensive R&D is done on the target market in order to design it, it's released, and a year later somebody else has simply copied the idea.
It goes to show that the SOFTWARE isn't the important part there. It's the IDEA. This is why MS makes claims about innovation all the time.
Most of the industry already knows this, and their solution is simple: protect the idea. Patents. And you know what? I can't think of any better idea. The alternative is to let it continue. Maybe that is an alternative. The best we can do then is guess about the future... will people just stop investing in R&D? I don't know for sure.
And if you're idealogically against patents for some reason, well... I can't help you! There are some people ideaologically against private property ownership at all. I can't help them either. =)
Slashdot Mirror
Well, we know the components of glycine, and we can synthesize it. It's not unreasonable to imagine that it can form from reaction with other elements: on or off our planet.
Just so happens we found some off.
It's even STILL possible that terristerial glycine is responsible for us, and this is just some other source.
Man I don't get how people are so polarized about this. Look dudes. It's against the law to infringe copyrighted material. It's against the law to aid somebody else breaking the law. File sharing therefor is Against The Law. It is the Proper Decision for these people to be convicted. Anything else would make me think the judges were asleep at the wheel.
If you dislike that so much, don't focus on whether somebody wins or loses these cases. It is Proper that they lose. It would be Wrong if the law bent so much to allow what is clearly outlawed. Instead, seek to CHANGE the law. Donate to lobbyists. Become lobbyists yourself. Civil disobedience is fine, but don't expect to get off the hook for doing it until you change the law.
As a lawyer. Duh. The lawyer will probably tell you that copyright applies.
And when has this happened? Link please.
Wrong. Atheist. a-theist. Negating theist. Anybody who is not a theist is an atheist. Answering "I don't know" to "is there a god?" makes you an atheist.
This is silly. An atheist is somebody who does not believe in God. Period. Atheist. Not a theist. Theist with an a in front of it. It's not that hard. Is there a God? A) Yes. B) I don't know. C) No. A) is a theist. B) and C) are both not theists, therefor, atheists. Agnostic is a seperate and overlaying word. No knowledge. Most people without knowledge answer B). That makes them an atheist and agnostic, at the same time.
I'm just going to throw this out there. I'm evaluating upgrading out existing Office install from 2003 to 2007. The cost for this is around $400 per desktop, $650 if we do software assurance. That's $650 per machine in the office. Some of these machines we bought from dell for $400. That means Office costs more than the entire computer and Windows itself. But I suspect we're still going to do it. Why? Because We're talking $650 for basically 3 years of productivity software per individual. That's about a week of salary for an employee. In total it makes back WAY more than a week of an employee's time over 3 years. So it may feel like a huge amount of money up front. And it is. But it *is* worth it.
Because there is a finite amount of sperm. This is about allocation of sperm. Allocate more sperm to attractive females, where attractiveness is established by ability to care for offspring. Strong body. Upright posture. Features which hint at youth, etc. The genes which then cause you to do the allocation are promoted more strongly.
I have worked on far more .Net server-side code bases in the last few years than Java. Far more. I get Java offers too, but the .Net ones come in quite a bit more often. .Net web services are super easy to use (basically you just drop a file in a directory and it works). .Net remoting. And now WCF. And of course ASP.Net web sites, which is basically serverside code.
It's been ages since I've had a serious project that used servlets come to light.
Disclaimer: I work in the small business sector, which massively out numbers the large business sector in terms of number of applications. Maybe not size of individual applications, but certainly totals. Java in this realm is essentially disappearing (in the US).
I agree with the ruling. Seems retarded to remove the paper's free speech. Good job judge!
Oh. I was thinking our government will probably just lower the taxes... since you know, the company is the one with the bargaining power here.
Uh huh. So what's wrong with AD?
Wait. Problems like what? It supports LDAP and Kerberos. You can query it just fine.
Plays fine. The problem of the PAC means Linux Kerberos servers cannot serve Windows clients. Nothing to do with the reverse.
I'd use AD for everything. It works out of the box. Isn't that expensive. Does replication properly. Tracks site locality. Is expandable instantly to huge networks. Has Kerberos set up perfectly by default. There's really no downside to using it in my experience. All of hte other solutions require massive hand holding. Linux can auth against it either as a normal LDAP directory, or using Winbind. Winbind recommended.
I think this stuff is absolutely stupid. If the BIOS were to just get out of the way in 0 seconds and begin booting the OS I'd have a desktop in 4 seconds. My Linux loads that quickly. If they can make Linux in the BIOS load that quickly, they can make Linux from a SSD load that quickly. The problem is the huge post steps. Long pauses. Scanning CD drives when there are no CDs.
Or do what the G1 does... use normal OS security between apps. The G1 just uses a different Unix UID per app. You can already run native code on it (with the caveat that you have to distribute said native code wrapped in Java stuff so the phone can be persuaded to run it.) G1 apps can actually spawn bash. That's how Terminal.apk works. The Terminal app actually has it's own UID, and it just forks() a copy of bash. Of course, that bash is limited to the Terminal UID: app_XX or something. The idea of a UID per app should be used on desktops too (though implemented a layer below that)
I don't get it. Can't you do this with Vista? And XP? Wasn't that the point of the Windows Components option in Add/Remove? I know each of these components on XP can be disabled with an autoanswer file during install... so I only assumed it was some package-like thing.
Dumb ass. You gave them permission when you ran their installation .exe on your system. Don't run it if you don't want them to do shit.
I'd also like to add that AD has been done and tested on huge networks since Windows 2000. This has not.
All the good stuff seems to be in Version 2, which is not released.
Pushing printers will not happen automatically. Printers will not be stored in LDAP. You will not have interfaces to 'find users and groups', or to identify computer accounts. You will not be able to delegate control to certain users to give them permission to join computers to the domain. You will not be able to store ACLs in the LDAP tree itself, if using OpenLDAP, instead they will be stored in the text configuration file. With RDS you can do this, but there is no UI to edit them. And you have to make them by hand.
When configuring anything, you will have to play with saslauthd. You will have to play with pam. You will have to understand pam like the back of your hand. And NSS. Desktops and laptops will not do credential caching by default. Disconnect from the network, desktop freezes. Kerberos creds won't store in LDAP without some Samba patches. DNS won't store in LDAP without Bind patches. There is no such thing as group policy. You cannot have nested groups. You will have to manually unify UIDs. You will not have automatic UID allocation. Your UIDs will not be scoped to the domain.
There is no comparable solution. Choosing anything else is a massive disservice to your users and the people responsible. AD is set up by default to work properly. It requires minimal maintence. It supports multimaster replication, automatically doing nearly everything required. It uses Kerberos. It does your DNS for you. Windows works perfectly with it. Linux sort of works with it with Samba. Your alternatives in the FOSS space are basically seting up FDS or OpenLDAP by hand. THat means making the schema by hand. OpenLDAP does not do multimaster replication. You will have to hand configure kerberos. You will have to manage most maintence tasks by hand, using tools like some Java LDAP UIs, which expose raw LDAP information to you. You will not have an easy interface to 'create users'. You will have interfaces to edit LDAP databases. FDS is a better LDAP server: but it is STILL JUST AN LDAP SERVER. It does not take care of DNS. It does not do Kerberos. Novel's commercial offerings are the closest: but they are woefully hard to get set up compared to AD, and they cost just about the same.
Well, some of this is inevitable, and something you can't change. People are spending time writing free software, and it will undercut commercial software... and you can't stop these people. The fundamental problem is pretty much exactly as MS says it. A commercial software is written, extensive R&D is done on the target market in order to design it, it's released, and a year later somebody else has simply copied the idea. It goes to show that the SOFTWARE isn't the important part there. It's the IDEA. This is why MS makes claims about innovation all the time. Most of the industry already knows this, and their solution is simple: protect the idea. Patents. And you know what? I can't think of any better idea. The alternative is to let it continue. Maybe that is an alternative. The best we can do then is guess about the future... will people just stop investing in R&D? I don't know for sure. And if you're idealogically against patents for some reason, well... I can't help you! There are some people ideaologically against private property ownership at all. I can't help them either. =)