I'm on the latest version (2.1.154 as of this comment). Based on the timestamps on those Issues being reported I think it's happening on the latest version.
I'm sure it will get fixed eventually/soon, just annoying to update and have your workflow break.
Unfortunately they seem to have straight up broken Claude Code either with this release in the backend or the new CC version. Errors about "can't modify thinking blocks" are bricking long-running sessions: https://github.com/anthropics/claude-code/issues?q=is%3Aissu...
Google really can’t help themselves but to have some internal re-org kill off a public thing people are actively using. It’s honestly impressive how consistent they are.
There was a moment about a week ago where Claude went down for about an hour. And right after it came back up it was clear a lot of people had given up and were not using it.
It was probably 3x faster than usual. I got more done in the next hour with it than I do in half a day usually. It was definitely a bit of a glimpse into a potential future of “what if these things weren’t resource constrained and could just fly”.
Seems like a big opportunity for Google to consider keeping Gemini ad-free as a differentiator. They can afford to burn cash on it for a long time to come if they choose to do so.
Did the client side JS being infected produce any issues which would have affected end users? As in if a web owner were on an affected version and deployed during the window would the end user of their site have had any negative impact?
Recently used a lot of HaxeUI for a game and it felt similar to this. A lot of components included out of the box that “just work” with some basic styling. And you can use CSS styling on top to further customize as needed. Works across a lot of different platforms as well.
I made one of the original posts on HN about this years ago after hearing about it from my CPA. Both then and now these changes make zero sense to me as a matter of good policy. I am also still surprised at the number of people in tech who either haven’t heard about this or are willfully ignoring it and likely filing their taxes incorrectly.
Somewhat related topic: anyone used something like the Luxedo to do a projection mapping? It seems like it’s more complicated and expensive but I love the idea of doing something cool to the house for Halloween and Christmas without having to lug out a ton of lights and decorations.
I think that ideally, every project would be setup from scratch in the beginning to use t() tags or something similar to have translation keys so that setting up translations is as easy as swapping out what t() returns (from e.g. a config file or the like).
Of course, we all know that this is very rarely how projects end up getting setup especially in the early stages, and then it's just massive amounts of work to go back and set it up later.
The thing that's the most intriguing to me about what you're describing is automatically setting up translations in the build step where you auto-detect strings to translate. But looking at the site, most of it seems to be focused around the VSCode extension which will just sort of find and replace strings in the source code with t() tags.
Can you talk more about the translations in the build step? Is there a reason you're not talking more about that on the site? (Is it just newer, not very reliable/good, or...)?
The idea that I could just throw something like this into my project, not have t() tags in my source code but still get translations, sounds like magic and I think it would be really neat.
At Roll20 we just released a beta version of our new VTT engine which is powered by Babylon. The devs on the team have really enjoyed getting to use the modern workflow compared to the legacy decade-old stuff we were using before. Thanks Babylon devs!
I don’t actually know how it works for paying yourself. But if you were paying someone else, in 2024 they would get 10k carried over from 2023 and $5k from 2024. You only get 10% the first year. I am not an accountant and this is not tax advice :-)
I'm sure it will get fixed eventually/soon, just annoying to update and have your workflow break.