home.social

#ide — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ide, aggregated by home.social.

  1. ✨ Zed 1.0 è finalmente realtà: l’editor in Rust con rendering GPU arriva alla versione stabile dopo cinque anni di sviluppo e fa sembrare VS Code lento e obsoleto
    gomoot.com/zed-1-0-leditor-di-

    #editor #ide #news #opensource #Rust #zed

  2. ✨ Zed 1.0 è finalmente realtà: l’editor in Rust con rendering GPU arriva alla versione stabile dopo cinque anni di sviluppo e fa sembrare VS Code lento e obsoleto
    gomoot.com/zed-1-0-leditor-di-

    #editor #ide #news #opensource #Rust #zed

  3. ✨ Zed 1.0 è finalmente realtà: l’editor in Rust con rendering GPU arriva alla versione stabile dopo cinque anni di sviluppo e fa sembrare VS Code lento e obsoleto
    gomoot.com/zed-1-0-leditor-di-

    #editor #ide #news #opensource #Rust #zed

  4. ✨ Zed 1.0 è finalmente realtà: l’editor in Rust con rendering GPU arriva alla versione stabile dopo cinque anni di sviluppo e fa sembrare VS Code lento e obsoleto
    gomoot.com/zed-1-0-leditor-di-

    #editor #ide #news #opensource #Rust #zed

  5. Use `:w !sudo tee %` to save a file that requires elevated permissions to edit, when you have forgotten to append sudo before opening it.

  6. Use `:w !sudo tee %` to save a file that requires elevated permissions to edit, when you have forgotten to append sudo before opening it.

    #linux #vim #neovim #nvim #ide #texteditor #arch #shortcuts

  7. Une histoire des IDE utilisés historiquement chez Google.
    Je trouve l'argumentaire de la "rationalisation" difficile à entendre ... sauf quand on prend en compte le fait qu'il s'agit d'IDE payants, à adapter à un environnement très loin des standards.
    Et franchement, ça donne vraiment l'impression d'une boîte absolument peu innovante. laurent.le-brun.eu/blog/a-hist #ide #vscode #histoire #google

  8. Une histoire des IDE utilisés historiquement chez Google.
    Je trouve l'argumentaire de la "rationalisation" difficile à entendre ... sauf quand on prend en compte le fait qu'il s'agit d'IDE payants, à adapter à un environnement très loin des standards.
    Et franchement, ça donne vraiment l'impression d'une boîte absolument peu innovante. laurent.le-brun.eu/blog/a-hist #ide #vscode #histoire #google

  9. Une histoire des IDE utilisés historiquement chez Google.
    Je trouve l'argumentaire de la "rationalisation" difficile à entendre ... sauf quand on prend en compte le fait qu'il s'agit d'IDE payants, à adapter à un environnement très loin des standards.
    Et franchement, ça donne vraiment l'impression d'une boîte absolument peu innovante. laurent.le-brun.eu/blog/a-hist #ide #vscode #histoire #google

  10. Une histoire des IDE utilisés historiquement chez Google.
    Je trouve l'argumentaire de la "rationalisation" difficile à entendre ... sauf quand on prend en compte le fait qu'il s'agit d'IDE payants, à adapter à un environnement très loin des standards.
    Et franchement, ça donne vraiment l'impression d'une boîte absolument peu innovante. laurent.le-brun.eu/blog/a-hist #ide #vscode #histoire #google

  11. The agonizing slow death of the power user

    This is a fascinating article to read. The facts are nailed to the wall in clear and easy to comprehend jargon, even for the non-grey beards

    Some quotes

    Ask a twenty-two-year-old to connect to a remote server via SSH. Ask them to explain what DNS is at a conceptual level. Ask them to tell you the difference between their router’s public IP and the local IP of their laptop. Ask them to open a terminal and list the contents of a directory. These are not advanced topics. Twenty years ago these were things you learned in the first week of any serious engagement with computers. Today they’re exotic knowledge that even a lot of working software developers don’t have, because you can go a long way in modern development without ever leaving the managed abstractions your platform provides.

    And that’s the real damage. It’s not just end users who don’t know this stuff. It’s developers. People who write software for a living who’ve never had to think about what happens between their API call and the response. Who’ve never had to debug something at the network layer. Who’ve never had to read a full stack trace and understand every frame of it. Because the frameworks handle all of that, and the frameworks are good enough, and figuring out how things actually work is optional.

    iOS set the template. Apple shipped a device in 2007 that was, by any reasonable technical measure, a computer. It had a CPU, RAM, persistent storage, a network stack, and a real operating system descended from BSD Unix. By every cultural and legal measure, however, Apple treated it as something else entirely: an appliance that you licensed rather than owned, that ran software only Apple approved, that couldn’t be meaningfully modified, and that communicated only through channels Apple controlled. No filesystem access. No inter-app communication beyond what Apple chose to expose. No background processes without explicit, limited, grudging permission. No ability to install software from any source other than the App Store — which Apple created, controls, taxes at thirty percent, and can pull your app from at any time for any reason with no meaningful appeals process.

    Some facts

    Power User

    A power user is a user of computers, software and other electronic devices who uses advanced features of computer hardware,[1][2][3] operating systems,[4] programs, or websites[5] which are not used by the average user. A power user might not have extensive technical knowledge of the systems they use[6] but is rather characterized by competence or desire to make the most intensive use of computer programs or systems.

    Term use

    The term came into use in the 1980s, as advocates for computing developed special skills for working with or customizing existing hardware and software. Power users knew the best ways to perform common tasks and find advanced information before the arrival of the commercial Internet. On PC platforms, power users read magazines like Byte or PC Magazine, and knew enough about operating systems to create and edit batch files, write short programs in BASIC, and adjust system settings. They tended to customize or "supercharge" existing systems, rather than create new software.[7]

    Notes

    This is systematically done by the factories of technology. I am baffled that a 41 year old litterate person, with secondary school and partial tertiary school, cant tell the difference between an email account, a FB account, a local machine account, a table, notebook and Android phone, from the basic technological perspective. This happened a couple of hours ago, which makes this article very relevant to me.

    This person was born two generations ago!

    WTF happened to reading manuals!?

    I read all manuals I get with hardware I buy, go online to fetch and read, PRINT IF I HAVE TO!

    Power Users are a sub-species of homosapiens which is in the greybeard stage.

    Eventually we will drop our current corpus and move on to other energy levels of existence

    Power users will become extinct in the next generation or two

    A bleak future for those left

    Z

    sources

    en.wikipedia.org/wiki/Power_Us

    fireborn.mataroa.blog/blog/the

    #Power #User #Death #Vigil #Eulogy #Abstraction #API #IDE #programming #DNS #networking #File #System #FileSystem #sadness #bleak #future #lisp

  12. The agonizing slow death of the power user

    This is a fascinating article to read. The facts are nailed to the wall in clear and easy to comprehend jargon, even for the non-grey beards

    Some quotes

    Ask a twenty-two-year-old to connect to a remote server via SSH. Ask them to explain what DNS is at a conceptual level. Ask them to tell you the difference between their router’s public IP and the local IP of their laptop. Ask them to open a terminal and list the contents of a directory. These are not advanced topics. Twenty years ago these were things you learned in the first week of any serious engagement with computers. Today they’re exotic knowledge that even a lot of working software developers don’t have, because you can go a long way in modern development without ever leaving the managed abstractions your platform provides.

    And that’s the real damage. It’s not just end users who don’t know this stuff. It’s developers. People who write software for a living who’ve never had to think about what happens between their API call and the response. Who’ve never had to debug something at the network layer. Who’ve never had to read a full stack trace and understand every frame of it. Because the frameworks handle all of that, and the frameworks are good enough, and figuring out how things actually work is optional.

    iOS set the template. Apple shipped a device in 2007 that was, by any reasonable technical measure, a computer. It had a CPU, RAM, persistent storage, a network stack, and a real operating system descended from BSD Unix. By every cultural and legal measure, however, Apple treated it as something else entirely: an appliance that you licensed rather than owned, that ran software only Apple approved, that couldn’t be meaningfully modified, and that communicated only through channels Apple controlled. No filesystem access. No inter-app communication beyond what Apple chose to expose. No background processes without explicit, limited, grudging permission. No ability to install software from any source other than the App Store — which Apple created, controls, taxes at thirty percent, and can pull your app from at any time for any reason with no meaningful appeals process.

    Some facts

    Power User

    A power user is a user of computers, software and other electronic devices who uses advanced features of computer hardware,[1][2][3] operating systems,[4] programs, or websites[5] which are not used by the average user. A power user might not have extensive technical knowledge of the systems they use[6] but is rather characterized by competence or desire to make the most intensive use of computer programs or systems.

    Term use

    The term came into use in the 1980s, as advocates for computing developed special skills for working with or customizing existing hardware and software. Power users knew the best ways to perform common tasks and find advanced information before the arrival of the commercial Internet. On PC platforms, power users read magazines like Byte or PC Magazine, and knew enough about operating systems to create and edit batch files, write short programs in BASIC, and adjust system settings. They tended to customize or "supercharge" existing systems, rather than create new software.[7]

    Notes

    This is systematically done by the factories of technology. I am baffled that a 41 year old litterate person, with secondary school and partial tertiary school, cant tell the difference between an email account, a FB account, a local machine account, a table, notebook and Android phone, from the basic technological perspective. This happened a couple of hours ago, which makes this article very relevant to me.

    This person was born two generations ago!

    WTF happened to reading manuals!?

    I read all manuals I get with hardware I buy, go online to fetch and read, PRINT IF I HAVE TO!

    Power Users are a sub-species of homosapiens which is in the greybeard stage.

    Eventually we will drop our current corpus and move on to other energy levels of existence

    Power users will become extinct in the next generation or two

    A bleak future for those left

    Z

    sources

    en.wikipedia.org/wiki/Power_Us

    fireborn.mataroa.blog/blog/the

    #Power #User #Death #Vigil #Eulogy #Abstraction #API #IDE #programming #DNS #networking #File #System #FileSystem #sadness #bleak #future #lisp

  13. The agonizing slow death of the power user

    This is a fascinating article to read. The facts are nailed to the wall in clear and easy to comprehend jargon, even for the non-grey beards

    Some quotes

    Ask a twenty-two-year-old to connect to a remote server via SSH. Ask them to explain what DNS is at a conceptual level. Ask them to tell you the difference between their router’s public IP and the local IP of their laptop. Ask them to open a terminal and list the contents of a directory. These are not advanced topics. Twenty years ago these were things you learned in the first week of any serious engagement with computers. Today they’re exotic knowledge that even a lot of working software developers don’t have, because you can go a long way in modern development without ever leaving the managed abstractions your platform provides.

    And that’s the real damage. It’s not just end users who don’t know this stuff. It’s developers. People who write software for a living who’ve never had to think about what happens between their API call and the response. Who’ve never had to debug something at the network layer. Who’ve never had to read a full stack trace and understand every frame of it. Because the frameworks handle all of that, and the frameworks are good enough, and figuring out how things actually work is optional.

    iOS set the template. Apple shipped a device in 2007 that was, by any reasonable technical measure, a computer. It had a CPU, RAM, persistent storage, a network stack, and a real operating system descended from BSD Unix. By every cultural and legal measure, however, Apple treated it as something else entirely: an appliance that you licensed rather than owned, that ran software only Apple approved, that couldn’t be meaningfully modified, and that communicated only through channels Apple controlled. No filesystem access. No inter-app communication beyond what Apple chose to expose. No background processes without explicit, limited, grudging permission. No ability to install software from any source other than the App Store — which Apple created, controls, taxes at thirty percent, and can pull your app from at any time for any reason with no meaningful appeals process.

    Some facts

    Power User

    A power user is a user of computers, software and other electronic devices who uses advanced features of computer hardware,[1][2][3] operating systems,[4] programs, or websites[5] which are not used by the average user. A power user might not have extensive technical knowledge of the systems they use[6] but is rather characterized by competence or desire to make the most intensive use of computer programs or systems.

    Term use

    The term came into use in the 1980s, as advocates for computing developed special skills for working with or customizing existing hardware and software. Power users knew the best ways to perform common tasks and find advanced information before the arrival of the commercial Internet. On PC platforms, power users read magazines like Byte or PC Magazine, and knew enough about operating systems to create and edit batch files, write short programs in BASIC, and adjust system settings. They tended to customize or "supercharge" existing systems, rather than create new software.[7]

    Notes

    This is systematically done by the factories of technology. I am baffled that a 41 year old litterate person, with secondary school and partial tertiary school, cant tell the difference between an email account, a FB account, a local machine account, a table, notebook and Android phone, from the basic technological perspective. This happened a couple of hours ago, which makes this article very relevant to me.

    This person was born two generations ago!

    WTF happened to reading manuals!?

    I read all manuals I get with hardware I buy, go online to fetch and read, PRINT IF I HAVE TO!

    Power Users are a sub-species of homosapiens which is in the greybeard stage.

    Eventually we will drop our current corpus and move on to other energy levels of existence

    Power users will become extinct in the next generation or two

    A bleak future for those left

    Z

    sources

    en.wikipedia.org/wiki/Power_Us

    fireborn.mataroa.blog/blog/the

    #Power #User #Death #Vigil #Eulogy #Abstraction #API #IDE #programming #DNS #networking #File #System #FileSystem #sadness #bleak #future #lisp

  14. The agonizing slow death of the power user

    This is a fascinating article to read. The facts are nailed to the wall in clear and easy to comprehend jargon, even for the non-grey beards

    Some quotes

    Ask a twenty-two-year-old to connect to a remote server via SSH. Ask them to explain what DNS is at a conceptual level. Ask them to tell you the difference between their router’s public IP and the local IP of their laptop. Ask them to open a terminal and list the contents of a directory. These are not advanced topics. Twenty years ago these were things you learned in the first week of any serious engagement with computers. Today they’re exotic knowledge that even a lot of working software developers don’t have, because you can go a long way in modern development without ever leaving the managed abstractions your platform provides.

    And that’s the real damage. It’s not just end users who don’t know this stuff. It’s developers. People who write software for a living who’ve never had to think about what happens between their API call and the response. Who’ve never had to debug something at the network layer. Who’ve never had to read a full stack trace and understand every frame of it. Because the frameworks handle all of that, and the frameworks are good enough, and figuring out how things actually work is optional.

    iOS set the template. Apple shipped a device in 2007 that was, by any reasonable technical measure, a computer. It had a CPU, RAM, persistent storage, a network stack, and a real operating system descended from BSD Unix. By every cultural and legal measure, however, Apple treated it as something else entirely: an appliance that you licensed rather than owned, that ran software only Apple approved, that couldn’t be meaningfully modified, and that communicated only through channels Apple controlled. No filesystem access. No inter-app communication beyond what Apple chose to expose. No background processes without explicit, limited, grudging permission. No ability to install software from any source other than the App Store — which Apple created, controls, taxes at thirty percent, and can pull your app from at any time for any reason with no meaningful appeals process.

    Some facts

    Power User

    A power user is a user of computers, software and other electronic devices who uses advanced features of computer hardware,[1][2][3] operating systems,[4] programs, or websites[5] which are not used by the average user. A power user might not have extensive technical knowledge of the systems they use[6] but is rather characterized by competence or desire to make the most intensive use of computer programs or systems.

    Term use

    The term came into use in the 1980s, as advocates for computing developed special skills for working with or customizing existing hardware and software. Power users knew the best ways to perform common tasks and find advanced information before the arrival of the commercial Internet. On PC platforms, power users read magazines like Byte or PC Magazine, and knew enough about operating systems to create and edit batch files, write short programs in BASIC, and adjust system settings. They tended to customize or "supercharge" existing systems, rather than create new software.[7]

    Notes

    This is systematically done by the factories of technology. I am baffled that a 41 year old litterate person, with secondary school and partial tertiary school, cant tell the difference between an email account, a FB account, a local machine account, a table, notebook and Android phone, from the basic technological perspective. This happened a couple of hours ago, which makes this article very relevant to me.

    This person was born two generations ago!

    WTF happened to reading manuals!?

    I read all manuals I get with hardware I buy, go online to fetch and read, PRINT IF I HAVE TO!

    Power Users are a sub-species of homosapiens which is in the greybeard stage.

    Eventually we will drop our current corpus and move on to other energy levels of existence

    Power users will become extinct in the next generation or two

    A bleak future for those left

    Z

    sources

    en.wikipedia.org/wiki/Power_Us

    fireborn.mataroa.blog/blog/the

    #Power #User #Death #Vigil #Eulogy #Abstraction #API #IDE #programming #DNS #networking #File #System #FileSystem #sadness #bleak #future #lisp

  15. The agonizing slow death of the power user

    This is a fascinating article to read. The facts are nailed to the wall in clear and easy to comprehend jargon, even for the non-grey beards

    Some quotes

    Ask a twenty-two-year-old to connect to a remote server via SSH. Ask them to explain what DNS is at a conceptual level. Ask them to tell you the difference between their router’s public IP and the local IP of their laptop. Ask them to open a terminal and list the contents of a directory. These are not advanced topics. Twenty years ago these were things you learned in the first week of any serious engagement with computers. Today they’re exotic knowledge that even a lot of working software developers don’t have, because you can go a long way in modern development without ever leaving the managed abstractions your platform provides.

    And that’s the real damage. It’s not just end users who don’t know this stuff. It’s developers. People who write software for a living who’ve never had to think about what happens between their API call and the response. Who’ve never had to debug something at the network layer. Who’ve never had to read a full stack trace and understand every frame of it. Because the frameworks handle all of that, and the frameworks are good enough, and figuring out how things actually work is optional.

    iOS set the template. Apple shipped a device in 2007 that was, by any reasonable technical measure, a computer. It had a CPU, RAM, persistent storage, a network stack, and a real operating system descended from BSD Unix. By every cultural and legal measure, however, Apple treated it as something else entirely: an appliance that you licensed rather than owned, that ran software only Apple approved, that couldn’t be meaningfully modified, and that communicated only through channels Apple controlled. No filesystem access. No inter-app communication beyond what Apple chose to expose. No background processes without explicit, limited, grudging permission. No ability to install software from any source other than the App Store — which Apple created, controls, taxes at thirty percent, and can pull your app from at any time for any reason with no meaningful appeals process.

    Some facts

    Power User

    A power user is a user of computers, software and other electronic devices who uses advanced features of computer hardware,[1][2][3] operating systems,[4] programs, or websites[5] which are not used by the average user. A power user might not have extensive technical knowledge of the systems they use[6] but is rather characterized by competence or desire to make the most intensive use of computer programs or systems.

    Term use

    The term came into use in the 1980s, as advocates for computing developed special skills for working with or customizing existing hardware and software. Power users knew the best ways to perform common tasks and find advanced information before the arrival of the commercial Internet. On PC platforms, power users read magazines like Byte or PC Magazine, and knew enough about operating systems to create and edit batch files, write short programs in BASIC, and adjust system settings. They tended to customize or "supercharge" existing systems, rather than create new software.[7]

    Notes

    This is systematically done by the factories of technology. I am baffled that a 41 year old litterate person, with secondary school and partial tertiary school, cant tell the difference between an email account, a FB account, a local machine account, a table, notebook and Android phone, from the basic technological perspective. This happened a couple of hours ago, which makes this article very relevant to me.

    This person was born two generations ago!

    WTF happened to reading manuals!?

    I read all manuals I get with hardware I buy, go online to fetch and read, PRINT IF I HAVE TO!

    Power Users are a sub-species of homosapiens which is in the greybeard stage.

    Eventually we will drop our current corpus and move on to other energy levels of existence

    Power users will become extinct in the next generation or two

    A bleak future for those left

    Z

    sources

    en.wikipedia.org/wiki/Power_Us

    fireborn.mataroa.blog/blog/the

    #Power #User #Death #Vigil #Eulogy #Abstraction #API #IDE #programming #DNS #networking #File #System #FileSystem #sadness #bleak #future #lisp

  16. Une info comme ça en passant : une installation d'#Eclipse, #IDE #java (mais qui peut servir pour d'autres langages), c'est :

    * 20 003 éléments (fichiers + dossiers) 😱
    * 1 Go occupés sur le disque.

    C'est pas nouveau mais ça me surprend toujours autant !

  17. Une info comme ça en passant : une installation d'#Eclipse, #IDE #java (mais qui peut servir pour d'autres langages), c'est :

    * 20 003 éléments (fichiers + dossiers) 😱
    * 1 Go occupés sur le disque.

    C'est pas nouveau mais ça me surprend toujours autant !

  18. Une info comme ça en passant : une installation d'#Eclipse, #IDE #java (mais qui peut servir pour d'autres langages), c'est :

    * 20 003 éléments (fichiers + dossiers) 😱
    * 1 Go occupés sur le disque.

    C'est pas nouveau mais ça me surprend toujours autant !

  19. Une info comme ça en passant : une installation d'#Eclipse, #IDE #java (mais qui peut servir pour d'autres langages), c'est :

    * 20 003 éléments (fichiers + dossiers) 😱
    * 1 Go occupés sur le disque.

    C'est pas nouveau mais ça me surprend toujours autant !

  20. Une info comme ça en passant : une installation d'#Eclipse, #IDE #java (mais qui peut servir pour d'autres langages), c'est :

    * 20 003 éléments (fichiers + dossiers) 😱
    * 1 Go occupés sur le disque.

    C'est pas nouveau mais ça me surprend toujours autant !

  21. Can you make dolphin an IDE, sure.
    Should you?
    Probably not.

    Can you?

    Sure can.
    #dolphin #ide

  22. Can you make dolphin an IDE, sure.
    Should you?
    Probably not.

    Can you?

    Sure can.
    #dolphin #ide

  23. Can you make dolphin an IDE, sure.
    Should you?
    Probably not.

    Can you?

    Sure can.
    #dolphin #ide

  24. Can you make dolphin an IDE, sure.
    Should you?
    Probably not.

    Can you?

    Sure can.
    #dolphin #ide

  25. Can you make dolphin an IDE, sure.
    Should you?
    Probably not.

    Can you?

    Sure can.
    #dolphin #ide