destructionator

12 ms·

91.
by destructionator 5y ago
> The biggest reason is security. X offers no GUI isolation. This is completely false. X offers both nesting for full isolation and a concept of "untrusted" connections for partial isolation. This is the reason why ssh -Y and s
92.
by destructionator 5y ago
> So it seems like it actually modifies the drawing at the application level rather than rescaling it like an image. X also supports exactly this. Qt uses this information. gtk doesn't for whatever reason, forcing the workarounds. M
93.
by destructionator 5y ago
nitpick but X11 is the protocol XCB speaks. You're probably speaking of Xlib which is a bit of a higher level library over the top of it (but... not really that much higher, for a great many tasks there's no real difference).
94.
by destructionator 5y ago
But the reality is those features were added to the first thing for reasons. Which means there's user pressure to add them again... which means the second system effect is virtually impossible to avoid. See for yourself: https:/&
95.
by destructionator 5y ago
They themselves also said there's no technical reason why they couldn't easily keep using X. They just didn't want to. < https://wayland.freedesktop.org/faq.html#heading_toc_j_5 > So it is putting their o
96.
by destructionator 5y ago
> while throwing backwards compatibility out of the window for no apparent reason on a regular basis. They are pure garbage to such an extent that they appear to be deliberate sabotage. This is exactly how I feel about Wayland. It is gra
97.
by destructionator 5y ago
I did D including a custom runtime in about +20 KB of webassembly over this (I just wanted to take a straight desktop program and port it over). The runtime doesn't have to be that big.
98.
by destructionator 5y ago
headline put the one compressed number instead of the uncompressed number. There's also ~10KB of javascript bridge it requires as well.
99.
by destructionator 5y ago
links actually does have a graphic mode... see http://links.twibright.com/features.php screenshots section. It really isn't too bad.
100.
by destructionator 5y ago
yeah im at the first screenshot and it just looks awful Have Microsoft forgotten the lessons they learned so hard since 1995? The start button being in the corner has real usability benefits. They ruined the taskbar a long time ago, the but
101.
by destructionator 5y ago
I wrote my own terminal emulator stack. I was annoyed that the colors were often unreadable on others and that shift+page up wouldn't work to scroll from inside gnu screen that I used to use. So I rewrote the whole thing from scratch,
102.
by destructionator 5y ago
> your main objective is to replace C++ D's main objective is to be useful. I did some hobby C++ that I replaced with D, but my main D migration was actually from PHP.
103.
by destructionator 5y ago
I stopped updating firefox on version 74 since the UI became unusably bad (it was already bad at 74, even with my userchrome.css hacks, but it went over the edge to unusable at 75). They need to separate out the UI updates from the the rest
104.
by destructionator 5y ago
> (Also this is why SF directors love transparent or "holographic" displays, because you can film the person looking at the screen and the thing being displayed at the same time) I caught an episode of NCIS a few weeks ago and
105.
by destructionator 5y ago
Not wrap per se, but bind. The parts of the .h file you need needs to be translated to D. There's no runtime cost to this and the function works the same as in C which is why I don't like calling it a wrapper. But doing this is ea
106.
by destructionator 5y ago
> Have you tried watching a video in full screen? Nah, I've actually never used a computer since 1995. What is this "yoo-tubes" thing all the kids are talking about nowadays anyway? You do realize that X applications can u
107.
by destructionator 6y ago
> With a compositor on top of X I reject that premise. I've never used a compositor and I don't know why anyone would, they seem utterly useless. But even if you do, the compositor only does one job: layer graphics. Most X mess
108.
by destructionator 6y ago
First off, a 45 minute long video isn't much of a citation. Where, exactly, are you citing? Secondly, this isn't the first time I've had people point to this same video. It doesn't actually say what you claim it says. It
109.
by destructionator 6y ago
First, this isn't true - watch the youtube the other person in this thread put where he tells a story about how they deleting about 1/3 of the code (15:19), but secondly even if they didn't, why is that a problem? Breaking us
110.
by destructionator 6y ago
> in opposition to what the actual X maintainers say, who actually created wayland? [citation needed]
111.
by destructionator 6y ago
> It is fundamentally broken. The Wayland developers disagree with you: https://wayland.freedesktop.org/faq.html#heading_toc_j_5 "It's entirely possible to incorporate the buffer exchange and update models that
112.
by destructionator 6y ago
> Allowing arbitrary clients to globally capture keys at will is impossible to do without opening up a hole for keyloggers https://www.x.org/wiki/Development/Documentation/Security/ The X.Org Foundati
113.
by destructionator 6y ago
and my approach is to do a minimal custom lib http://dpldocs.info/this-week-in-d/Blog.Posted_2020_08_10.ht...
114.
by destructionator 6y ago
> they more than anyone else know why they would need to start from scratch over improving x11. That's not what they actually say though: https://wayland.freedesktop.org/faq.html#heading_toc_j_5 "It's enti
115.
by destructionator 6y ago
Yes, D does it trivially. I don't think that's terribly unique though, as I understand it Rust and several others can too.
116.
by destructionator 6y ago
You do have to be legitimately careful with that. I've tripped myself before while sending objects through a self-pipe. The D GC only runs upon a function call, so with a bit of care you can defer runs, but here I allocated a new objec
117.
by destructionator 6y ago
C# is a pretty good language and for some tasks, probably a better choice. But D is very versatile, so once you get into it, you can expand your use into all kinds of different areas. It can do your regular application or line of business s
118.
by destructionator 6y ago
See the api divide wouldn't matter if the runtimes were merged (this actually happened, you can still use Tango today if you like) since you'd just import the other modules and have them side by side. Sure some libs might depend o
119.
by destructionator 6y ago
What irks me is this stuff is all from before 2007 - that's when the runtime support lib branches were merged - yet social media comments make it sound like it is today. I'm a bit irked personally at people saying "D1" v
120.
by destructionator 6y ago
The api wasn't really the problem, it was more about the language runtime. Upstream wasn't exactly receptive to big changes, so a segment of the community forked and made the changes themselves. But since these hit the core langua

More ›