desumeku

Why would you ever do opts.URL instead of opts.FooService.URL or opts.BarService.URL? What does ambiguity and imprecision gain you here when you can just write out from which struct you want it from? I don't even know why opts.URL would compile, it's completely unstated that you're not grabbing it from opts but grabbing it from some other structure contained within opts. Shouldn't even compile IMO, but at least I found something I disagree with Go's designers on.

>This increasingly likely future is made all the more infuriating by the annoyances of the current reality of AI. The fact that AI is so presently inescapable despite how many glaring security-affecting flaws it causes, how much it propagates slop in the information commons, and how effectively it emboldens a particularly irksome brand of overconfidence in the VC world is preemptive insult to injury in the lead up a reality where AI will nevertheless control everything.

So basically: "yes, I know AI is actually completely and totally useless and a net negative on the world just like you say it is, but I can imagine that things will suddenly turn into the sci-fi ultraverse for no reason so therefore you're wrong."

This article has nothing to do with the inflationary or deflationary nature of the currency, this is a problem solely caused by the block size limit, which other cryptocurrencies are free from and don't worry about.

All content that violates the law of the United States is banned on 4chan. I don't know where you got that idea.

4chan culture itself is derived from polish, finnish and japanese imageboard culture and 4chan has always had a large international userbase.

4chan is more moderated than you'd imagine.

You say potato, I say po-tat-o. You "market failure and waste", I say "taking advantage of local efficiencies and powering a global financial system". Did you miss the part where they share revenue with the energy company?

> The bitcoin mine now accounts for around 30% of the plant's revenue allowing them to keep the prices down for the local town.

Rust is supposedly post-1.0 but it still doesn't have a standard that isn't just documenting the output of the compiler.

Tone is important. You are insufferable. I am 21 years old and would also rather write C and hang around the "old conservatives" than be in a community of people who talk about others the way you do.

Yes, and if BSD was what everyone used for servers instead of Linux, then there would be nothing stopping Oracle from selling you Oracle BSD for a nice subscription price. Of course, they and red hat are already doing this in their own way that gets around the GPL, but a more permissive license would just allow them to do it even more.

> Correctness and maintainability trumps performance

Great, please make all the software even slower than it already is. I am overjoyed to have to purchase several new laptops a decade because they become e-waste purely due to the degradation of software performance. It is beyond ridiculous that to FP programmers daring to mutate variables or fine-tune a for loop is an exceptional scenario that you don't do "unless you have to" and which requires "knowing what you're doing". Do you know what you're doing? How can you be a software engineer and think that for loops are too difficult of a construct, and that you need something higher-level and more abstract to feel safe? It's insane. Utterly insane. Perhaps even the root of all evil, Code Golf manifested as religion.

> The compiler can make it mutable for better performance

Well, we already know that no pure FP language can match the performance of a dirty normal imperative language, except for Common Lisp (which I am happy to hear an explanation for how it manages to be much faster than the rest, maybe it's due to the for loops?). And another comment here already mentioned how those "significantly slower" scripting languages have a healthy dose of FP constructs -- which are normally considered anti-patterns, for good reason. The only language that competes in speed in Rust, which just so happens to let you have fast FP abstractions so long as you manually manage every piece of memory and its lifetime, constantly negotiating with the compiler in the process, thereby giving up any of the convenience benefits you actually get from FP.

The language server, maybe?