Interests: News, Finance, Computer, Science, Tech, and Living

  • 16 Posts
  • 906 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle
  • flatbield@beehaw.orgtoLinux@lemmy.mlWayland forwarding?
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    edit-2
    1 day ago

    This is the big issue. It breaks a lot of X11 features. Remote desktop via VNC or RDP should still be possible. Another is ssh and sftp. Edit the file on the client. Another go all in with command line. Nano is easy. Emacs or VIM more powerful but harder. Screen is a useful command line tool too.

    Interested in what others suggest.




  • Except for MS format compatiblity, not my experience, Not sure where MS format compatibility stands now, but that has histically been the biggest issue.

    Keep on mind that MS supplied LibreOffice translator is not great either so they have issues too. MS really does not plan on being compatible even between versions of their own software.






  • My first printer in the early 80s was an EPSON dot matrix for $800. The second was an Apple laser printer in the late 80s for $3500. The third was a Brother momochrome MFC laser printer for $500 in the 00s. You can see why they are crap, huge price reductiions. Even more if you consider inflation and capability.

    Always look at per page cost. Generally that means monochrome laser.

    Edit: The issues I have had with Linux and the Brother MFC is firmware upgade as it wants to use Windows for that. I have had some Postscript compatability issues too. The paper feeder for the scanner is not perfect either. It can skew the paper and you have to watch for double feeds. Not a defect but a missing function, I cannot figure out how to fax from my computer or USB stick. An oddity, it does not seem to maintain time when the unit is off and never has which is really annoying especially for faxing. Mostly like the printer but not the above issues so much.




  • The need to do it plus the realization that you can script anything based on it.

    Drivers. Using recovery mode. Administration. Wanting to describe what to do rather then manually do it. Wild cards are really powerful and so is find and xargs. The text processing commands are useful too.

    The other thing is having started computing in the 1970s. Everything was command line back then. GUI systems only become universal in about 1995.









  • I think you just like the truth test. Frankly I have used Python for over 25 years and have been doing programming for almost 50 years in many different languages. If you think I am somehow a beginner, I would disagree. The truth test is just like so many other Python specific idioms that grow in number by the year. They are not at all obvious unless you are deep into Python. Moreover, the truth test and the len() test are not the same test. One might be able to use either in a specific case, but that is case specific and which is more readable is up to the developer and we may well disagree on that choice. The other consideration in Python, speed of writing code which is often why many of us use Python and that may lead to different choices too including based on habit.

    Lot of this reminds me of the Pascal vs. C debate of the 1980’s. Pascal was all about readability over compactness. C on the other hand, seemed to attract people that loved to write very compact code that was almost impossible to figure out on first glance. Me personally, I guess I’d choose C over Pascal but write the C in more of a Pascal authoring philosophy. Similarly, with Python, I often do not go for all of the Python idioms. Lot of that is just writing what I am thinking, and the rest is probably habit. If I am going to test 0 length then I’ll probably test zero length. I do not find it at all obvious that, oh, I want to test 0 length so the Python idiom for that is to truth test. I absolutely know that to be the case on certain types of objects, but it probably is not going to be my first choice.