zeedude

> Trying to raise a software engineering discipline to the standard of the real engineers would leave you with an employee too expensive to do what his professional ethics wouldn't allow him to.

Nah. The vast majority of software projects are of the lower echelon variety e.g., the slapdash shopping cart web apps. Considering JavaScript is still the language of choice in that realm, engineering rigors can’t exactly be of any real consideration.

No, it’s not the expense keeping real engineering away, it’s the culture.

Manifold provides this feature and supports IntelliJ IDEA and Android Studio.

https://github.com/manifold-systems/manifold/tree/master/man...

Manifold already provides this feature:

https://github.com/manifold-systems/manifold/tree/master/man...

With an article having the same name as your post:

https://github.com/manifold-systems/manifold/blob/master/doc...

Not every day you get your wish.

https://github.com/manifold-systems/manifold/tree/master/man...

Recovery?

They mostly have to do with design decisions / implementation details, not issues with extension methods in general.

Ding!

I believe Manifold already does this.

https://github.com/manifold-systems/manifold/tree/master/man...

There are good reasons. When you begin writing IDE support you will discover that:

1. Without annotations you’ll be forced to index all static methods based on the first argument, globally.

2. Method call code completion will be ridiculous. How many static methods have String, File, List, Object(!) etc. as the first parameter? I don’t think anybody wants their code completion to be invaded like that.

The annotations provide intention. Essentially, adding an extension method is not something to be taken lightly, it requires careful consideration, weighing context, frequency, etc.

My sentiments exactly. The “API designers should control their APIs” one is my favorite and one of the more ridiculous things I’ve heard him say, which is saying something. It’s beyond humor, though, that all of his reasons are fallacies.

Nice redirection of focus there.

The “truth”

Limit training to stackoverflow input and wham! we have automated modern programming ;)

They are good about supporting latest JDK release and all LTS releases, going back to 8.

It’s Oracle’s saber rattling lately concerning plugins like Lombok and Manifold that make me more disappointed than nervous.

The West has been importing its population for decades, full gas since 1965. Not only is this strategy failing, it is a significant contributor to the West’s current decline. The core problem is more centered on the dynamics of the 20th century that led to mass immigration.

It’s all about the bottom line. Touch screens consolidate a ton of otherwise expensive switch gear. Going back to physical knobs and buttons means going back to paying for engineering, assembling, testing, etc.

A general purpose language as the basis for a build tool always felt like a sledgehammer/nail situation to me. Personally, I prefer less concise, less flexible build config tooling.

Here we are in the current year and we still i/o source as raw form text. Personally, I’ve always hoped for standardized AST formats with comprehensive tooling, including source control. Many more problems vanish than are created with source as AST. For instance, this discussion.

>The OS/2 API was, IMO, more logically designed and documented than anything else since.

Absolutely. I was disappointed when I began writing Windows apps after having used Presentation Manager etc. Windows APIs felt like children’s toys.

I recall learning Prolog for a CS class back in the late 80s to model problems using its backtracking (chaining) algorithm with facts. Sometime later Rete-based rules languages became popular, but I always thought Prolog’s language approach was more suitable.

The manifold project integrates code gen directly into the compiler. The GraphQL[1] module is amazing.

The JSON[2] module for REST looks similarly impressive, but I haven’t personally used it.

1. https://github.com/manifold-systems/manifold/tree/master/man...

2. https://github.com/manifold-systems/manifold/tree/master/man...

Not sure what you’re getting at, sharing here does for you exactly what you would do with explicit composition.

There’s a Java compiler plugin, manifold, that makes this type of syntax easy. There’s an example covering the date “literal” case…

https://github.com/manifold-systems/manifold/tree/master/man...