The Rise of Microsoft Visual Studio Code

Re:The Rise of Microsoft Visual Studio Code by meowface on Thursday December 06, 2018 @06:26PM (#18623556)

If Go adds generics and a smoother method of doing error handling, I could see it eventually taking Python's place. It already is doing so to an extent, but with those features plus everything else it can do better than Python, it'd be tough to beat. 95% of my programming is in Python, and I honestly don't really enjoy coding in Go that much, but with those changes I could see myself switching.

[ Parent | on HN ]

Re:The Rise of Microsoft Visual Studio Code by Waterluvian on Thursday December 06, 2018 @06:29PM (#18623575)

Same. 99% of my back-end and robot code is Python. Maybe this is a grass is always greener kind of thing but I'm hitting projects of a size where I miss static typing.

I will say that asyncio is amazing and really solves concurrency for me. But Go looks like you also get parallelism without a lot of work.

[ Parent | on HN ]

Re:The Rise of Microsoft Visual Studio Code by 1996 on Friday December 07, 2018 @08:31AM (#18627454)

Asyncio is good but it will not give you true parallelism: asyncio still uses the GIL, on a single thread

[ Parent | on HN ]

Re:The Rise of Microsoft Visual Studio Code by Waterluvian on Friday December 07, 2018 @02:46PM (#18630898)

Yep. Concurrency is not parallelism. But a lot of the time it's just not necessary.

[ Parent | on HN ]

Re:The Rise of Microsoft Visual Studio Code by pjmlp on Friday December 07, 2018 @03:46AM (#18626055)

On the other hand if Python community had more love for PyPy, to follow up on JavaScript and Julia footsteps, maybe that wouldn't be even an issue.

[ Parent | on HN ]