21–30 of 161 posts
Did they explain why they switched? Not that I'm complaining. Love Python, dislike JS being everywhere.
There's a mention of it in the "Motivation" page on the GitHub wiki. Basically the big thing seems to be the feedback from Linux users that most distributions bundle Python but not Node. Also that AWS and Google CLI tools are still more Python than Node.
Earlier quoted context omitted.
All of these platforms offer a free trial and a lot of products have free tiers. I'd check them out and decide for yourself. (I work for Google Cloud and am happy to answer questions about GCP)
Thank you , but what I meant was in heavy work load. I know the basic ideas. But I am curious in heavy work load which one is preferred for what. AFAIK Spotify went with GCP, many big companies went with azure, most startups chose AWS. What was the reason behind these, personal preference? Or technical superiority? The reason for my curiosity is Microsoft and Oracle kind of sees Cloud Computing as life and death situ…
gce has really nice apis but limited features and unless you do things like google you'll have to do a lot of your own integration work
i've never seriously used azure
Did they explain why they switched? Not that I'm complaining. Love Python, dislike JS being everywhere.
There's a mention of it in the "Motivation" page on the GitHub wiki. Basically the big thing seems to be the feedback from Linux users that most distributions bundle Python but not Node. Also that AWS and Google CLI tools are still more Python than Node.
Good ole' inveteracy. Unfortunately, it's really as good a reason as any when it comes to managing resources on a long-term project (people, time, $).
Always needs to be balanced against using the right tool for the job, even if that means the initial pain of carrying a codebase written in a "relatively" newer language. To be clear, both Python and JS (NodeJS) are great tools with excellent communities and ecosystems.
Earlier quoted context omitted.
All of these platforms offer a free trial and a lot of products have free tiers. I'd check them out and decide for yourself. (I work for Google Cloud and am happy to answer questions about GCP)
Thank you , but what I meant was in heavy work load. I know the basic ideas. But I am curious in heavy work load which one is preferred for what. AFAIK Spotify went with GCP, many big companies went with azure, most startups chose AWS. What was the reason behind these, personal preference? Or technical superiority? The reason for my curiosity is Microsoft and Oracle kind of sees Cloud Computing as life and death situ…
Amazon and Azure are going to be around for at least a decade.
This reminds me of companies rewriting applications from VB to c++/c#. Half the people complained about VB being good enough and more popular. But the overall feeling was that once the rapid application dev version is out the door and ok then it's a good time to redo it with something more engineering-y, for long term support before the first version gets too ossified. (i'm sure i'm going to burn karma for comparing…
The directory structure is beautiful.
azure-cli/src/azure-cli-core/azure/cli/core/
That's.... definitely not beautiful
This reminds me of companies rewriting applications from VB to c++/c#. Half the people complained about VB being good enough and more popular. But the overall feeling was that once the rapid application dev version is out the door and ok then it's a good time to redo it with something more engineering-y, for long term support before the first version gets too ossified. (i'm sure i'm going to burn karma for comparing…
I'll take the hit for you and flat-out say that node.js is the new VB.
In fact, for those of you that have been around a while, I think we can all agree that node.js is the new PHP was the new Visual Basic, etc.
Not in the sense that they do the same things, but that they were purposely built for non-programmers (baby-devs) to be able to program (which is good!) but by the same token, invited entire (and continuing) mountains of half-assed, unsupported(unsupportable) code that just begets generations of garbage.
If you are a consultant, fixing this garbage can be a whole career.
Surprised this is getting so much attention here. They re-wrote their CLI in another language. What's the big deal...
Are you not interested in why they rewrote it and what made them choose Python? Did they have a problem with it in JS that JS could not solve? Lots of interesting questions here.