90 points

Disinvestment into Python, Flutter, and Dart is a clear signal that those tools are unimportant to Google. I won’t be recommending that anyone use Dart or Flutter on new projects.

permalink
report
reply
55 points

You shouldn’t have ever been recommending dart or flutter.

Python ain’t going anywhere tho

permalink
report
parent
reply
10 points
*

You shouldn’t have ever been recommending dart or flutter.

Why not?

permalink
report
parent
reply
38 points

I would argue so, because Google has quite a reputation for killing projects: https://killedbygoogle.com

Especially with a programming language or framework, you don’t want to invest in it, only to find out that it’s going on the chopping block.

permalink
report
parent
reply
20 points

I’m mostly just biased because I do native mobile development but flutter has always seemed like a false economy to me. You’re trying to build cross platform but it’ll take more than 2x as long as building each platform to get the same quality of experience. So either you have a shittier experience or you take even longer than true native dev.

But I’m obviously very biased here.

permalink
report
parent
reply
2 points

Python is going to die eventually. It’s too slow and the infrastructure is too painful for it to survive super long term.

It’s ridiculous popular now though so it’s going to take decades to die down.

permalink
report
parent
reply
27 points

Has anyone used Dart the past decade?

permalink
report
parent
reply
33 points

Aside from everyone who’s using flutter?

permalink
report
parent
reply
5 points

I sorta forgot it existed.

permalink
report
parent
reply
2 points

That’s a terrible language IMO

permalink
report
parent
reply
9 points

It was originally meant as a better JavaScript and it was. It failed when none of the other browsers expressed interest in supporting it. It languished for a while and then was taken up by the Flutter team. At the time Flutter took it up it was somewhere around the level of Java 8 in features but not quite on par. Since then it’s seen some massive improvements to the type system and language. It’s completely null sound, not just null safe like Kotlin. It recently got records/tuples and one of the more capable pattern matching syntaxes I’ve ever seen in a functional imperative hybrid language. The next stable version of dart will introduce a compiler macro system that is very promising. The syntax isn’t always the prettiest due to it trying to not totally break old code. I do think that it offers a wide range of modern language features that competes heavily with Swift and Kotlin in the mobile space.

permalink
report
parent
reply
8 points

Just had to look at it out of curiosity and man, it looks like yet another C+=1. The code samples on Wikipedia contain one of those gaudy for-loops and a ternary, as if that was still peak language design four decades after C got published.

But what I seriously don’t get: Why the hell did they develop Go then? That’s yet another C+=1, with even some design similarities to Dart, e.g. it’s garbage-collected but compiles to machine code.
Like, yeah, it wouldn’t be the first time that different teams develop competing products at Google, but what kind of culture leads to there even being demand for two C+=1s?

permalink
report
parent
reply
5 points

I won’t be recommending that anyone use Dart or Flutter on new projects.

You seem to think Google cares at all. Android has been languishing and Flutter is lightyears ahead. KMP is junk compared to what Flutter has accomplished with a fraction of the bells and whistles.

permalink
report
parent
reply
9 points

You seem to think Google cares at all.

Odd conclusion to draw. I’m simply not inclined to recommend tools that are not going to be supported by the organization that created them. Development ecosystems are important when planning a project.

permalink
report
parent
reply
3 points
*

What I mean to say is that Google isn’t invested in native android either. It’s been repeatedly strip mined by first-timers looking for a quick promotion and left to burn.

Things got so bad that Google gave up on native Views and created Jetpack Compose, which has been a source of many complaints related to performance.

In 2024 Flutter has instant hot-reload, and the “native” (but 100% bundled) solution still requires a complete reinstall on the device. In fact, Dart can compile to native code (or JIT) without an issue, yet Kotlin Native is barely in GA in the new compiler support has been lagging while the new compiler isn’t out of beta and is still poorly supported by tooling.

Consider the absurdity: React Native is the only true native framework out of RN, Jetpack Compose, and Flutter. And all of this barely scratches the surface of the tooling problems that Flutter 99% avoids by allowing development on desktop, web or iOS simulator.

permalink
report
parent
reply
1 point

Flutter

looking at you, canonical.

permalink
report
parent
reply
3 points

I’m not sure how cononical is connected to this.

permalink
report
parent
reply
3 points
*

they pledged, with google’s backing no less, to focus on it to develop ubuntu apps. they even spent a few of cycles working on porting their installer and snap store to it.

permalink
report
parent
reply
3 points
*

they pledged to adopt flutter heavily in ubuntu’s apps, in partnership with google. they even took like a couple cycles to port their entire installer and snap store to it.

permalink
report
parent
reply
1 point

Sass won’t be too happy

permalink
report
parent
reply
74 points

Laying people off instead of offering to move them to the now-more-important projects has to be one of the dumbest management moves that tech companies repeatedly do. These are people already trained on all the policies and procedures and tooling and “culture” specific to your company.

It’s going to be more expensive to hire and train new people when the dumdums in upper management finally figure out the mistakes they made that got them to a point where they decided they need to cut jobs and projects, and the ramp-up time before you actually start seeing progress on those priorities is going to be seriously lengthened. Of course they won’t acknowledge it was their fault in the first place, and again the heads roll on the wrong end of the corporate ladder.

permalink
report
reply
23 points

If I’m reading their CEOspeak right, their objective is to fire the very experienced people, that costs a lot of money, and replace them with people that costs less.

I never worked at Google, so I don’t know for sure, but it sounds like the Python team is important and that this will backfire. As the people that costs less will also be less skilled, and Python is an important piece for AI/ML research, where Google is already lagging behind. The AI people in Google will get lower quality help with Python, and Google will lag even further behind.

That what happens when the CEO is an MBA and not an engineer.

permalink
report
parent
reply
8 points

Engineers over index in their own ways, but I think you’re spot on with decoding the PR speak.

The Python team was very involved with the Python Software Foundation and was influencial with directing priorities for the Python programming language reference implementation (which is by far the most widely used implementation of Python). Google just gave up their say in how the language will evolve. Seems like an incredibly bad strategy. But then again, Google has been, from a financial perspective, nothing more than a digital classified ads platform for decades. If a smart MBA were running Google they’d start spinning off divisions into new IPOs and cashing in with dividends like other large conglomerates have done in the past when they have stopped inovating or actually commit to their projects long term.

permalink
report
parent
reply
0 points

Maybe we just need CEOs to be more receptive to developers’ wishes.

permalink
report
parent
reply
21 points

They are not stupid at all. Their interests are in conflict with the interests of tech workers and they are winning effortlessly, over and over again.

The big tech companies are all owned by the same people. If these layoffs cause google to lose market share to another company, it’s fine because they own that company too.

What matters is coordinating regular layoffs across the whole industry to reduce labour costs. It’s the same principle as a strike: if the whole industry does layoffs, workers gradually have to accept lower salaries. In other words, the employers are unionised and the employees are not.

This process will probably continue for the next 20 years, until tech workers have low salaries and no job security. It has happened to countless industries before, and I doubt we are special.

I’m sure the next big industries will be technology-focused, but that’s not the same as “tech”. They won’t involve people being paid $200k to write websites in ruby.

permalink
report
parent
reply
6 points

That’s why we need to negotiate in block, likely through unions.

permalink
report
parent
reply
18 points

It’s going to be more expensive to hire and train new people when the dumdums in upper management finally figure out the mistakes

Unfortunately that’s not the case. Those who have been laid off are those paid high salaries to build up the foundation. Now that the foundation is already there, they future work won’t be as complex as before and need less training. So why would they still pay the very high salaries? They’ll just get rid of the used-to-be-important programmers and hire the can-be-hired-for-a-lot-less programmers from India. It’s sad, but that’s the reality.

permalink
report
parent
reply
7 points

Those who have been laid off are those … to build up the foundation. Now that the foundation is already there, the future work won’t be as complex as before and need less training.

Small-to-medium companies see you at least as investment. So this is where i work.

permalink
report
parent
reply
5 points

They’re hiring replacements in Germany, not India.

permalink
report
parent
reply
2 points

have you seen the salaries in Germany? still much much cheaper than Bay Area

permalink
report
parent
reply
1 point

Now that the foundation is already there, they future work won’t be as complex as before and need less training.

LOL, LMAO even.

permalink
report
parent
reply
2 points

Yeah, at least give you argument so I can also laugh at myself too.

Anyway, take a look at this article that just came out just earlier, which means that by no chance it’s been referenced when I wtote my earlier comment. And do take note of the BOLD words.

The Core unit is responsible for building the technical foundation behind the company’s flagship products and for protecting users’ online safety, according to Google’s website. Core teams include key technical units from information technology, its Python developer team, technical infrastructure, security foundation, app platforms, core developers, and various engineering roles.

permalink
report
parent
reply
3 points

It’s not dumb. They understand what they are doing. They think firing multiple people at once can flood the market with developers, and the situation could be used to hire new people with a lower compensation.

Don’t think the rationale behind this is work quality or developer productivity. This is a power move. For Google and many big tech companies devs are replaceable and are just cogs in the machine. The problem is that they became too costly with the advent of COVID.

permalink
report
parent
reply
3 points

They fired 50 people. What market is that going to flood exactly?

permalink
report
parent
reply
1 point

I don’t mean this layoff but all that are happening in the last months.

permalink
report
parent
reply
25 points

“As we’ve said, we’re responsibly investing in our company’s biggest priorities and the significant opportunities ahead,” said Google spokesperson Alex García-Kummert. “To best position us for these opportunities, throughout the second half of 2023 and into 2024, a number of our teams made changes to become more efficient and work better, remove layers, and align their resources to their biggest product priorities. Through this, we’re simplifying our structures to give employees more opportunity to work on our most innovative and important advances and our biggest company priorities, while reducing bureaucracy and layers”

There was this incredible management consultant in france in the 18th century. Name eludes me, but if he was still around Google could hire him and start finding some far more convincing efficiencies.

The guy was especially good at aligning resources to remove layers

permalink
report
reply
13 points

Robespierre?

permalink
report
parent
reply
16 points

I also cannot name him from the top of my head…interesting

permalink
report
parent
reply
3 points

Or any part of your head, I imagine.

permalink
report
parent
reply
5 points

You could make a religion out of this.

permalink
report
parent
reply
5 points

No don’t

permalink
report
parent
reply
1 point
22 points

I am a manager at a big tech and I hate capitalism. CXOs really only care about profits, and thus everybody high-level proposes new enshittification strategies.

permalink
report
reply
19 points

Can’t really make heads of tails of this. I thought they were really into AI and Python is a big part of that. Which other languages are they going to invest in? Rust for Chromium?

Anti Commercial-AI license

permalink
report
reply
19 points

Python is in essence the interface for AI tools that are optimized with languages that are easier to get high performance results with.

permalink
report
parent
reply
12 points

They hired cheaper talent from elsewhere for python.

permalink
report
parent
reply
-6 points

They’re probably not using python for AI

permalink
report
parent
reply
22 points

They’re almost certainly using it as glue code. You have to go out of your way not to use Python for it.

permalink
report
parent
reply
6 points
*

You do, but considering the scales they process data I suspect Google would be better building Go tooling (or whatever the dominate internal language is).

A few years back I was trying to teach some graduates the importance of looking at a programming language ecosystem and selecting it based on that.

One of my comparison projects was Apache OpenNLP/Camel vs Flask/Spacy.

Spacy is the go to for NLP, I expected it to be either quicker to develop, easier to use, better results or just less resources.

I assigned Grads with Java experience Spacy and Python experience OpenNLP.

The OpenNLP guys were done first, they raved about being able to stream data into the model and how much simplier it made life.

When compared with the same corpus (Books, Team emails, corporate sharepoint, dev docs, etc…) OpenNLP would complete on 4GiB of RAM in less than a second on 0.5vCPU. Spacy needed 12GiB and was taking ~2 seconds with 2vCPU. They identified the same results…

Me and a few others ended up spending a day reading the python and trying to optimise it, clearly the juniors had done something daft, they had not.

It rather undermined my point.

permalink
report
parent
reply

Programming

!programming@programming.dev

Create post

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



Community stats

  • 3.6K

    Monthly active users

  • 1.6K

    Posts

  • 26K

    Comments