91–97 of 97 posts
LO has a lot of room for improvement. I am confident it will improve. I use it in a way that is pretty incredible and goes beyond the uses people are discussing on HN. I have watched developers of the project discuss what they are working on and seen their various presentations on things they've improved over the years. Some of the flaws cause all sorts of performance issues that have recently been fixed. It will get…
I am really curious how you are using LO?
Earlier quoted context omitted.
Things you should never do: https://www.joelonsoftware.com/2000/04/06/things-you-should-...
Interesting blog post, but I'm unconvinced. First, there's no such thing as something you should "never" do, especially when it comes to code. Our problems are so abstract that few if any tools should be off-limits. Second, the author leaves out any examples of where rewrites succeeded. Windows NT was effectively a rewrite and is the grandfather of every version of Windows that came after Windows ME. Game engines and…
LO can barely keep the lights on and has well capitalized competitors at all sides. A ground up rewrite is not gonna happen unless someone with deep pockets shows up. No doubt any new product will be created by youngsters that despise 90s pragmatism, local data model, and lack of telemetry. Meaning it won’t be a product for me.
Earlier quoted context omitted.
Recently tried the markdown+pandoc route but couldn't get pdf rendering to look decent or for document links to work, or for a multitude of other things to work... Which is a shame because markdown is great for everything else
Are you using LaTeX as the rendering engine? I think that's the default in pandoc. It always produces great looking docs for me.
Earlier quoted context omitted.
Wrong. LO 7.3 crashed with a new Writer Document after I tried to change the toolbar. Imagine such a bad test coverage. icons still blurry on macOS retina display. Chronic bug unsolved since aeons Also due to one-process for all architecture, if one document crashes, it crashes all other documents with it.
Pushing a new rendering engine without extensively testing it on a new OS release is simply nuts.
Earlier quoted context omitted.
Strange, I never encounter any bugs. I am on Windows in corporate land and Linux at home, all good!
I don't even use LO that much, and I'm panic saving in cycle every time I do because it crashes of me so often. Hell, it crashed on me this week, on a 5 pages doc with images, text, one table and a few titles. Nothing fancy. I keep reading people saying it's stable for them, but I've was using it already when it was called OOo, before we had docx support, before docx even existed. And it always has been this buggy. I…
Trying it for the first time in 3 years and it doesn't work on Mac OSX intel. Everything is huge and the the cursor hitpoint is off by 150-200px so you have to click above everything. Is anyone testing this software on the Apple hardware? Bizarre that a clean install on a 2 year old computer causes such issues.
Earlier quoted context omitted.
Interesting blog post, but I'm unconvinced. First, there's no such thing as something you should "never" do, especially when it comes to code. Our problems are so abstract that few if any tools should be off-limits. Second, the author leaves out any examples of where rewrites succeeded. Windows NT was effectively a rewrite and is the grandfather of every version of Windows that came after Windows ME. Game engines and…
Windows NT was made by company with a monopoly position and truckloads of money pouring in. They hired Dave Cutler to do the preliminary designs. LO can barely keep the lights on and has well capitalized competitors at all sides. A ground up rewrite is not gonna happen unless someone with deep pockets shows up. No doubt any new product will be created by youngsters that despise 90s pragmatism, local data model, and l…
> No doubt any new product will be created by youngsters that despise 90s pragmatism, local data model, and lack of telemetry. Meaning it won’t be a product for me.
*sigh* Yes.
Although LibreOffice has one thing going for it in that regard... which is that it seems less likely that youngsters would even be interested in creating a word processor to replace the legacy LibreOffice. Many of them may not even know what LibreOffice is. Unless the word "blockchain" became attached to it (don't get any ideas, kids!), word processors are boring. If a rewrite ever happens, maybe there's at least a slight chance the engineers will be some coding veterans with wizard beards.