Announcement

Collapse
No announcement yet.

GNU Debugger "GDB" Adds Support For Microsoft's Debug Adapter Protocol

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • GNU Debugger "GDB" Adds Support For Microsoft's Debug Adapter Protocol

    Phoronix: GNU Debugger "GDB" Adds Support For Microsoft's Debug Adapter Protocol

    Merged today to the GNU Debugger (GDB) is initial support for the Debug Adapter Protocol (DAP) that is a JSON-RPC interface for use by integrated development environments (IDEs) to better communicate with debuggers...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    This is great! Along with LSP, this is one of the few good things Microsoft did for the wider ecosystem

    Comment


    • #3
      Originally posted by vohcjdwd
      "UTF-16" appears 20 times in the specification, ergo it's obsolete on arrival. Microsoft have a really disgusting habit of forcing obsolete encodings into new protocols (LSP being another one).
      You don't know QT then? I don't like utf-16 at all, but it's here to stay. Don't like text-based protocols either, you should always be able to just skip x bytes to drop one element.


      No one else did something, and it appears to be good enough. So kudos to them.

      Comment


      • #4
        Originally posted by vohcjdwd
        "UTF-16" appears 20 times in the specification, ergo it's obsolete on arrival. Microsoft have a really disgusting habit of forcing obsolete encodings into new protocols (LSP being another one).
        Today's state of the art is tomorrow's obsolete if all you're doing is keeping up with bleeding edge. Most professional developers don't like that, however. They want stable, useful tools with a stable UX for as long as they're working on a project.

        If you're not a regular user of GDB and IDEs though, you're really just screaming at the clouds for drifting on the wind. No one is going to listen.

        Comment


        • #5
          UTF-16 is lame indeed, and completely pointless because in order to handle it correctly you need to handle surrogate pairs anyway, and for symbols (almost entirely ASCII) it doubles the size of most strings vs UTF-8... but sadly it isn't fatal to projects.

          Comment


          • #6
            Most agree that utf8 is better, but for historical reasons utf16 isn't going anywhere being the encoding for Java, JavaScript, C#, and the Windows API.

            Comment


            • #7
              Shrugs, ascii/c is just fine for me.

              Not many people desire chars not readily typed by a standard keyboard.

              Comment


              • #8
                Originally posted by rogerx View Post
                Shrugs, ascii/c is just fine for me.

                Not many people desire chars not readily typed by a standard keyboard.
                you have got to be trolling. so to you the physical keyboards people that speak pretty much every other european language use aren't "standard keyboards"? or what about the billion or so people who rely on pinyin input, are their input methods not standard enough for you? how come "not many people" desire chars outside the 26-letter english roman alphabet?
                Last edited by IndioNuvemChuva; 04 January 2023, 05:42 PM.

                Comment

                Working...
                X