Live data from Hacker News

Ask HN: What developer tools would you like to see?

news.ycombinator.com

211–220 of 230 posts

Re: Ask HN: What developer tools would you like to see?

#211

3D graphics especially interactive interfaces is still far too complicated, presently needing to be build over layer upon layer of libraries and toolkits. I think a simpler approach will be a good thing to have for developers.

Spline.design is great.

Re: Ask HN: What developer tools would you like to see?

#212
A toolkit that inputs HTML, MarkDown, PDF, or any other "markup" language and separates out the Text, Layers of Markup, Images and Code.

All the markup should then reference the range of the characters in the text being marked.

If the text is edited as a set of transforms, you can then apply the same transforms to the ranges, and in effect, edit any marked-up format.

Having the layers separate makes a lot of things easier.

When you're done, you could flatten things back out into any of the supported formats.

Re: Ask HN: What developer tools would you like to see?

#213
A Reference Counted, Prefix Counted, String library for C.

That is, automatic reference counting of strings, to eliminate manual memory management, and avoid garbage collection.

Counted Strings (with a \x00 on the end for compatibility) solve problems with binary data in the string.

Prefix Counting means that the beginning of the structure is BEFORE the pointer, so that if you just reference the pointer, you get the first character of a "normal" null terminated C string.

Using the "cleanup" attribute support of modern C, it should be possible to make a Defer macro to allow strings going out of scope to be dereferenced, and if their reference count goes to zero, deallocation.

Re: Ask HN: What developer tools would you like to see?

#214

I feel like this must exist and I just haven’t found it, but I’d love a tool that can automate seeding a staging/local db from production. It would need live in a vpc to access the prod db, but then expose itself to access slices of anonymized data that can be used to restore external dbs. Essentially a configurable pgdump that includes the ability to anonymize personal info, take recent slices of data, and serve the…

Maybe you're looking for this: https://github.com/Qovery/Replibyte.

Re: Ask HN: What developer tools would you like to see?

#216
post #132

Earlier quoted context omitted.

The limitations are that these are very plain regexes. I've screwed up a good amount of time doing that, it's not good enough. We need actual structured semantic analysis, the way the compiler / interpreter does it.

This sounds like a great use case for Tree-sitter ( https://tree-sitter.github.io/tree-sitter/ ) GitHub uses Tree-sitter for code highlighting and goto definition, so it already has grammars for many languages

Thanks for the link! This looks interesting. I agree with the parent comment that we need better tools. Perhaps this would be a good starting point.

Re: Ask HN: What developer tools would you like to see?

#219

I don’t have any great ideas. A big one for me would be ‘better/much faster language server for the language I use’ but that’s a lot of work. But if you like working on developer tools, the best way to do it is to find a sufficiently large company that care’s sufficiently much about developer tools that they will be willing to pay you to work on in-house developer tools. This can be much more stable than trying to se…

Do you have any tips on how to find such companies? I've always wanted to work on developer tooling but only ever found one company willing to invest in that.

Any big tech company will invest in developer tooling. E.g. Google has tens of thousands of software engineers. They have internal build systems, internal source control, internal code review, internal code search, and so on. Facebook is similar. Microsoft make and sometimes sell developer tools to be used outside their company.

Re: Ask HN: What developer tools would you like to see?

#220

TypeScript stuff: 1. A tool for debugging TypeScript (in VSCode) that shows the provided and expected types, and how they are different, in a way that is easy to read. Instead of having a bunch of nested paragraphs in plain text, show it in two columns, each displaying how a normal person would write a type declaration. Maybe even use color (highlighting?) to show which parts are different. 2. A tool for VSCode that…

For #2 you can hold CTRL when hovering over a type to expand the type definition. If you hold CTRL+click it will go to the definition.
Post reply on HN