• 0 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: August 3rd, 2023

help-circle






  • It’s not intended to be a carbon sink. It’s essentially intended to be a more carbon efficient way of producing margarine without having to grow e.g. palm oil and destroy forests. They thought, instead of making plants do the work of turning water and CO2 into fats, let’s just do it in the lab.

    The basic science could work, although it’s usually tough to beat “put seeds into ground and wait” on pure cost. However the fact that they compare this to butter makes me sceptical. Given how wasteful growing a whole cow is just to make some milk fat, it’s easy to look efficient compared to that. They would compare themselves to sustainably produced margarine if they were honest.



  • I don’t really care about the declarative/imperative thing, to me how many commands you “really need” is beside the point. This is essentially the same argument as the people who say “git is not complex because you only really need checkout/commit/push, just ignore all the other commands.” This doesn’t matter when the official documentation and web resources keep talking about the other billion commands. Even home-manager has this warning at the very top of the page that basically tells you “you need to understand all the other commands first before you use this,” and “if your directory gets messed up you have to fix it yourself.”

    These are exactly the same kinds of problems people have with git.


  • The confusion arises because there are 5 different ways to do the same thing, the non-experimental methods shouldn’t be used even though they’re recommended in the official docs

    I appreciate what you’re trying to say, but you’re kind of illustrating exactly the point I was making about conceptual simplicity and atrocious UX.




  • The numbers are different because the site doesn’t naively count every line but merges some as a single package. For example, at the very top of the Debian list we have 0ad, 0ad-data, 0ad-data-common. These are all counted as one single “package.”

    One might argue that doing the comparison in that way is more useful to an average user asking “which distribution has more software available.”





  • Seems like there’s a bunch of solutions out there:

    As of 2020, there are several projects that use these methods to provide GUI access to remote computers. The compositor Weston provides an RDP backend. GNOME has a remote desktop server that supports VNC. WayVNC is a VNC server that works with compositors, like Sway, based on the wlroots library. Waypipe works with all Wayland compositors and offers almost-transparent application forwarding, like ssh -X.

    Do these not work for your use case?




  • I think for these types of discussions it’s really necessary to clearly define what “low level” really means, something both you and the author kinda skip over. I think a reasonable definition is about the amount of layers of abstraction between the language’s model of the machine and the actual hardware.

    The author is correct that nowadays, on lots of hardware, there are considerably more abstractions in place and the C abstract machine does not accurately represent high performance modern consumer processors. So the language is not as low level as it was before. At the same time, many languages exist that are still way higher level than C is.

    I’d say C is still in the same place on the abstraction ladder it’s always been, but the floor is deeper nowadays (and the top probably higher as well).