Skip Navigation

Posts
17
Comments
227
Joined
3 yr. ago

  • ISO/OSI is a neatly separated model mostly used on theory.

    In practice, actual network stacks are often modeled after a simpler model that is called TCP/IP. Which despite the name is not actually TCP specific.

    Here's the general description and correspondence to ISO/OSI:

    1. Host to network / network access layer: it's mostly the nic and nic driver. It's sometimes numbered as 0 because some don't consider it part of the TCP/IP stack, but simply the nic driver. Corresponds to:
      1. Physical
      2. Datalink
    2. Network layer: Corresponds to:
      1. Network
    3. Transport layer: Corresponds to:
      1. Transport
    4. Application layer: everything that's part of the application and not the network stack. Corresponds to:
      1. Session
      2. Presentation
      3. Application

    Or, you can just not care about how the actual software stack is separated, and continue to use the most complete model, knowing that everyone will understand what you when you say "layer 2/3/4" anyway.

    Plus, some could say that the TCP/IP model is equally unfit because the Linux network subsystem doesn't care about layers.

    Edit: I hope the formatting of that table isn't broken on your client, because it is on mine

  • Rule

    Jump
  • That's Tungsten

  • It places you one year ago before they rebranded in rocq (obviously to stop the puns)

  • Then, the year of the freebsd desktop came many years ago when apple released MacOS

  • What disconnecting problem?

  • My system should be fully updated, I will try an Xbox 360 cabled controller

  • That's a flattering thought, but I think that kind of improvement is a pipedream.

    The os shenanigans might be the reason tho

  • You are correct, it also lacks a decorative groove that the "one" one has near the top.

    I think the "series" d-pad is the best modern d-pad, especially since Nintendo forgot how to make them just before releasing the Wii u. I'd say on par with classic Nintendo d-pads, maybe a bit less comfortable for platformers though.

    On the other hand, the 360 d-pad is the worst most horrible piece of crap ever devised.

  • I am seeing higher latency even plugged via cable though, even if less so

  • No, kde

  • Linux @lemmy.ml

    Gamepad latency of the XBOX series S controller

  • yeah, but the point of a platform are the applications it supports, you don't want to be The King of Nothing. If even after buying into wayland, applications still work bad on gnome because they expect to get support for X, than gnome needs X or to give a better option (better for the applications, not just according to themselves).

  • PING. Commenting just for the notification. I edited to respond to the other points but in the meantime you had already answered.

  • The point 2.1 "less to implement in the compositor" doesn't apply, because for xwayland go work (which is intended to stay around for the foreseeable future) mutter still needs to implement SSD, it's only skipping on implementing the Wayland SSD protocols.

    Points 1 and 2.2 are not strong points. "We do

    <thing >

    because we always did before <thing 2>" is not a good point. For example, after all, we always used X10 before Wayland, and we always did implicit sync before last year. And compositor shouldn't limit programming styles, they should support as many things as possible, and let the application decide their programming design. Plus, most modern applications on windows and macos embed a copy of chrome to display a single offline Web page, but I don't see you suggesting we replace compositors with browsers.

    Point 2.3 is also weak because most of the things a compositor does are already hard, but they implement them because it makes the experience better. If something is hard, it just means it will be worked on more. Take a look at explicit sync, it took like 4 years to be rolled out, but it was necessary and got implemented.

    I'll give you point 2.3.1... in general I think KDE looks pretty bad, and gnome is really more polished in many aspects. Unfortunately I really prefer the KDE workflow on big screens (but gnome on laptops).

  • You mean about adding SSD to gnome, which will not happen?

    As an argument in favour, I see:

    • Support for more applications that "don't want" to implement CSD (i.e. foot terminal, davinci resolve, that one archive manager I can't remember)
    • Lifting burden for applications that don't need custom decoration buttons, and so don't care about implementing their own decorations
    • Making the decorations on those applications consistent with the theming of the system

    As an argument against, I personally don't see any. Sure, most gtk apps are designed for CSD and will not translate well to SSD, but I just don't see why that should stop gnome from implementing SSD. I remember the gnome maintainers were strongly convinced against SSD, but I don't remember their argument

  • X.Rule

    Jump
  • Ahhh, Verona, the city of Romeo and Juliet, and of trademark infringements

  • If you are writing a parser in haskell just use Happy and get it over with

  • I experience something similar on a vega56, but it doesn't happen on generic high loads, it happens only

    • in some specific loads (for me it was mainly A Plague Tale: Requiem)
    • when something touches the grounding of my monitor (the display port of the GPU is faulty, it seems)
  • I like many of your points, but your comment is facetious.

    You said it yourself, "it's good for someone trying to bang out scripts"... and that's it, that's the main point, that's the purpose of python. I will argue over my dead body that python is a trillion times better than sh/bash/zsh/fish/bat/powershell/whatever for writing scripts in all aspects except availability and if that's a concern, the only options are the old Unix shell and bat (even with powershell you never know if you are stuck ps 5 or can use ps 7).

    I have a python script running 24/7 on a raspberry that listens on some mqtt topics and reacts accordingly asynchronously. It uses like 15kiB (literally less than 4 pages) of ram mostly for the interpreter, and it's plenty responsive. It uses about two minutes of CPU time a day. I could have written it in rust or go, I know enough of both to do it, it would have been faster and more efficient, but it would have taken three times the time to write, and it would have been a bitch to modify, I could have done it in C and it would have been even worse. For that little extra efficiency it makes no sense.

    You argue it has no place in mainstream software, but that's not really a matter of python, more a matter of bad software engineers. Ok, cool that you recognise the issue, but I'd rather you went after the million people shipping a full browser in every GUI application, than to the guys wasting 10 kiB of your ram to run python. And even in that case, it's not an issue of JavaScript, but an issue of bad practices.

    P.S. "does one thing well" is a smokescreen to hide doing less stuff, you shouldn't base your whole design philosophy on a quote from the 70s. That is the kind of shit SystemD hater shout, while running a display server that also manages input, opengl, a widget toolkit, remote desktop, and the entire printer stack. The more a high profile tool does, the less your janky glue code scripts need to do.

  • I'll be honest, I think modern python is cool. You just need to accept that it has some limitations by design, but they mostly makes sense for its purpose.

    It's true that the type system is optional, but it gets more and more expressive with every version, it's honestly quite cool. I wish Pylance were a bit smarter though, it sometimes fails to infer sum types in if-else statements.

    After a couple large-ish personal projects I have concluded that the problem of python isn't the language, but the users.

    On the other hand, C's design is barren. Sure, it works, it does the thing, it gives you very low level control. But there is nothing of note in the design, if not some quirks of the specifications. Being devoid of innovation is its strength and weakness.

  • I would like to interject for a moment. This statement is technically true but disingenuous and facetious.

    While it's true that Linux is just the kernel, what most people refer to as Linux is actually the Operating System GNU/Linux, or, as RMS would now call it, GNU plus Linux, or sometimes, a less GNU depended, but mostly GNU/Linux compatible OS, or, as I have literally just now come to call it */Linux.

    Moreover, a modern */Linux system is expected to be based on SystemD, unless explicitly avoiding it due to some technical constraint or some desired feature of another init system. One could come to call this SystemD/Linux.

    And lastly, this kind of use case would be the perfect match for a Wayland shell, as opposed to an X11 shell. Which would be more efficient, and would give the shell more freedom in the management of windows.

    As a result, when asking about a Linux phone, we could expect one is talking about a phone running a SystemD+Wayland/Linux OS, or at least a mobile-focused */Linux OS.

    The Android kernel is a, largely downstream, fork of the Linux kernel, but the Android OS is in almost no way compatible with any */Linux OS, and it's instead its own completely different OS.

  • Linux @lemmy.ml

    How to manage configuration files

  • linuxmemes @lemmy.world

    Everything is so tiny

  • Programmer Humor @programming.dev

    His man.go

  • linuxmemes @lemmy.world

    His man.go

  • Linux @lemmy.ml

    Why can ffmpeg kmsgrab capture the tty without root permissions?

  • Linux Gaming @lemmy.ml

    Shadow of the tomb raider, native or proton-experimental

  • Linux @lemmy.ml

    I can now control external display brightness from KDE and I don't know why. Thank you, nameless Linux contributor

  • Linux Gaming @lemmy.ml

    PhysX on Batman Arkham Asylum

  • Linux @lemmy.ml

    Storing SSH keys on gnome-keyring, kwallet, ibsecret or similar

  • Linux @lemmy.ml

    Switching rgb range at monitor plugin

  • Linux @lemmy.ml

    Splitting headphones and internal speakers on a thinkpad with fedora

  • Linux @lemmy.ml

    Imagine trusting oracle

  • Memes @lemmy.ml

  • Linux @lemmy.ml

    Can I apply a shader to the whole screen?

  • Reddit Migration @kbin.social

    remember to update your review of the official reddit app

  • Memes @lemmy.ml

    No more sad dinners