Dmitry Babokin

ISPC maintainer. Opinions are my own.

[Dmitry Babokin @DmitryBabokin]

Looks like Anthropic just knocked down the last wall protecting my work-life balance 😱

[Noah Zweben @noahzweben]

Announcing a new Claude Code feature: Remote Control. It's rolling out now to Max users in research preview. Try it with /remote-control

Start local sessions from the terminal, then continue them from your phone. Take a walk, see the sun, walk your dog without losing your flow.

[Dmitry Babokin @DmitryBabokin]

@bcherny Any hints how to avoid slash commands duplication in the worktree? I guess https://t.co/gHfevr2R5d is also duplicated in the context, right?

[Dmitry Babokin @DmitryBabokin]

@bcherny Ha! it worked on the second attent, but didn't work on the first try. Probably it had to create some folders and failed silently 😕

[Dmitry Babokin @DmitryBabokin]

@bcherny Bug report: -w doesn't work (while --worktree works).

[Chris Lattner @clattner_llvm]

One not very hot take - The Claude C Compiler has the best internal architecture docs of any compiler I've ever seen. Far, far, better than any compiler I've ever written, lol :-)

[serafim @serafimcloud]

The best products of the 21st century have yet to be shipped.

With 21st, any idea can find its aesthetic and design, even if you aren’t a designer.
Meet the first vibe crafting tool for everyone….

So every product can have soul.

[Dmitry Babokin @DmitryBabokin]

@sama Codex is good, but please make sure that all the essential features are there, like "resume the session" in CLI. I'm also looking forward to subagents!

[OXMIQ @realoxmiqlabs]

Oxmiq Labs, founded by GPU legend Raja Koduri, emerges from stealth with a dream team and $100B+ in past impact. Rebooting the GPU stack from atoms to agents™ with breakthrough IP, hundreds of patents, and a bold vision for AI and graphics. Visit https://t.co/c4kcta24vE

[ISPC @ispc_updates]

🚀 New ISPC v1.26.0 Release! 🚀
🔹 Improved ARM support & performance
🔹 New "generic" targets simplify ISPC design & ease new targets support
🔹 Better code generation for x86 & ARM
🔹 Lots of stability fixes
https://t.co/pzb96481pn

[Arina Neshlyaeva @ArinaNeshlyaeva]

Recently we released ISPC v1.25, featuring exciting updates: improved code generation, faster compile times, enhanced templates support, and new standard library functions! Dive into the full details here: https://t.co/dS9g5TLeJT

[Dmitry Babokin @DmitryBabokin]

@iruletheworldmo 🍓

[Dmitry Babokin @DmitryBabokin]

@karpathy It looks like Telegram solved exactly this problem when introduced "star" likes in Telegram. One star is approximately $0.02. People can like with as many stars as they want.

[Dmitry Babokin @DmitryBabokin]

@ashvardanian Based on github search it’s not that popular :) Actually I haven’t found any legitimate calls of it, only definitions. Apparently people are not educated enough about the existence of this gem!

[Dmitry Babokin @DmitryBabokin]

@ashvardanian I use free tier Oracle Cloud Arm instance with 4 cores and 24GB of RAM to run self-hosted Github runner. It's pretty fast, possibly it can handle your 10 projects.

[Dmitry Babokin @DmitryBabokin]

@ashvardanian And SierraForrest is Atom cores and it will be 288 cores. But it's not going to be and an edge chip - at least 288 version.

[Dmitry Babokin @DmitryBabokin]

@ashvardanian Looks like you are mixing things up. D-line is for edge and the current offering for D is IceLake. Sapphire/Emerald is not available for edge, it's big servers only. So Granite vs IceLake comparison looks fair. Note Granite is Big Core product, it's not going to be 288 cores.

[Dmitry Babokin @DmitryBabokin]

@science_dot And by saying that autovectorization problem is not "solved", I mean it doesn't work perfectly out of the box. To get optimal code you either need to put a bunch of pragmas, rewrite your code in specific way, or write explicitly vector code.

[Dmitry Babokin @DmitryBabokin]

Hey, CS twitter, I need your help with CS archeology. Some time ago my senior compiler colleague told me a story that when Cray released the first vector machine in 1975 (Cray-1), they promised to solve autovectorization problem in one year. Almost half a century has passed (1/2)

[Dmitry Babokin @DmitryBabokin]

@science_dot Thanks for the slides. As I understand, there are pragmas/directives to guide the vectorizer. But it's not much different from modern Fortran/C/C++ autovectorizers - they have a bunch of pragmas to guide them or make their work easier.

[Dmitry Babokin @DmitryBabokin]

@JukkaSuomela @science_dot Yeah, hardware was quite different, but from software perspective the autovectorization problem is very similar to autovectorization problem on the modern hardware.