I've used tree-sitter for a few projects, but I never touched the tree-reuse stuff. The value of tree-sitter came from the fact that grammars compile to a .so and can be easily distributed through package managers. Adding support for a new grammar in ast-grep might just mean pointing to the .so at runtime (idk, I haven't checked). So this optimization might make sense for this project.

Comments URL: https://news.ycombinator.com/item?id=46089455

Points: 1

# Comments: 0

I don't think it's fair to say "no one wants to invest in proper instrumentation" - the OpenTelemetry community has built a massive amount of instrumentation in a relatively short period of time. Yes, OpenTelemetry is still young and unstable, but it's getting better every day.

As the article notes, the OpenTelemetry Collector has plugins can convert nearly any telemetry format to OTLP and back. Many of the plugins are "official" and maintained by employees of Splunk, Datadog, Snowflake, etc. Not only does it break the lock-in, but it allows you to reuse all the great instrumentation that's been built up over the years.

> The core issue is that, with otel, observability platforms become just a UI layer over a database.

I think this is a good thing - when everyone is on the same playing field (I can use Datadog instrumentation, convert it to OTel, then export it to Grafana Cloud/Prometheus), vendors will have to compete on performance and UX instead of their ability to lock us in with "golden handcuffs" instrumentation libraries.

  fn(x=,y=,z=)

edit: nevermind, that PEP was rejected :/

Is the pattern matching API not sufficiently high level? In my experience, it's a huge improvement over implementing visitors for everything.

https://tree-sitter.github.io/tree-sitter/using-parsers#patt...

https://github.com/OpenLoco/OpenLoco/blob/master/src/Interop...

So, Go?

https://github.com/larkery/zsh-histdb

- Learning more advanced Vim techniques, adding new Vim plugins

- Learning more shortcuts for my daily drivers like my IDE(s), shell, etc.

- Adding new shell plugins

- Learning "modern" tools like ripgrep and fzf (There's a list here: https://github.com/ibraheemdev/modern-unix)

- Anything related to Kubernetes like kubectl-aliases or k9s

What do you find essential? What gives you the most bang for your buck, and conversely, what do you think is overhyped and not worth the time? It doesn't have to be strictly related to productivity; if you found something that makes your job more enjoyable I want to hear about that too!

One thing I wish I picked up earlier is a familiarity with Perl regular expressions and basic Perl syntax. Perl seems to be everywhere and being able to whip up a fancy one-liner with lookarounds and embedded code execution can be incredibly useful. I wouldn't say there's a steep learning curve, but, like most things, the skill atrophies if not exercised regularly.

Comments URL: https://news.ycombinator.com/item?id=38970893

Points: 3

# Comments: 1

I have also found this to be the case, even with engineers that have years of experience. It's both impressive and awful.

Bonus SO post to enhance your fury:

https://stackoverflow.com/questions/61762189/installing-gnu-...

Not in adults https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4195639/ https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9884156/ https://pubmed.ncbi.nlm.nih.gov/27553219/ https://pubmed.ncbi.nlm.nih.gov/25317367/