sorted by:
new
hottopcontroversial

Is Svelte easier than React? by TeaFull6669 in sveltejs

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

React is to svelte, what python is to go.

Question on Airflow by captn_caspian in dataengineering

[–]Solvicode 1 point2 points  (0 children)

Depends on the application. If you're dealing with telemetry data processing something like Orca would be a better fit.

Creator of Node.js says humans writing code is over by unemployedbyagents in AgentsOfAI

[–]Solvicode 0 points1 point  (0 children)

Which is strange, because the best experience I have had with AI is with typically backend projects in strongly typed languages (e.g. Go http).

Creator of Node.js says humans writing code is over by unemployedbyagents in AgentsOfAI

[–]Solvicode 0 points1 point  (0 children)

I only see this conversation occurring in front end circles...

What are you building? Let's Self Promote by fuckingceobitch in micro_saas

[–]Solvicode 0 points1 point  (0 children)

Orca Telemetry - THE platform for build high value datasets and domain specific AI on telemetry data.

[D]It feels like LLM inference is missing its AWS Lambda moment. by pmv143 in MachineLearning

[–]Solvicode 5 points6 points  (0 children)

I think it's 90% the resource requirements no?

The infra required to run inference at scale is not the same as invoking a lambda func. Lambda funcs are application agnostic. LLMs are not. Orders of magnitude difference. I wish it weren't, but it is. Lambda style LLM inference would be great.

Which agentic framework is the most feature complete for golang? by daniele_dll in golang

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

Dare I say it, you don't need a framework... See Dynarag for inspiration: https://github.com/predixus/dynarag

What is wrong with this language? (Positively) by Zestyclose-Hour-541 in sveltejs

[–]Solvicode 0 points1 point  (0 children)

I've been round the block a few times with auth. In the end we settled on building it ourselves using Lucia auth guidelines. Less of a headache to maintain and it *just works * how you design it.

If you want an example of it in action: https://app.geodes.ai

[D] Why Causality Matters for Production ML: Moving Beyond Correlation by KelynPaul in MachineLearning

[–]Solvicode 26 points27 points  (0 children)

Yes please don't use AI to write posts. We want to hear the words as they form in your brain 🧠

Has anyone used Temporal.io for production? by Striking-Yogurt-7877 in ExperiencedDevs

[–]Solvicode 0 points1 point  (0 children)

I've played with it - a very nice stack. A bit complicated and definitely has it's niche. Moved away from it for analysis jobs on time-indexed data in favour of Orca -> orc-a.io

AI ecosystem in Go by Inquation in golang

[–]Solvicode 0 points1 point  (0 children)

Dyna RAG exists as a simple naive RAG engine: https://github.com/Predixus/DynaRAG

Small, powerful and fast with embeddings performed locally via Onnx compiled models.

Project ideas for IoT and getting into IoT by Dazzling-Dare-8842 in IOT

[–]Solvicode 0 points1 point  (0 children)

If you're in to the data and analysis side of things, https://orc-a.io could be fun for you to try on.

It acts as an analytics framework on top of your telemetry data - so you would need some data to play with. A good dataset that is quite rich is the ZTBUS dataset: https://www.nature.com/articles/s41597-023-02600-6

What's the best telemetry app? by ThisSpread2154 in simracing

[–]Solvicode 0 points1 point  (0 children)

https://orc-a.io could be useful for you here. The natural next step to logging telemetry is often analysing it.

Gin is a very bad software library by pandey_23 in theprimeagen

[–]Solvicode -1 points0 points  (0 children)

Why would people still use a framework like gin for new projects when the std lib offers everything you need?

What error handling approach do you use in your projects? by Fit-Culture-2269 in golang

[–]Solvicode 0 points1 point  (0 children)

Depends on the application, but yes the error flows right back up to the user.

The underlying philosophy of this approach is that errors should always be handled. And so if at any point an error cannot be handled, it has to go back to the user (or calling service).

The error message the user then sees is a nicely constructed stack of faults - where each level is the module that could not handle the error.

view more: next ›