mihai_maruseac

It's very close to 123456 * 8 + 6 = 987654 and the rest.

I just wrote an article on that (and the fact that this submission on HN exists, I was not expecting that)

https://mihai.page/ramblings-on-a-math-pattern/

Flutter was already affected in this wave.

The issue is that now they're hiding. Those who do the decision no longer send emails, no longer show up in townhalls (if they organized).

There was a townhall for the past wave of layoffs where the exec in charge preferred to take the meeting via video call from a huddle in the same building as the auditorium where the townhall was taking place. Just to not be seen with the employees.

This. There was a sudden push to reduce costs and people with decision power tried to make sure their teams won't get affected.

Flutter team (Front End), was also axed.

Already answered in this thread: https://news.ycombinator.com/item?id=40176338

Yes, and not to repeat myself: https://news.ycombinator.com/item?id=40182940

Yes, I admit that this was a little bit reductionistic. I was aiming it to be mostly a joke about the situation, didn't expect it to garner so much response

Rather than repeat myself: https://news.ycombinator.com/item?id=40182940

Yes, production code is C++, but the way the models are built is Python code, colab, save via Orbax/TF SavedModel, etc and then serve in C++. All (most, to hedge it) development is done via Python.

I don't directly develop the models, I played with some for fuzzing [1] and I'm working on security for them [2]. And, before joining GOSST, I was leading the OSS DevInfra team in TF. I still have the most number of commits made by a human [3] even after 2 days of leaving the team, though I see the next person only needs 4 more :)

[1]: https://security.googleblog.com/2023/08/ai-powered-fuzzing-b... [2]: https://security.googleblog.com/2023/10/increasing-transpare... [3]: https://github.com/tensorflow/tensorflow/graphs/contributors

Google is an AI first company

Google's future is strictly tied to its AI products

All AI is written with Python.

Google lays off all Python team.

Segmentation fault

Based on the contents of the blog (as that's the only think I can talk about -- I was in the team pre 2022), it's mostly dead.

JAX (and Keras) is where the push is now. And, grudgingly, PyTorch

On tax day here in US. To keep in mind for next year.

It's the same article, same content, same title, but different publication date.

At the same time, posts filled with expletives but from people pro-government are reviewed as "we didn't find anything wrong"

Next call for contributions at end of September.

People are working on that and this is not really happening now if you're using sandboxes.

There is this version, always released in parallel with the PDF. https://www.haskell.org/communities/11-2014/html/report.html

I was thinking of starting to generate only the PDF version but you just provided the best argument to also keep an HTML version. Thanks.

Thanks. Most of the work has been done by the authors of the projects and the reports, I merely integrated their entries.

Editor here. I just wanted to thank the submitter and send an informal invitation to submit any Haskell project you're working on for the next version. I'd be more than happy to double the size of the report and include more work which is not yet shown on the report.