131–140 of 161 posts
I wish they had used GO. If you worry about distribution and dependencies, GO static binaries are clear winner. One issue with GO binaries is that they can become very big.
https://github.com/Azure/azure-sdk-for-go
Azure is mostly a lot of REST apis.
Earlier quoted context omitted.
> i'm sure i'm going to burn karma for comparing node with vb but... 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 (wh…
Node.js wasn't built for baby devs, it was built for professional devs who had to use JS anyway because browsers to be able to use the same technology on the back-end rather than using different languages front- vs. back-end.
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.
http://jugad2.blogspot.in/2013/01/some-google-command-line-t...
My IBM developerWorks tutorial on writing command line utilities (C) is not at that IBM link in post now (archived after 10 years), but can be found here:
http://jugad2.blogspot.in/2014/09/my-ibm-developerworks-arti...
Earlier quoted context omitted.
Node.js wasn't built for baby devs, it was built for professional devs who had to use JS anyway because browsers to be able to use the same technology on the back-end rather than using different languages front- vs. back-end.
There is this radical idea in software development that sometimes you use the language that is best for the job -- not just the one you are already using!
Earlier quoted context omitted.
People generally say Azure suits the enterprise, AWS suits tech-driven companies (i.e. those where the CEO knows what an API is), and Google supports special/hobby projects. Google is probably awesome but nobody trusts them to not just abandon the whole thing in a few years time. Amazon and Azure are going to be around for at least a decade.
Google is not going to abandon cloud. I'm not sure anything I say can convince you, but the fact the Spotify, Evernote, Disney, Home Depot, Snapchat, etc all run on GCP says a lot.
Earlier quoted context omitted.
> You do realize that Python was not only built to appeal to "non-devs" ... as an alternative to C++ and Perl. And in that respect, it is a snap to pick up. It is pretty easy, not as easy as, say, Javascript, but still easy to pick up, I agree. Node.js is cancer. We all use it, because of the momentum it has with designers instantly being able to declare themselves "full-stack devs", but make no mistake -- Node.js an…
I'm surprised to see JS described as easier than Python. I'd say it's considerably harder and more complex. The first reason being that it forces you to think about asynchronosity constantly, and that's something a beginner's going to struggle with -- not just the idea that your code won't run in order, but that there are so many ways to deal with it (callbacks, promises, async/await, event emitters) all with their o…
But I do agree: Sometimes I see people try to push Node/Express as a good choice for teaching basic APIs. Its not the worst choice, but its startling how easy it is to forget how insanely confusing async callbacks are for new devs.
Earlier quoted context omitted.
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…
aws generally has the most features but clunky apis and high costs 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
Google Compute Engine alone has lots of nifty features that even AWS EC2 lacks, like custom VMs, generalized VM types (no need to go for specific instances to get fast networking, for example), preemptible VMs, live migration, disk hot-grow, and sustained use discounts, while generally being cheaper.
(work on GCP)
Earlier quoted context omitted.
Google is not going to abandon cloud. I'm not sure anything I say can convince you, but the fact the Spotify, Evernote, Disney, Home Depot, Snapchat, etc all run on GCP says a lot.
Google doesn't have a good track record supporting its products. I have no doubt that GCloud will stick around, but the fact remains that Google has trust problems.
Google Cloud is paid b2b, not free b2c - companies like Disney, Spotify, Evernote build very close multi-year relationships with Google, rely on Google, pay Google, etc. Google Cloud going away would shut down, for example, all of Snapchat.
(work at GCP)
* I'm interested in seeing how they plan on handling keeping an 'evergreen' state on ubuntu repos that they don't control.
* jmespath! It's great to see it spread more! Such a useful spec.
* There's an awful lot of dependencies, 59 vs 10 in the aws cli.
* No windows installers?
* Does that server side completion cost money?
* With such a crazy file structure, it would be great to see a getting started guide for contributing.
* The readme should really list the supported python versions.
* It's hard to tell how much is code generated and how much is custom.
* Help text prints right to the shell without using a pager.
Earlier quoted context omitted.
Google doesn't have a good track record supporting its products. I have no doubt that GCloud will stick around, but the fact remains that Google has trust problems.
This comes up sometimes, and is really not well supported. Happy to discuss every time it does come up :) Google Cloud is paid b2b, not free b2c - companies like Disney, Spotify, Evernote build very close multi-year relationships with Google, rely on Google, pay Google, etc. Google Cloud going away would shut down, for example, all of Snapchat. (work at GCP)