4 ms·
We built LLMs so that you can express your ideas in English and no longer need to code. Also, English is really too verbose and imprecise for coding, so we dev
by lich_king 7mo ago
We built LLMs so that you can express your ideas in English and no longer need to code.
Also, English is really too verbose and imprecise for coding, so we developed a programming language you can use instead.
Now, this gives me a business idea: are you tired of using CodeSpeak? Just explain your idea to our product in English and we'll generate CodeSpeak for you.
- theK 7mo agoDamn, I am the product A-GAIN?
- amelius 7mo agoCOBOL?
- souvlakee 7mo agoNo joke. I'm 100% sure that if it's successful, we will find CC's skill to write specs for CodeSpeak.
- lucasoshiro 7mo agoYeah. It's hard to express and understand nested structures in a natural language yet they are easy in high-level programming languages. E.g. "the dog of first son of my neighbour" vs "me.neighbour.sons[0].dog", "sunny and hot, or rainy but not cold" vs "(sunny && hot) || (rainy && !cold)". In the past maths were expressed using natural language, the math language exists because natural language isn't clear enough.
- lich_king 7mo agoDid you mean AbstractNeighborDispatcherFactory?
- Sharlin 7mo agoI'm sure that this time the language will be simple and English-like enough that execs can use it directly, similarly to COBOL and SQL.
- mosburger 7mo agosssssh! if this catches on we can keep our jobs! (j/k, mostly)
- kevin_thibedeau 7mo agoThe idea is this would be a kind of IL for natural language queries. Then the main LLM isn't dependent on quirks of English.
- cratermoon 7mo agorelevant Dijkstra https://www.cs.utexas.edu/~EWD/transcriptions/EWD06xx/EWD667.html https://www.cs.utexas.edu/~EWD/transcriptions/EWD06xx/EWD667... "In order to make machines significantly easier to use, it has been proposed (to try) to design machines that we could instruct in our native tongues. this would, admittedly, make the machines much more complicated, but, it was argued, by letting the machine carry a larger share of the burden, life would become easier for us. It sounds sensible provided you blame the obligation to use a formal symbolism as the source of your difficulties. But is the argument valid? I doubt."
- ramon156 7mo agoI'm really glad random HN commenters know it better than someone that built a language that has been used in thousands of products.
- awkwardpotato 7mo agoStandard appeal to accomplishment, past success does not guarantee future success... especially on this joke comment
- allthetime 7mo agoKotlin is generally considered a bit of a dud in the modern programming language space.
- prophesi 7mo agoIt's a blessing when you're in the native Android / React Native / Flutter space.
- allthetime 7mo agoTrue. Not having to write Java for native modules anymore makes me really happy. Shame they haven’t replaced gradle yet though
- hitekker 7mo agoI reckon this comment from 6 years ago predicts Kotlin's fate https://news.ycombinator.com/item?id=24197817 https://news.ycombinator.com/item?id=24197817 I consider it prophetic. My gut says Kotlin is great for individual developer experience. But I never heard or saw credible reports on the Total Cost of Ownership, e.g., Kotlin engineers hiring, swapping out on a team.
- bschmidt1 7mo ago[dead]
- anthk 7mo agoEven Noble Prize owners made huge mistakes after the prize.
- dragonelite 7mo agoSomewhere Dijkstra is laughing his ass off.
- devmor 7mo agoThat seems like it could lead to imprecise outcomes, so I've started a business that defines a spec to output the correct English to input to your product.