DarkNova6

And yet. None of these issues exist in Maven to begin with.

Apples and oranges. Maven is leagues beyond npm. Screw Gradle.

How many mass security incidents have there been with npm just the last few weeks?

Only if there are is organizational disconnect… which is the norm.

It’s the main reason I prefer Mistral. It has a reasonable and respectful tone.

In contrast, ChatGPT repeatedly speaks in an authoritative tone which exceeds its own competence by an order of magnitudes.

I think the problem is a lack of "engineering culture".

The barrier for entry is primarily capital these days: have a moat, prevent competition, extract money, cease R&D. And if a competitor does come up, just buy them outright. This is the current economic model, as it is practiced by Private Equity.

Power has become infectious and capitalism has changed. The game is about power and extracting more and more money from the productive economy, making it less competitive. Who wins? Those who already have excessive capital.

The only one who would have enough legal power is exclusively the state. It’s no surprise the state is under attack from so many fronts.

The bug occurs because of the power discrepancy of those who have the demand and those of who can supply. For some reason, the problem if insulin prices and absurd health costs only exist in the US. I wonder why.

> An overly aggressive mock can work fine, but then break much later. Why?

Because you are testing against implementation, not specification.

You’re welcome.

The way I like yo phrase it: concretion over indirection.

That is indeed a technical difference. But I don’t see much significance in it.

Spring is a de-facto extension of the core java libraries and alternatives like Quarkus follow the same mental model with a better technological foundation.

I think this was a fair statement up until a couple years ago, but right now I am lamenting the actual progress in C# and CLR technology.

I think the progress on Java and the JVM has been nothing but impressive. Not only compared to the baseline to where things were 10/15 years ago, but simply how much stuff comes out each year and how well-thought it all is.

Frankly, it's an inspiration for my private and professional projects.

How so? It striked me that the .Net library and Java frameworks like Spring or Quarkus are virtually identical.

I'm not new to C# myself and I have been writing a hobby game project in it for the better part of 2 years. I know the C# features pretty in-depth by now, and while you can definitely make an argument that C# has more and better features, I found that Java has greater synergies in its features.

Don't get me wrong, there are some features like "abstract static" in interfaces which give C# superpowers... until you realize that this only works one layer deep. Or the non-break switch expressions, which require a return type. Lack of an equivalent to Java's "Sealed Classes" (that you can switch over). Or that you can't validate primary constructors up until recently.

Lack of value objects are definitely hurting, but JEP401 addresses this and is available as preview as of now. I am absolutely blown away by the depth of their value-narrative and I think they uncovered something much deeper than "value or not" with gradual performance gains based on gradual constraints.

But I absolutely see the value of C# in teaching. Java works more via libraries and convention, whereas C# has ingrained many concepts directly into the syntax level.

But maybe I am a Java fanboy, haha. I even prefer the Erasure of Generics, the times it has complicated my code in C# is much higher by now than I ever thought it would be.

Ah, got you.

> I haven't kept aware of changes to Java in the last decade, but the things I didn't like about it then were:

It's almost a shame. I am genuinely impressed with the gains the team has made in both, language aspects as well as JVM technology. They have some brilliant people working on it and I love to hear their talks (Brian Goetz and Mark Reinhold, mostly).

But I suppose I would say the same about .Net, it's just that you guys have much less public exposure of your internal reasoning.

Silly question. If you want the C# experience but more community/OSS driven… why not Java?

It's true that currently US technology is among the forefront, but having a single economic pillar is fragile and bound to break, the same is happening with the automotive industry in Germany right now.

But a primary problem is financial. There is too much financial wealth that is desperately looking to find lucrative opportunities which do not exist. So everybody follows the hype and creates the largest bubble we have seen in human history. And those who don't invest in AI, are largely bound in private equity or real estate, which extracts wealth from everybody without giving anything in return. This makes all other businesses less competitive.

It's a huge bottom-up scheme because the incentives are wrong, lacking transparency and unchecked financial power. This is simply not sustainable and nothing but a systemic change is needed.

In the lie for search of productivity, the west didn't become more efficient. We simply outsourced lower-margin industries to Asia and we are now faced with: Lost knowledge, lacking infrastructure, vulnerable supply chains and people without jobs.

AI cannot and will not change this.

Edit: Not sure why you got downvotes, I think it is a valid question.

It is quite preposterous to claim that "OpenAI" is a "startup". Neither is it "Open" while we are at it.

> The only future where the US maintains its relative success involves American leadership in AI and robotics, with humans supporting them

I never understood this take. It strikes me more as "faith in our lord and savior AI" without actual evidence to support this.

Ah yes, -2. Predictable result on this emotional topic.

And syntax is what most programmers will complain about. Even if it makes the wrong code easier to type.

This is really just a syntactical issue. Not one of types or semantics.

Non trivial operations have errors when the happy path fails. And with web apps IO can fail anytime, anywhere for any reasons.

Sometimes you want to handle them locally, sometimes globally. The question is how ergonomic it is to handle this all for a variety of use cases.

We keep reinventing the wheel because we insist that our own use cases are “special” and “unique”, but they really aren’t.

Personally, I think Java’s proposal on catching errors in switches, next to ordinary data is the right step forward.

Monads are great. You can do lots of great things in them, but ergonomic they are not. We should avoid polluting our type systems where possible.

To be fair, Carmack has advocated for immutability and other good practices at least since the 2000s.

Sounds Like „Tell me about Generics in Go without telling me about Generics in Go“

As somebody who only views Go from a distance, I see this list as a combination of „what‘s the big deal?“ and „please don‘t“.

> Locality is the design principle of grouping related things together. It’s a mental shortcut or heuristic that allows the mind to assume a higher degree of independence from the code block being read, easing the mental burden. Spreading code across your codebase diminishes locality.

> Linearity is the idea of having instructions be read one after the other, from top to bottom, just like how code is executed. Having to jump back and forth from function call to function call reduces linearity.

1000 times yes.

Tech industry in a nutshell

> All that said, it is possible that SQLite might one day be recoded in Rust. Recoding SQLite in Go is unlikely since Go hates assert(). But Rust is a possibility. Some preconditions that must occur before SQLite is recoded in Rust include:

- Rust needs to mature a little more, stop changing so fast, and move further toward being old and boring.

- Rust needs to demonstrate that it can be used to create general-purpose libraries that are callable from all other programming languages.

- Rust needs to demonstrate that it can produce object code that works on obscure embedded devices, including devices that lack an operating system.

- Rust needs to pick up the necessary tooling that enables one to do 100% branch coverage testing of the compiled binaries.

- Rust needs a mechanism to recover gracefully from OOM errors.

- Rust needs to demonstrate that it can do the kinds of work that C does in SQLite without a significant speed penalty.

What is the code quality of the average developer? What is the code quality of coding agents?

There is your answer why many find AI coding productive while others do not.

*The race for quick profits is eating away our future.

I don't think we have a lack of concepts, but a lack of concept connectivity.

To avoid feature bloat of unconnected pieces of ad-hoc syntax Java does the right thing and focuses on expressing easily-composable language building blocks.

As a last adopter language, Java has the luxory of cherry-picking good features of other languages but I think their line of thinking should be the reference moving forward.