If X11 was designed for an era of worse bandwidth and latency, doesn't that imply, that it should perform vastly better on today's systems?
KiCAD doesn't work properly with Wayland, even with Xwayland. That's a show stopper for me.
If X11 was designed for an era of worse bandwidth and latency, doesn't that imply, that it should perform vastly better on today's systems?
KiCAD doesn't work properly with Wayland, even with Xwayland. That's a show stopper for me.
Anyway, the GPU-is-also-display-adapter model has been dragging down computer architecture and still is to this day.
There's an important difference in doing highly complex rendering sourcing large set of data ( >100 MiB per frame), and just throwing a couple of simple-ish primitives onto a UI.
GUIs should be fully representable as simple draw lists (see e.g. ImGui).
Yes, no modern X11 app will submit draw commands because of ill-advised group think and most developers seemingly turning off their higher brain functions when writing graphics related stuff.
@mia @navi @neal @dalias @miah
So can anything that can talk to a GPU driver.
This is not an X.org issue. GPU clients locking up the GPU have been known for a long time and on every platform that have APIs that grant a direct channel to the GPU.
Windows has a watchdog timer, reseting the GPU if it gets stalled by more than 250ms. macOS as a watchdog timer doing the same thing.
@mia @navi @neal @dalias @miah
X.org is not a special citizen. It's been using the very same interfaces to kernel land as Wayland-land does as well (DRM). If X.org can lock up drivers in kernel code, so can Wayland. Which is then a bug that should be fixed DRM side in the kernel.
I repeat:
Do not use GPU rendering if your application doesn't absolutely need it. Are you writing a text editor? Don't use the GPU. Are you writing a terminal? Do not use the GPU! Seriously, Terminology and Alacritty should never have been created.
Are you writing a CAD program, or a 3D modeller? Then of course use GPU APIs.
Are you writing a massively parallelizable signal processing system. Yes, then using the GPU is called for.
But not for mere GUIs.
I thought so for a very long time, too. Until I started developing applications that push a sustained stream of >100 GBit/s from digitizer to GPU for realtime signal processing and visualization.
Your mental model of a GPU should be co-processor, not programmable display-interface.
It took me a while, too, to come to realize that. But technically GPUs shouldn't even be on the cards we plug displays into.
Wayland/waypipe doesn't transmit the actual draw commands, though and instead resembles a per-client VNC.
My main motivation is building a compiler boostrap ladder.
tcc → tcc.static → tccmusl.static → tcc.static-tccmusl → gcc4.9.static-tccmusl → musl.static → gcc4.9.static-musl → musl → gcc4.9-musl
From there it should be mostly straightforward to climb the ladder of every major GCC version, and also branch out into LLVM/clang and glibc.
The starting point I'd approach this from would be this repository
https://github.com/GataOS/musl-tcc
Do a merge / rebase against latest musl, look at the diff to musl upstream and clean up and rewrite anything I don't like. If / where necessary introduce conditional compilation blocks active only when used by/with tcc.
What's your stance on including the/some tinycc-musl-support patches into mainline musl?
@benjamineskola @SheRaPantsuit @Beatpoet13
It's even worse. Interactive LLMs create a linguistic bypass channel that "connects" parts in our minds/brains that are ordinarily separated by filters for plausibility and attenuating uncontrolled feedback. Furthermore, they can be tailored to adversely amplify select thought patterns.
They're the first, rudimentary implementation of the kind of cognitohazards that used to be science fiction.
Already they're potent cult-indoctrination machines.
1/
You know what company I hold a fiece grudge on? Analog Devices.
They've been gobbling most if not all of my second source suppliers for precision electronics circuits.
These days I rather spend weeks designing circuits from discrete parts, around wide operational ranges, and if I really have to put an IC in there, it's going to be a part that has hundreds of similar performing replacements.
Yes, I know. ADI's actions over the past decade (and a half) should have triggered several cartel regulation authorities (FTC, etc.) to spring into action.
ADI is already holding monopolies on several key component classes. There might be a couple of Chinese replacements in existence, but they're more or less invisible to the western markets.
The EU is asleep at the wheel. They should have incentivized creation of European counterparts decades ago.
I'll happily spend 40 hours a week doing science. What really grinds my gears is all the bureaucracy BS hustling for grant money.
Just give me a lab and a yearly total budget of ~250000€ for buying stuff, paying contractors and paying my salary from, and allow me to carry any leftover into the next fiscal year. I'll churn out royalty free medical imaging tech.
@khm @akkartik @dalias @Byte @inata
Same. In 2012 I was approached by Google for an SRE role in Zürich or Dublin. I went through the interview in Zürich, but the whole place gave me a massive ick.
It's also a lot more accurate (IMHO) with respect to what the actual goals are/should be.
Oder, man könnte sich auch einfach aufhören Fossilenergie zu nutzen und endlich mal in der Zukunft ankommen.
Liebe Tagesschau: Es wäre EURE Aufgabe, als Teil der 5. Gewalt im Staat diesen absoluten Blödsinn den die Gaskathi permanent von sich gibt zu korrigieren und einzuordnen.
Die Frau ist von vorne bis hinten, unten wie oben untragbar für das Land.
And once again the Zig language project shows, that there's a better way: https://ziglang.org/code-of-conduct/#strict-no-llm-no-ai-policy
@aparrish For some time now I've been calling out interactive LLM systems as almost perfect cult indoctrination systems.
The day I realized, what these things are I vowed to myself to never engage with LLMs whatsoever.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.