Live data from Hacker News

Dear Google Cloud: Your Deprecation Policy Is Killing You

medium.com

211–220 of 417 posts

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You

#211
There are other tradeoffs between cloud providers that are important to keep in mind here. In my experience, GCP has been easier to get started with, and has offerings that are by-and-large more comprehensible. One thing I really appreciate is that a lot of their client libs have automatic auth within GCP (last time I used AWS this wasn't the case or I didn't know about it).

As someone who hasn't been burned by it personally, it is hard to quantify the actual risk and maintenance cost of GCP's deprecation policy, but I know decision makers at larger organizations that are rightfully afraid of it.

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You

#212
post #6

I really want to like google cloud. Every time I use it things seem better set up than in AWS. I feel like I can't even bring it up at work though because of the issues with deprecation.

I hear you. At the end of the day though a little more effort on front end setup is infinitely better than the time wasted later on when you have to rebuilt everything every time Google decides to get rid of another product / service / platform / setting. Burned by that one too many times and moved on.

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You

#214
post #66

> Let’s say hypothetically that Apple was dumb enough to pull a Guido van Rossum, and declare that Swift 6.0 is backwards-incompatible with Swift 5.0, much in the way that Python 3 is incompatible with Python 2. Damn, I was waiting for this. The whole essay was a setup for this paragraph. Reframes the argument using a shared traumatic experience for everyone. This humanizes the effect, we all know someone that lost s…

Apple already ~mandated moving apps to Swift. I don't see why they couldn't do it again? Purely because of the existence of Flutter?

When did Apple “mandate” apps move to Swift? The majority of code out there is still Objective C.

The problem isn’t making an incompatible “v2”. It’s getting rid of “v1”.

If I can’t take advantage of new functionality without moving to a new version that’s a headache. But it doesn’t cause me to throw away all of my existing investment. Especially if you can combine the old and the new.

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You

#215
>Businesses are taking a mercenary’s accounting of their dual mobile teams (iOS and Android), and starting to realize that those phony-sounding dog-and-pony-show cross-platform development systems like Flutter and React Native have real teeth, and using them could cut their mobile team sizes in half, or alternately, make them twice as productive.

Is there much Flutter and React Native dev going on at big companies outside of Google and Facebook?

I know plenty of smaller companies are using them because they don't have what sometimes feels like near-infinite money to throw at mobile engineers, but I can't think of a single Big Name On Blind with iOS or Android position listings that mention Flutter or RN. They're all native.

Even at Google and Facebook, usage of either of their respective frameworks seems to be an exception and not the norm, and they're still just components in a larger native project. I wonder if the goal is to eventually re-write everything? But that seems impossible given the size of these applications' source.

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You

#216
post #147

Earlier quoted context omitted.

As a counter argument, I don't hold much confidence in my former professor's ability to rank the real-world competence of their student's.

You may be right, I can only give my point of view. Also, even if I am right, real-world competence may involve more bluffing, less high quality knowledge of algorithms, than I would like.

Maybe the ability to get along with people is more important than some people are willing to admit?

I’ve met plenty of “smart people” who couldn’t get things done to save their lives partially because they couldn’t communicate well or play well with others.

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You

#217
post #97

Earlier quoted context omitted.

Of course. I'm well aware that I'm considered mentally defective (or maybe just garden variety low IQ) by the hiring committee. That doesn't really change my observation here.

You pop up in every post about Google or Facebook and make the conversation about yourself, wallowing in self pity because you didn't land a job there straight out of college. This might sound harsh, but you need to get over it and move on.

I was about to disagree with what seems like a personal attack but then without looking at the posting history of the poster you replied to and just looking at the username. I have to agree.

On another note, I’m in my mid 40’s spent all of my time bouncing between yet another CRUD job most of my career (not complaining, it’s paid for a decent lifestyle in my relatively low cost of living area) and I’m always encouraging fresh CS grads to go for broke and take the r/cscareerquestions route of “grind leetCode and work for a FAANG”, knowing they will make more fresh out of college than I did until a few months ago.

Someone else’s success is not my failure.

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You

#218

There are other tradeoffs between cloud providers that are important to keep in mind here. In my experience, GCP has been easier to get started with, and has offerings that are by-and-large more comprehensible. One thing I really appreciate is that a lot of their client libs have automatic auth within GCP (last time I used AWS this wasn't the case or I didn't know about it). As someone who hasn't been burned by it pe…

Easier to get started ? Their UI , IAM architecture and firebase being kind of separate is so confusing .

Aws used to be simpler , while they are screwing it up now, the recent route53 upgrade was terrible , a single click action has now become 4-5 clicks they are still better than GCP.

Azure has the really the best interface (outside of DO) , it is easy to go to related and nested resource in one freaking app. Both google and aws end up forcing you to open three four tabs to setup interconnected apps .

DO interface is really really good ,however they don’t have the complexity of features that the big three do , so not a fair comparison

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You

#219
And then there is AWS, which has depreciated exactly one service, SDB, but only after they created a much better replacement (DynamoDB) and offered to help migrate all of their large customers, so they could get the usage percent so low that almost no one was affected by the shutdown.

Re: Dear Google Cloud: Your Deprecation Policy Is Killing You

#220
post #172

Earlier quoted context omitted.

Unfortunately I understand that Azure is not exactly what one would call "mature software". I have a colleague who's been using it for a few months, and he complains about it constantly. He's had to submit a couple of pull requests for somewhat silly issues like string escaping not working properly.

I don't have the same issues as your colleague. I've been using Azure for 8 years and rarely run into any issues. Maybe his issues isn't with Azure.

I have heard similar from more than one person. Maybe it depends on the services you use.
Post reply on HN