3 ms·
> /usr/local/bin is an implementation detail from an OS nobody has used for decades. Are you taking the piss? Should we also remove SOCKET's because they were
by dijit 6y ago
> /usr/local/bin is an implementation detail from an OS nobody has used for decades.
Are you taking the piss? Should we also remove SOCKET's because they were introduced in that same OS?
It should be noted that _EVERY_ modern operating system implements a "path" system, even the ones that are very divergent.
- maweki 6y agoAlso, Namespacing and search paths are a concept in every environment where people name things. Be it the filesystem or a programming language itself. Even in normal Life, when identifying people or things, we have concepts of this everywhere. How can people see that as pointless?
- TeMPOraL 6y agoAnd environmental variables, too. You can see the same pattern: process :: function path :: namespacing command line argument :: function argument environmental variable :: dynamically bound variable (Ok, that last concept may be alien for non-Lisp people.)
- user-the-name 6y agoShould we remove sockets? Possibly. We could most likely design a better API today.
- kaoD 6y agoGo ahead and do so, please. You keep saying that things could be better but show no counterexample. Lead the change or stop whining. Nobody is going to do the job for you if they're satisfied by their current tools, especially if they think you're wrong. Do it and prove everyone else wrong. If everyone thinks the status quo can't be improved, but you're enlightened, it's your chance to turn your "likely can be improved" into reality. The non-programmer user base is immense. You can get rich by selling your alternative.
- AnIdiotOnTheNet 6y ago> Lead the change or stop whining. Ugh. Look, just because they themselves have not attempted to create something better doesn't mean that their criticisms are invalid.
- robertlagrant 6y agoThey are if they are nonspecific. Saying "X is bad" requires a counterexample, at least.
- AnIdiotOnTheNet 6y agoThey gave counter examples, specifically "we didn't need this in the past, therefore it is not actually necessary". Which is entirely correct. We do things the way we do things largely for historical reasons and beginner users are right to point that out.
- kaoD 6y agoI was there in the past and the tools are really not comparable. I just inserted a floppy disk and did A: then TP.EXE (which was just as arcane as knowing $PATH) but do I really want to work on Turbo Pascal in MS-DOS? Of course complexity skyrocketed! That's not a counterexample because beginners have contemporary expectations. There are simpler alternatives that just work. Why do beginners want to use Node.js locally then? > We do things the way we do things largely for historical reasons Nobody challenged that. The question is: is the alternative better or just a different (but equally arcane) set of quirks? If you're not using $PATH you'd be using an analogue system to solve the same problem, and you'd lose portability with current OSes. Sounds like NIH to me.
- AnIdiotOnTheNet 6y ago> I was there in the past and the tools are really not comparable. I just inserted a floppy disk and did D: then TP.EXE but do I really want to work on Turbo Pascal in MS-DOS? Of course complexity skyrocketed! Did it do so for reasons that are still relevant today, is the question. > That's not a counterexample because beginners have contemporary expectations. Alright I'll present a counterexample: Lazarus. You download it and install it [0], then you run it and make programs. It has a WYSIWYG GUI builder and produces stand-alone executables for multiple operating systems. There is no complicated build environment to set up. > If you're not using $PATH you'd be using an analogue system to solve the same problem, and you'd lose portability with current OSes. I contend that the problem $PATH solves has nothing to do with programming. $PATH is a solution for finding programs when you type their name on the commandline, nothing more. Windows and Mac programs don't really use or need it for the vast majority of tasks. Programming does not fundamentally require $PATH. > Sounds like NIH to me. And arguments that understanding $PATH is somehow a necessary pre-requisite to get into programming sound like needless complexity fetishism to me. [0] I would argue that the installation step here is also unnecessary as there is no reason Lazarus cannot operate as a stand-alone self-contained portable folder other than the developers insistence on hardcoded paths.
- aspaceman 6y ago"<CR><RET> is an implementation detail from an OS nobody has used for decades" Yeah they're taking the piss. You can make the same argument about GUI tools too. We're gonna be dealing with "implementation details" for awhile lol. This thread is wild. Makes me understand why all the juniors I work with suck so much.