Not anymore, the US Supreme Court struck down the 1992 law prohibiting sports betting at a federal level [1]
Now, it’s up to each state to decide if and how they want to legalize it. New Jersey is actually the reason this went to the Supreme Court, and you can now take wagers within NJ if you have a physical operation in Atlantic City [2]
I think it's your incorrect assumption that bash's popularity is due to it being a "fetish" for anyone. There aren't alternatives that are both better and more available / cross-platform / standard.
I agree its a crappy language, but remember, it's a shell, not a language. It serves a different purpose than being good for pure code, so saying something like "<your favorite scripting language here> is better than bash" doesn't hold a whole lot of water. It is way better than batch though.
"<your favorite scripting language here> is better than bash at the kind of tasks that bash is used for" would be a pretty substantial claim, though. (Unfortunately, it's almost never the claim that people are making. "X is better than bash at creating UIs/database lookups/OO/web programming"? Yeah, of course it is. Water's wet, too.)
Until your enterprise security people have a fit at something like PowerSploit [1] existing and turn on AllSigned via Group Policy. Then it's pretty much impossible to use PowerShell - edit, sign, test, edit, sign is quite painful with the current tooling (and that's even if you're "trusted" enough to get the codesigning cert). Not to mention that some of the scripts that Visual Studio uses aren't signed!
PowerShell took everything that was great about .NET and combined it with everything that was terrible about Bash. So we have, yet again, a difficult to understand language for shell scripting.
Why is it bad? I've been able to write some pretty great PS scripts to automate tasks. It's easier than firing up Visual Studio and writing a C# program I'd need to recompile if I ever want to change it.
It's very powerful but the syntax is step back 20 years:
If ($Number -gt 0)
That's just one example. There is a lot of really confusing stuff in powershell that's entirely unnecessary. There were going for some kind of Bash-shell familiarity which, oddly enough, most Windows developers don't even have.
The shell is a mess of symbols making any sane programming language impossible. Instead of perhaps rethinking the "mess of symbols" issue they ruined the language instead.
And PowerShell is an awful shell; it's great for script automation of windows, but as a shell, just no. Microsoft recognizes this, it's the reason a full Ubuntu bash shell is available in Windows 10.
The problem with PowerShell is its syntax, not the extra features of the shell environment. Trying to expose the .Net runtime to the command line is an admirable goal for a scripting language, not a shell. It comes down to this, PowerShell is a catherderal, bash and tools are a bizarre, and that's why they win IMHO. Personally the best shell for any Windows box is to install cygwin and treat it like a Linux box, and on Windows 10 just install Ubuntu and have a real Linux shell.
Windows servers are a dying breed and Microsoft knows it, they've lost that war and are quickly porting everything they can to run on Linux including their .Net runtime and Sql Server; they know they've lost the war, it's only a matter of time.
Most of my big complaints about syntax are related to the shell-ness of PowerShell. For example, when comparing things, I really want to use '<' and '>' rather than -le and -gt.
Generally though, the syntax is different but once you learn it, it's mostly fine and sometimes the text-based nature of Unix commands means you have to do a lot more reg-exing.
My point still stands. They are different but (IMHO) both excellent. Ubuntu on Windows may eventually reach parity with PowerShell but until then, PowerShell is worth knowing (especially if you follow Microsoft's advice and run servers without the GUI installed).
I agree it's worth knowing, I just don't like it. My prefferred avenue will be porting all .Net stuff to Linux servers and just getting rid of all Windows servers as it becomes possible. .Net is great, C# is great, Windows isn't and I'm glad to see Microsoft's new CEO isn't blind to that reality.
Really? I though PowerShell was designed primarily to replace cmd. Surely Windows people use actual programming languages for the majority of tasks with PowerShell/cmd for smaller scripting tasks.
Not really. The Linksys WRT1900AC has a 1.2ghz dual core CPU as well.
At some point you need a general purpose CPU to run everything and it's not hard to just throw an ARM SoC at it which is going to be in the 1-1.5ghz range and dual core because that's just what low-end is now.
The CPU is inline with top of the line routers these days (e.g. Asus RT-AC87U is a 1Ghz dual core). 1+Ghz dual core CPUs are really cheap these days.
The RAM is about 4x what other routers are packing but the cost difference between a 1Gbit chip and 4Gbit chip is a few dollars. Prices have been plummeting this year and 8Gbit chips replaced 4Gbit as the new hotness. Not to mention DDR4 rolling out so there might just be dumping going on that makes adding 1GB of RAM a non issue.
Taylor Swift is by far the most influential person in the music industry right now. Ignoring her when trying to launch a new music service in this competitive market would have disastrous results, even for Apple
Game Maker is the best way to go at that age. I used it when I was younger and the drag and drop functionality was great. As I grew older and started learning to code, the editor let me easily start writing scripts and such to give me more control over the gameplay
Which is daft, because to produce a separate app specifically for debugging React Native would be a huge undertaking with zero extra benefit. Chrome's Dev Tools are best in breed (IMO) and it makes sense to leverage them.
If there were things being added to Chrome Dev Tools specifically to support React Native, that'd be different.
That might be a core problem right there. There's no developer influence in product meetings? While on the business end there might be a need for a feature, business people are not going to understanding what complexities are involved in a particular feature. What you might think takes a day could take 3 weeks. On the other hand, you may be passing over useful features you think are complex but only take a day. If you trust your developers with as much as you say you do, they should have a voice in your meetings. That may be a way to retain this lead developers interest
I was involved with theater when I was younger, and would always read the script 50-60 times outside of rehersal. Halfway through a 4 month production, I would not only know my lines, but they would come to me naturally, leading me to interact as if I was that character.
The book I've probably read the most is One of the Eragon books.... last count I was at 24 read through. I really love that book. You do notice something different every time
Now, it’s up to each state to decide if and how they want to legalize it. New Jersey is actually the reason this went to the Supreme Court, and you can now take wagers within NJ if you have a physical operation in Atlantic City [2]
[1] https://www.supremecourt.gov/opinions/17pdf/16-476_dbfi.pdf
[2] https://www.nj.gov/lps/ge/sportsbetting.html
Edit: adding a link to the NJ sportsbetting rules