bgrainger

2 months agodiscuss

https://github.com/L1v1ng0ffTh3L4N/Proof-of-Concepts/blob/ma...

3 months agodiscuss

The promise was that WPF would use hardware-accelerated libraries such as DirectWrite to put text on the screen even faster than GDI+ (using the CPU) could do. The reality turned out to be quite different: multiple layers of abstraction and just plain inefficient WPF code [1] meant that users needed powerful CPUs and GPUs just to get reasonable performance.

[1] https://faithlife.codes/blog/2019/06/improving-wpf-text-disp...

bgrainger

3 months agodiscuss

I first encountered this in Bjarne Stroustrup's 2000 book, _The C++ Programming Language_. As he notes in the introductory material:

> In code examples, a proportional-width font is used for identifiers. … At first glance, this presentation style will seem “unnatural” to programmers accustomed to seeing code in constant-width fonts. However, proportional-width fonts are generally regarded as better than constant-width fonts for presentation of text. Using a proportional-width font also allows me to present code with fewer illogical line breaks.

I switched years ago and would never go back to monospace.

bgrainger

8 months agodiscuss

This feels like a dumb question, but why doesn't Cursor implement that tool?

I built my own simple coding agent six months ago, and I implemented str_replace_based_edit_tool (https://platform.claude.com/docs/en/agents-and-tools/tool-us...) for Claude to use; it wasn't hard to do.

bgrainger

8 months agodiscuss

https://news.ycombinator.com/item?id=45968731

  Why can I not authenticate into Google Antigravity?
  Google Antigravity is currently available for non-Workspace personal Google accounts in approved geographies. Please try using an @gmail.com email address if having challenges with Workspace Google accounts (even if used for personal purposes).

https://antigravity.google/docs/faq

bgrainger

9 months agodiscuss

Completely agree, and I've started writing more Roslyn analyzers to provide quick feedback to the LLM (assuming you're using it in something like VS Code that exposes the `problems` tool to the model).

I also want C# semantics even more closely integrated with the LLM. I'm imagining a stronger version of Structured Model Outputs that knows all the valid tokens that could be generated following a "." (including instance methods, extension properties, etc.) and prevents invalid code from even being generated in the first place, rather than needing a roundtrip through a Roslyn analyzer or the compiler to feed more text back to the model. (Perhaps there's some leeway to allow calls to not-yet-written methods to be generated.) Or maybe this idea is just a crutch I'm inventing for current frontier models and future models will be smart enough that they don't need it?

bgrainger

9 months agodiscuss

Storing issues in a local SQLite database reminded me of Fossil SCM, which natively supports "tickets" as a source code artifact (and which uses a SQLite database under the hood): https://fossil-scm.org/home/doc/trunk/www/bugtheory.wiki.

Submissions

AI-Assisted Breach of Mexico's Government Infrastructure Report

Planning Center is the newest Rails Foundation Contributing member

comments