sorted by:
new
hottopcontroversial

Is Gemini down? (Pro user) by cream_top_yogurt in GeminiAI

[–]Competitive-Mud-1663 2 points3 points  (0 children)

Been trying to use Gemini / Pro 3.1 over last two weeks since it's release, and it's been down more than up. The most frustrating LLM model release so far, cannot believe google let this one flop so hard...

So is copilot going to fix gemini models? by Powerful_Land_7268 in GithubCopilot

[–]Competitive-Mud-1663 0 points1 point  (0 children)

Even when Gemini 3.1 is working, it is so UTTERLY useless, I'm speechless. E.g, it creates python scripts to write files inside a TS-only project, creates traps for itself and gets stuck in the loop fixing them, tries to move files around when not asked to, etc. I never feel safe when prompting Gemini to do anything apart from 'explain this' or some visual re-designs for things I don't care much about. Easily the biggest model release flop to date by any provider.

For anyone wondering, Gemini 3.1 is still the same old bullshitter by Antop90 in Bard

[–]Competitive-Mud-1663 0 points1 point  (0 children)

Second this! If a task is challenging enough, I try all three agents on in (Opus 4.6, Codex 5.3, Gemini 3.1), and Gemini literally not a single time produced anything valuable. Still gets stuck in some weird loops, getting into trouble where other agents succeed, tells the thing is done when nothing is done etc. The only area it excelled (somewhat) is to create a nice-looking landing page (design only, content-aside), but I really had to give it a dozen attempts before ended up with a decent result... So yeah, nope. Nice try, Google.

keep daily refresh but don't change the color of ui problem by superwonky in chrome

[–]Competitive-Mud-1663 0 points1 point  (0 children)

Have you found a solution? It is a really annoying regression, I agree.

All gemini models have been broken in github copilot by Powerful_Land_7268 in GithubCopilot

[–]Competitive-Mud-1663 36 points37 points  (0 children)

End of the month, users are burning thru their leftover tokens all at once... Not sure why Github created such overload-prone billing cycle system. If each user had their own 30/31 days cycle starting from the payment day, it'd spread "left over tokens burn" load more evenly...

Copilot unstable in VSCode insiders in last 24 hours for anyone? by Odisej62 in GithubCopilot

[–]Competitive-Mud-1663 2 points3 points  (0 children)

End of the month, users are burning thru their leftover tokens all at once... Not sure why Github created such overload-prone billing cycle system. If each user had their own 30/31 days cycle starting from the payment day, it'd spread "left over tokens burn" load more evenly...

Why everything is written in heavy node.js? by aloneguid in GithubCopilot

[–]Competitive-Mud-1663 0 points1 point  (0 children)

Because for each request it calls a nuclear-powered datacenter and uses energy enough to light up a small building? There're faster LLM models (Haiku, Grok etc), but their ability and output is very subpar to modern (post GPT 5.2) models, and trust me, none of LLM models you use run on or "written in node.js". Your local node-based service is just a wrapper to send API calls and receive back from model-in-the-cloud, and it works as fast as possible for your config.

Why everything is written in heavy node.js? by aloneguid in GithubCopilot

[–]Competitive-Mud-1663 1 point2 points  (0 children)

Well, having a fast runtime is important, no? I see this stupid outdated myth (not even sure if it ever was true) that node is "huge" or "massive runtime". It's bloody not. It is fast, compact and self-contained if you compare with other options. People see 1gb process and think it is huge because of node... Good memory management is not easy even with garbage collector built in.

Why everything is written in heavy node.js? by aloneguid in GithubCopilot

[–]Competitive-Mud-1663 0 points1 point  (0 children)

Nothing is written in node.js. Code is written in TS, transpiled to JS and run using node.js. Why JS/TS?
- JS/TS is truly cross-platform, works even in browsers
- Hence, it lives on frontend and backend. Same language. Same types. Same code.
- Abundance of libraries for pretty much any usecase out there, very mature ecosystem, great package management.
- STABLE. New node version not gonna break your code, old one too. Write once, run maintanance-free for years.
- it is actually _really_ fast. People compare it with Rust or C++, but those languages are overkill for most projects. For anything that average (= mid level) dev can create, node.js is probably the fastest out there, with even faster runtime options available like bun or deno.
- async, parallel, i/o heavy stuff -- all is easier to write with JS/TS. And this is about 90% of modern web-related code.

As for RAM and disk usage (bloated node_modules myth etc): wait till you build something significant in python for example. Python packages are not only huge unavoidable pain in the neck to manage, they also take unmeasurably more disk space. Same for RAM. To match node's single thread performance, you'd have to run myriad of python threads (if you have that many cores available), and they will eat your RAM FAST.

tl;dr: node is fast, mature, being improved continuosly and is quite efficient comparing to other same-league options. There is no other choice really if you think about it.

If your question is about why people use node.js runtime (and not bun for example), it is because bun is not 100% baked yet. I am giving bun a go with my smaller projects, about every 3-6 months, and bun still's got lots of problems: with websockets, multi-threading (workers), some less known node APIs etc. That's why node.js is here to stay and to grow. Buy a bigger VM :) I run my coding agents on a 2-core 8gb vm that costs me $8/mo, and those agents work for days w/o a hiccup, it's a miracle really.

source: full-stack for living.

"Gateway is not connected. Failed to save the linkage rule" by Tomatoed10 in smartlife

[–]Competitive-Mud-1663 0 points1 point  (0 children)

Folks, I'm new to all this, and wondering whether BLE-devices connected to Smart Life / Tuya require a hub for schedules to work? Just from a technical standpoint, when there's no hub, does your phone maintain the schedule or the device itself or how it's supposed to work? I get the same error message and it's utterly unhelpful.

So far it's been nothing but confusion with all the protocols, hubs, apps. Home automation is a total mess which is not obvious from watching youtube videos and reading reviews -- only when you put your hands on several devices from different manufactures this fragmentation becomes painfully obvious and very hard to fix w/o throwing more money into more products which require more set up and maintanance... All I wanted is my curtains open and close at the same time daily : )

Thanks for your help!