Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
adamddev1
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
61.
▲
by
adamddev1
3mo ago
I still think internal tools are kind of in a category closer to end-user applications. They are limited in how widely they are used, and therefore they don't have to be as solid as say libraries used by millions.
62.
▲
by
adamddev1
3mo ago
I ask because I think there's a huge difference between the two. People making end-user applications might think they can tolerate more errors and bloat from AI. Just because they can get away with doing that with AI (and that's d
63.
▲
by
adamddev1
3mo ago
Are you writing code for end-user applications, or for tools or libraries that other stuff is built with?
64.
▲
by
adamddev1
3mo ago
Great article. Yes, often what's needed are better (rock-solid) abstractions that we can manipulate around quickly and confidently (think Abelson/Sussman SICP style), not a machine that can take good guesses at piles of spaghetti
65.
▲
by
adamddev1
3mo ago
Yes, I agree. I'm just trying to be charitable for the sake of the argument. I think it's better to make nothing with AI.
66.
▲
by
adamddev1
3mo ago
In this whole discussion of what can be done with AI, I think a lot of people are missing the distinction between: A. making consumer end-user apps, basic enterprise applications (making end products) B. making tooling, libraries, languages
67.
▲
by
adamddev1
3mo ago
The author talks about how Haskell needs to catch up to stay relevant in "the AI era." > That means taking AI seriously as a first-class user of the ecosystem. Honestly for me any time a language or a tool markets itself as &
68.
▲
by
adamddev1
3mo ago
I think the big thing is that Lisp is (aside from mutable variable assignment) basically all declarative, rather than the imperative paradigm. Even without static types, and even allowing macro craziness, there's just such a stronger b
69.
▲
by
adamddev1
3mo ago
That sounds like people who don't understand anything about the messiness at the boundaries of the program. Just because there's a type defined, it doesn't mean that the data from the outside world will fit that type.
70.
▲
by
adamddev1
3mo ago
I found https://surge.sh to be a nice version of this kind of thing. Just go into a folder and type `surge` and there you go.
71.
▲
by
adamddev1
3mo ago
Now I'm just waiting for DependentTypeScript :-)
72.
▲
by
adamddev1
3mo ago
I'm a Haskell and FP nerd as well. I just meant the argument and the popularity inside the JS/TS world, which is fairly significant. I think the world is a better place because of the widespread adoption of TS over JS.
73.
▲
by
adamddev1
3mo ago
Remember when people would argue about how types weren't worth the effort? I love TypeScript, if nothing else for how it's been able to popularize types.
74.
▲
by
adamddev1
3mo ago
It's a fork of Gitea. I am very happy with it.
75.
▲
by
adamddev1
3mo ago
Self-hosted. It runs great on a tiny VPS with other services. But I did have to get a cheaper Hetzner server (5 Euros-ish for 4GB RAM) to run the runner. Forgejo feels like a refreshing blast from the past. No intrusive AI cramming. The Web
76.
▲
by
adamddev1
3mo ago
Excellent anecdote. I'm not sure if you're making a judgement about their behavior at the team event. I'm an English native speaker, new in Germany, and learning German. I personally find it really annoying and awkward when o
77.
▲
by
adamddev1
3mo ago
I'm done. Moving to Forgejo. It's wonderful and everything works better. Seriously like everything is instant when you click around, and CI with a runner works beautifully. (The documentation for setting up the runner could be a t
78.
▲
by
adamddev1
3mo ago
What a beautiful website.
79.
▲
by
adamddev1
3mo ago
It would be nice if they would at least say __unintelligable__ when they couldn't get things, but alas. I also notice it with YouTube auto generated subtitles and translations. They misrepresent SO much.
80.
▲
by
adamddev1
3mo ago
These AI Note-Takers can also mangle the summaries. A few weeks ago I read anecdotes here about a doctor getting completely wrong information about a patient, and a manager getting upset because he was depending on a summary of something a
81.
▲
by
adamddev1
3mo ago
I agree 100%. I was just trying to say people can sort of get away with more, or justify it easier.
82.
▲
by
adamddev1
3mo ago
That's why I say, just don't use LLMs. I think conceptualizing and refining the abstraction is the essence of the beauty of the craft and progress.
83.
▲
by
adamddev1
3mo ago
Of course Windows is garbage. But this is the sort of defeatist argument that always shows up among both AI optimists and places where corruption is rampant. Corruption and incorrectness is established as an inescapable baseline, and then
84.
▲
by
adamddev1
3mo ago
exactly, it seems like people run away when a tool becomes heavily AI developed.
85.
▲
by
adamddev1
3mo ago
Please correct me if I'm wrong, but aren't AI agents replacing the coding mostly being done on the outer layers of development? I mean, end user applications, apps, dashboards, business applications? On this "outer crust"
86.
▲
by
adamddev1
3mo ago
Do you mean that to implement the same features, the agents write 2-3 times as much code as a human would write before?
87.
▲
by
adamddev1
3mo ago
What's the "tiger book?"
88.
▲
by
adamddev1
3mo ago
I thought this was about writing proofs with RPG the programming language and I was intrigued. To make it clear that it is with an RPG (role playing game) it needs an "an" in the title.
89.
▲
by
adamddev1
3mo ago
There's a lot of good descriptions and observations on this article. But I don't like this language that just assumes we all use AI, we've all pulled away from the code. It all seems to be part of the collective brainwashing
90.
▲
by
adamddev1
3mo ago
Weird. I remember hearing about how one of they key markers for longevity was exposure to heat and cold.
More ›