• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle

  • Tempy@lemmy.temporus.metoLinux@lemmy.mlNeat factor
    link
    fedilink
    arrow-up
    1
    ·
    8 months ago

    If you are on endeavour, I don’t think there’s much point jumping to plain Arch if you are all setup and comfortable. I say this as a pure Arch user 😛 Not much will change for you, you’ll just be pissing away a day to setup everything you’ve already setup on endeavour again.




  • Vim or emacs? I mean I know they were created a long time ago, but they are both pretty good pieces of software, both highly configurable. I don’t understand people aversion to them, rather than having the false belief that they are too complicated? When in reality they just aren’t intuitive in terms of modern stuff. But they aren’t difficult, just different.









  • I mean for most Linux derivatives, getting SSH setup for outgoing connections is usually install the openssh package from your distros repos, though I imagine many preinstall it, no reboot should be necessary, and you just type ssh user@hostname into a terminal to connect to the remote ssh server to access stuff on that computer. There shouldn’t be a need to reboot for installing app that’s not a service.

    Wanting to enable ssh access to the computer you are using so a remote client can connect to it? Well the same openssh package should have come with sshd which acts as the server to allow remote ssh client to connect. It’d probably need enabling (so it’s run automatically on boot) and starting (so you don’t have to reboot to have it going), on distributions using systemd that’s usually just systemctl enable sshd.service (which makes sure the sshd daemon will be started on next boot) followed by systemctl start sshd.service to start it immediately so it’s running straight away, (or systemctl enable sshd.service --now to roll both steps into one).


  • I’d just point out, for running an executable, wine isn’t JITting anything at least as far as I’m aware. They’ve implemented the code necessary to read .exe files and link them, and written replacements libraries for typical windows DLLs, that are implemented using typical Linux/POSIX functions. But since, in most cases, Linux and windows runs on the same target CPU instructions set most of the windows code is runnable mostly as is, with some minor shim code when jumping between Linux calling conventions to windows calling conventions and back again.

    Of course, this may be different when wine isn’t running on the same target CPU as the windows executable. Then there might be JITing involved. But I’ve never tested wine in such a situation, thoughI’d expect wine to just not work in that case.






  • I started using Linux many moons ago when the LAMP stack was common for web development. (Linux, Apache, Mysql, PHP). But that was only on servers. It’s only in the last couple of years I’ve switched to seriously using Linux on the Desktop. I finally got fed up of Microsoft writing software as if using their OS meant they owned my machine and they could do what they liked with it. So I’ve switched. While windows still sits on a partition due to a couple of games, I find I’m going months without needing to touch it. I suspect I’ll be rid of windows entirely in the near future.


  • Depending on your language, your closest analogue is going to be interfaces. C# even has a where clause where you can restrict a generic type such that any type substituted must implements one or more interfaces. You can get quite a bit of trait like working there, from the function input side of stuff.

    The biggest problem is, you can’t implement an interface for a type unless you have access to the type. So you’d have to really on wrapping types you don’t own to apply trait like interfaces to it.

    And then there’s minor issues like, no such thing as associated types, or being able to specify constants in a definition. But you can usually work around that in a less nice way.