Earlier quoted context omitted.
It’s not useless because it’s able to accomplish the same without having to memorize yet another syntax trick. - Someone who knows the trick
It's a basic shell feature that every terminal user should know from day 1. Hardly a "trick".
cat mario.nes | nc play-nes.org 4444
51–60 of 76 posts
Re: cat mario.nes | nc play-nes.org 4444
#52> let cart = Cartridge::blow_dust("path/to/rom.nes")?; I chuckled.
That's like those objected-oriented programming examples you get in college, from professors who learned in the 90s and literally think in terms of "modelling" real objects with OOP.
Re: cat mario.nes | nc play-nes.org 4444
#53Earlier quoted context omitted.
Isn't this the regular story of Google though? "Let me give a half effort on X product. Oh, see, nobody likes it. Well, guess I'll go ahead and shutter it." It's a shame that products with so much potential have all the resources put into them wasted with their behavior.
I've seen it mentioned on here a lot that promotions/career stability inside google are heavily based around launching new products, and maintaining existing ones is kind of a dead end. Seems like the outcome reflects the incentives.
Re: cat mario.nes | nc play-nes.org 4444
#54Re: cat mario.nes | nc play-nes.org 4444
#55Earlier quoted context omitted.
It requires forethought in many cases. Cat-initiated pipelines can be built iteratively in a natural fashion.
What's natural about cat on only one file? > Briefly, here's the collected wisdom on using cat: > The purpose of cat is to concatenate (or "catenate") files. If it's only one file, concatenating it with nothing at all is a waste of time, and costs you a process. The fact that the same thread ("but but but, I think it's cleaner / nicer / not that much of a waste / my privelege to waste processes!") springs up virtuall…
Despite the dismissive tone of the article you linked, if the overhead of one single process was remotely relevant, shell wouldn't be a good fit.
Re: cat mario.nes | nc play-nes.org 4444
#56Earlier quoted context omitted.
What's natural about cat on only one file? > Briefly, here's the collected wisdom on using cat: > The purpose of cat is to concatenate (or "catenate") files. If it's only one file, concatenating it with nothing at all is a waste of time, and costs you a process. The fact that the same thread ("but but but, I think it's cleaner / nicer / not that much of a waste / my privelege to waste processes!") springs up virtuall…
Of course it's reasonable to use cat on one file. Why should it work for all 𝑛≥2 files, but suddenly fail at 𝑛=1? Despite the dismissive tone of the article you linked, if the overhead of one single process was remotely relevant, shell wouldn't be a good fit.
Re: cat mario.nes | nc play-nes.org 4444
#57Earlier quoted context omitted.
I was sincerely hoping I wouldn't be the first person to notice the useless use of cat. https://en.m.wikipedia.org/wiki/Cat_(Unix)#Useless_use_of_ca...
Hopefully this[0] should be the last word on "useless" uses of cat > When I offer a pipeline as a solution I expect it to be reusable. It is quite likely that a pipeline would be added at the end of or spliced into another pipeline. In that case having a file argument to grep screws up reusability, and quite possibly do so silently without an error message if the file argument exists. I. e. `grep foo xyz | grep bar x…
See Jonathan Leffler's comment on SO (also demonstrated by the the top-level parent comment here):
> As noted in the answer by kojiro, it is perfectly possible and legal to start the pipeline with `output` and `output`.
Re: cat mario.nes | nc play-nes.org 4444
#58Earlier quoted context omitted.
It’s not useless because it’s able to accomplish the same without having to memorize yet another syntax trick. - Someone who knows the trick
It's a basic shell feature that every terminal user should know from day 1. Hardly a "trick".
I have more important things to worry about than making the line less readable and less maintainable
Re: cat mario.nes | nc play-nes.org 4444
#59ApplePy experimented with providing a client-server model years ago for the 6502: https://github.com/jtauber/applepy It's great to see somebody picking up the idea again and extending it. It's a cool idea. Lots of possibilities for fun RPC projects with distributed processing. Remotely accessible 80-column cards and custom mappers FTW, eh? Good reminder that projects are meant to be implemented.
(Yes, this isn't entirely serious, but people could and did make use of it)
Re: cat mario.nes | nc play-nes.org 4444
#60> let cart = Cartridge::blow_dust("path/to/rom.nes")?; I chuckled.
That's like those objected-oriented programming examples you get in college, from professors who learned in the 90s and literally think in terms of "modelling" real objects with OOP.