Slashdot Mirror
Star Office to become Open Source?
kwelty wrote in to tell us that this morning's Wall Street Journal has a bit more about Sun buying Star Office. The crazier bit tho (and the bit for while there currently is no URL following: "Sun, of Palo Alto, Calif., plans to make the Star Office applications available via the Internet and may give away the program's underlying source code free as well, these people said."
Cross your fingers.
I'm not a professional Sun observer nor am I a professional Microsoft observer. But I don't like the idea of a big bully just being replaced by another one.
Does Sun like GNU? Why should they? Do they like a community could make their software AND hardware obsolete? I don't think so.
I'm suspicious toward sun, right now they got someone to kill. But what happens when Microsoft's gone?
It's slow. Really Slow. Really Really slow.
I mean start it up and go out for coffee slow. Remember Corel Office for Java? It's that kind of slow. Have I mentioned that it's slow?
I've finally had it: until slashdot gets article moderation, I am not coming back.
This sounds great! Two things I'm interested in (1) What the HELL is Staroffice written in, and what GUI toolkit does it use (someone said some weird QT derivative, (2) It's a nice GUI, and if it was extracted and made into a GUI/API Framework, possibly companies could use it to port their apps to linux easier. Nonetheless, I use Staroffice 5.1 everyday under linux, and it's great - a good, solid, well-featured app. Only thing is, will Stardivision be under Sun, or will all those developers just disappear...
In short, I'll believe it when I see it.
-=-=-=-=-
-=-=-=-=-
My mom's going to kick you in the face!
If this is true, then Sun is probably going to put it under their SCSL. If they do that, it won't be open source, since SCSL puts limitations on redistribution.
-russ
Don't piss off The Angry Economist
Given their questionable involvement in the open-source effect, this would give them the chance to release something to the OSS community that doesn't really bite into their core business (which right now appears to be selling servers and Java-related stuff). And there's every chance that an open-source StarOffice could integrate with an open-source Mozilla, providing the free counterpoint to Office/IE.
Sun saves on developers and time (unless they just intended to buy it and let it stagnate); they get brownie points with the free-software geeks; they get a competing office product that's already nicely cross-platform.
Nothing worth doing is worth doing today.
I would love to see StarOffice go open source. I think it a very nice program, being able to run it under linux and (god forbid) windows, the good integration with M$ Office, and a fairly efficient interface. As much as I like it, I think it too bloated (~70 meg download is too much) and suffers from M$ envy. Star Division seemed to be making M$ Office for linux which I don't want. I would love to see the open source community get their hands on this program and make it quicker, more usable, and create a complete replacement for Micro$oft Office. I would love to be able to start recommending this program to Windows and linux users alike. A good office program, compatible with M$ Office, is one of those things that is keeping linux out of a number of corporate environments.
-- All misspellings and grammatical errors courtesy of yours truly --
will there really be an effor by the open source community on star office? I think the source is just to big, especially considering download for start office is something like 36 megs. It is a good idea, but it may suffer the same fate as mozilla, where it will recieve some outside input, but not that much. Just My opinion thou. It will be nice if you find a bug, , but will you want to debug it? How long will it take to compile?
Only 'flamers' flame!
Yep. If true (about open sourcing StarOffice), this is a clear second front on the assault on MS's market share. "Cutting off their air supply", to quote Microsoft from a different context.
Linux is depriving MS of sales on the OS front, and a free office suite would do the same on that front. StarOffice already runs on Windows and (IIRC) on Macintosh as well as Linux, providing obvious migration paths. (At least one Windows user I know of has switched to StarOffice just so it'll be easier if/when he later switches to Linux.)
It could have some of this effect even without being GPL'd if it's, say, 'free beer' software or almost open source, but the effect will be much bigger with a real open license. Meanwhile Sun can bundle it with Solaris or as a Java client and make its money on that side. (It needs to justify the cost of buying StarOffice to its stockholders somehow.)
Interesting that the most active stock on the market this morning was Applix, up $7 or so, on the strength of its Applixware for Linux. Corel is also up. The market obviously recognizes some potential there. Microsoft can't be happy about this. (Wonder if it'll prompt an "Office for Linux"? Smart move would be to develop that in-house but hold it until Windows and Office sales are really starting to hurt.)
(BTW, Bill has enough invested in other things that he's unlikely to ever be a pauper even if MS stock went to zero. And he could always get a job as a programmer, if there's any market for Basic)
-- Alastair
Star Office dev team/mgmt = SO.
33. The money may not be in end-user licensing--but in selling consulting time to modify SO scripts that automate the document flow of a company (think VBA).
32. The money may not be in end-user licensing--but in consulting time to link together Oracle Financial/SAP R/3 logic with custom made SO documents and spreadsheets.
31. The money could come from create Sun "MS Terminal Server--like" VNC servers that serve hundreds of SO sessions--companies and schools can save on administration with this method of deploying SO.
30. It took a long time to educate enough people to script MS Office a certain way--it certainly will be the same situation with Sun's SO--this means advertising money, creating a certification infrastructure money--to balance the balance sheet consider utilizing the cheaper development model of GNU software and third party documentation--this is most effective if a significant percentage of your SO developers and technical writers comes from the hungry and over-drive world of OSS.
29. End-user licensing is unhealthy when you use existing non-net-download methods. The cost is high (paid to distributors of glossy boxes), the erratas late (wait for the next version boxes), and the only people you can contact in the view of end-users is Sun's SO division, not their local consultants.
28. With net-distribution, you save on bandwidth (each download would be the glorious 500+ Megabytes after all) with source and executable mirrors.
27. Consumers will associate SO download with visiting local SO Consultant's website--which happens to be an important source of executable and source mirrors--even distributors of physical cds--but they are SMART DISTRIBUTORS--be they certified by SO certifications or Sun employees--Consumers would immediately be exposed to the possibility of scripting and customizing their product--hiring consultants--Sun can get revenue by training consultants and testing consultants as SO gain important customization features.
26. If GPLing the source of SO provides the incentive and thus trend and drive for consumers to download from SO mirrors--this will educate them to the importance of getting persistant connections such as cable modem and dsl--with these connections as the norm Sun technicians can better remotely login to user's computer and fix problems, educate, and enhance copies of software. Again, lowering technical support hours and effectiveness. (Tools like VNC enable SO technicians to visually remote control Macs, PCs, and UNIXes, servers and even dumb terminals to debug settings and problems)
25. In return for consumer investment in DSL and cable modem--Sun can push other net-reliant technologies like Sun webservers and java products. Opening the channel to other products. (This is a long stretch--sorta like saying the hog that Win9x/Office has helped bring about the requirement for powerful computers that could finally make use of unix's many great features--bringing about a renaissance of Linux--so I'm making the analogy to requirement of DSL and cable modem to get work done as opening the floodgate to the use of java and other net products)
24. Making SO on Java work is a trillion dollar proposition. It involves the assumption of more than just getting networking to work--it's reliable java stations and java servers, programmers understanding the ins and outs of the latest Java technologies. Let's talk about educating programmers... What's the chance that your everyday no-cs education programmer will care about the source of JFC? How about SO on Java? How about the scripts that automate SO on Java? It's like a stepping ladder--there are more interest as you get more higher level. But most importantly--if you closed any of the tiers (JFC/SO/Scripts for SO) it gives scripting programmer doubts--who can they trust nearby who actually seen and played with the codes? Who can fix the bugs? GPLing SO on Java helps to bring future programmers and scripters confidence they'll find support nearby--maybe even for free. The argument gets better when you realize with the GPL developers will read SO's source even if they only use a tiny portion of SO's code for a totally unrelated project--but I'm saving this for a latter point.
23. GPLing SO has the way of also answering anothe important question with the first choice. The question is When do we GPL? The first choice answer is now. The second choice is later. The mozilla project suggests now. The Darwin/Quicktime Streaming Server suggests now. Why? What's their incentive? Finding out could help you determine what role SO is about to take on when it's popular among MS Office folks. Here are my assessments: 1. They feel their users/developers could benefit from these product's compliance with standards--somehow they determine that GPL help them achieve that goal. 2. That their users/developers would choose their products over non-GPL products because they have access to key technologies they can take home and use in other projects (Mozilla's Gecko renderer as activex object for example, or the Rhino drop in javascript on java product, or the XML renderer)--some how the decision to GPL now helps them find developers who use the exact same technologies in diverse industries but these developers as a result can contribute to the future health of Mozilla and Darwin/QT Streaming Server product)
22. GPLing SO will help business users with weather-worthy old computers to walk away from your SO-Customer relationship with less "abandonware" pains. When some SO developers and SO consultants move on to fresher products of the future--business users can walk their path knowing they can try to hire a developer who can tackle and repair the bugs not only associated with busines logic written in scripts--but unforseenable bugs that reside in SO's executables and libraries.
21. SAP R/3 products that are based on a solid DB+OS+NET+IRON can now trust on a few stable fundation. They'll be able to incorporate SO onto the age old hierarchy (SO+DB+OS+NET+IRON). Before we get theoretical. I can see it already as a more document or spreadsheet oriented front-end to business logic--one small businesses and big businesses are familiar with--with the help of extensive exposure to web sites. This aids businesses to make more money with your products.
20. Businesses can also use such a SO+DB+OS+NET+IRON to isolate softwares that needs to be designed in the most scalable way and request proper and real world modifications to SO. The end result being a serious development track of SO that could benefit SO on Java. You'll be able to understand better than Microsoft what it is like to create a Office application designed for scalability--giving administrators and MIS people the same benefit of reliability and ease of configuration.
19. There will be businesses already sold on this idea of extending SO for scalability even if you never spend on dollar on researching this possibility. Giving them the GPL source allows you to freely benefit from such end-user development and research (which may go very far--as one can see with NASA's contribution to Linux's networking kernel and NIC driver research in order to benefit from a working Beowulf product).
18. A user like NASA doing the extending for you has a way of not only doing research for you. But supporting the product without you. Reselling the product without you. This is all very scary to those who rather entertain the possibility of one copy of software = one check sent to Sun economy--those in Sun and SO's competitors (MS/Corel/IBM/Apple). But the only one who can giggle AND be nervous at the same time is Sun/SO--because NASA would be using your software--not someone elses. Other's have nothing to celebrate.
17. Outside developers sympathetic to BeOS/MacOS/Research OSes/Embedded OSes/Evil Empire OSes/UN*X varients users would not forget your GPL'ed code base--they'll try to port these products to these platforms. To the users of these platforms--Sun would finally be seen as a champion of popular software--not just expensive super-computer research. And they'll be open to related products Sun has to sell them.
Bonus Point for Free. I lost my points 16-10 when netscape crashed due to what I suppose is an buffer overload to the slashdot reply forms. I went around looking through the core files and found nothing. No backup. Nah dah. Good thing I copy and paste 33-17 to a text file and have perfect memory of points 16-10. Unlimited undos, journaling of all changes, and all sorts of features might need SO's own team to develop--but your dedication to a GPL'ed source will mean that other products of unrelated nature will benefit from SO's components in the future. Imagine a drop-in unlimited undo-history module to enhance the text frame one would definitely love to have when perl scripting a quick and dirty application. If something breaks you get a free bug report--even since these group of users are in the 3rd-world countries--not using a full-blown PC--but rather a setup-box. Maybe I didn't remember all 16-10 points. Oh well. Let's hope future generations of computer users can benefit fully from Sun/SO's innovation.
16. Don't remember.
15. Don't remember.
14. Don't remember.
13. Don't remember.
12. I'm going to extend out my neck and claim what's important to wordprocessor and spreadsheet business users and consultants of past and future--they're ultimately very excited about these things: a) potential great music that can be produced from an amazing relationship between the scripting engine and the application/b) amazing scripting engine features and ability to bring the proper features to the surface and hide the unnecessary features out of the executable when the consultant is customizing the product for a business/c) ability to not only add to SO through things like MS's ActiveX objects (which is basically BONOBO in Linux) and not excited at all about these things: x)speed of scripting engine--especially if it's an proprietary engine--learn from BeOS--they don't force any scripting language on anyone/y)number of features in new applications when they aren't exposed to scripting engine or very useful even when exposed/z)huge manuals that explain all the new features to those who need it and those who don't. Conclusion/Claim: GPL fuels the real world touch and experience and dynamic nature of the former (a/b/c) where as close-source fuels the research oriented touch of the latter (x/y/z).
Another Bonus Point for Free. GPLed software based of mature and large projects does not force outside developers and contributors to the fundation source base to use SO or understand all of SO in order to sustain their contribution to SO. Even if they try to make a tiny technology inside of SO work (like Rhino in Mozilla) for them--this little technology could play a key role (say a unlimited undo text editing module from SO) in set-up boxes--without any managers knowing. The technology and brain-share is helping SO--however--it will concentrate on key technologies. It's always rewarding when someone out there make it their No.1 to make sure an seemingly unimportant part of your project work well and perfectly in the real world--it gives you a chance to leave features in even if you lack the programming money or time to sustain it otherwise.
11. The interest of wordprocessor and spreadsheet users and consultants are in automating these documents as a poor-man's way of bringing business logic to the webserver scripts running on the same computer. Give them the piece of mind that thousands of eyeballs are looking and fixing security bugs that may exist in SO and the scripting engine or architecture SO may deploy--just as major webserver projects and scripting engines for webserver projects GPL their source. Why don't they adapt a Sun half-ass OSS licensing like the Sun community license? Because under that shadow there are no incentive to use the source. Potential eye-balls will only use something they can apply elsewhere for free--free to modify at will. Only retarded idiots will submit to the reading of thousands of lines of source code which will benefit no one but SO developers.
10-1. That's Letterman's job.
I thought of posting my thoughts on this in response to the earlier Freshmeat article responding to the Open Letter to Red Hat, but they make more sense here.
An open source office suite like KOffice or Gnome Office does not attack the real issue.
- The first priority should be a cross-platform Office Suite. An Office suite just for Linux doesn't instantly make people switch to Linux instead of Windows. Applix, Wordperfect, and StarOffice already exist and the defection has not occurred. We can all complain about how much these Suites suck, but MS Office sucks too. People will put up with the pain if the gains are worth it. It worries me a bit that SUN is now in control of the most platform independent Office Suite and they have a vested interest in one of the platforms. StarOffice needs to be ported to Mac (the second most popular desktop OS). They used to promise it on their web pages but after months of non-delivery it disappeared without notice.
- The Suite must start out as Word DOC compatible or noone will care. Even if my company switches to StarOffice our customers will still send us files in Word format and only be able to read Word format. Fortunately switching DOC formats hurt MS so bad that Office 2000 is compatible with '97, SUN should take advantage of this extra time to make document exchange perfect.
- SUN should try and work with WordPerfect and Applix to create an open document format that all Office Suites agree on. This won't be perfect, but at least as an open standard they should be able to read each others formats. SUN will not succeed if they let MS control the file format, and SUN should be smart enough to realize that they should not try to take on MS with the same proprietary attitude.
- I hope that SUN understands that this is the best way to attack MS. AFAIK MS makes more money on their Office suite than on their OS. Star used to give Office away to non-commercial users, and they were far from pulling in one-tenth of what MS was. However much money SUN might make on StarOffice won't make a dent in their bottom line. However providing an OfficeSuite to any platform will encourage more people to use more SUN products, where they can actually make the money (Java licenses, Solaris sales, and workstations). If SUN wants to make money off of StarOffice they should not let that get in the way of making it open source. Do not try to take on MS on their own terms; in this case selling a proprietary Office Suite.
- The two most important Applications for any desktop OS today are a browser and an Office Suite. With Mozilla and StarOffice maybe we will finally have a chance to have people give *nix a try.
- A lot of people have been disappointed by the Open Source community response to Mozilla, however I think the problem has been that when Mozilla started their codebase sucked. The project made the correct decision to rewrite everything, but until I can hack on the same code I use on a daily basis I probably won't contribute any code, the itch isn't there. If StarOffice is actually decent code and SUN doesn't piss of the OpenSource people too much, maybe they will see a greater response than Mozilla. Equally as likely is that the code blows as much as Netscape 4.x and there will be a transition period similar to Mozilla that SUN will have to be tolerant through.
PS Other people have commented on the SCSL. I don't know much about this so I won't speak directly on it; except to say that I'm not a big fan of the GPL and "GPL or else" campaigns. GPL is not that great for companies, something more like the license Mozilla is under would make more sense and hopefully still make the community happy.I am an ASIC engineer and in my field you often end up with the marketing and sales people on Windows boxes and the engineers on UNIX boxes having to fight through Word DOC email. I love UNIX and would love to have it on my desktop, but that doesn't mean that I think we should put UNIX on all of the marketing departments machines. People should be able to choose their platform and I think an Office Suite that empowers this will be rewarded. Right now people in our office can't even use Mac if they want to, because MS Office doesn't interoperate very well.