Saturn V was a 'multi-gear' rocket. To lift off the pad, all 5 main rockets fired. As altitude increased, the center rocket turned off to minimize stress on the rocket (stay subsonic???)
Space shuttle also has multiple speeds. If you remember the Challenger disaster - the last message from ground was "Go with throttle up" Apparently the shuttle was high enough to go full throttle (again) and not worry about aerodynamic stresses.
Most liquid fueled rockets are throttleable. Both the space shuttle and Saturn V's throttle down to avoid putting "too much stress" on the airframe. What this really means, is that they didn't want to put more weight into airframe structure, and instead reduce throttle to the point where the atmosphere thins enough that one can throttle up without surpassing the design strength of the airframe. By the way, this point is called Max-Q and for the space shuttle, it is at 11km in altitude. For the space shuttle main engines, this means they throttle up to 104% of specification power (due to improvements over the years, the SSME maximum safe throttle is actually 109% of specification).
One of the issues with the shuttles solid rocket boosters - they are steerable - allowing insertion into a very precise orbit.
Compare that with the typical home built - solid rocket, that basically goes were you point it...usually...give or take a bit.
The problem with solid rocket motors for space travel is two fold. The first is that they cannot be throttled or turned off. The second is that they are considerably less efficient pound-for-pound than liquid fueled rockets. The typical measure of rocket efficiency is specific impulse, which is measured in seconds. For example, the solid rocket boosters of the shuttle have a specific impulse of 242 seconds, while the space shuttle main engines produce a specific impulse of 363.
Google hired developers to work on OpenOffice.org, but found it difficult to fill all the vacancies. They seemed unwilling to work on the project understaffed and the people they hired now work on other things.
Based on your account number, your obviously not new around here
Back in my day, when trolls were trolls and karma was numeric, slashdot was too obscure for companies to astroturf. It was fanboi vs fanboi for glowing praise and the comment threads were full of flame. How I miss the days of ole'. It just makes me want to pour hot grits down my pants.
Did they finally add the "write my code for me" command? It seems to be one of the few things emacs hasn't implemented. I suppose a "materialize a 5'4 asian Girl Friend" command would be useful too. I think we should push for that in the next revision.
It's all in there, you just don't know the right modeline.
While the proposed act may make the attempts to infringe illegal, there are more pressing loopholes in existing copyright law.
Currently, consumers can view or hear content and later recall it without paying royalties. While humming a tune to yourself or quoting bits of recalled dialog is clearly a 'performance,' and therefore infringement, if they are particularly attentive during the 'performance,' they may even be able to visualize or 'hear' it in their memory. Does this not consist of infringement? This Brain-Hole is of far greater concern than other sorts of grey area infringement. We must close the Brain-Hole and ensure that there is still an incentive to create.
Who will be first to introduce such a bill? Write your congressmen and demand action!
You are experiencing a bug. That is not the normal behavior. I would suggest filing a bug with Ubuntu. First starts are known to be slow (sometimes up to 15 seconds), but second starts should happen on the order of two seconds or less. If you have the quick-starter enabled, they are almost instant. The screen flickering is definitely aberrant behavior.
1. It's just like the manpage says "ooffice -headless" Headless mode is used all the time for use in servers.
2. Quick answer: write a macro. Long-term: file a bug if you think this is errant
3. Well, this behavior is sensible when you think of it as oo.o will start headless and listen for API calls. If you filter fails, then the status of that method invocation is errant, but the office as a whole did not encounter an error.
4. This will be fixed eventually, but the API is not multi-thread safe.:-( The only workaround is to start multiple processes, which is possible.
It's a mess of spaghetti code, and the whole monstrosity is held together with duct tape and bailing wire.
While I agree that OpenOffice.org code is complicated, the allegation above is unsupportable. Would you care to support your allegation? Are you knowledgeable about the inner-workings of OpenOffice.org?
Re: LGPL, Novell and Microsoft proudly announced the other day that they managed to work around the GPL (Or in their words "They had the GPL in mind") and their work around applies equally well to the LGPL. That's why Microsoft isn't giving people a "Patent license", instead they sort of promise not to sue suse customers.
The GPL does not say that you must be the owner of the patent. Novell may not L//vbaGPL code that to their knowledge require patent licensing by anyone.
Re: Joint Copyright Assignment, we are talking patents here. Does the JCA say anything about patents? Could it be that Novell was previously sitting on code that, based on internal legal review, had a high likelyhood of infringing on existing or yet to be issued Micrsoft patents that they are now starting to commit because thanks to their new Micrsoft partnership this will give them a comptetive edge at no (patent) risk to them?
As I stated before, these are not "starting to be committed." From gnome-cvs, I can see that these some of these patches were committed 19 months ago.
The RTFA is an accurate statement of fact. The summary on slashdot is not. Facts of interest:
Noel, who not a MS schill and is actually a very nice guy, has been working on this for a long time and this code has been shipping with ooo-build for a long time. The ooo-build code is in gnome-cvs, and you can peruse the history youself if you like. The patches are in the patches/src680 directory. You probably are interested in the ones with the vba- prefix.
ooo-build is a build wrapper that also applies patches. You can select which patches you want and which patches you don't. Most Linux distros use ooo-build to build their packages. Thus these patches go through evaluation by most distros for their "freeness" (DFSG and others). All patches in ooo-build must have a JCA (Joint Copyright Assignment) signed, which amongst other things requires that the contributor actually own the copyright of the code in question.
This code is all LGPL. For those that are not familiar with the LGPL, here is a snippet
For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.
As the joint copyright holder (see above), this means Novell.
For the last time, Openoffice.org is not mostly Java. It's almost entirely C++.
Openoffice.org is a very challenging project and is in need of good hackers. For all the bashers on slashdot who say that it is too bloated or too old, I invite you to help. Few free software projects enable you to have your code literely run by millions of people all over the world. If you want to help, jump on #openoffice.org or #go-oo or one of the mailing lists and dive in.
the people are harmed because these sorts of schemes are sopping up mind-share time of the people who might be doing something actually useful.
This is the guns vs butter economics analogy. Like it, this argument is flawed. As cows can't make guns, most hackers aren't equiped to solve the hunger problem in poor villages.
Although I don't disagree that hunger is a greater problem than the lack of information technology, to say that work on both uses the same scarce resources, is perhaps a stretch.
At the last OOcon, there were three talks about making the code more modular and two talks on performance. If you watch Michael Bemmer's talk (http://ooocon-arnes.kiberpipa.org/media/OOo_2x_an d_beyond_Michael_Bemmer/video.ogg), you will see that they are aware of the performance and modularity problems and working very hard to fix it.
In slashdotese: "You don't know WTF you're talking about and STFU"
Re:My main problems with OpenOffice (on any OS)
on
Office Delayed, Too
·
· Score: 1
I'm not an OpenOffice.Org developer, so if someone knows otherwise about this I'm keen to know.
I am an OpenOffice.org developer. Great.
Correct me if I'm wrong, but it feels like there's so much legacy code and design in OpenOffice that it's difficult to implement important changes.
I had no idea one could "feel" the legacy code just from using it. Perhaps that was an unfair jab. The fact is that OpenOffice.org is an older application that has millions of lines of code. Indeed, there are several parts of it that rely on deprecated designs or implementations, but for the most part work. Code is constantly being revised and architectures updated. The characterization of ther being so much of it that it is difficult to implement changes, is incorrect in my opinion.
It turns out that making an office suite that is fully functional is very complicated. Unlike writing a POSIX kernel, or web server, there is no specification to follow. There are no college classes one can take or FOSS predecessors out there to build upon. Don't forget, that in addition to being a GUI suite, OpenOffice.org provides API's for office automation work.
Searching further, I discovered that the OpenOffice code was apparently still so messy from the Sun days that it simply hadn't been feasible to port to a 64 bit app in any reliable way, and probably wouldn't be for a long time to come.
The Sun days? Sun still employs the vast majority of OpenOffice.org developers. When it was open-sourced, a proprietary product turned into a FOSS one. An instant community of volunteer developers does not appear out of nowhere. I very much encourage you to become one, though. There is an effort to make it work under 64-bit. Go to the developer wiki and see if you can help (link at bottom)! If you feel that OpenOffice.org is too slow or resource hungry, feel free to help in performance optimization. OpenOffice.org developers are in short supply and your contribution would be appreciated. If you need help or run into trouble, jump on #openoffice.org or the dev mailing list and ask for help.
You will get paid terribly. However, being only moderately competent is enough to hold your job. Since performance and pay are not strongly linked, you can work at a leasurly pace without worrying much.
Adjust to the academic lifestyle. Your principle worries should be: What parking do you get and how much will it cost you?
Nor does it take very long to mop a floor- 2 minutes, if you include filling the bucket with warm water.
Wow. You can mop really fast. I used to live in a place with 1250 square feet (138 sqm) of hard floors. It took me much longer than two minutes. I could have used your services.
Oddly enough, cars one of the most highly recycled products on the market. Unlike, say a television, they are easy to strip down to individual materials, such as steal.
Slashdot Mirror
Turing completeness. You can emulate those if you wish, although it won't necessarily be pretty.
Therefore, we can likewise say:
It can do anything. Anything any other language can do, can be done in BrainFuck
It can do anything. Anything any other language can do, can be done in C++.
Such as reflection or anonymous functions? Such generalizations do little to help.
Saturn V was a 'multi-gear' rocket. To lift off the pad, all 5 main rockets fired. As altitude increased, the center rocket turned off to minimize stress on the rocket (stay subsonic???)
Space shuttle also has multiple speeds. If you remember the Challenger disaster - the last message from ground was "Go with throttle up" Apparently the shuttle was high enough to go full throttle (again) and not worry about aerodynamic stresses.
Most liquid fueled rockets are throttleable. Both the space shuttle and Saturn V's throttle down to avoid putting "too much stress" on the airframe. What this really means, is that they didn't want to put more weight into airframe structure, and instead reduce throttle to the point where the atmosphere thins enough that one can throttle up without surpassing the design strength of the airframe. By the way, this point is called Max-Q and for the space shuttle, it is at 11km in altitude. For the space shuttle main engines, this means they throttle up to 104% of specification power (due to improvements over the years, the SSME maximum safe throttle is actually 109% of specification).
One of the issues with the shuttles solid rocket boosters - they are steerable - allowing insertion into a very precise orbit.
Compare that with the typical home built - solid rocket, that basically goes were you point it...usually...give or take a bit.
The problem with solid rocket motors for space travel is two fold. The first is that they cannot be throttled or turned off. The second is that they are considerably less efficient pound-for-pound than liquid fueled rockets. The typical measure of rocket efficiency is specific impulse, which is measured in seconds. For example, the solid rocket boosters of the shuttle have a specific impulse of 242 seconds, while the space shuttle main engines produce a specific impulse of 363.
Google hired developers to work on OpenOffice.org, but found it difficult to fill all the vacancies. They seemed unwilling to work on the project understaffed and the people they hired now work on other things.
You can see a C|Net article about their hiring from a while back:
http://news.cnet.com/Google-throws-bodies-at-OpenOffice/2100-7344_3-5920762.html
Based on your account number, your obviously not new around here
Back in my day, when trolls were trolls and karma was numeric, slashdot was too obscure for companies to astroturf. It was fanboi vs fanboi for glowing praise and the comment threads were full of flame. How I miss the days of ole'. It just makes me want to pour hot grits down my pants.
This post just gushes about VIA. Since when did slashdot become a site for vendors to have their sock puppets write glowing posts for them?
probably makes them the best-supported framebuffers Linux has ever had
Give me a break.
The names are mostly after Oregon rivers: http://en.wikipedia.org/wiki/List_of_Intel_codenames
Did they finally add the "write my code for me" command? It seems to be one of the few things emacs hasn't implemented. I suppose a "materialize a 5'4 asian Girl Friend" command would be useful too. I think we should push for that in the next revision.
It's all in there, you just don't know the right modeline.
While the proposed act may make the attempts to infringe illegal, there are more pressing loopholes in existing copyright law.
Currently, consumers can view or hear content and later recall it without paying royalties. While humming a tune to yourself or quoting bits of recalled dialog is clearly a 'performance,' and therefore infringement, if they are particularly attentive during the 'performance,' they may even be able to visualize or 'hear' it in their memory. Does this not consist of infringement? This Brain-Hole is of far greater concern than other sorts of grey area infringement. We must close the Brain-Hole and ensure that there is still an incentive to create.
Who will be first to introduce such a bill? Write your congressmen and demand action!
You are experiencing a bug. That is not the normal behavior. I would suggest filing a bug with Ubuntu. First starts are known to be slow (sometimes up to 15 seconds), but second starts should happen on the order of two seconds or less. If you have the quick-starter enabled, they are almost instant. The screen flickering is definitely aberrant behavior.
1. It's just like the manpage says "ooffice -headless" Headless mode is used all the time for use in servers.
:-( The only workaround is to start multiple processes, which is possible.
2. Quick answer: write a macro. Long-term: file a bug if you think this is errant
3. Well, this behavior is sensible when you think of it as oo.o will start headless and listen for API calls. If you filter fails, then the status of that method invocation is errant, but the office as a whole did not encounter an error.
4. This will be fixed eventually, but the API is not multi-thread safe.
It's a mess of spaghetti code, and the whole monstrosity is held together with duct tape and bailing wire.
While I agree that OpenOffice.org code is complicated, the allegation above is unsupportable. Would you care to support your allegation? Are you knowledgeable about the inner-workings of OpenOffice.org?
The RTFA is an accurate statement of fact. The summary on slashdot is not. Facts of interest:
the people are harmed because these sorts of schemes are sopping up mind-share time of the people who might be doing something actually useful.
This is the guns vs butter economics analogy. Like it, this argument is flawed. As cows can't make guns, most hackers aren't equiped to solve the hunger problem in poor villages.
Although I don't disagree that hunger is a greater problem than the lack of information technology, to say that work on both uses the same scarce resources, is perhaps a stretch.
At the last OOcon, there were three talks about making the code more modular and two talks on performance. If you watch Michael Bemmer's talk (http://ooocon-arnes.kiberpipa.org/media/OOo_2x_an d_beyond_Michael_Bemmer/video.ogg), you will see that they are aware of the performance and modularity problems and working very hard to fix it.
In slashdotese:
"You don't know WTF you're talking about and STFU"
I'm not an OpenOffice.Org developer, so if someone knows otherwise about this I'm keen to know.
e
I am an OpenOffice.org developer. Great.
Correct me if I'm wrong, but it feels like there's so much legacy code and design in OpenOffice that it's difficult to implement important changes.
I had no idea one could "feel" the legacy code just from using it. Perhaps that was an unfair jab. The fact is that OpenOffice.org is an older application that has millions of lines of code. Indeed, there are several parts of it that rely on deprecated designs or implementations, but for the most part work. Code is constantly being revised and architectures updated. The characterization of ther being so much of it that it is difficult to implement changes, is incorrect in my opinion.
It turns out that making an office suite that is fully functional is very complicated. Unlike writing a POSIX kernel, or web server, there is no specification to follow. There are no college classes one can take or FOSS predecessors out there to build upon. Don't forget, that in addition to being a GUI suite, OpenOffice.org provides API's for office automation work.
Searching further, I discovered that the OpenOffice code was apparently still so messy from the Sun days that it simply hadn't been feasible to port to a 64 bit app in any reliable way, and probably wouldn't be for a long time to come.
The Sun days? Sun still employs the vast majority of OpenOffice.org developers. When it was open-sourced, a proprietary product turned into a FOSS one. An instant community of volunteer developers does not appear out of nowhere. I very much encourage you to become one, though. There is an effort to make it work under 64-bit. Go to the developer wiki and see if you can help (link at bottom)! If you feel that OpenOffice.org is too slow or resource hungry, feel free to help in performance optimization. OpenOffice.org developers are in short supply and your contribution would be appreciated. If you need help or run into trouble, jump on #openoffice.org or the dev mailing list and ask for help.
http://wiki.services.openoffice.org/wiki/Main_Pag
It would be Verizon that went to bat with RIAA all the way to Federal Appeals Court. They tried to go all the way, but were denied hearing.
n ion-20031219.pdf
http://www.eff.org/legal/cases/RIAA_v_Verizon/opi
No, this hasn't been true for almost 20 years.
You will get paid terribly. However, being only moderately competent is enough to hold your job. Since performance and pay are not strongly linked, you can work at a leasurly pace without worrying much.
Adjust to the academic lifestyle. Your principle worries should be:
What parking do you get and how much will it cost you?
Do you get an office? Is it a shared office?
There is no substitute for the Model M. I don't trust any clone.
For those who don't know, the model M:
Nor does it take very long to mop a floor- 2 minutes, if you include filling the bucket with warm water.
Wow. You can mop really fast. I used to live in a place with 1250 square feet (138 sqm) of hard floors. It took me much longer than two minutes. I could have used your services.
Water takes one calorie of energy input per degree Centigrade raise in temperature.
Oddly enough, cars one of the most highly recycled products on the market. Unlike, say a television, they are easy to strip down to individual materials, such as steal.
Even if AMD is beating Intel, it has nothing in the consumer electronics domain.
Have you heard of Xscale? Perhaps StrataFlash?