LogoThread Easy
  • 探索
  • 撰写 Thread
LogoThread Easy

您的一体化 Twitter 线程助手

© 2025 Thread Easy All Rights Reserved.

探索

最新在前,按卡片方式浏览线程

开启时会模糊预览图,关闭后正常显示

guys, hear me out...what if actually the entire behind the scenes was AI generated using a new Siri video model?

guys, hear me out...what if actually the entire behind the scenes was AI generated using a new Siri video model?

✨ dabbler 🏒 collector 🔮 @maybe 🪀 @superfantoys 🧰 @ToolstashApp ☠️ https://t.co/cjSO6O7GmD 🟦 https://t.co/90dqFQGadZ

avatar for Josh Pigford
Josh Pigford
Fri Nov 07 17:19:53
RT @SchmidhuberAI: The most cited paper of the 21st century is on deep residual learning with residual connections. Who invented this? Time…

RT @SchmidhuberAI: The most cited paper of the 21st century is on deep residual learning with residual connections. Who invented this? Time…

Invented principles of meta-learning (1987), GANs (1990), Transformers (1991), very deep learning (1991), etc. Our AI is used many billions of times every day.

avatar for Jürgen Schmidhuber
Jürgen Schmidhuber
Fri Nov 07 17:18:20
Being on a podcast I'm a huge fan of is a bit surreal.

Grateful to @SamCharrington and @TWIML for the space to talk about why this moment in AI + mathematics feels special -- not just because models are smarter, but because three worlds are finally converging: LLM reasoning, Lean, and code generation.

At @axiommathai we are assembling a team of world experts in these three pillars.

Being on a podcast I'm a huge fan of is a bit surreal. Grateful to @SamCharrington and @TWIML for the space to talk about why this moment in AI + mathematics feels special -- not just because models are smarter, but because three worlds are finally converging: LLM reasoning, Lean, and code generation. At @axiommathai we are assembling a team of world experts in these three pillars.

@axiommathai : careers@axiommath.ai

avatar for Carina Hong
Carina Hong
Fri Nov 07 17:16:37
Here is the plaintext:

### ast-grep vs ripgrep (quick guidance)

**Use `ast-grep` when structure matters.** It parses code and matches AST nodes, so results ignore comments/strings, understand syntax, and can **safely rewrite** code.

* Refactors/codemods: rename APIs, change import forms, rewrite call sites or variable kinds.
* Policy checks: enforce patterns across a repo (`scan` with rules + `test`).
* Editor/automation: LSP mode; `--json` output for tooling.

**Use `ripgrep` when text is enough.** It’s the fastest way to grep literals/regex across files.

* Recon: find strings, TODOs, log lines, config values, or non‑code assets.
* Pre-filter: narrow candidate files before a precise pass.

**Rule of thumb**

* Need correctness over speed, or you’ll **apply changes** → start with `ast-grep`.
* Need raw speed or you’re just **hunting text** → start with `rg`.
* Often combine: `rg` to shortlist files, then `ast-grep` to match/modify with precision.

**Snippets**

Find structured code (ignores comments/strings):

```bash
ast-grep run -l TypeScript -p 'import $X from "$P"'
```

Codemod (only real `var` declarations become `let`):

```bash
ast-grep run -l JavaScript -p 'var $A = $B' -r 'let $A = $B' -U
```

Quick textual hunt:

```bash
rg -n 'console\.log\(' -t js
```

Combine speed + precision:

```bash
rg -l -t ts 'useQuery\(' | xargs ast-grep run -l TypeScript -p 'useQuery($A)' -r 'useSuspenseQuery($A)' -U
```
**Mental model**

* Unit of match: `ast-grep` = node; `rg` = line.

* False positives: `ast-grep` low; `rg` depends on your regex.
* Rewrites: `ast-grep` first-class; `rg` requires ad‑hoc sed/awk and risks collateral edits.

Here is the plaintext: ### ast-grep vs ripgrep (quick guidance) **Use `ast-grep` when structure matters.** It parses code and matches AST nodes, so results ignore comments/strings, understand syntax, and can **safely rewrite** code. * Refactors/codemods: rename APIs, change import forms, rewrite call sites or variable kinds. * Policy checks: enforce patterns across a repo (`scan` with rules + `test`). * Editor/automation: LSP mode; `--json` output for tooling. **Use `ripgrep` when text is enough.** It’s the fastest way to grep literals/regex across files. * Recon: find strings, TODOs, log lines, config values, or non‑code assets. * Pre-filter: narrow candidate files before a precise pass. **Rule of thumb** * Need correctness over speed, or you’ll **apply changes** → start with `ast-grep`. * Need raw speed or you’re just **hunting text** → start with `rg`. * Often combine: `rg` to shortlist files, then `ast-grep` to match/modify with precision. **Snippets** Find structured code (ignores comments/strings): ```bash ast-grep run -l TypeScript -p 'import $X from "$P"' ``` Codemod (only real `var` declarations become `let`): ```bash ast-grep run -l JavaScript -p 'var $A = $B' -r 'let $A = $B' -U ``` Quick textual hunt: ```bash rg -n 'console\.log\(' -t js ``` Combine speed + precision: ```bash rg -l -t ts 'useQuery\(' | xargs ast-grep run -l TypeScript -p 'useQuery($A)' -r 'useSuspenseQuery($A)' -U ``` **Mental model** * Unit of match: `ast-grep` = node; `rg` = line. * False positives: `ast-grep` low; `rg` depends on your regex. * Rewrites: `ast-grep` first-class; `rg` requires ad‑hoc sed/awk and risks collateral edits.

Former Quant Investor, now building @lumera (formerly called Pastel Network) | My Open Source Projects: https://t.co/9qbOCDlaqM

avatar for Jeffrey Emanuel
Jeffrey Emanuel
Fri Nov 07 17:16:32
A useful addendum to your AGENTS dot md or CLAUDE dot md file. First ask codex or claude code to install ast-grep for you if you don't have it already. 

It's pretty handy for systematically finding general patterns in code that could be tricky to do using regular string matching that's not syntax-aware.

A useful addendum to your AGENTS dot md or CLAUDE dot md file. First ask codex or claude code to install ast-grep for you if you don't have it already. It's pretty handy for systematically finding general patterns in code that could be tricky to do using regular string matching that's not syntax-aware.

Here is the plaintext: ### ast-grep vs ripgrep (quick guidance) **Use `ast-grep` when structure matters.** It parses code and matches AST nodes, so results ignore comments/strings, understand syntax, and can **safely rewrite** code. * Refactors/codemods: rename APIs, change import forms, rewrite call sites or variable kinds. * Policy checks: enforce patterns across a repo (`scan` with rules + `test`). * Editor/automation: LSP mode; `--json` output for tooling. **Use `ripgrep` when text is enough.** It’s the fastest way to grep literals/regex across files. * Recon: find strings, TODOs, log lines, config values, or non‑code assets. * Pre-filter: narrow candidate files before a precise pass. **Rule of thumb** * Need correctness over speed, or you’ll **apply changes** → start with `ast-grep`. * Need raw speed or you’re just **hunting text** → start with `rg`. * Often combine: `rg` to shortlist files, then `ast-grep` to match/modify with precision. **Snippets** Find structured code (ignores comments/strings): ```bash ast-grep run -l TypeScript -p 'import $X from "$P"' ``` Codemod (only real `var` declarations become `let`): ```bash ast-grep run -l JavaScript -p 'var $A = $B' -r 'let $A = $B' -U ``` Quick textual hunt: ```bash rg -n 'console\.log\(' -t js ``` Combine speed + precision: ```bash rg -l -t ts 'useQuery\(' | xargs ast-grep run -l TypeScript -p 'useQuery($A)' -r 'useSuspenseQuery($A)' -U ``` **Mental model** * Unit of match: `ast-grep` = node; `rg` = line. * False positives: `ast-grep` low; `rg` depends on your regex. * Rewrites: `ast-grep` first-class; `rg` requires ad‑hoc sed/awk and risks collateral edits.

avatar for Jeffrey Emanuel
Jeffrey Emanuel
Fri Nov 07 17:16:05
RT @adamdangelo: Enjoyed my conversation with @amasad and @eriktorenberg!

RT @adamdangelo: Enjoyed my conversation with @amasad and @eriktorenberg!

ceo @replit. civilizationist

avatar for Amjad Masad
Amjad Masad
Fri Nov 07 17:14:21
  • Previous
  • 1
  • More pages
  • 548
  • 549
  • 550
  • More pages
  • 2127
  • Next