1,092 karma · joined January 20, 2016
As for your point about specific features, I plan to treat this as a STS-esque project. TLDR: de-emphasize linear models of technology development. Besides, I feel that the history itself would be useful to other practitioners.
This is also one of the bits I’m having difficulty with — what was it like to actually use these systems? For instance, how did one even maneuver the process of posting on CompuServe or on Usenet?
This design doesn’t preclude the usage of additional information in the commit blob that isn’t used to compute the hash.
(Think for example how file access times do not affect its hash)
(Not sure if such a field already exists in the commit blob)
In fact, I don’t see why the ability to have a good standard of living should be predicated on your profession in the first place.
The fact that engineering training is… unpaid as you say seems to put people who cannot afford to not make money for rent, food, etc. at a clear disadvantage. Those already rich (and able to afford unpaid training) would just get richer if they are paid more than an “untrained” worker.
It’s important to note, however, that sshfs has been archived by its creator. What this entails with regard to the future of the project is uncertain though.
In my opinion, people who would like to study engineering would do so not so because of what they are paid (the situation today), but because of their genuine interest.
On further reflection, it seems ludicrous to believe that that hardest professions are the most paid. The average CS job pays obscenely well, but is relatively trivial. Primary healthcare providers, essential services workers and so on are severely underpaid.
I’m going to get this stuff sorted out beforehand before working anywhere in the future.
`import {foo} from ‘bar’;`
This makes reading code really really hard as I can’t tell where some symbol is coming from.
There also seems to be a general aversion against using classes to model types. Instead we have a host of functions that manipulate JSON/dataclasses, which means business logic is scattered around 10 different places!
In fact, you never have to call any binaries specifically; just do it through code and everything should link at compile-time and become one big binary.