HackerTrans
トップ新着トレンドコメント過去質問紹介求人

roggenbuck

no profile record

投稿

Hello, World (2006)

berndhopfengaertner.net
1 ポイント·投稿者 roggenbuck·3 か月前·0 コメント

Incident with Actions

githubstatus.com
3 ポイント·投稿者 roggenbuck·8 か月前·0 コメント

Show HN: Kronicler – capture performance analytics with custom rust database

github.com
1 ポイント·投稿者 roggenbuck·9 か月前·0 コメント

Show HN: Regolith – Regex library that prevents ReDoS CVEs in TypeScript

github.com
27 ポイント·投稿者 roggenbuck·11 か月前·25 コメント

Show HN: Regolith – Regex library for TypeScript made to prevent ReDoS attacks

github.com
3 ポイント·投稿者 roggenbuck·11 か月前·0 コメント

コメント

roggenbuck
·24 日前·議論
The longest answer is the correct answer for a lot of the questions
roggenbuck
·先月·議論
Thanks Eric! That makes sense and I appreciate the thoughtful response! Excited to read the new book (arriving tomorrow)!
roggenbuck
·先月·議論
Hey Eric!

How often do you see companies recover from financial gravity? Or is it mostly irreversible?

How much do you attribute worsening of company values to things like professional managers, too much hierarchy, and less founder-mode; versus financial gravity?

In a case like GitHub where their focus seems less on open-source these days, should developers try to help GitHub better support open-source or should the focus be on building alternatives?

Thanks, Jake
roggenbuck
·2 か月前·議論
Loving superset! Congrats on the launch! Excited to try remote workspaces so I don’t have to leave my computer open while I have autoresearch running.
roggenbuck
·2 か月前·議論
This is some excellent work Henry! Very excited to try it out.
roggenbuck
·6 か月前·議論
Flameshot is excellent! I’ve been happily using it for years.
roggenbuck
·6 か月前·議論
https://jr0.org
roggenbuck
·6 か月前·議論
The roads in Davis are great! Super easy to bike and drive. Except for Mace Blvd.
roggenbuck
·7 か月前·議論
I’ve used superset at work this last week, and it’s great! Excited to see what’s next!
roggenbuck
·8 か月前·議論
I’m working on a performance capture library for Python because I often need to know the performance of backend systems I maintain. I frequently build tooling to capture performance and save it for later analysis. I/O operations get costly when writing lots of data to disk and creating good real-time analytics tools takes a lot of my time. I wanted a library that captures real-time performance analytics from Python backends.

https://github.com/jakeroggenbuck/kronicler

This is why I wrote kronicler to record performance metrics while being fast and simple to implement. I built my own columnar database in Rust to capture and analyze these logs.

To capture logs, `import kronicler` and add `@kronicler.capture` as a decorator to functions in Python. It will then start saving performance metrics to the custom database on disk. You can also use the middleware for FastAPI.

You can then view these performance metrics by adding a route to your server called `/logs` where you return `DB.logs()`. You can paste your hosted URL into the settings of usekronicler.com (the online dashboard) and view your data with a couple charts. View the readme or the website for more details for how to do this.

I'm still working on features like concurrency and other overall improvements. I've added a lot since the last time I shared on HN. I would love some feedback to help shape this product into something useful for you all.

Thanks! - Jake
roggenbuck
·9 か月前·議論
I’m working on a performance capture library for Python because I often need to know the performance of backend systems I maintain. I frequently build tooling to capture performance and save it for later analysis. I/O operations get costly when writing lots of data to disk and creating good real-time analytics tools takes a lot of my time. I wanted a library that captures real-time performance analytics from Python backends.

https://github.com/jakeroggenbuck/kronicler

This is why I wrote kronicler to record performance metrics while being fast and simple to implement. I built my own columnar database in Rust to capture and analyze these logs.

To capture logs, `import kronicler` and add `@kronicler.capture` as a decorator to functions in Python. It will then start saving performance metrics to the custom database on disk.

You can then view these performance metrics by adding a route to your server called `/logs` where you return `DB.logs()`. You can paste your hosted URL into the settings of usekronicler.com (the online dashboard) and view your data with a couple charts. View the readme or the website for more details for how to do this.

I'm still working on features like concurrency and other overall improvements. I would love some feedback to help shape this product into something useful for you all.

Thanks! - Jake
roggenbuck
·9 か月前·議論
This was a well written post! It makes me want to create my own forth-like language
roggenbuck
·10 か月前·議論
This is really creative! Very well done. Surprisingly fast too.
roggenbuck
·10 か月前·議論
This is great!
roggenbuck
·10 か月前·議論
Yea, it's fun to know and it can be useful from time to time. I know the alphabet but cannot copy very fast at all.
roggenbuck
·10 か月前·議論
Really great stuff! Congrats on the launch!
roggenbuck
·11 か月前·議論
Yea, I can expand the description to include other features that may cause issues. Here is an example of how counting can cause latency too: https://www.usenix.org/system/files/sec22fall_turonova.pdf
roggenbuck
·11 か月前·議論
> and it would have been great if the default had been safe.

I totally agree here. Safety can and should be from the language itself.
roggenbuck
·11 か月前·議論
Thanks for the feedback! Yea, you're totally right. I'll update the docs to reflect this.

> why not just wrap vanilla JS regex, rejecting patterns including them?

Yea! I was thinking about this too actually. And this would solve the problem of being server side only. I'm thinking about making a new version to do just this.

For a pattern rejecting wrapper, how would you want it to communicate that an unsafe pattern has been created.
roggenbuck
·昨年·議論
[dead]