I’m one of the software developers with Open Law Library (http://www.openlawlib.org/). We needed our VS Code extension, Codify, to communicate with our codification engine (basically a compiler for laws) which is written in Python. So we needed a native Python language server. We found Palantir's excellent python-language-server, but instead of targeting Python directly, we needed one targeting legal XML. Basically, we needed a pythonic generic language server. Thus was born, pygls (pronounced like "pie glass").

Our goal with pygls is to make it incredibly easy for anybody to write a language server for anything in Python. We have created a thin pythonic layer over the Language Server Protocol - giving the developer the core of what they need without getting in the way. Currently, it targets Python 3.5+ and has support for sync, async and threaded (using an @thread decorator) features and commands.

Python is one of our favorite languages, and VS Code one of our favorite editors. We hope pygls will make it possible for people to build many new and exciting language servers that leverage the power, ecosystem, and flexibility of Python.

This wouldn't be possible without Daniel Elero's hard work. Thank you, Daniel!

Thank you for kind words, it is my pleasure to work with OLL team on great tools.

It seems one small approach in the right direction would be for someone+ to provide a discovery/marketing service for helping spotlight, bring to the forefront those working on the infrastructure-type projects. Thinking more along the lines of a podcast, blog, etc. that would generate revenue from sponsors. Akin to Changelog or other podcasts, but specifically focused on the behind-the-scenes/infrastructure/maintaince type stuff - the "backstory" if you will. Folks could donate to this service and funds could be funneled to the highlighted projects/developers.

The "marketing service" angle would be to provide free marketing to these types of projects. Inviting folks as guests, writing about projects, etc.

It does solve the overall problem for everyone, but it would be going in the general right direction. There may be efforts like this already, but I am not aware of them.

+ I do not have the time it would take to do this well.

Finally, we get hot exit. :)

Hot Exit is one of those features that I didn't think I needed or wanted...until I started using Sublime like a notepad to store text, but not save it. I'm excited that this feature is now in VSCode now, and it also works with files that have never been saved just like Sublime.

+1

Now I only hope they add in hot-disk support.

Sublime Text 3 checks to see if the currently opened version differs from the file system. If it does, it prompts the user to keep the current version or replace it with the disk version. VS Code just replaces the current version with the disk version and doesn't retain history so you can't undo this.

I lost about an hour of work yesterday because I had a file open in both VS Code and Sublime Text. Pressing save in Sublime Text wiped out all changes. :(

FYI that's being tracked here https://github.com/Microsoft/vscode/issues/15749

Thanks Tyriar!

Sublime's updates are dismal. https://www.sublimetext.com/blog/ I had to switch to Atom just because the development is stagnant. I liked Sublime very much. But it's been 2 years already..

But what is missing in sublime?

The official download page says "Sublime Text 3 is currently in beta" It's been like that for years. First build is from January 2013, it's almost 4 years already. I don't know what specifically is missing there, I just know I'm not comfortable using beta version (with little hope it will ever come out of beta) of a product for daily work. I see it as even developers don't consider it stable enough.

I think that sublime text 3 beta is like debian testing, they are more solid that some others lts products.

VScode and Atom are constantly receiving new features. So we can say that they are still in beta too.

Beta is just a word.

I wished they had this feature 2 days ago... I spent 3h writing issues in VSCode before submitting them on Github issues, then my laptop ran out of battery (and of course it was in an untitled file so it was unsaved)... I just wanted to cry.

BTW, really awesome job VSCode team :) I love what you're doing!

Agreed. This is my favourite new feature. It didn't hold me back from using it at all, but now I can get rid of my other "scratchpad" editors.

Agreed. And now I hope they could improve the startup speed.

+1 ... been waiting for this. Just the support for large files now and I can drop Sublime.

(I use it to edit a very large JSON test fixture file)

Hot exit is still useful when auto save is on as it works with untitled files. Crash recovery also comes with hot exit regardless of whether the feature is on or off. (I'm on the vscode team)

The question is intentionally generic as I am trying to find out what most folks would do if they were starting with something fresh. Your comment reminded me I needed to narrow the focus a bit. I edited the question to add an assumption that this is a Web API.

I don't know why did you get the impression that my comment somehow doesn't apply to API-first web services.

I didn't - it just reminded me that some might take it in a more general way than I intended. :)

subtitle: "Robotics pioneer Sebastian Thrun is building an open-source autonomous car."

"Swift calling convention was ported to ARM."

Edit: simplify

Death Tax hike?

Having the month and year of the "interview" would be helpful. Down-the-road, it will help give context to the information. A neat idea would be to allow for follow-up "interviews" later.

I like that you can filter on solo vs. multiple founders. Very cool.

Interesting that there is only 1 multi-founder project listed.

Thanks for your response. This is the type of thing I am wanting to do, even if not with CHICKEN Scheme. :)