Electron should have never existed and should be cometeñy banned, yeah

Is slow because of both. Using bad languages is one form of bad design itself, in fact.

Too many abstraction layers

We've been using seawater as coolant in the industry for many, many decades. The impact is well understood. Does a datacenter produce as much heat as a nuclear reactor? How much thermal energy do they output?

Classic environmentalists making the acceptable the enemy of the clearly worse.

But in any case underwater data centres make zero sense. If you weren't already convinced by using your brain for 5 seconds, Microsoft proved this a decade or two ago.

If you want easy access to seawater just build it on the coast. There's a reason nuclear power stations are built on the coast and not underwater!

Even nvim will eat up about 5GB of RAM when used as an IDE. MCP alone will use that much of RAM independent of the editor.

Agreed. I use it for coding too. Even using it as a kind of interactive editor is a huge productivity boost. E.g. I was working on some assertions that were all like assert (... |-> a && b && c) (|-> is implication) and I was like "Claude, split the consequent conjunctions into separate assertions " and it did it in about 5 seconds, vs 10 minutes of tedious hand editing.

Being able to find the cause of a bug and being able to build a decent codebase from scratch are definetly not the same

Yes indeed, the cheap models still produce slop. Slightly annoying because I'd love to use them for personal projects, but as you say I can't really justify the cost.

For work though it's a no brainer, given my salary and the productivity boost. At my previous company I sometimes spent an entire day debugging a complex test failure that Claude can figure out in 5 minutes. No exaggeration.

I think that's true for many tools. Programming tools are the one thing that has most advancement because so many programmer are there to improve on them. And even if you don't use it, not knowing about it completely makes it a bit odd. Although most tools I have used to make flamegraph were as easy as just running the program as a argument to another program that tracks the function calls.

I hate these kinds of comments that have no other purpose than to sling shit and start arguments.

Since this is a programming community (and giving you the benefit of the doubt, I assume you're not a vibe coder), you know your argument is nonsense. Writing something in Python doesn't automatically make it slow or use a lot of RAM or whatever. Synapse is shitty because Synapse is shitty. You can write slow and inefficient software in any language, and it feels really tedious to type this out because it's obvious and common sense.

Flame graphs have really only been a thing for the last decade or so. The free tooling for profiling code has been shitty and difficult to understand for most of my career. And most companies aren't willing to pay for it if the product runs "good enough". These days companies lock down their shit so tight that you can't even install an unapproved app no matter how free or useful.

People are dumb

If only lemmy.world didn't ban my accounts.

Don't donate to lemmy.world guys its managed by reddit it seems.

This was awesome! as a huge FP fan, I hadn't heard of Roc. It seems pretty amazing. The systems-level FP language. Can we test it against common lisp and haskell also?

True, but it will still reduce the chance of success to close to zero. If you assume your own users devices are compromised, there is nothing you can do to avoid exposure.

It is so good to see some quality articles shared on Lenmy 😊 more ! Thanks for sharing

I don't understand how this is even possible.

As an OPS guy you know what really grinds my gears? Developers not paying attention to shit like this.

We have a job in production that is a powershell script calling a powershell script calling a java applet. Now you may already be thinking "what is this abomination?" And you're right, but that java application is set to DEBUG. IN PRODUCTION. So every time it runs it generates 1gb of logs.

Do they fix it? No of course not because if it's not broken don't fix it. But Jesus Christ we have people developing without understanding fundamentals like "YOU DONT LEAVE DEBUG ON IN PRODUCTION".

Both matter...

I do some vibe coding using recent affordable models, it's still slop. I guess the better, more expensive models are less sloppy, but 1. I don't have unlimited funds and 2. I kind of hate that everyone is now asking their favorite models to re-invent the wheel. The token money that collectively goes into these projects would be spent so much better on financing established open source projects and their maintainers.

Anyway, even with "good" models and Rust, you'll still get logic bugs which are usually far easier to actually exploit than memory corruption (for which going beyond crash/DoS to RCE often requires adapting to the specific build of the target, and generally a lot more time and effort)

A lot of these bot requests come from what seems to be compromised hosts turned into scanners and residential proxies.

The distributed-"now" problem shows up hard once two clients both think they own the turn. Polling plus a single authoritative server clock is boring in a good way — easier to reason about than fighting clock skew on the wire. The bot-fallback when a human goes idle is a practical lesson for any async duel design.

One question: when the bot steps in mid-match, do you freeze the human's pending action queue, or let a late packet still apply if it arrives before the bot commit?

Freaking good article. Super in depth with good explanation and analogy. Thanks for sharing.

Not if your threat model is "bots that scan the internet for vulnerable installations of X".