2,425 karma · joined May 9, 2020
I'd like to read an even more thorough overview of how it works and all the gotchas before I'd consider using this 'in production' but the API looks very easy to use and very elegant.
EDIT: just hit the section on portability, seems like you would always have to use that API, yeah? I feel like when you are writing network code you simply have to make it portable from the get-go. I guess I'm always thinking about having it run on client machines.
The problem is that the USA is capable of far more force and strength than Canada is. It's like an abusive relationship, but one where due to geography, Canada cannot simply leave.
This is the vibe of a bully taking a kids lunch money and then saying 'What are you gonna do about it?'
I'll never forget this feeling. The world is watching.
Our economy is already down. All of our tech elite move to Silicon Valley. Our energy infrastructure cant get off the ground. The USA dictates so much of what Canada is able to do.
What is the point of squeezing us more? We have so little we can offer you.
We've already given you the lives of our soldiers as we follow you into pointless wars. What more do you want? The pennies in our pockets?
Bringing this into your system seems like a huge liability.
The syntax of shell scripts is terrible, but we write it to do simple things easily without needing more external tools.
git-bash on windows is generally good enough to do the kind of things most shell scripts do.
This tool feels like the worst of both worlds: bash syntax + external dependency.
I'm not sure when, but I've been "long Intel" for a long time.
I think that's a really interesting insight that has application to using 'AI' in jobs across the board.
JSON is self describing, you can mostly just call the API, read the JSON response and figure it out from there.
Ignoring that detail is ignoring the elephant in the room.
You can do it all in bash, yes, but it's very conceivable this "just" thing actually provides real value.