I've worked 12 years at Google. When I was tech lead, I periodically checked Memegen and searched for my project name. I found it useful to get this feedback. Sometimes I converted the meme into a proper bug report; sometimes I responded to the meme with an explanation.
Not everyone will use Memegen in the same way. But quite often a high voted meme can be treated like a high voted bug report. It provides signal to the team.
Note that I worked on internal tooling. External facing teams have lots of other feedback channels, and they know that Googler's feedback is biased. So how the team responds to the feedback can be vary a lot.
For security reasons, the VSCode marketplace is not accessible, but many (in the 3-digit range) external extensions have been imported. One technical limitation is that some extensions are not designed for the web (e.g. try to run local things).
It's VSCode, so it's 90% similar to https://vscode.dev
There are internal extensions, but they don't dramatically change the look and feel.
I think many VSCode users are not familiar with the Comments UI, but it's used in e.g. the "GitHub Pull Requests" extension. Apart from that, some changes in the list of directories/files (for performance reasons) and a redesigned SCM integration.
I'm not sure about the dates.
At some point (2014?), the use of IntelliJ was discouraged in favor of Eclipse. One year later or so, the decision was reversed and the effort focused on IntelliJ (and Eclipse were considered deprecated).
Although the tool is internal, a lot of information about it is not confidential.
As the team had to collaborate with the VSCode team, we got clearance for sharing information about it.
The screenshots in the article were posted publicly on GitHub (in vscode issues). You can also find screenshots in https://research.google/blog/smart-paste-for-context-aware-a...
More generally, a lot has been communicated on developer infrastructure at Google.
I like the approach in Lingua Latina per se Illustrata (sometimes called the "natural method"). I've noticed that it was adapted for other languages too, but most of the adaptations seemed old and outdated.
Recently I was wondering if I should work on a modernization of the concept (using audio and a more interactive medium). If anyone has thoughts on this topic, I'd be happy to discuss more.
There's a lot of push back against AI-generated graphics and music. For code, it's more difficult to know. AI is used by some people to automate the boring tasks, so that they can focus more on the artistic side.
There's no specific filter. The main effect is blending the previous frame with the current frame. When blending, I modify the coordinates and add some noise. This makes the graphics look less basic and it creates this noisy trail when things move.
Interesting topic. I appreciate the effort that went into this, there are some good animations.
But I find this kind of presentation much harder to read than a classic blog post. It's difficult to skim through the text to see how far it goes (and the article structure is not apparent); instead, I was kind of forced to read the text sentence by sentence (since I was familiar with the topic, I wanted to skip over the basics).
Very nice project!
Thanks for making it open-source and very easy to use. I hope you'll find contributors and be able to get a nice collection of animations!
I'm starting a new project, I may have to use this tool in the next few months.
Each time I read this kind of feedback, I wonder if there should be a free, community driven, alternative to Duolingo.
- Content may be provided by contributors (like Duolingo did for many years)
- It could be supported by donations (I believe the costs can be kept low)
My feeling is that lots of problems with Duolingo are caused by monetization (and many things were better in Duolingo a few years ago).
I'm still not sure of how it should be designed and what we need exactly. One of the problems is also to get enough contributors. I'd be interested in hearing more thoughts on this.
As a hobby, I started building an alternative to the Duolingo Stories feature (https://lingostories.org), but it's still fairly limited.
I agree that many vibe-coders are likely to skip reviews completely, but it doesn't have to be like this.