We're mostly volunteers, so people implement whatever they feel like doing :-) The essence of open-source.
Come help out if you can, or sponsor some fixes with one of the LibreOffice consulting companies.
1,739 karma · joined August 21, 2009
We're mostly volunteers, so people implement whatever they feel like doing :-) The essence of open-source.
Come help out if you can, or sponsor some fixes with one of the LibreOffice consulting companies.
C and C++ have as a basic design rationale
"as close to machine performance as possible"
"don't pay for what you don't use"
"don't break backwards compatibility"
The last one is what is what is responsible for most of the issues. It would be nice to fix stuff like UB, but the reason that C/C++ is so popular and still alive is precisely because it does care more about compatibility than fixing stuff likethat.Breaking existing code is extremely uncool for long-lived codebases.
It plays to the strengths of both becuase the reverse proxy handles long-lived but slow connections very well, and the Tomcat server gets to have fewer, but hotter threads.
So just build a deeper stack of layers, rather than flipping and grinding.
But probably there is a reason.
Other teens convince themselves that some shoplifting, or car stealing, or drug dealing is "acceptable".
Why does the first group get a pass?
"Fail early, fail hard"
i.e. if I can make the error message happen near the beginning of a process, I can get away with making it a hard error.
Hard errors in the middle of a multi-hour operation tend to annoy people.
Which can be tricky, because the degree of negative feedback that is appropriate to the person in question can range from
"Polite one-on-one suggestion that you read the error message more than once before calling me"
to
"Full on yelling at the person in the middle of an open-plan office".
Thankfully, type II is rare, but they do occur.
Although to fair on the NRC, there was a case where, due to lack of experience, the contractor cast an enormous slab using the wrong rating of concrete, which then had to be removed at great expense and delay.
Not quite the same. X11 (notably the xfree86 project which maintained things for the last decade or so), was always quite free-wheeling about allowing things. They subscribed to something similar to the linux kernels approach of "mechanism, not policy".
No, I don't think there is any conspiracy. Nor do I think they are bad people.
Nor do I think the whole thing is over-engineered. It's mostly pretty impressive.
But if you actually want to __use__ your extension/protocol with someone else, it needs to get accepted into various core libs and repositories.
....And then the gatekeepers step up and your problems start.
Every frame is perfect requires extreme amounts of coordination. Frequently multiple buffering, which increases latency and increases latency. All these are costs which most use-cases don't care about.
Under normal conditions, with display managers that don't care, frames are extremely rarely "not perfect". And when they aren't perfect they are seldom "not perfect" for more than a single frame.
This is a fine example of "the perfect is the enemy of the good"
X11 was very much a "everything is a work-in-progress" culture. Experiments were fine, clients and servers could support whatever they wanted, etc, etc.
Wayland is an "opinionated" culture. Everything the core devs don't like is not allowed.
Everything HAS to fit into the "every frame is perfect" mantra. Which is ridiculous over-engineering and disallows a large number of perfectly acceptable (to end users) use-cases.
For many years Canada (and similar countries) have relied on cutting costs by importing health care professionals from other countries. That pipeline has now shrunk considerably, resulting in the exposure of the underlying problem.
So we have a collection of plugins, see here: https://cgit.freedesktop.org/libreoffice/core/tree/compilerp...
Which verify a variety of things.
We focus on 2 things: finding dodgy code and using APIs correctly. We don't try to modify the C++ language, just restrict accidentally straying into some of the really nasty corners.
But I like to keep an eye on experiments like yours for ideas :-)
e.g.
no c-style casts: https://cgit.freedesktop.org/libreoffice/core/tree/compilerp...
use the comma-operator sparingly: https://cgit.freedesktop.org/libreoffice/core/tree/compilerp...
is your loop variable really big enough: https://cgit.freedesktop.org/libreoffice/core/tree/compilerp...
calling virtual methods from destructors is dodgy: https://cgit.freedesktop.org/libreoffice/core/tree/compilerp...
IBM asks Japanese manufacturer to make 100 boards, specifying 1% failure rate.
On the day of the delivery from the manufacturer, the Japanese CEO comes to inspect the final shipment.
After doing so, he discusses the contract with his chief engineer, and the engineer mentions the failure rate spec.
The CEO nods, takes a board from a box, breaks it over his knee, and says "There is our failure rate".
And then, of course they killed it and made it a web UI thing and made it majorly worse at the same time