interlocutor

Ever heard of Django? ASP.NET? Most UI frameworks, including ASP.NET Core, Spring Boot (Java based framework), Ruby on Rails, and Django (Python) are all based on MVC.

Here's a better list:

- Being under the public eye—all the time—is one of the top reasons to not be famous. Famous people must constantly self-monitor what they say and do because casual mistakes can trigger disproportionate backlash or headlines.

- You lose the ability to have genuine, equal interactions—people treat you differently, with deference or expectation, rather than as a peer.

- Privacy disappears as curious strangers can easily discover where you live, details about your family, and how much wealth you have—information you'd normally share only with people you trust.

- Strangers form opinions about you before ever meeting you, based on whatever fragments of your public persona they've encountered.

- A public persona can become a cage, limiting your freedom to change, experiment, or reinvent yourself.

There is a method to this madness.

Elon Musk's strategy is to control the government operations through controlling its IT department.

The smart people of 18f stands in the way. By removing it and hiring his loyalists to run the government IT he gets to control the government's operations.

In go you mix state with logic (example below), which apparently is a "major catastrophe" according to some on this thread.

   type Engine struct {
       HorsePower int
   }

   func (e Engine) Start() {
       fmt.Println("Engine is starting with", e.HorsePower, "horsepower.")
   }

Also, Visual DB has Airtable-like features

Wasn't he president of some kind of startup incubator? Some "combinator" company.

It seems you only support Postgres. Do you have plans to support other databases as well, such as MySQL?

In the case of map function hopefully you're using it with methods that don't fail in serious ways, and don't need strong error recovery. If so Java has RuntimeException to handle that case. If serious errors are possible and strong error recovery is needed, then you need to avoid the conveniences offered by functional style programming.

> write generic functions that take functions as arguments and re-throw the errors thrown by these functions

There is a philosophy that applies here: simple things should be simple, complex things should be possible. The scenario you're mentioning is not common enough that the language design should be centered around it.

Do you mean Turbo Pascal? He didn't design it, Niklaus Wirth did. Or do you mean C#? James Gosling designed most of that (C# got its start by copying 90% of Java). Do you mean TypeScript? That's mostly JavaScript.