Re:Should have released it on Monday
on
FreeBSD 5.3 Released
·
· Score: 1, Flamebait
November 1st, you know "Day Of The Dead" and all that. November second is Day Of the Dead (all souls day). If you're going to troll, at least do it with some intelligence... If not, you're just another stroke (pun intended) repeating the same warmed over hash.
I've read programs that I thought were obfuscated, but later found out were just poorly written. Some user has in their.signature here: "That's not encrypted - that's a perl script I'm working on." from crObar's now defunct matrix parody.
apache doesn't follow that, though it skips releases every once in a while when it finds the release has a bug. They put out brand new code, and don't reuse the version number.
I don't really want to change over to a pre-1.0 release unless someone can convince me that it is prety darn stable and feature-complete You do realize that these are two separate questions and have two completely different answers. Stability: objective measurement of how many crashes and lockups you typically have. From what I hear, Thunderbird is pretty solid Feature complete: subjective, does it fit my model of what a mail client should look like and do. You can't ask anyone this, you have to try for yourself. If you have an IMAP mail account, you can test it without disrupting your current mail workflow too much
C++ supports// comments! how can you pass that up? I know this was a joke, but gcc has supported// for years. The newer versions of the C spec (I think starting with C99) has made this an official part of the language.
i don't see the need to taint that image of proper tried and tested built like a brick *nix reputation, really the kernel should be written in assembly (since its _ment_ to be for the x86) but c isn't too far off. C actually was created to make UNIX more portable. C was created to do all the higher level parts of UNIX, and only the really fast bits needed to be assembler. At the time, there was a lot more diversity in machine hardware, and having it written in assembler would have very much slowed its early growth. Yes, Linux started on the x86 line, mostly as an excuse for Linus to hack around with the 386's new features, but it's on many architectures now. Targetting even solely x86 now would be a challenge, since there are so many x86's to choose from. Do you really want to spend time hand tuning your assembler to perform well both on plain 386 machines, and OOO and Pentium4 HT units? Or do you say the compiler people can deal with this tuning crap and you can get your work done.
Jokes aside, NT was actually the first OS certified as POSIX compliant. MS needed it so certified because a lot of government contracts required POSIX compliance. At first, UNIX companies were slow getting this certification, essentially believing the obviousness of them being UNIX would eliminate the need for the certification (the process wasn't free you know). Once they started losing contracts to MS, they all got certified.
The original NT was a microkernel will "personalities" not altogether different than the current MacOS X, and it shipped with OS/2 command line and POSIX environments. The non-Win32 environments were bare bones, just enough to scrape by with the certification (in the POSIX case) or satisfy contractual obligations (in the OS/2) case. MS has since dropped all pretense of supporting OS/2, and has moved in a different direction to support POSIX with the new SFU (which should be USFW if you ask me).
By the way, you got the ordering wrong. One of the first productivity studies was in a factory where the researcher first reduced the light, and productivity increased; then the researcher increased the light, and productivity still increased. The end result is that worker productivity increased indirectly merely by changing the work environment.
They had a theory that increasing the light would increase productivity, that efficiency was based on some purely physical aspects, and that aiding these physical aspects (like ability to see because of available light) and people would basically respond to thse in easily calculable formulas. They knew base productivity, so they started increasing light from there, and productivity rose. After they proved themselves right, they decided to "extend the curve" to see what the graph would look like with less light, expecting decreases as extensions of the physical graph they had alreday "proved". They found that there was an emotional component, that people improved even though the physical situation was worse, and in fact kept improving until it got close to twilight lighting levels. This was groundbreaking, and led to a lot of further research on the nature of employees as people, and lead to a newe branch of psychology.
Hmm, the Hawthorne Effect is a bit deeper than just changing the work environment, it's that they realized they were being studied, so they increased productivity. They wanted to have the experiment "work" so they did what they thought they wanted, increase productivity, even when the light was dimmed to candlelight intensity. This is why we have control groups. Awareness of being studied and wanting to do the "right" thing for the experiment is a confounding factor.
As a trivia thing, I actually lived not that far from there. It was the Western Electric Hawthorne works plant, Cicero and around 24th just outside of Chicago. My best friend's dad still wears his old jackets every once in a while. It's now a strip mall. I doubt that maybe.00001% of the people that go by there have any idea that some of the great work psychological experiments were performed somehwere in (what's now) that parking lot.
This isn't a beta, it is a developer preview for ISVs to get their hands on the new technogies and target them. The price is because Apple had to make a cut at some point and spend developer and QA resources to polish up a release that will never sell in general availability. These developers cost money, and they need to be paid. Developers have a much higher threshhold for prices than the general public does. Can you really say to your CEO "well, we can save $300 and change if we have all of our developers just sitting around for 6 months, and let's not worry about the competition that's going to have a 6 month head start either...".
The price also acts as a filter. Joe Schmo will not get this. Only ISVs and hard core techies will get this. This filters a lot of support calls, and probably makes them hugher quality as well, since any bugs in the DP may affect the ISV's ability to make money, so it's in his financial interest to make the bug process as clean as possible.
Re:Here's what i want in a spam filter...
on
DSPAM v3.2 Released
·
· Score: 1
Hmm, with forged headers and tons of SPAM coming from zombie windows hosts, this seems to just add to the noise without any real chance of fixing anything.
Unix is designed for development. The original UNIX was designed as a document processing system. Development is just a means, not an end. OSes are used to run apps. Windows, whether or not you like it, has a set of tools failry well designed to get people coding quickly. The back end APIs are a bit icky at times though.
Secondly, it would be a very rare and odd thing for your unix code not to be easily portable to the Windows environment. Whether it's portable doesn't necessarily make it usable. Windows has a very different paradigm than UNIX does. Cygwin is just a compatibility layer. It's not native, and performance will suffer. It also adds a complexity layer. It is good for making UNIX utilities run on Windows, it is not good for cross platform development.
For whomever decides to submit the article for the RELEASE of 5.3 would you please post a torrent? THis is a little less necessary for FreeBSD. A majority (though of course not all) people who would use Beta 7 would be people actively tracking 5.3 sequence, meaning they'd be much more likely using cvsup, not downloading full isos. A smaller subset of people would need the ISO, thinking that it will be out of date in a very short period of time, and if they're going to go through the trouble of downloading full isos, then burn them, they'd just wait for 5.3-RELEASE. I for one installed 4.8 off of floppies, now up to 4.10 through cvsup.
Another difficulty, how do you know how that word is used, it may be part of a legitimate discussion, or it may be a troll. I remember web filtering horror stories, where pages of honors graduates "cum laude" and breast cancer pages were blocked.
Funny story, I had dsl installed recently, during install the guy couldn't make an account. Finally tracked it down to my name it didn't like the homo in homolka. I changed my account name, and it worked fine.
All things move from amateur to professional.
on
Amateur Revolution?
·
· Score: 1
When I first saw that list, I was thinking all of things were at one time amateur (and still may be at some level) but are now more or less commercial. We're runnign redhat, essentially a fork of Linux that gets a lot of upstream stuff. Rap is now big time commercial (I knew it was gone when I heard a radio commercial for a local micro-brewery with the "German Brewmesiter Rap"). Russel Simmons and Puffy have no qualms about saying they want to create rap empires, super commercial. THe only change is the mix of who owns what.
1) You can do multiple master with OpenLDAP if you read the configure file, but it's probably alpha quality code, and I wouldn't recommend in production. It does seem to "want to do" just hasn't polished the code. as an aside, we run multiple master, and a lot of our breakage comes from this. 2) OpenLDAP is multithreaded as well, not multiple processes.
The big issue we've found (and we run both) is complexity. OpenLDAP is a simple daemon, vs. netscape/iplanet is more of an environment, with a config directory server and an admin server besides your base server. With OpenLDAP, it's easier for me to wrap the daemon with a restart loop, we haven't done this yet with netscape, too many internal pieces, and I think we'd break the admin server if we did.
The contax full frame is even more expensive. Now there are a few full 35mm frame SLRs, none cheap.
The 1Ds, 2 versions. The Kodak which now has 3 different mounts, Canon, Sigma, and Nikon. The weird thing, this may be actually 2 cameras, the old version used a Nikon body and mount, the new one uses Sigma for the Sigma and Canon, presumably since Canon people would throw a fit. I'm assuming Nikon F80 for the Nikon mount still. And the Contax, which is still 5 figures I think.
"Pre-development", do you mean this is before any code is written? Were those screenshots drawn in crayon? If you're releasing code for public consumption it's no longer pre-development. Call it alpha/beta whatever, but it's time to stop hedging bets and call everything "pre-pre-pre-release".
If part of the greatness of the open source model is people using code early and often and giving you feedback, then punting all issues back saying "we're not going to support you, this is pre-pre-pre-release" just goes against that model.
Slashdot Mirror
November 1st, you know "Day Of The Dead" and all that.
November second is Day Of the Dead (all souls day).
If you're going to troll, at least do it with some intelligence... If not, you're just another stroke (pun intended) repeating the same warmed over hash.
Check it out
Hmm, can we slashdot fark, or will it fark slashdot?
Saved search folders are part of Outlook 2003, which was probably the original inspiration.
I've read programs that I thought were obfuscated, but later found out were just poorly written. .signature here:
Some user has in their
"That's not encrypted - that's a perl script I'm
working on." from crObar's now defunct matrix parody.
Hmm, Pinto 1.0 wuz da bomb...
apache doesn't follow that, though it skips releases every once in a while when it finds the release has a bug. They put out brand new code, and don't reuse the version number.
I don't really want to change over to a pre-1.0 release unless someone can convince me that it is prety darn stable and feature-complete
You do realize that these are two separate questions and have two completely different answers.
Stability: objective measurement of how many crashes and lockups you typically have. From what I hear, Thunderbird is pretty solid
Feature complete: subjective, does it fit my model of what a mail client should look like and do. You can't ask anyone this, you have to try for yourself. If you have an IMAP mail account, you can test it without disrupting your current mail workflow too much
C++ supports // comments! how can you pass that up? // for years. The newer versions of the C spec (I think starting with C99) has made this an official part of the language.
I know this was a joke, but gcc has supported
i don't see the need to taint that image of proper tried and tested built like a brick *nix reputation, really the kernel should be written in assembly (since its _ment_ to be for the x86) but c isn't too far off.
C actually was created to make UNIX more portable. C was created to do all the higher level parts of UNIX, and only the really fast bits needed to be assembler. At the time, there was a lot more diversity in machine hardware, and having it written in assembler would have very much slowed its early growth.
Yes, Linux started on the x86 line, mostly as an excuse for Linus to hack around with the 386's new features, but it's on many architectures now. Targetting even solely x86 now would be a challenge, since there are so many x86's to choose from. Do you really want to spend time hand tuning your assembler to perform well both on plain 386 machines, and OOO and Pentium4 HT units? Or do you say the compiler people can deal with this tuning crap and you can get your work done.
Jokes aside, NT was actually the first OS certified as POSIX compliant. MS needed it so certified because a lot of government contracts required POSIX compliance. At first, UNIX companies were slow getting this certification, essentially believing the obviousness of them being UNIX would eliminate the need for the certification (the process wasn't free you know). Once they started losing contracts to MS, they all got certified.
The original NT was a microkernel will "personalities" not altogether different than the current MacOS X, and it shipped with OS/2 command line and POSIX environments. The non-Win32 environments were bare bones, just enough to scrape by with the certification (in the POSIX case) or satisfy contractual obligations (in the OS/2) case. MS has since dropped all pretense of supporting OS/2, and has moved in a different direction to support POSIX with the new SFU (which should be USFW if you ask me).
and me without mod points...
By the way, you got the ordering wrong.
One of the first productivity studies was in a factory where the researcher first reduced the light, and productivity increased; then the researcher increased the light, and productivity still increased. The end result is that worker productivity increased indirectly merely by changing the work environment.
They had a theory that increasing the light would increase productivity, that efficiency was based on some purely physical aspects, and that aiding these physical aspects (like ability to see because of available light) and people would basically respond to thse in easily calculable formulas. They knew base productivity, so they started increasing light from there, and productivity rose. After they proved themselves right, they decided to "extend the curve" to see what the graph would look like with less light, expecting decreases as extensions of the physical graph they had alreday "proved". They found that there was an emotional component, that people improved even though the physical situation was worse, and in fact kept improving until it got close to twilight lighting levels. This was groundbreaking, and led to a lot of further research on the nature of employees as people, and lead to a newe branch of psychology.
Hmm, the Hawthorne Effect is a bit deeper than just changing the work environment, it's that they realized they were being studied, so they increased productivity. They wanted to have the experiment "work" so they did what they thought they wanted, increase productivity, even when the light was dimmed to candlelight intensity. This is why we have control groups. Awareness of being studied and wanting to do the "right" thing for the experiment is a confounding factor.
.00001% of the people that go by there have any idea that some of the great work psychological experiments were performed somehwere in (what's now) that parking lot.
As a trivia thing, I actually lived not that far from there. It was the Western Electric Hawthorne works plant, Cicero and around 24th just outside of Chicago. My best friend's dad still wears his old jackets every once in a while. It's now a strip mall. I doubt that maybe
This isn't a beta, it is a developer preview for ISVs to get their hands on the new technogies and target them. The price is because Apple had to make a cut at some point and spend developer and QA resources to polish up a release that will never sell in general availability. These developers cost money, and they need to be paid. Developers have a much higher threshhold for prices than the general public does. Can you really say to your CEO "well, we can save $300 and change if we have all of our developers just sitting around for 6 months, and let's not worry about the competition that's going to have a 6 month head start either...".
The price also acts as a filter. Joe Schmo will not get this. Only ISVs and hard core techies will get this. This filters a lot of support calls, and probably makes them hugher quality as well, since any bugs in the DP may affect the ISV's ability to make money, so it's in his financial interest to make the bug process as clean as possible.
Hmm, with forged headers and tons of SPAM coming from zombie windows hosts, this seems to just add to the noise without any real chance of fixing anything.
Actually prosco.com has a cybersquatter on it now. That didn't take long.
Silly post, flames are for kids...
Unix is designed for development.
The original UNIX was designed as a document processing system. Development is just a means, not an end. OSes are used to run apps. Windows, whether or not you like it, has a set of tools failry well designed to get people coding quickly. The back end APIs are a bit icky at times though.
Secondly, it would be a very rare and odd thing for your unix code not to be easily portable to the Windows environment.
Whether it's portable doesn't necessarily make it usable. Windows has a very different paradigm than UNIX does.
Cygwin is just a compatibility layer. It's not native, and performance will suffer. It also adds a complexity layer. It is good for making UNIX utilities run on Windows, it is not good for cross platform development.
We use SourceSafe for version control.
My condolences.
For whomever decides to submit the article for the RELEASE of 5.3 would you please post a torrent?
THis is a little less necessary for FreeBSD. A majority (though of course not all) people who would use Beta 7 would be people actively tracking 5.3 sequence, meaning they'd be much more likely using cvsup, not downloading full isos. A smaller subset of people would need the ISO, thinking that it will be out of date in a very short period of time, and if they're going to go through the trouble of downloading full isos, then burn them, they'd just wait for 5.3-RELEASE. I for one installed 4.8 off of floppies, now up to 4.10 through cvsup.
Another difficulty, how do you know how that word is used, it may be part of a legitimate discussion, or it may be a troll. I remember web filtering horror stories, where pages of honors graduates "cum laude" and breast cancer pages were blocked.
Funny story, I had dsl installed recently, during install the guy couldn't make an account. Finally tracked it down to my name it didn't like the homo in homolka. I changed my account name, and it worked fine.
When I first saw that list, I was thinking all of things were at one time amateur (and still may be at some level) but are now more or less commercial. We're runnign redhat, essentially a fork of Linux that gets a lot of upstream stuff. Rap is now big time commercial (I knew it was gone when I heard a radio commercial for a local micro-brewery with the "German Brewmesiter Rap"). Russel Simmons and Puffy have no qualms about saying they want to create rap empires, super commercial. THe only change is the mix of who owns what.
1) You can do multiple master with OpenLDAP if you read the configure file, but it's probably alpha quality code, and I wouldn't recommend in production. It does seem to "want to do" just hasn't polished the code.
as an aside, we run multiple master, and a lot of our breakage comes from this.
2) OpenLDAP is multithreaded as well, not multiple processes.
The big issue we've found (and we run both) is complexity. OpenLDAP is a simple daemon, vs. netscape/iplanet is more of an environment, with a config directory server and an admin server besides your base server. With OpenLDAP, it's easier for me to wrap the daemon with a restart loop, we haven't done this yet with netscape, too many internal pieces, and I think we'd break the admin server if we did.
How about donkey kong instead
The contax full frame is even more expensive. Now there are a few full 35mm frame SLRs, none cheap.
The 1Ds, 2 versions.
The Kodak which now has 3 different mounts, Canon, Sigma, and Nikon. The weird thing, this may be actually 2 cameras, the old version used a Nikon body and mount, the new one uses Sigma for the Sigma and Canon, presumably since Canon people would throw a fit. I'm assuming Nikon F80 for the Nikon mount still.
And the Contax, which is still 5 figures I think.
"Pre-development", do you mean this is before any code is written? Were those screenshots drawn in crayon? If you're releasing code for public consumption it's no longer pre-development. Call it alpha/beta whatever, but it's time to stop hedging bets and call everything "pre-pre-pre-release".
If part of the greatness of the open source model is people using code early and often and giving you feedback, then punting all issues back saying "we're not going to support you, this is pre-pre-pre-release" just goes against that model.
Render /. correctly 100% of the time?
This is patched in the trunk, releases... umm, real soon now