shikck200

Lisp allows for some really, really complex and spaghetti code bases. I have seen the ultimate macro-hell from top to bottom. I know syntax does not matter, but i just cant honestly say i read lisp code as clear as something like Go. I guess it boils down to style. I have seen 100 lisp styles, and only one Go style.

Looking at the source i was not surprised. A shell html page, that uses a shittonne of javascript, and obviously does not even include the static content per page load. Its sad that this is the status quo of the AI slop you see.

"How do we finally get rid of trump?"

> Chat is unavailable right now.

> Criticise person X for being a "absolute scumbag"

> Yolo

> Switch to person X software anyway.

This is the most weak double standards i have seen in a while. IF you mock someone for what they did 10 years ago, have the balls to stand by it.

The fact that i would use 99% less dependencies, and overall have a WAY more simple deployment story. Also a typed language is always better than the PHP way, where you have functions that are hard to reason about, and edge cases llms miss easily.

I never had issues with token use at this scale. More so i would say a huge bloated framework uses more tokens as the LLM might read the source to understand why something works as it does. With stdlib only most LLM already knows it.

Also a laravel "rate limiter" sound suss. Its probably needs some extra dependency like redis + a supporting php library to work. On the contrary i can mock up a reasonably efficient in memory rate limiter in pure Go, and only go to redis when i need the scale.

You could. But thats rarely where the perf hit is. You rarely need more CPU juice than Go provides, and if you do you probably use Rust or C. There is little to gain from dropping down to ASM, as you most likely run on an OS that is more powered than a microkernel, where you would need ultimate low level control.

Sure. I like Rust. But i also know when not to use Rust.

Meh.. sure a DR is not the same as an RC, but i would class it as a subset of the same thing. You you cant have an RC, you cant have DR, but the other way around.

In the end its the same problem, dressed up differently.

Indeed.

Shared Go slices are a bad mix in concurrent code. This is a given. But its also not a fair comparison, you should instead compare java arrays to go arrays, not slices.

This goes for slices, strings and maps. Those a usually wrapped in a mutex, or used with sync primitives like sync.Map.

Neither Java or Go guarantees data-race freedom. A data race does not by itself make ordinary Java or Go code memory-unsafe in the C/C++ sense.

I fail to see how a racy Java program is more memory safe than a racy Go program?

I have not written a line of Java in 15 years. But im pretty sure Java has threads? Once you have threads, you pretty much have data races.

        Thread a = new Thread(() -> x++);
        Thread b = new Thread(() -> x++);

        a.start();
        b.start();

Now you are pushing pixels. A data-race IS a kind of race condition.

My point is "races" happen all over. In concurrent code, databases, http and pretty much anywhere where you have some kind of timing, not scoped to a unit.

Memory safety != Data race free

Are you saying any language that does not promise data-race freedom is memory unsafe? That would rule out almost every programming language.

Sure, but a data race is, IMHO not the same as memory safety. A data race, can be 100% memory safe, but just cause a logic bug in some program. I often see people mixing memory safety with racing. Go has bounds checks so you end up with a panic either way. Not UB.

As an (outside go) example, Ocaml (5) promises strong memory safety, but not to be data race free. A data race is not something we can prevent, because its usually not bound by code, but by time and the race-source rarely in source-code.

This means we have data races in http, database inserts etc. The source is usually not a concurrent task in source code-land.

You can write unsafe code in Go (import unsafe), but then, you can do the same in Rust. Unsafe code is not the default, and in day to day Go i rarely see the use of the unsafe package.

That does not make sense to me. Go is memory-safe, but it does not guarantee data-race freedom.

So whats your point here? Haskell?

With LLMs the language DOES NOT MATTER. The framework DOES NOT MATTER. This is the thing we are talking about here. Laravel is 100% useless for a LLM first project. I can pretty much do anything in vanilla Go i can in Laravel and be 100x more performant, 100x more typesafe, and produce 100x more maintainable systems.

This is why dynamic languages, and even more so BAD ones like PHP are just useless going into 2027 and the future. Its simple, the language gives you what it gives in perf, builtin RUNTIME features, and COMPILETIME features.

From that you pick the best for whatever you are building, be it Go, Rust, Ocaml etc. The language does not matter.

Go has 90% of stuff builtin, you rarely need any dependencies. Look at Laravel ITS A HUGE CODEBASE and a high risk for any real software project. I would stay FAR away from it.

PHP is sync. This means every IO operation i do runs sync. This is why PHP will always be the slowest ones out there. Open a file, SQL queries, sending emails etc. Its all sync. Its all slow.

PS. I fully aware of hacks around this like reactphp and the other related async things, but those are all just heavy dependencies and for most sane devs non starters.

No... no its not. PHP is bound by IO in 99,9% of cases. This means im pretty much fucked the moment i need to do something even a little more complex. Say one request need 5-10 separate sql queries, and some http call and possibly some task like sending a mail. PHP need to run these all sync. I have to hack around and use a shit-tonne of deps like message queues and all sorts of plugins to get something like this working performantly.

Before you go on that apologist route, no, im not installing any random shit just to do simple stuff like this..

Rails, or even more so php have VERY little to bring to the table in 2026 going forward. Rails (ruby) is still a saner language than PHP, but as slow as php is. (granted ruby is not idiotic like PHP and runs rather than start/die).

If you go the LLM route something like Go is probably the goto default for MOST networking/web-first apps. You get static types, and a fast compile cycle (rust is still very slow here), and IF you want more from the language you can use something like Lisette (https://lisette.run/).

Bottom line is dynamic languages are obsolete. There is really no benefits from using them outside very small throw away scripts.

Nah. They are not, everyone is losing money, and just staying alive from gov subsidies. A claude PRO license is 20 usd/month, and for it to be profitable it should be somewhere around 200-300/month.

The bubble is going to burst soon.

Not sure what your point is? Are you saying that this mountain of complexity is somehow justified for the 99% of stuff out there? Complex stuff can and should be as simple as possible, and that something a good software developer strive to do.

But now we have abstractions upon abstraction, slow ands heavy solutions for almost every thing.

Software is slower than ever, not because of hardware, but because of the endless bloat and abstraction every framework brings.

Thats not a true comparison, MAYBE that was sort of a thing back in the IE6 era. Today the web is capable of "a good enough" UX for most things. But how we do interactive apps on the web today is just madness. Most sites dont need anything close to React, and those who do could have just used something more simple without the madness what is the react ecosystem / bundlers / packages etc.

Webdev is the pinnacle of over engineering. And now with AI, it will get even worse. I think the web truly needs a reset.

Side note: PLEASE DONT hijack scroll. Its just a bad bad thing to do. Please dont.

Nah. 99% of meetings are fluff. Something that could have been just an short email. Meetings are for people who do not get anything done. for people who like to waste other peoples time. The actual good meetings are the ones that have a VERY clear context, and goes down to details that EVERYONE in the meetings know by heart. These are rare, maybe one a year.

RTO steals one work day from me per week, at a minimum. When i work from home i can start 6am (or whenever i want to), and if im in a flow state, i can push to 5pm easily. I get SOOOO much done. Other days i can lax, have a few teams meetings and chill on the couch and quit work early.

When i go to the office it takes 2 hours from each day only for commute, add meetings, lunch breaks, and the office bullshit chitchat and non-stop blabber that distracts you. People on the phone, or just "hanging" out next to you.

Bottom line is when i have to work from the office i get 5% done of what i do from home. I get angry, and unmotivated. I usually also leave early.

Like i said, the dash IS a thing, and only in practice used by "experienced writers", common folk NEVER use it. LLMs stole all the books, so obviously the AI spits out dashed like there is no tomorrow.

You cant argue about this, just looking at github, i never saw dashes used pre AI. Today you see a dashes in code comments, PRs, issues etc EVERY time. Its all AI generated.