624 karma · joined March 6, 2015
I'd be curious to know whether Rust developers believe Visual Studio is the right place for Microsoft to invest Rust specific coding capabilities.
LSP works best when using dependencies that are already compiled locally, but if all source is available, yeah... I still don't have a solid answer on which one is best.
But again, for already compiled dependencies (think Java bytecode), without LSP configs, the agent is likely going to attempt to extract binaries from JAR files, use grep and javap, and potentially attempt to decompile the .class files.
However, one annoying thing for TOML was the lack of schema, and the reliance on JSON Schema for that. Which I decided to tackle years ago when I started the TOML Schema project. In the past few months I leveraged code agents to take to the finish line and got something compelling: tomlschema.org
Their video demo was posted 13 hours ago, and it only has 38 views as of the time of this post.
The post on HN is 4 hours ago.
This is it.
Also, I may have already started looking into it, but now this other person just wasted money.
Probably the author
We could think that this is a conspiracy from TV manufacturers and streaming platforms, but it's just shrinkflation at its best (aka enshittification) for reduced cost in building remote controllers.
So far, we are still lucky to have alternatives like Universal Remote Controls, but how long will they last?
"Your job is to not mess up."
Also applicable to any corporate job.
I myself had preferred to use MySQL because it was so simple and easy to get started and using it.
Until I learned how many MySQL databases were configured without user/password and many instances were reachable over the internet.
Then, eventually products started to move towards "don't even ask the user to set a password, otherwise they will set a stupid password" and just generate the password during installation. This made the user think more before saving that password or changing the password to something less stupid. But better than all that, liability was no longer with the software maker.
I wonder if anyone has tried to build an LLM that has actual built-in types of prompts: system prompt, user prompt, and data prompt.
It comes down to accountability, IMO. We tend to be forgiven to humans because we are humans too and we know we, humans, make mistakes, and these can have serious consequences.
When a human makes a mistake, they are immediately accountable, and therefore judged and forgiven (or not). When technology makes a mistake, who's to blame? The CEO? The software developer who wrote the code? The tester? The architect?
Yes, we want technology to be an order of magnitude safer than humans for this reason, because we know that, given the current way our judicial system works, when technology makes a mistake, no one is held accountable.
Yeap. Most users want someone else to think for them. Not just "something" (AI). Having a vision on what works best (design) is still, for the time being, a human task IMO.
> Several times a day I'll prompt regular Claude chat to "Clone x/y from GitHub and tell me how Z works".
Still highly dependant on one's access to SOTA AI models (availability and funding). Most people praising LLMs publicly for this sort of use case, are the ones with unlimited access to tokens / AI credits, or simply with a lot of money to burn.
But reality is that between using one's limited employer-sponsored quota of tokens to do their 9-5 business logic coding maintenance job, versus exploring 3rd-party software as end-users, I am sure of which one their managers will prefer.
I believe it will eventually happen, whether with SOTA local models on highly capable local hardware, or super cheap inference APIs... or both.
I strongly suggest watching some of their talks from JVMLS (JVM Language Summit), especially the ones from Brian Goetz and Mark Reinhold.
https://www.youtube.com/playlist?list=PLX8CzqL3ArzUOgZpIX6Gs...
But when it comes to troubleshooting and debugging, especially business logic, I image based on my past experience working on insurance and banking systems, that I would still rely on an IDE to dive into the code.
I have a hunch that his tweet will not hit the demographic of 9-to-5 developers working in maintenance of boring business systems.
And I hope it stays like that