wannabe44

Google docs fixes all grammatical mistakes.

Only real difference is that `fold` is denser. Both require prior knowledge to understand in their respective paradigms.

Adding numbers like this is not common in real world code. Now let's say instead of adding x, you have too look up X in a cache with an additional "type" param and update a metric of cache hits (or misses). You have to define a free function to keep your fold readable and understandable. In for loop it's much easier to understand.

You're underestimating web developers.

This. I don't want your browser engine to use all my cores. I want the rest of my cores to be compiling C++.

What is /r/pcj? In any case, memes start due to real world examples.

I wouldn't have any confidence on a car which invokes coreutils in any manner. Too much surface area for embedded systems.

> `fold` is awesome and super useful. It's the easiest and most convenient way to turn a collection into a single value.

You will eventually learn about something called "for loop", and it will be nice.

Beside the license thing mentioned, rust folks are obsessed with an idea of memory safety to an extent of discarding every other value in programming. To the extent of considering other choices "immoral". This manifests in their disproportionate initiatives of rewriting otherwise fine programs. Of course this doesn't include copious amounts of unsafe in popular libraries because can't leave any benchmarks defeated. But somehow Go is sinful because multiword data races are theoretically memory unsafe (a property which has led to zero (0) CVEs). This may also be the result of jealousy that something plebian like Go became more popular than their perfectly designed language.

Let's not mention other aspects of security, such as the recent supply chain issue, or the old story of the serde maintainer shipping a binary blob just because...

I always advocate having custom-built docker images for CI, periodically refreshed for security fixes. CI should not run more than few seconds over the standard time to run the same thing from a dev machine.

However, other people around me are fine with apt installs and pip installs from global mirrors in every CI run. So I may be just autistic.

At least something they don't claim to automate with AI. Apparently Anthropic acquired stainless for $300M instead of vibing it.

For many people a beautiful language is which looks beautiful, as opposed to one which reads beautifully.

Thanks Mr. Steve not Jobs for outsider information.

The friction between coming up with an Idea and implementing it is a feature in most corporates. Otherwise managers will be too focused on creating shiny slides and marketing nonsense - which is happening with AI.

Only ways to rise in a UBI society where AI is supposed to replace intellectual work is crime and prostitution. Smart people who want better lives than the average will have to get into crime.

Begin, Muse, when the two first broke and clashed, Alex lord of data labellers and brilliant LeCun.

The masculine urge to quit the industry amid this costly-slop-machine psychosis...

From a cursory search, this woman looks credentialed and worked at many FAANGs. How can someone with that pedigree not understand a prompt isn't 100% followed to the letter?

Maybe the emails weren't worth it? I have little to bother if most of my emails go away, especially if I am switching companies every few years anyway.

> The overlap between what you learn from studying people who thought the sun was a chariot drawn over the sky by magic horses and that the Sahara was caused by some idiot driving them wrong, and what you need to know to deal with a highly connected globally integrated supply chain, is not exactly zero.

The classical epics speak of heroism and virtue. Understanding certain human morality which is timeless is very useful.

It's not like education in practical domains like CS or supply chain are highly efficient either. Something which forms your outlook is important. While most of the modern literature is not that influential, kids should read the Iliad, Odyssey and Havamal.

People don't understand exceptional control flow. They think they have to catch them at every point, instead of using them as intended (having a central boundary of error handling where you have enough context whether to retry or abort the operation). So they think Go errors are better.

With exceptions you can

1. Set exception breakpoints.

2. Have real stack traces.

3. No need to write 3 lines of boiler plate every 1 line of code which interacts with outside world.

Ironically this is the case in Go's niche - devopshit, cloud webshit - where the boilerplate error handling makes even less sense since because

1. You are making a network call or OS interactions every 2 lines which can err

2. The consequences of an unhandled exception are actually quite less severe. At worst your request will 500 or the application will restart - which is a consideration you can't escape in these environments.

3. I have seen indiscriminate error handling written by substandard developers which simply concatenates the full wrapped error string to API, leaking full details. At least with exceptions, you can designate different types of exception for 404s vs ayth errors vs bad requests vs Internal errors, and have a central handler which filters out. In go theoretically you can do this, but I have never seen someone utilize errors.As over stringy error handling.

I like Go - it has nice stdlib, nice compiler and runtime, and actually dared to innovate away from the fat-ass LLVM monoculture and made green threads popular. But error handling and uninitialised values sticks out like a sore thumb. It's impossible to read code which does many API/network/OS interactions.

I want to ignore Naysayers in the thread but even SOTA LLMs write boilerplate like it is Go 1.14. I have to constantly nudge it to use newer language features properly, even if it's also in my rules/ CLAUDE md files.

I like to know the average age of accounts which upvoted this post.

Oh it is not returning full tool schema. You can't cut down that much by serialisation alone.

And urban civilizations eventually collapse?

I am not going to trust a single number thrown by these AI hustlers written in that salesman voice.

Leave alone 97%.

> Your agent calls 20 tools. Each returns 500-3,000 tokens wrapped in {"content":[{"type":"text","text":"..."}]}.

This is a problem with your tool design. Most MCPs are fully vibe coded without any thought about tool selection.

> On a 128K context window, that's 30-55% gone. Not on work. On syntax.

Tool output is not "syntax" you donkey clanker.

Again, use the code approach, let the LLM filter out the JSON using tools. This TOON thing is just vibes. Most of the time your tool output should not even be JSON. It should be well formatted markdown. In cases where it's large structured data, your LLM should have tools (code / jq) to dissect it. So TOON is pointless.

I presume they organized some cringe dances and cultural programme when GP visited, which might have led the GP to conclude that these people live great WLB.

The RCE vulnerability drama made me never touch it, in any case.

I come up with at least two ideas like this every time I sit down in the toilet to poop.

> great work life balance

Oh dear

No, they're just trained to impress the C-suite motherfuggers with dense vocab.

That makes it sound like a PM problem. The hardest part is building the mental model which doesn't crumble. I have worked with humans who had the same failure modes as LLMs.