emersion

21 ms·

211.
by emersion 8y ago
Just having this is a huge improvement over what most lists have (e.g. https://lists.freedesktop.org/archives/wayland-devel/ ). There are also patch formatting features that let you comfortably review patches: htt
212.
by emersion 8y ago
"Open" doesn't mean "read", it means "freedom". If I look up the definition of "open-source" for instance on Wiktionary [1], it says "permit modifications and redistribution" (and refer
213.
by emersion 8y ago
There are two issues. First, naming is confusing, as you said, and wording implies "<open source license> + something more" instead of "<open source license> but with more restrictions". Second, some open-sou
214.
by emersion 8y ago
This is not the point. The point is: stop calling open-source stuff that isn't. You shouldn't lie to your users.
215.
by emersion 8y ago
R has a lot more issues than Python IMHO.
216.
Writing a Wayland client rendering loop(emersion.fr)
1 points by emersion 8y ago|0 comments
217.
Go 1.11 got me to stop ignoring Go(drewdevault.com)
12 points by emersion 8y ago|0 comments
218.
by emersion 8y ago
GNOME and KDE have working support for remote desktop. Weston supports RDP. Sway (and other wlroots-based compositors) have been working on protocols to support it.
219.
by emersion 8y ago
>Ultimately, since I can't go wrong with X and I can go wrong with Wayland, the choice was easy. Keep in mind that Wayland has been designed by people who've been maintaining X11 for years. >it also offers no mode that would
220.
by emersion 8y ago
When I asked one of my professors about doing a PhD he told me: "Doing a PhD is like getting married: choose your advisor wisely". It seems that good advisors are a key factor of a successful PhD.
221.
by emersion 8y ago
Sure, but then it's quite difficult to say that one is "more resource efficient" than the other. Only implementations can be compared. And in fact, when you e.g. open Gedit, hundreds of messages are exchanged on X11 (getting&
222.
by emersion 8y ago
Nothing stops you from building a very small Wayland compositor.
223.
by emersion 8y ago
No, it won't work. There are some possible replacements (e.g. [1]) but it's still a work-in-progress. [1]: https://github.com/swaywm/wlr-protocols
224.
by emersion 8y ago
>Is it a fact that X is "smaller" than Wayland, and more resource efficient? This statement doesn't really make sense. Wayland is just a protocol, and you can build bloated compositors on top of it -- just like you can bui
225.
by emersion 8y ago
I've seen some Xwayland patches to make the proprietary NVIDIA driver work in compositors that support it. Mandatory link to NVIDIA rant: https://drewdevault.com/2017/10/26/Fuck-you-nvidia.html
226.
by emersion 8y ago
>Wayland, on the other hand, is just a compositor. Wayland is _just_ a protocol. There a multiple compositors (GNOME, KDE, Weston, Sway, etc) implementing the protocol differently. >I'm sad because X is fun to figure out. I'
227.
by emersion 8y ago
>It's not bloated X11 has a big number of issues. Security, very complicated mechanisms (like how clipboard is handled), HiDPI are some of these issues. X11 _is_ bloated (for instance it has an drawing API). It's not like Wayla
228.
by emersion 8y ago
Heterogenous graphics card configurations can be supported on Wayland (e.g. Sway 1.0 supports them). GPU hot plugging could be supported by compositors as long as you don't need the compositor to change the GPU it's rendering on (
229.
by emersion 8y ago
Hmm, I don't think you could say that. Wayland restricts a lot more what clients can do.
230.
by emersion 8y ago
In case you haven't found it yet, the "please draw a frame" event you get from the compositor is wl_surface.frame: https://wayland.freedesktop.org/docs/html/apa.html#protocol-...
231.
by emersion 8y ago
Sometimes there are tasks that are not really suited for the GPU. For instance, drawing text is much easier to do on the CPU. Also for clients that only draw a few frames occasionally (status bars, background images) drawing on the CPU is t
232.
by emersion 8y ago
I've been developing such a thing, mainly for git-send-email and CardDAV sync: https://github.com/emersion/hydroxide
233.
by emersion 8y ago
>Neither is a GPU. https://en.wikipedia.org/wiki/Direct_Rendering_Manager#Rende...
234.
by emersion 8y ago
I didn't link the code to say "hey look this code is bad", my intent was just to illustrate that functions inside functions indeed do happen, and unzip is also used, etc. >OCaml has support for bytes in the Bytes module. H
235.
by emersion 8y ago
We need optional values for bytes, as a way to say "this byte is undefined", so we can't use Bytes directly. But yes, we're doing it wrong for sure. EDIT: seems like you edited your reply, so let me add this to mine :) &
236.
by emersion 8y ago
Here are a few examples: - Inferred types: you're constantly wondering "what is the type of this variable?". Type errors occur far from where the real type error is. Annotating is complicated because you're often dealing
237.
by emersion 8y ago
I'm contributing to a linker written in ~OCaml [1], and now I understand writing systems code in OCaml is really a bad idea. It makes things more complicated when you really don't want them to be. As James Mickens says [2]: >Yo
238.
by emersion 8y ago
>I think the text format for interleaving source and commentary needs its own discussion somewhere, and probably a standalone repository separate from implementation (and some day preferably too, an RFC, or at least a MIME type registrat
239.
by emersion 8y ago
Hi, I'm the author of emailthreads, mentionned in the article. I believe the library is already able to do something pretty close to what you want. See for example this output: https://github.com/emersion/python-em
240.
by emersion 8y ago
Damn. Too many javascripts on this page, including Facebook's. I guess I'll pass.

More ›