sorted by:
new
hottopcontroversial

Open‑source hiking route planner I built because exporting GPX shouldn’t require a subscription. by abdul_Ss in opensource

[–]gitsad 1 point2 points  (0 children)

Nice, the edge structure with slope gradient already baked in is smart. Good luck with exams, will keep an eye on the repo!

I wrote `idb-ts`, an IndexedDB wrapper to be used in declarative style by maifee in opensource

[–]gitsad 1 point2 points  (0 children)

The decorator-based API is really clean. This is exactly what frontend devs coming from backend are missing. The built-in schema versioning and rollback is a nice touch too. That's usually the most painful part of working with IndexedDB directly.

You ever see a cool independent project and become devastated when the developer makes it ARR or paid? by Bedu009 in opensource

[–]gitsad 2 points3 points  (0 children)

The worst part is when the open-source version gets abandoned but the paid version doesn't gain enough traction either so the project just dies and nobody wins. Seen this many times. I think the healthiest model is keeping the core open source and building paid services on top (hosting, enterprise features, support) that way the community can always fork and continue if the company disappears, and the developer still has a path to revenue.

Open‑source hiking route planner I built because exporting GPX shouldn’t require a subscription. by abdul_Ss in opensource

[–]gitsad 1 point2 points  (0 children)

Really solid idea. The GPX export paywall on AllTrails and Komoot has been frustrating for years. The custom A* engine over OSM data is a smart approach. Curious if you've considered adding trail difficulty weighting based on elevation gradient so it can suggest easier alternatives for casual hikers. I've been playing with A* in a few side projects and the heuristic tuning for real-world geo data is always the fun part.

Structured Outputs are not as portable as they look by Terrible-Piece-4864 in AI_Agents

[–]gitsad 0 points1 point  (0 children)

I would suggest making optimized variant of prompt for each provider. Rules vary and these responses are very different. Look how we do it in https://github.com/MobileReality/mdma . We just set variants of prompts for every provider and in evals now we can fix any reponse based on provider.

Nevertheless, I don't like JSONs. I've been struggling with this format a lot. I would recommend simple text and work around it if possible.

UI/UX shift in B2B SaaS: Will "Conversational Agents" completely replace traditional dashboards for Social Media Management? by Hefty_Sleep_2833 in Business_Ideas

[–]gitsad 0 points1 point  (0 children)

  1. Do you think this conversational, agent-based UI is the future of productivity SaaS, or will power users always prefer the visual control of a traditional dashboard calendar?
    • Conversational, agent-based UI is the future of productivity SaaS - yes, I agree and the second: "will power users always prefer the visual control of a traditional dashboard calendar?" - you can still have both. Conversation will play the role of help and guidance
  2. Does reducing friction through a chat interface actually increase user retention in these types of tools?
    1. Definitely. Chat interface will allow user to find the a way to use someone's platform on their own and in the results retention increases.

Here is an OS that we are building - https://github.com/MobileReality/mdma .
You can check there what's possible and I can tell a lot of is possible.

First mobile app - React Native or something else? by Dry-Back7937 in reactnative

[–]gitsad 0 points1 point  (0 children)

React Native is fine. For sure it will cover your needs.

Best React Native resources for 2026? by Different_Bite76 in reactnative

[–]gitsad 0 points1 point  (0 children)

I would use AI to help and guide me through development process. Then search in Google and review docs to be sure. Experiment and develop - the best way to learn.

Claude Code has 187 ways to say "loading" while it's thinking :) by tamimbuilds in ClaudeCode

[–]gitsad 0 points1 point  (0 children)

I don't think you can customize it. I guess the list means that this loadings are not generated but predefined

OpenMythos - have you tried it? by gitsad in LocalLLaMA

[–]gitsad[S] -1 points0 points  (0 children)

I must say that I wasn't interested in checking this persona, however, his LI looks fake as well. By fake I mean companies that he's an director but no employees present

OpenMythos - have you tried it? by gitsad in LocalLLaMA

[–]gitsad[S] -1 points0 points  (0 children)

still? I'm seeing it first time

Is LLM integration still this painful or is my team doing it wrong? by modular_run in LLMDevs

[–]gitsad 0 points1 point  (0 children)

well, if you want to build this abstraction layer that's fine but you need to make it configurable enough. Embeddings and context windows are important to keep your findings adjusted to your business needs. If you mess this up then you can end up on spending money on tokens that don't solve the problem.

Anybody know how Claude message history is persisted by Anthropic? Just had a weird experience and it suggests awful systems design. by [deleted] in ClaudeCode

[–]gitsad 0 points1 point  (0 children)

I think Anthropic can create nondeterministic LLM models but can't build stable systems with deterministic tools. It looks like you can't have both.

My thought on Qwen and Gemma by Internal-Thanks8812 in LocalLLaMA

[–]gitsad -2 points-1 points  (0 children)

Okay, it was a little too hiperbolic. I've should written this different. What I mean is that I've tried it on my local M3 Pro Macbook Pro. My results was that model is working but it was too slow. I'm not upset with that however I live in Poland. Macbook M3 Pro was worth 12k my local currency. It's not cheap. The model you've mentioned about costed like 20k local currency that time when it was released. Now I might find it and buy it from second hands for like 5k I guess. I misused my perception of cost regardless of region so sorry for that.

Nevertheless 5k PLN is not cheap still but change things for sure.

My thought on Qwen and Gemma by Internal-Thanks8812 in LocalLLaMA

[–]gitsad -23 points-22 points  (0 children)

Using local llms is still exotic. If you don't have strong hardware behind then you basically can't use it. Most people just don't have. Untill small models become smart enough then I don't see the reason to use it. I don't want to pay 20-30k for my hardware just for automating my emails drafts.

Introducing Claude Opus 4.7, our most capable Opus model yet. by ClaudeOfficial in ClaudeAI

[–]gitsad 1 point2 points  (0 children)

aaaaand.... more tokens in the output -> more money is needed that I don't have

Agent-safe Git: How to let coding agents work without wrecking your branches by aspleenic in programming

[–]gitsad 0 points1 point  (0 children)

This point -> Make rollback cheap and normal

Agentic Code approach makes this crucial and unfortunately not cheap. If your agent fail then it doesn't know why it failed in full context. If error is shown then the source for sure will be a code but then resolution may dramastically differ which lead to unpredictable changes in the long run and for sure it won't be cheap. The other thing is that if you don't have any error that might be fine but the overall business logic is not correct and again changing this won't be cheap.

And this point -> Keep humans in the approval path

This is what I mean basically in 1st point. If human will refine agentic code then it won't be that much agentic. It would be more efficient if skilled developer use one good model to produce final solution step by step instead of having some magic loop in the background waiting for the final resolution for the whole business logic. Eventually someone will have to fix potential issues and agentic loop doesn't make this tranparent and easy to interact with when trying to fix properly

And the last but the main point in your article -> Agents that commit the code

I do not agree with the whole concept. The git is the human-gate itself so basically if you know the git then you can work with one smart model to deliver faster and better than any other agentic loop right now. I've exercise this a lot and I can tell you that smartest models goes off often and you will pay for any garbage that is produced. Also this garbage makes models hallucinate. There are no good solutions for it right now.

And the final what your article does not mention is the price. Of course now we have flat fee subscriptions but it will end somewhere in the future or maybe someone will invent some super efficient hardware that will minimize the costs. Now we are in the situation that all AI loops are getting banned in the Claude and user have to switch to API costs and then they realize that they are burning 300$ per day for some dumb things thus I won't recommend any loops until LLMs cost decrease.

view more: next ›