3 ms·

> Working with hierarchies of objects is a lot more complicated. Compared to a flat list of related strings? No, its not. Its like saying that categorisation i

> Working with hierarchies of objects is a lot more complicated. Compared to a flat list of related strings? No, its not. Its like saying that categorisation is worst then keeping everything in large bin. > Comparing things becomes a nightmare. Comparing objects deeply can be done in one line. If anything is nightmare, its people who judge without RTFM. > So, it's OK to use it as a gimmick I am amazed about lack of recognition on amount of work that MS and community have put into it (during two decades of gimmicking) :)

crabbone 4y ago
> I am amazed about lack of recognition on amount of work that MS and community I'm amazed by how irrelevant all MS products are without a fault when it comes to catering to people who are on the more experienced and knowledgeable end of the spectrum. Their products seem to always completely misunderstand the target audience, but bruteforce their way in nevertheless due to the huge investment in marketing and "grease" to secure deals. In a way, it's very similar to that last showing of Tesla trucks, where it became apparent to truck drivers that whoever designed them simply didn't know what truck drivers value or need. So, Tesla trucks are no joke to design. Definitely, a lot of effort went into making them, and yet they fail on very simple stuff like having enough room to put your dirty shoes away. In a very similar way, every product by MS I ever touched was usually decently invested in (outside of things like MS Outlook, or MS Word original file format etc.), decently tested, decently documented and... completely irrelevant in any context I could think of applying it. I use various shells daily for a huge number of tasks. My shell history just for a single terminal may be couple hundreds lines a day (but usually I have several tmux sessions in several ascii-term buffers in Emacs open with typically 6-10 buffers per tmux session). I do write some reusable Shell code too, but less often. As a general infra / system person I have to touch every aspect of the system, be it storage, virtualization, networking, user management... and there simply isn't any place in any of that where I'd say "well, PowerShell seems like a good fit". There's always an obvious way to do things better without it. That's not to say I don't want my tools to improve -- far from it. There are plenty of things that Unix Shell gets wrong. None of those problems are addressed by PowerShell. Like I said, it's a gimmick for MS Windows users. Maybe it makes the experience of using MS Windows more palatable -- I don't even want to know. On a very rare case, like when a relative asks me to help them with their computer, I see the horror show that MS Windows is, and I want none of that stuff.
crabbone 4y ago
> Comparing objects deeply can be done in one line. This deserves a good laugh. How do they keep making programmers so naive every new iteration? Seriously? Some famous Java dude wrote a whole book about how Java got object comparison wrong. And how seven or so versions and twenty or so years later they still had problems with sorting because of that stupid dysfunctional comparison. And you solved it. In a single line? I sense I might be talking to the next Turing award nominee!

crabbone 4y ago

> I am amazed about lack of recognition on amount of work that MS and community I'm amazed by how irrelevant all MS products are without a fault when it comes to catering to people who are on the more experienced and knowledgeable end of the spectrum. Their products seem to always completely misunderstand the target audience, but bruteforce their way in nevertheless due to the huge investment in marketing and "grease" to secure deals. In a way, it's very similar to that last showing of Tesla trucks, where it became apparent to truck drivers that whoever designed them simply didn't know what truck drivers value or need. So, Tesla trucks are no joke to design. Definitely, a lot of effort went into making them, and yet they fail on very simple stuff like having enough room to put your dirty shoes away. In a very similar way, every product by MS I ever touched was usually decently invested in (outside of things like MS Outlook, or MS Word original file format etc.), decently tested, decently documented and... completely irrelevant in any context I could think of applying it. I use various shells daily for a huge number of tasks. My shell history just for a single terminal may be couple hundreds lines a day (but usually I have several tmux sessions in several ascii-term buffers in Emacs open with typically 6-10 buffers per tmux session). I do write some reusable Shell code too, but less often. As a general infra / system person I have to touch every aspect of the system, be it storage, virtualization, networking, user management... and there simply isn't any place in any of that where I'd say "well, PowerShell seems like a good fit". There's always an obvious way to do things better without it. That's not to say I don't want my tools to improve -- far from it. There are plenty of things that Unix Shell gets wrong. None of those problems are addressed by PowerShell. Like I said, it's a gimmick for MS Windows users. Maybe it makes the experience of using MS Windows more palatable -- I don't even want to know. On a very rare case, like when a relative asks me to help them with their computer, I see the horror show that MS Windows is, and I want none of that stuff.

crabbone 4y ago

> Comparing objects deeply can be done in one line. This deserves a good laugh. How do they keep making programmers so naive every new iteration? Seriously? Some famous Java dude wrote a whole book about how Java got object comparison wrong. And how seven or so versions and twenty or so years later they still had problems with sorting because of that stupid dysfunctional comparison. And you solved it. In a single line? I sense I might be talking to the next Turing award nominee!