4 ms·
Lmao flogging off wrappers over things other people have built is "hacker spirit" or whatever now is it? This place has gone completely to shit.
by BigJono 2y ago
Lmao flogging off wrappers over things other people have built is "hacker spirit" or whatever now is it? This place has gone completely to shit.
- thiht 2y agoAs an example jQuery literally started as a wrapper lib around JS features, and it became so influential over time that tons of features from jQuery were upstreamed to JS. Yes, wrapping stuff to give a different developer experience contributes to new ideas, and can evolve into something more.
- darepublic 2y agoIt's a double edged sword. I suppose when I started my career I would just take the popularity of something as proof positive it was truly helpful. At this point I am a lot more cynical having gone experienced the churn of what is popular in the industry. I would say jQuery was definitely a good thing, because of the state of web at the time and the disparity between browsers. More recently, and on topic, I am dubious about langchain and the notion of doing away with composing your own natural language prompts from the start. I know of at least some devs whose interactions with llm are restricted solely to using langchain, and have never realized how easy it is to, say, prompt the llm for json adhering to a schema by just, you know, asking it. I suppose eventually frameworks/ wrappers will arise around in-browser ai models. But I see a danger in people being so eager to incuriously adopt the popular even as it bloats their project size unnecessarily. If we forecast ahead, if LLMs become ever better, then the need for wrappers should diminish I would think. It would suck if AI and language models got ever better but we still were saddled with the same bloat, cognitive and code size, just because of human nature.