Slashdot Mirror
LibreOffice 4.2 Busts Out GPU Mantle Support and Corporate IT Integration
Billly Gates points to this basic summary of the features of the recently released LibreOffice 2.4, writing: "In catching up with MS Office, the new LibreOffice 4.2 now has full Windows 7/8 integration including Aero peek, thumbnails, jumplists, and recent documents all from the taskbar. In addition, one weak area for LibreOffice has been enterprise network support and the lack of active directory tools: LibreOffice now has GPO and active directory support for system administrators to deploy and manage LibreOffice over corporate networks. LibreOffice also includes an expert configuration Window to assist power users and system administrators when deploying to hundreds of workstation at a time." Read on for some more details about the release, including some information about support for AMD's Mantle CPU acceleration support.
Also of particular interest is AMD/ATI is expecting to finally release Mantle in the next coming hours for games like Battlefield 4. Surprisingly LibreOffice also supports mantle as well according to the release notes. However you will need the 14.1 driver which is being compiled and uploaded at the time of this writing to utilize this feature. Mantle will accelerate lower-end CPUs by up to 300% in some tasks while having modest improvements for those with more recent powerful CPUs. Real niceties for those like myself on AMD phenom IIs with the later 7000 series cards.
The only issue (some on Slashdot may say benefit ) is the lack of a ribbon UI. However, for recent articles about governments considering OpenOffice this release addresses shortcomings with the new active directory and GPO support."
The only issue (some on Slashdot may say benefit ) is the lack of a ribbon UI. However, for recent articles about governments considering OpenOffice this release addresses shortcomings with the new active directory and GPO support."
4.2 not 2.4... are you messing with us intentionally, just to see who is awake?
Unclear if I can get a copy without all this unwanted bloat.
"Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
logic fails you
if a business used LibreOffice, the board would be using LibreOffice Impress to view LibreOffice Impress documents and giving presentations with the PC hooked to the big screen running LibreOffice Impress.
Maybe some loaner using PowerPoint would have their slide looking like garbage in such a company....
The only issue (some on Slashdot may say benefit ) is the lack of a ribbon UI.
The majority of Office power users I know (mostly lawyers) were disgusted by the replacement of the menu-driven UI with the infamous ribbon. It's not just left-brained Slashdotters that prefer an easily navigable interface.
I submitted the story.
While ATI has listed LibreOffice for one of the few programs that use Mantle I can not find any other information on this?
This begs to differ if LibreOffice uses GPU directwrite or OpenGL and does it work on platforms than Windows. Of course this is not critical unless you do multimedia heavy presentations I am somewhat curious. I wonder if anyone who develops it can care to comment?
Also I use LibreOffice in conjunction with MS Office. I can't afford publisher and it is nice to use it to repair office documents that MS Office says are corrupt. This is a highly recommended upgrade even if you use MS Office full time.
http://saveie6.com/
Nobody can, at least until Microsoft opens up their entire API library. Until then, when someone gets close enough to endanger Microsoft's cash cow, they will change just enough stuff to keep them at arm's length. Repeat ad nauseam.
Anyone who tried to move files between different versions, system with different system languages or, if you are really daring, different platforms knows this.
MicroSoft can't guarantee compatibility with a lot of formats either, including older versions of their own formats. Any major upgrade or change is going to give compatibility and training/skill issues, regardless of what vendor you had or will go to. Sure, it'd be really nice if OpenOffice and/or LibreOffice would actually be able to fully work with at least current MicroSoft formats without messing up some of the formatting some of the time, but if you're looking beyond that, you'll be fine once you've migrated.
I was promised a flying car. Where is my flying car?
Nobody can
Not even Microsoft, which is pretty funny. Transferring files between versions of MS Office or between Windows and Mac versions often results in garbage layouts/formatting. It's really quite sad on Microsoft's part. I worked years as an audio-visual tech to know that this is very true. When a client wanted do to a PowerPoint presentation with a laptop provided by us, we always had to ensure the versions matched.
Even Microsoft Office does not guarantee 100% compatibility with older documents. And I've personally witnessed simple things breaking between MS Office on a Mac or on Windows.
When I dug through some very old Office 98 docs of mine a few years back, Office 2007 broke rather badly, but OpenOffice was able to read them. I'm sure it wasn't pixel-perfect, but it was readable and more-or-less as intended, unlike Office proper.
As far as trading between various offices, I've noticed more problems with Office For Mac than with LibreOffice. Granted, most people in my office are using either Google Docs, iWork or LibreOffice, but we get a fair number of outside docs that were made in MS Office.
For most uses of Word (glorified RTFs), everything is compatible. I've even had no issues going from AbiWord to MS Word. If you get crazy with auto-summaries or embedded docs, it might get problematic, but do you really use those? Presentations are much the same, although I've not worked with them nearly as much (because I do real work).
For spreadsheets, its a bit more hit-or-miss. If all you're doing is glorified CSVs, once again everything works, but the crazier your formulae get the more likely it will only work in one program.
Yes and no. Even between Office 2007 and 2010, documents don't always look the same... we have run into this for pretty simple documents. I have no idea why it's so ridiculously complicated that even the software provider can't get it right, but I'm guessing it has more to do with trying to intentionally hurt interoperability than anything else.
Call me a cynic, but I've been around for a very very long time and I've seen a lot of poor sportsmanship in the Microsoft camp.
The funny thing is now we're intentionally using older versions of MS Office simply because everyone hasn't learned the 2007 version yet, so what's the use of overloading everyone by going to the newest version every 2-3 years? The couple of users who will benefit can have the upgrade. The rest can have an upgrade every x versions.
We manage to deal with the incompatibilities between different versions of Office, so I think we could handle LO/OO if my company chose to do so.
W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
What about OneNote? Anything about a Libre OneNote? It's the only thing keeping me on Windows.
When our name is on the back of your car, we're behind you all the way!
... you still cannot perform a search and replace using manual page breaks. A simple shortcoming, but it keeps me from being able to dump MS Office.
Nobody can, at least until Microsoft opens up their entire API library. Until then, when someone gets close enough to endanger Microsoft's cash cow, they will change just enough stuff to keep them at arm's length. Repeat ad nauseam.
All of the MS Office file formats, both legacy binary and OOXML, are publicly documented. The binary documentation, I think, was released at the insistence of the European Union regulators.
Now, it is true that the formats are really badly designed and inelegant, and that there are a lot of MS Office "guts" spilling out of the specs. They are not easy to implement. But with enough time and effort, it should be doable. And MS is not introducing new breaking changes – to the contrary, they are finally introducing compliance with OOXML 'strict', which fully complies with the ISO standard. (MS Office 2010 can read 'strict' OOXML documents, and MS Office 2013 can both read and write them.)
Open Office/LibreOffice are both so obsessed with competing against MS that they, just like Microsoft, have no interest at all in people who actually write narratives for a living. As a desktop publishing package, LibreOffice is constantly improving. As a tool for corporate administrative assistants, it may very well be wonderful. As a useful tool for someone who actually writes stories, it is becoming increasingly more of a pain in the rump that it is worth. It is a painful truth that Word 2000 (shudder) is honestly more writer friendly than anything, commercial or open source, that has been put out since then. FYI, just in case someone mentions yWrite5 and/or Scrivener (someone always does) they are not writing programs. They are organizing programs. RoughDraft, and some others like Jarte, can be used for small stories or articles. But they are old and not being maintained. Plus they lack the necessary fonts and/or other tools for modern submission requirements. Many of us would gladly invent something for ourselves, but we are wordsmiths. We don't program. So we're screwed.
Just curious, what specific features are needed for writing prose that aren't available in MS Office or LibreOffice? What does Word 2000 do right that later versions do wrong?
Okay if you wanna pull that trick then Microsoft Office fails also the list (not exhaustive) of things that can futz with getting a MSO file to work correctly
1 Different Fonts on the system
2 any difference in the default(or current) printer
3 version patch level and hotfix presence for MSO
4 Language version of MSO
5 Phase of Moon at both sites
6 presence of any addons (includes version numbers)
7 Applied Hotfixes/ Updates to Windows
in fact some folks have found that opening some MSO files works better in OO or LO
Any person using FTFY or editing my postings agrees to a US$50.00 charge
Some simple things, such as performing a search and replace using manual page breaks. A simple shortcoming, but it keeps me from being able to dump MS Office. Also, many frequently used functions, while still there, are less "available", meaning they require more keystrokes to use. This costs time. Also, if you can't write without the mouse, it takes too long.
Even MS Office can not guarantee 100% compatibility with other versions of MS Office Documents. This is especially important to know if you are more then 2 generations behind (Office 2010) is the break point. I've had issues with docs from Office 2003 being screwed up by 2010 and those are local to my system. So if I have problems with formats from 2 generations before (office 2007 doesn't give me problems) then how in hell can you ensure that your latest Office 365 hasn't been updated to actually corrupt anything other then the latest version of Office-xxxx? This is how MS locks you into using the fucking products.
Mod me up/Mod me down: I wont frown as I've no crown
The real answer. The code is the spec. Not even Microsoft can guarantee 100% backwards compatiblity. They only offer compatibility. The file format version for an Office product can only be read perfectly by the same version that created it, even down to the patch level sometimes. Every newer version offers compatiblity because the code in the new version isn't exactly 100% identical to the code in the original version.
If Office is made available on Linux Windows will get steamrolled.
The non-Microsoft office providers should all agree on a formal file format standards with compliance testing and a scripting language like VBscript and then start pushing that standard, but it will take years.
Guess the world shouldn't have thrown Word Perfect under the bus?
Or, how about Word Star? There was a time when its editing keystrokes were widely adopted, like in Borland's integrated development environments.
Or, why not use LaTeX? Admittedly, it's a bit of a learning curve, but you can just bang out text, and worry about formatting later, even change it around relatively easily.
Intellectual Property is a monopolistic, selfish, and defective concept. It is "tyranny over the mind of man"
If it'd still reliably run on 64-bit systems, my suggestion would be to try and get a copy of StarOffice 5.2, the ancestor. No version of OpenOffice[.org] or LibreOffice has met my demands as well yet. Unfortunately, it doesn't. So what I'm doing today is running StarOffice 5.2 on 32-bit systems, like my netbook, and OpenOffice 3.3 on 64-bit systems, which is the latest of the StarOffice descendants still capable of saving documents in StarOffice 5 compatible format. (StarOffice 5 binary formats are still fully readable with current versions of OpenOffice and LibreOffice, for that matter.)
"All of the MS Office file formats, both legacy binary and OOXML, are publicly documented".
Great. Where's the explanation of "AutospaceLikeWord95"?
General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
Regex support in the Find/Replace dialog works in LibreOffice. It took a moment to familiarize myself with their implementation, but it works, and it's more powerful than anything else. Try doing that in MS Office.
It took me 10 minutes of thinking and experimenting to figure out what you were talking about. Why would you have a phrase spanning a manual page break? Why are you doing formatting during authorship? Maybe your process needs to change to reflect the tools. Not the creative one, but the technical procedure you use to save, recall, and share your writing. And Word and Writer are both jack of all trades, master of none programs anyway. There's an article I can't find about how adding presentation features to the editor is a mistake. Not that your text shouldn't look pretty while you type it, but that you should never type extra spaces to make it look _just_right_. Or page breaks.
i am curious, wouldn't http://www.gnu.org/software/emacs/ emacs do everything you need? you said mouse less editing, and there are a lot of functions that can be added to emacs, through it's lisp programs. and easily modified nature.
i write in my spare time, but only for my own needs and i use the mouse. i have used emacs for some of it, but i like the bloated office suites a little better and since my time isn't rationed and i don't find and replace much at all.
https://www.gnu.org/philosophy/free-sw.html
Sadly, the version of OOXML in 2007 (and I think 2010) is not the same as the released spec.
I'm starting to think GNU is the problem with "GNU/Linux" these days.
Big one that breaks PowerPoint is different screen resolutions, especially if the aspect ratio is different.
I'm starting to think GNU is the problem with "GNU/Linux" these days.
Right here.
I remember there being a plug-in (from Microsoft) to add Open Office support to Microsoft Office. I remember having it installed on my old laptop (Office 2007), and know I've used it with 2010. I can't answer what it does with spreadsheets or presentations, but normal text documents do just fine. (I don't see ODT in the SaveAs on my Mac running Office 2011)
I'm starting to think GNU is the problem with "GNU/Linux" these days.
I use LibreOffice a lot and actually like it, not as much as FrameMaker (before Adobe layed of its creators), but it's still a good software. But if a fairy came by and offered me to realize a wish list with up to a thousand entries regarding Libre Office improvements, I would still not even come close to wishing GPU support for it...
logic fails you
Zealotry blinds you. An overwhelming majority of businesses currently use Microsoft Office products and therefore have their current collection of documents stored in Microsoft Office formats. Until LibreOffice can create, open, edit, save, or convert those formats with reliable accuracy, its adoption will be hindered significantly. Even assuming that a business had gone 100% LibreOffice, there's no guarantee any other business or individual they interact with would also be using LibreOffice, necessitating the need for compatibility with MS Office.
The greatest thing I found about the OO.org distribution from a few years ago was that it would open MS Office document better than MS Office. People would come to me and say they could not open a MS Word document, I would pop it up in OO.org, save back in MS Word format, and they were good to go. I assume that since the OO and LO are the same base, that those capabilities are similar. I don't know because I only recently started looking at LibreOffice. I did download a couple years ago, but it crashed. Really the main reason I never used it is because the Libreoffice people seem to have an irrational hate of OO.org, and since OO.org has save my ass on so many occasions, I don't really have any time for those who feel the need to disrespect it instead of just compete. That said, the modern OO distribution does not seem to be able to deal with the modern MS Office files. I don't know if that is MS fighting back or OO/LO not being able to keep up.
"She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
> It took a moment to familiarize myself with their implementation
hhhuuummmmmm... it seems to be a standard regex though... https://help.libreoffice.org/C...
As someone using LibreOffice to write a huge manuscript that has been in development for several years, I would like some really good change control tools. I may be dense, and not quite understanding the problem, but it seems to me that integrating LibreOffice with Github to support distributed editing of huge projects, and version control, would be a natural... Am I just to ignorant to understand why this isn't being done? -Stony
Yes, LibreOffice is Word compatible. Specifically, it scores better than Word 2011 on compatibility with three of the four .doc formats. See the Microsoft article "What happens when I save a Word 2007 document in the OpenDocument Text format?"
I experienced this myself when my mother couldn't open any of her old documents on her Win7 computer with MS Word. I opened them in LibreOffice for her and converted them to the latest version the .docx format.
The talent and inspiration modules?
The world's burning. Moped Jesus spotted on I50. Details at 11.
http://en.wikipedia.org/wiki/A...
Mantle is a low-level API specification developed by AMD as an alternative to Direct3D and OpenGL, primarily for use on the PC platform.
Emphasis mine. I can't be the only one seeing this as a bad strategy (versus pushing this into Openxx).
Ah yes, the "YouDontNeedThat" response:
http://www.tmrepository.com/tr...
It doesn't matter what you think he should be doing instead - if MS Office allows him to accomplish things using a particular workflow and LO requires change for no obvious benefit, then MS Office is superior.
It's absolutely essential for people to realize that good software bends to the user, not the other way around. Proprietary developers seems to know this better than open source ones apparently.
It would never occur to me to do calculations demanding enough to benefit from GPU usage by using a spreadsheet application. And even if a GPU can accelerate the rendering of some 3D graphics in a document, I would rather want the application to do such rendering in the background once and retain the rendered image in a cache while I scroll around in the document - so that rendering speed would not really matter a lot.
No, it cannot, but then neither can MS Office.
The truth is that all men having power ought to be mistrusted. James Madison
funny, we use LibreOffice where I work, with over 400 employees...maybe your blindness is caused by wanking too much?
Really? Pretty sure you're trolling.. because this is not really an explanation:
This algorithm typically results in the following:
An increase in the inter-character spacing added between non-ideographic and/or number characters and certain full-width characters
No inter-character spacing between non-ideographic and/or number characters and certain half-width characters
*Typically* results?
*Increase* in character spacing? how much increase?
*Certain* full/half width characters? Which ones?
Even Foxit has got that horrible thing now.
I also use LaTeX for writing text documents. However, I still use LibreOffice a lot... mostly for the calc (spreadsheet) component and occasionally the presentation tool. LibreOffice is a very competent office suite and certainly a no-brainer for replacing MS Office.
Friends don't let friends use PowerPoint.
You miss the point.
The WYSIWYG stuff is almost desktop publishing but not quite - so not full control but it has the appearance of having it. It ends up with all those situations where you have to waste time trying to "trick" the document into doing what you want because you can't directly tell it what to do.
Welcome to the world of document specifications. None of them really describe what you need to implement. Remember when people criticised Microsoft's ODF support because they implemented what the spec said rather than what OpenOffice actually used? (Fortunately the spec has been updated since then)
In the case of this tag, it is only going to be found in 18 year old documents that have been converted into XML format. I bet the number of times that it because the subject of complaint here on /. is way more than the number of documents that actually contain the tag. And then if you find the subset of the times where a few pixels different padding is actually noticed in those documents... well, I bet it has never happened.
But all this is moot, as the original claim was that AutospaceLikeWord95 was not publicly documented, where as it clearly does have an explanation - even if there may be room for improvement.
Neither does MS Office. It is not 100% backwards compatible with itself.
Actually a *lot* of businesses have been changing to web services like Google Apps. Not even small ones or bleeding edge ones. I mean things like insurance companies.
The scripting language is called Python. It can even be run from inside OO.
The explanation is not something you can implement since it does not define a clear spec. It is vague and omits info.
It is pretty uncalled for to claim zealotry when you are uncompromisingly demanding an absolute 100% accuracy with MS-Office documents before LibreOffice could be used.
There are plenty of businesses where pixel perfect accuracy is not required when sending documents outside the company. If people really need to read my documents with absolute accuracy, then I can PDF it. If I want to test a slideshow then I can use the Powerpoint viewer (it even works under Linux using Wine).
Even without changing the version of Word, a document's pagination can vary wildly depending on the printer driver being used. You don't even change your software for Word to go wrong.
Excel can be a problem if you use complex macros, but 99% of the ones that I see are just being used a glorified table editors with basic calculations. I constantly move between different computers, using Excel, Calc and even the shareware spreadsheet Spread32 (when I want to view something quickly) and it all works better than I had expected. The bigger problem that I have is when a package doesn't implement a feature that you are used to. For example, if I want to search for something spanning the sheets of a workbook I will always use Excel because LibreOffice disables the "Find All" button when you choose the option to span worksheets.
But even you there may end up being some problems, you should not dismiss the use of LibreOffice within any business environment just because you might have some formatting problem.
I think that it has enough description that you could take a stab at it, but if you don't want to worry about exactly how much extra spacing to use then don't implement the feature. This is not a core feature of the spec; it is a very rare bit of backwards compatibility for software that dates back two decades. I guarantee that nobody who complains about this tag possesses a document containing this feature.
If not knowing exactly how much white space to implement is going to be a major problem for you, then no standard office specification will be suitable. Look hard enough at any spec and you will find parts where they miss giving exact measurements. And if you don't do that, then the complaint will be that the specification is too verbose that it is unworkable.
And once again, it is amazing how seamlessly people can move from the argument that "there is no explanation" to "that explanation isn't good enough". It is just moving the goalposts.
Really? Pretty sure you're trolling.. because this is not really an explanation:
This algorithm typically results in the following:
An increase in the inter-character spacing added between non-ideographic and/or number characters and certain full-width characters
No inter-character spacing between non-ideographic and/or number characters and certain half-width characters
*Typically* results?
*Increase* in character spacing? how much increase?
*Certain* full/half width characters? Which ones?
if you read entire link, you'd see the part where it says,
"Characters in the following Unicode ranges should be treated as ideographic, even though those characters are full-width forms of non-ideographic text: U+FF10–U+FF19, U+FF21–U+FF3A, and U+FF41–U+FF5A. [Note: This results in the unnecessary addition of space. end note]
Characters in the following Unicode ranges should be treated as non-ideographic, even though those characters are ideographic: U+FF66–U+FF9F. [Note: This results in the omission of the intended additional space. end note]"
Its not something that a typical developer can just decide to do on a weekend. To take an honest stab requires a foundations understanding of the specification and the terminology, structures, and special cases that go along with it. To use an analogy, to randomly jump to "AutospaceLikeWord95" is the equivalent of a first-year law student critiquing complex legal contracts without understanding the framework of contract law. Contracts, even complex ones, do not fully define and cite all legal authorities from which the clauses derive its legal standings.
Sure you can argue that an engineering specification should be written like a law, but consider the fact that the ISO Office OpenXML file format spec is over 6000 pages long. There are bound to be areas where quality gaps remain. In this case, consider the fact this particular class exists. It means that even Microsoft didn't properly document Word95 so that it could be re-implemented in a future spec. The guy who probably wrote the actual spec is long gone and it is left to a junior program manager straight out of college to decipher the re-implementation and new documentation around it. There is a reason why document fidelity between Office 97 and Office 2003 was good, because it had better documentation and planning. Pre-Office 97 formats were engineered for another era when competition was high and deadlines were more important than perfect documentation.
Yes and no. Even between Office 2007 and 2010, documents don't always look the same... we have run into this for pretty simple documents. I have no idea why it's so ridiculously complicated that even the software provider can't get it right, but I'm guessing it has more to do with trying to intentionally hurt interoperability than anything else.
Call me a cynic, but I've been around for a very very long time and I've seen a lot of poor sportsmanship in the Microsoft camp.
The funny thing is now we're intentionally using older versions of MS Office simply because everyone hasn't learned the 2007 version yet, so what's the use of overloading everyone by going to the newest version every 2-3 years? The couple of users who will benefit can have the upgrade. The rest can have an upgrade every x versions.
if the document was generated or originated using pre-Office 97 formats, and were converted to Office 97-2003 formats, then there is still a chance that Office 2007 or Office 2010 can render differently. I would like to see an example where a native 2007 file looks different when opened in 2010. Yes, such examples exist, but I've only seen evidence of this produced by Microsoft in public disclosure to showcase a hypothetical. In practice 2007 and 2010 are effectively the same, with 2007 being pre-ISO OpenXML, and 2010 being ISO OpenXML.
Competition was high with what? Tell me another prominent word processing program for Windows 95. I dare you.
Everything else came out one year afterward and it sucked. I remember. Corel's Wordperfect back then was trying to move its application suite to Java of all things.
Same thing applies for Mac vs Windows versions of Office. I mostly use a mac for research and development, but Office (alongside Solidworks) are the reasons I keep a decent Windows computer at my side. As a Ph.D. candidate, I have a horrible time with formats and template compatibility every time I try to write a paper using Office for Mac. Even boring academic/university bureaucracy documents are a nightmare on Office for mac simply because they are made on Office for windows. Simply blows my mind.
Unfortunately, as a guy who uses LibreOffice for personal note taking, I've also seen some format errors/inconsistencies when I open an odp file on a different OS. I'm not far from knowledgeable on this subject but I suspect all those office suits rely too much on OS shared resources and GUI factors. Sometimes I really wish pdfs were more edit friendly(at least using cheap/free software).
When Word 95 came out there were many people still using WordPerfect in business environments. In fact even today there are legacy record systems that still require WordPerfect format for archiving purposes. Like many people today, people were not just jumping to the latest and greatest OS and office suite. Businesses would require many more years before they left DOS and OS/2 at the time.
Rob Weir is that you again? ;)
Microsoft's attempt to make ODF useless was due to using ambiguity in the spec as an excuse to make something that did not work at all. If I remember right, some ODF applications would set a spreadsheet cell from the text "1" in quotes to the integer 1, while others would set it to a string containing the digit '1'. Microsoft then made some incredibly convoluted "logic" to twist this into a reasoning to not produce *either* of these possibilities, but produce a third that was not readable by anybody! They printed many "research papers" full of garbage to convince the PHBs that what they did was somehow logical and required by the laws of nature. Pure evil I think. Most of what Microsoft does that is bad is just due to incompetence and ignoring existing standards, but the attempts to defend the Word monopoly are obviously straight premeditated vileness.
Windows was never meant for servers, phones or tablets either... An android desktop is likely to be just as lacklustre but that doesn't mean it won't be successful.
http://spamdecoy.net - free throwaway anonymous email - avoid spam!
I had a few problem case .docx's that I had lying around that came from MS Office users. I am happy to report that they have rendered correctly for the first time in LO 4.2. Well done !
And finally the taskbar/aero peek stuff finally behaves properly on Windows !
Pet peeve taken care of ! I also feel a certain improvement in speed and responsiveness in general Nice nice nice.
https://dalgamotor.wordpress.com/ - Elektronik beyinlere ozgurluk asisi (Turkish)
It works for other OSes too:
Linux was never meant for servers, phones or tablets either... An android desktop is likely to be just as lacklustre but that doesn't mean it won't be successful.
Note: Quoted part does not represent my opinion of Linux.
No colour or religion ever stopped the bullet from a gun
No. I remember that time. WordPerfect, like most other 3rd parties, took forever to port to Windows 95. IIRC part of the problem was that Microsoft was developing Office and Windows simultaneously taking advantage of APIs they had not publicly disclosed until much later so they had a much greater head start than any of the competition. Using Windows 3.1 applications in Windows 95 was pathetic. No one wanted to use them. They could not even support Windows 95 long filenames properly. I remember that quite well.
I remember it also. What you stated in your last comment does not dispute what I'm saying. Additionally Microsoft was far from monopoly back then. I was using OS/2. They had no obligation to be open. What Microsoft did back then pales in comparison to the current closed garden stuff that Silicon Valley companies have been pulling for the last few years.
The only way I find out a new version of LibreOffice is available is either by visiting the website and click on download to see the version number or when someone posts something on slashdot.
These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
Pretty sure linux was meant for servers.
Watch for Penguins, they eat Apples and throw rocks at Windows.
Microsoft Office wouldn't even run on my main work desktop. It runs linux. As do most of my co-workers. Instead, some of us use LibreOffice or OpenOffice, some use Microsoft Office on Windows. I have yet to open a document and have it come out all messed up. Maybe I've just gotten lucky, but it's probably more likely the case that the vast majority of commonly used functions work just fine, and if there's the occasional almost-never-used function that doesn't work right, people avoid using it.
Watch for Penguins, they eat Apples and throw rocks at Windows.
Linux was originally developed as a free operating system for Intel x86-based personal computers.
No colour or religion ever stopped the bullet from a gun
"Work on your skills" is a crutch used by people who think PowerPoint users have time and resources to do so. And, possibly do not understand that the target audience considers you unprepared if you did not put time into making some slides, or don't happen to have a slide deck for reference.
Sometimes, it is so deep in the culture that the best presenter ever could not avoid PowerPoint, if only as a record that something was done.
we were discussing issue of businesses choosing to change what they use, and possible consequences.
nothing you said has any relevance whatsoever
I'd say it's more due to AC like yourself, posting venting spew with no contribution to the topic whatsoever. Are you a general failure in life?
...because they don't know what they're doing and don't understand the playing field to begin with. They think that presenting similar windows and icons is all that's needed, when its really the "platform-ness" of the OS that matters the most. This includes a lot of qualities and business practices which Apple and Microsoft adhere to but are known only internally or not even expressed at all (along with others that are commonly talked about in MS/Apple circles but are completely ignored in most FOSS projects).
You sit at the personal computing table, you watch, you reverse-engineer the dynamics and you learn. Then you can try to figure out which elements can be adapted to FOSS or possibly even improved upon.
No? Then get out of the way, cuz users have expectations and aren't attracted when systems developers are trying to impress only their peers --as well as that works in the server world, its just a pile unrecognizable pieces to everyone else. Barging in with piles of tools, plus 6 or 8 candy-coated DEs and calling it all "Linux" hasn't worked... cannot work.
My god, man, its just a confusing mess.
What Google did with Android was very savvy: They lost the "Linux" identity, published an SDK (so app devs see a stable target) and started with a select group of hardware vendors to support it (instead of that horrible pretence of 'try different distros and see which one works on your system'). But Android is not meant for the desktop...
Trollmods with no counterpoint, I see.
The only issue (some on Slashdot may say benefit ) is the lack of a ribbon UI.
You're quite right. I still have to see the benefits of that attrocious "innovation"!