What I thought was most interesting was the statement at the very end: "The poetic nature of writing in grievance in Arabic is much more effective than in English." Differences between languages are so interesting to me. Anyone here know Arabic and feel the same way as the author? What makes Arabic different in that sense?
I just watched the film about Spotify "The Playlist". It took a few minutes before I picked up that it was dubbed. I switched back to Norwegian with English subtitles and the film became instantly enjoyable. All languages hold a beauty.
I think almost all multilingual people would agree that writing cordially is easier in their native language - whatever that language may be. Expressing heartfelt messages in the language you spoke when developing your identity and emotional maturity is more about just that, rather than what the language happens to be.
Pretty much all APIs at Amazon , internal and external, are either defined using this or its precursor and then per-language clients and server stub implementations are autogenerated based on the model. That’s true of boto3. Not sure how much the of CLI is autogenerated, but the CLI uses boto(core) under the hood so it’s involved one way or the other.
It is! I’ve been watching a bunch of Asian TV shows lately and I’ve seen that phrase crop up in both Thai and Taiwanese shows. I had the same question so I asked a friend who’s Thai about it. She said it’s equivalent to “I should get going”, “I’m going to head out”, or something of that nature.
Whenever I see posts about hiring, the comments here tend to land at the "this is bad advice" end of the spectrum. Does anyone have any resources that give good advice? Or is hiring such an unsolved problem that we don't even have generally applicable guidelines, however vague they may be?
I see your point, but I think it's increasingly rare to find sysadmins who haven't been exposed to OOP. A little programming has become less and less optional to be successful at the job. At my job, I'm pretty sure even the entry level helpdesk staff have been exposed to a bit of Java, C#, or the like.
When powershell comes up, someone always gripes about how they can't do this or that like they can in bash. I'm not going to deny that grep is nicer to use that the powershell equivalent (Select-String). But you don't configure Windows and other software in the Microsoft ecosystem by messing around with text. For example, if you had a new user and you wanted to set up an account, email address, and phone number (so AD, Exchange, and Lync/Skype for Business in Microsoft land), it wouldn't just be hard using something like Cygwin, it would probably be impossible. There is just no way to talk to those programs text streams or config files.
I guess what I always want to know when people complain about powershell is what they were actually trying to do. I think it's an excellent tool for system administration in a Microsoft environment. When you start moving away from that use case, it gets less and less useful.
the problem with powershell is that it is incredibly stupid if you're not on a full windows stack (desktops, servers and near enough to everything inbetween) and running the most recent version of windows (ever tried getting winrm installed and reliably working on a 2008 box?)
perhaps if they were not too opposed early on to horrible open source things and just one of the languages that already fit fairly well in that area (python for example) they wouldn't have had to go out of their way to make pretty shitty hacks (i really wonder if anyone in the powershell\winrm team did any testing or development with the machines more than 10 metres away)
Yeah, PS remoting is basically a no-go before server 2012, and even then it's just barely functional enough to be occasionally useful. They're planning on adding SSH support though, so I'm cautiously optimistic.
I don't think something like Python would have been a good choice to use instead of PS. While I'm sympathetic to the complaint that PS is more of a programming language than a shell, that's even more true of Python. I use PS as a shell far more often than I use it for complicated scripting, and as much as I like Python, I just can't see using it as a shell.
PowerShell has "providers" that let you interact with things as if they were a file system, which is what is going on in your example. I agree that it's not a great way to expose IIS settings.
The other place you see providers in use is when you use PS to edit the registry, but it's HKLM:\ (or whatever other hive) instead of IIS:\, and it makes a lot more sense there since people naturally think of the registry in a filesystem sort of way.
Yeah, that really bothered me coming from bash. I agree it's not as good from a discoverability perspective. Having said that, it's not the kind of thing that has continued to bother me over time. I've gotten used to it.
