sprash

34 ms·

301.
by sprash 5y ago
ASMUTILS were specifically made for this. All your typical unix command line applications implemented in x86 assembly. You can still download the floppy image here: http://asm.sourceforge.net/asmutils.html
302.
by sprash 5y ago
This looks amazing. This app would make half of my current job more or less redundant.
303.
by sprash 5y ago
Your link contains is a nice article [1] how the resolution independent "raster type" looks like when zooming in including ancient Windows software to try it yourself. Sadly wine crashes when I try to start it. 1.: http:/&#x
304.
by sprash 5y ago
This format was very interesting because it was essentially "resolution independent". You could zoom in further and further and see nonsensical made up details by the fractal algorithms without getting any blurriness or interpolat
305.
by sprash 5y ago
If toolkits can "abstract that away" they can do the same on X11 and there is even less reason for Wayland to exist. There is no reason for you to even care about X11/Wayland if you only work with toolkits. So stop participat
306.
by sprash 5y ago
> I have always seen X as complex. True, but don't assume Wayland to be less complex [1]. It has a lot less features, sure. 1.: https://wayland.app/protocols/
307.
by sprash 5y ago
You think this is bad? Just look at a native Wayland "Hello World" client [1]. This doesn't even print hello world. You have to do the text rendering yourself. And you need at least 500 more lines to implement the equivalent
308.
by sprash 5y ago
Wow, dtksh is very interesting. It looks like tcl/tk just with a POSIX style shell as programming language.
309.
by sprash 5y ago
All "equivalents" you mention have less functionality than their originals and some only work on specific compositors like wlroots/sway. Like all things Wayland it's a mess with zero benefits for the user. HTTPS vs HTT
310.
by sprash 5y ago
This is not an organic transition. Major organizations seems to "push" it but there is not much "pull". Compare this to the "transition" from CVS/SVN to git. There was no need to even advertise git. People
311.
by sprash 5y ago
The final "composing" step in Wayland does require Wayland to use a "giant" buffer as well. Also My GPU has 16 GB of GDDR how can any frame buffer be "giant" in that context? The support of hidpi scaling is som
312.
by sprash 5y ago
> right as the replacemeant for Xorg starts to take off though It has been "taking off" for 13 years at this point. It seems like it doesn't have much thrust behind it.
313.
by sprash 5y ago
Yes I was referring to the "WebGPU Shading Language" which I abbreviated with WebGPU which should be obvious. The WebGPU API is the boiler plate you need to make WGSL over the wire work. My original proposal was an X extension in
314.
by sprash 5y ago
Instead of playing the strengths of the UNIX desktop they are purposefully omitting them and trying to be a subpar copy of Windows/Mac all while throwing backwards compatibility out of the window for no apparent reason on a regular bas
315.
by sprash 5y ago
WebGPU translates 1:1 to SPIR-V.
316.
by sprash 5y ago
Then why not use a wire protocol for Vulkan? SPIRV already exists. It only needs some wrapper code tacked on to work as a X extension and you have perfectly efficient server side rendering that potentially works even over the network withou
317.
by sprash 5y ago
> The problem with X11 drawing commands is that there are a lot of round-trips over the network. This is not a problem with drawing commands or the fact that the X11 wire protocol supposedly inefficient (it is actually very efficient). I
318.
by sprash 5y ago
> The GPU acceleration in Glamor doesn't really help According to benchmarks at the time 700-800% speedup. > everything still needs to be serialized by the X protocol Drawing in general needs to be serialized. As soon as the obje
319.
by sprash 5y ago
All XRender operations are already GPU accelerated via Glamor. The spline tesselation step of drawing is notoriously hard to do on GPUs. Hence the separation at that point was actually a smart choice.
320.
by sprash 5y ago
> So, your X server is really effectively nothing more than a shitty Wayland compositor. No it is a much better Wayland compositor because unlike Xwayland it provides full backwards compatibility. You even need much less boiler plate co
321.
by sprash 5y ago
> And going back to some client rendering enabling features like anti-aliasing. The xrender extension already supports server side drawing, anti-aliasing, transparency, gradients and so on. If you use for example Cairo with the xrender b
322.
by sprash 5y ago
> Sure, it has better performance if there is not a networking protocol in the middle. That's not even true. The DRI3 X11 extension uses the exact same buffer swap mechanism like most Wayland compositors. Running locally you get the
323.
by sprash 5y ago
For some applications you want "every frame is recent" and can tolerate some glitches as trade off for not having perfect frames. Also displays have different pitch values, subpixel arrangements, color spaces, etc. A line from A t
324.
by sprash 5y ago
The biggest problem of Wayland is that it has the wrong philosophy ("Every frame is perfect") and the wrong abstractions ("Everything in the universe is an array with RGBA values"). If your foundations are flawed like th
325.
by sprash 5y ago
Wayland makes the wrong abstractions and does not offer vital functionality usually needed on a Desktop system. As a result every Toolkit/Compositor has to implement that additional functionality itself and most of the time it is incom
326.
by sprash 5y ago
Rather bad news. Meson introduces a rat-tail of build dependencies.
327.
by sprash 5y ago
So far there is no viable replacement around that is "more adequate for the job" (Wayland is fundamentally flawed at the concept level). So Xorg will stick around much longer probably decades.
328.
by sprash 5y ago
None of those projects support the new compute module which is the only viable option for day to day desktop use. The only attractive looking device from Waveshare has a fake touchpad and can't be used for anything serious either. Th
329.
by sprash 5y ago
> bash is far behind concerning interactivity. Is it really? Projects like ble.sh [1] seem to pull off advanced features like syntax highlighting and enhanced completion with pure bash without the need for reimplementing a whole shell fr
330.
by sprash 5y ago
> You should not be using the low level Wayland API unless you're developing a toolkit The main reason the Linux Desktop is shit is because the main toolkits gtk and qt are shit. Wayland makes it incredibly hard to write a toolkit h

More ›