Just one last thing. I can see why we gravitate towards the different language ecosystems. You come from the C world and I come from the .NET world. So, it is much easier for you to make the leap towards Go and it is much easier for me to make the leap towards F#. Especially now that I have kids which really limits my time.
One thing that I did want to learn is PostgresQL. But the leap from SQL Server to PostgreQL is pretty high for me. Partly because the tooling around SQL Server makes the tooling around Postgres look rather primitive. I use SQL Server Data Tools which makes writing tables/stored procs/inline table valued functions/etc all declarative and it can do diffs against the database and gives me great intellisense. I believe there are tools out there for diffs with Postgres but they are rather rudimentary and the IDE for Postgres is also pretty rudimentary from what I tried. When I tried the IDE for Postgres it couldn't even differentiate between the columns of a joined table. But I always wonder if I am approaching it wrong of it there is some tool that I didn't find that works better or if there is something that I was doing wrong. I know Postgres has built in language parsers that can make the tooling just as powerful as SQL Server. I imagine if I knew someone that programmed with Postgres then the leap would be much easier.
Sorry, I'm just rambling. I'm looking forward to any other work you put out about this. It is all so fascinating!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Just one last thing. I can see why we gravitate towards the different language ecosystems. You come from the C world and I come from the .NET world. So, it is much easier for you to make the leap towards Go and it is much easier for me to make the leap towards F#. Especially now that I have kids which really limits my time.
One thing that I did want to learn is PostgresQL. But the leap from SQL Server to PostgreQL is pretty high for me. Partly because the tooling around SQL Server makes the tooling around Postgres look rather primitive. I use SQL Server Data Tools which makes writing tables/stored procs/inline table valued functions/etc all declarative and it can do diffs against the database and gives me great intellisense. I believe there are tools out there for diffs with Postgres but they are rather rudimentary and the IDE for Postgres is also pretty rudimentary from what I tried. When I tried the IDE for Postgres it couldn't even differentiate between the columns of a joined table. But I always wonder if I am approaching it wrong of it there is some tool that I didn't find that works better or if there is something that I was doing wrong. I know Postgres has built in language parsers that can make the tooling just as powerful as SQL Server. I imagine if I knew someone that programmed with Postgres then the leap would be much easier.
Sorry, I'm just rambling. I'm looking forward to any other work you put out about this. It is all so fascinating!