#softwarearcheology — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #softwarearcheology, aggregated by home.social.
-
@0xced @santi @RogueAmoeba Panic.com with Transmit et al for Mac OS X:
https://help.panic.com/general/os-compatibility/
And for Mac 68k:
-
@0xced @santi @RogueAmoeba Panic.com with Transmit et al for Mac OS X:
https://help.panic.com/general/os-compatibility/
And for Mac 68k:
-
@0xced @santi @RogueAmoeba Panic.com with Transmit et al for Mac OS X:
https://help.panic.com/general/os-compatibility/
And for Mac 68k:
-
@0xced @santi @RogueAmoeba Panic.com with Transmit et al for Mac OS X:
https://help.panic.com/general/os-compatibility/
And for Mac 68k:
-
@0xced @santi @RogueAmoeba Panic.com with Transmit et al for Mac OS X:
https://help.panic.com/general/os-compatibility/
And for Mac 68k:
-
I just read about MUSH (Microsoft User Shell) – which is the keyboard-based pre-pulldown menu system that existed in Multiplan, Word or XTree – and early drafts of Microsoft Interface Manager, an text UI precursor of Windows which resembled DOSShell from MS-DOS 4, on the website of @nina_kali_nina . I remembered there actually was a Visual Shell, vsh in Microsoft Xenix (their Unix OS). Sadly, browsing was not very intuitive … #softwarearcheology #unix #unixshells
-
I just read about MUSH (Microsoft User Shell) – which is the keyboard-based pre-pulldown menu system that existed in Multiplan, Word or XTree – and early drafts of Microsoft Interface Manager, an text UI precursor of Windows which resembled DOSShell from MS-DOS 4, on the website of @nina_kali_nina . I remembered there actually was a Visual Shell, vsh in Microsoft Xenix (their Unix OS). Sadly, browsing was not very intuitive … #softwarearcheology #unix #unixshells
-
I just read about MUSH (Microsoft User Shell) – which is the keyboard-based pre-pulldown menu system that existed in Multiplan, Word or XTree – and early drafts of Microsoft Interface Manager, an text UI precursor of Windows which resembled DOSShell from MS-DOS 4, on the website of @nina_kali_nina . I remembered there actually was a Visual Shell, vsh in Microsoft Xenix (their Unix OS). Sadly, browsing was not very intuitive … #softwarearcheology #unix #unixshells
-
I just read about MUSH (Microsoft User Shell) – which is the keyboard-based pre-pulldown menu system that existed in Multiplan, Word or XTree – and early drafts of Microsoft Interface Manager, an text UI precursor of Windows which resembled DOSShell from MS-DOS 4, on the website of @nina_kali_nina . I remembered there actually was a Visual Shell, vsh in Microsoft Xenix (their Unix OS). Sadly, browsing was not very intuitive … #softwarearcheology #unix #unixshells
-
I just read about MUSH (Microsoft User Shell) – which is the keyboard-based pre-pulldown menu system that existed in Multiplan, Word or XTree – and early drafts of Microsoft Interface Manager, an text UI precursor of Windows which resembled DOSShell from MS-DOS 4, on the website of @nina_kali_nina . I remembered there actually was a Visual Shell, vsh in Microsoft Xenix (their Unix OS). Sadly, browsing was not very intuitive … #softwarearcheology #unix #unixshells
-
If you are interested in the proper usage and concepts of #subversion (or #svn) I can highly recommend this book. Pragmatic Version Control using Subversion, by Mike Mason.
I was digging into version control history during the holidays, as I started using #jj aka #jujutsuvcs in addition to git and wanted to know more about the concepts it is designed with. I had the luck of being able to start my version control life with git, so I never worked with Subversion a lot (some people might say fortunately). But as many people seem to hold it in high regard, I wanted to understand why.
This books takes you through all you need to know to use it. As an "normal being" just using it. Handling normal things, releases, branches. But also from an administration side, handling and organizing repositories. Backing them up. Splitting and uniting them.
And all of that written in a very enjoyable way.
#vcs #MikeMason #PragmaticVersionControl #softwarearcheology
-
If you are interested in the proper usage and concepts of #subversion (or #svn) I can highly recommend this book. Pragmatic Version Control using Subversion, by Mike Mason.
I was digging into version control history during the holidays, as I started using #jj aka #jujutsuvcs in addition to git and wanted to know more about the concepts it is designed with. I had the luck of being able to start my version control life with git, so I never worked with Subversion a lot (some people might say fortunately). But as many people seem to hold it in high regard, I wanted to understand why.
This books takes you through all you need to know to use it. As an "normal being" just using it. Handling normal things, releases, branches. But also from an administration side, handling and organizing repositories. Backing them up. Splitting and uniting them.
And all of that written in a very enjoyable way.
#vcs #MikeMason #PragmaticVersionControl #softwarearcheology
-
If you are interested in the proper usage and concepts of #subversion (or #svn) I can highly recommend this book. Pragmatic Version Control using Subversion, by Mike Mason.
I was digging into version control history during the holidays, as I started using #jj aka #jujutsuvcs in addition to git and wanted to know more about the concepts it is designed with. I had the luck of being able to start my version control life with git, so I never worked with Subversion a lot (some people might say fortunately). But as many people seem to hold it in high regard, I wanted to understand why.
This books takes you through all you need to know to use it. As an "normal being" just using it. Handling normal things, releases, branches. But also from an administration side, handling and organizing repositories. Backing them up. Splitting and uniting them.
And all of that written in a very enjoyable way.
#vcs #MikeMason #PragmaticVersionControl #softwarearcheology
-
If you are interested in the proper usage and concepts of #subversion (or #svn) I can highly recommend this book. Pragmatic Version Control using Subversion, by Mike Mason.
I was digging into version control history during the holidays, as I started using #jj aka #jujutsuvcs in addition to git and wanted to know more about the concepts it is designed with. I had the luck of being able to start my version control life with git, so I never worked with Subversion a lot (some people might say fortunately). But as many people seem to hold it in high regard, I wanted to understand why.
This books takes you through all you need to know to use it. As an "normal being" just using it. Handling normal things, releases, branches. But also from an administration side, handling and organizing repositories. Backing them up. Splitting and uniting them.
And all of that written in a very enjoyable way.
#vcs #MikeMason #PragmaticVersionControl #softwarearcheology
-
If you are interested in the proper usage and concepts of #subversion (or #svn) I can highly recommend this book. Pragmatic Version Control using Subversion, by Mike Mason.
I was digging into version control history during the holidays, as I started using #jj aka #jujutsuvcs in addition to git and wanted to know more about the concepts it is designed with. I had the luck of being able to start my version control life with git, so I never worked with Subversion a lot (some people might say fortunately). But as many people seem to hold it in high regard, I wanted to understand why.
This books takes you through all you need to know to use it. As an "normal being" just using it. Handling normal things, releases, branches. But also from an administration side, handling and organizing repositories. Backing them up. Splitting and uniting them.
And all of that written in a very enjoyable way.
#vcs #MikeMason #PragmaticVersionControl #softwarearcheology
-
As one does between the years, I have started digging into #subversion (the version control system) to learn more about its concepts. Because, why not? At least it helps me to be grateful for the ease of use I have with #git (sorry subversion...).
In case you want to have a look, I built a #vagrant setup to easily play around with Subversion:
https://github.com/johanneskastl/subversion_vagrant_libvirt_ansible
As I am on a reading spree, #Mercurial will be next. And no, before you ask, I will not get into CVS after that...
#svn #vcs #versioncontrol #softwarearcheology #oldiesbutgoldies
-
As one does between the years, I have started digging into #subversion (the version control system) to learn more about its concepts. Because, why not? At least it helps me to be grateful for the ease of use I have with #git (sorry subversion...).
In case you want to have a look, I built a #vagrant setup to easily play around with Subversion:
https://github.com/johanneskastl/subversion_vagrant_libvirt_ansible
As I am on a reading spree, #Mercurial will be next. And no, before you ask, I will not get into CVS after that...
#svn #vcs #versioncontrol #softwarearcheology #oldiesbutgoldies
-
As one does between the years, I have started digging into #subversion (the version control system) to learn more about its concepts. Because, why not? At least it helps me to be grateful for the ease of use I have with #git (sorry subversion...).
In case you want to have a look, I built a #vagrant setup to easily play around with Subversion:
https://github.com/johanneskastl/subversion_vagrant_libvirt_ansible
As I am on a reading spree, #Mercurial will be next. And no, before you ask, I will not get into CVS after that...
#svn #vcs #versioncontrol #softwarearcheology #oldiesbutgoldies
-
As one does between the years, I have started digging into #subversion (the version control system) to learn more about its concepts. Because, why not? At least it helps me to be grateful for the ease of use I have with #git (sorry subversion...).
In case you want to have a look, I built a #vagrant setup to easily play around with Subversion:
https://github.com/johanneskastl/subversion_vagrant_libvirt_ansible
As I am on a reading spree, #Mercurial will be next. And no, before you ask, I will not get into CVS after that...
#svn #vcs #versioncontrol #softwarearcheology #oldiesbutgoldies
-
As one does between the years, I have started digging into #subversion (the version control system) to learn more about its concepts. Because, why not? At least it helps me to be grateful for the ease of use I have with #git (sorry subversion...).
In case you want to have a look, I built a #vagrant setup to easily play around with Subversion:
https://github.com/johanneskastl/subversion_vagrant_libvirt_ansible
As I am on a reading spree, #Mercurial will be next. And no, before you ask, I will not get into CVS after that...
#svn #vcs #versioncontrol #softwarearcheology #oldiesbutgoldies
-
I really enjoyed this post by @chadaustin where he goes deep into the history (and related mistakes) of introducing 8-bit and 24-bit support in SGR sequences. Fantastic blast to the past!
-
I really enjoyed this post by @chadaustin where he goes deep into the history (and related mistakes) of introducing 8-bit and 24-bit support in SGR sequences. Fantastic blast to the past!
-
I really enjoyed this post by @chadaustin where he goes deep into the history (and related mistakes) of introducing 8-bit and 24-bit support in SGR sequences. Fantastic blast to the past!
-
I really enjoyed this post by @chadaustin where he goes deep into the history (and related mistakes) of introducing 8-bit and 24-bit support in SGR sequences. Fantastic blast to the past!
-
I really enjoyed this post by @chadaustin where he goes deep into the history (and related mistakes) of introducing 8-bit and 24-bit support in SGR sequences. Fantastic blast to the past!
-
I was actually somewhat aware f the coinciding nature of it that I suspected the old NEWS files would not mention it. So I think we would find this in the very early tarballs of R may before 1.0.0 or even 0.60.0 when it became GNU R. I think the first one I ever laid hands on was 0.64.0 or so and IIRC it had data.frame. Tagging @rsbivand who will likely know...
-
I was actually somewhat aware f the coinciding nature of it that I suspected the old NEWS files would not mention it. So I think we would find this in the very early tarballs of R may before 1.0.0 or even 0.60.0 when it became GNU R. I think the first one I ever laid hands on was 0.64.0 or so and IIRC it had data.frame. Tagging @rsbivand who will likely know...
-
I was actually somewhat aware f the coinciding nature of it that I suspected the old NEWS files would not mention it. So I think we would find this in the very early tarballs of R may before 1.0.0 or even 0.60.0 when it became GNU R. I think the first one I ever laid hands on was 0.64.0 or so and IIRC it had data.frame. Tagging @rsbivand who will likely know...
-
I was actually somewhat aware f the coinciding nature of it that I suspected the old NEWS files would not mention it. So I think we would find this in the very early tarballs of R may before 1.0.0 or even 0.60.0 when it became GNU R. I think the first one I ever laid hands on was 0.64.0 or so and IIRC it had data.frame. Tagging @rsbivand who will likely know...
-
I was actually somewhat aware f the coinciding nature of it that I suspected the old NEWS files would not mention it. So I think we would find this in the very early tarballs of R may before 1.0.0 or even 0.60.0 when it became GNU R. I think the first one I ever laid hands on was 0.64.0 or so and IIRC it had data.frame. Tagging @rsbivand who will likely know...
-
Yesterday, I found (and fixed) an at least 37 years old bug in #IRAF CL. It appeared already in the first IRAF version where we have source code (2.8). If you have an older version, please let me know! #SoftwareArcheology
-
Yesterday, I found (and fixed) an at least 37 years old bug in #IRAF CL. It appeared already in the first IRAF version where we have source code (2.8). If you have an older version, please let me know! #SoftwareArcheology
-
Yesterday, I found (and fixed) an at least 37 years old bug in #IRAF CL. It appeared already in the first IRAF version where we have source code (2.8). If you have an older version, please let me know! #SoftwareArcheology
-
Yesterday, I found (and fixed) an at least 37 years old bug in #IRAF CL. It appeared already in the first IRAF version where we have source code (2.8). If you have an older version, please let me know! #SoftwareArcheology
-
¿Cómo yo no estaba siguiendo esa hashtag (y #SoftwareArcheology)?
-
¿Cómo yo no estaba siguiendo esa hashtag (y #SoftwareArcheology)?
-
¿Cómo yo no estaba siguiendo esa hashtag (y #SoftwareArcheology)?
-
¿Cómo yo no estaba siguiendo esa hashtag (y #SoftwareArcheology)?
-
- Because I was wanting to borrow some code from it, I fixed bitrot in https://git.lukeshu.com/2git/cvtutf-make/ which is the scripts that make the https://git.lukeshu.com/2git/cvtutf repo, which is the history of the CVTUTF #Unicode library. #SoftwareArcheology
-
- Because I was wanting to borrow some code from it, I fixed bitrot in https://git.lukeshu.com/2git/cvtutf-make/ which is the scripts that make the https://git.lukeshu.com/2git/cvtutf repo, which is the history of the CVTUTF #Unicode library. #SoftwareArcheology
-
I got a 15-year-old Blender to run, thanks to @jix! \o/ I'm working on a writeup on how we made this happen! #eh20 #softwarearcheology
-
I got a 15-year-old Blender to run, thanks to @jix! \o/ I'm working on a writeup on how we made this happen! #eh20 #softwarearcheology
-
I got a 15-year-old Blender to run, thanks to @jix! \o/ I'm working on a writeup on how we made this happen! #eh20 #softwarearcheology
-
I got a 15-year-old Blender to run, thanks to @jix! \o/ I'm working on a writeup on how we made this happen! #eh20 #softwarearcheology
-
I got a 15-year-old Blender to run, thanks to @jix! \o/ I'm working on a writeup on how we made this happen! #eh20 #softwarearcheology
-
Remarkable I found this line in some really old #Ruby code I apparently wrote … once upon a time…
$: << "C:/Stephan/Programmierung/Ruby"
I use a Mac since 2006… Guess I haven't touched this stuff in a while. #SoftwareArcheology