To emphasise the team’s commitment to move the project along, it also gave a short walkthrough upcoming features. ![]() If all is well, and there aren’t any issues with crash reporting, the new version will then be pushed into the release channel. In addition, the continuous delivery system for new versions has been revamped so that upcoming releases are put into an insider channel first. It also got a remote extension and an option for inline results that developers more used to Juno will surely appreciate. Those included, maybe most importantly, a reworked debugger and some basic profiler implementation, which might still take a while before it is ready for prime-time. The only criteria are that the new name should start with a J, be short and recognisable, and have some sort of relation to either Juno or Jupiter.ĭuring his talk, the team also launched version 1.0 of the project, which came packed with useful new features. A new name could help those well versed in the old IDE develop a better sense of ownership for the new project, so it probably wasn’t a bad idea to step away from the somewhat longish current designator. Pfitzner also took the opportunity to start a naming discussion for the new project, debating if Juno would be a good moniker for its reincarnation and asking the community for feedback. Juno is still said to be “perfectly usable” but will switch to maintenance-only mode. Other benefits include better stability, while the opportunity to put more work into the language server is hoped to help the whole editor ecosystem. According to Pfitzner, the future therefore lies with VS Code, which is why he and his colleague decided to focus on LanguageServer.jl and join the efforts of the team behind VS Code for Julia.Īs the IDE extension is almost at feature parity with Juno, switching should be comparatively easy, while also adding useful capabilities such as “proper” linting, as Pfitzner put it. ![]() ![]() With JuliaCon in full swing, Julia IDE Juno developer Sebastian Pfitzner took to the virtual stage to brief users about the state of things and present them with… Julia for VS Code 1.0.Īfter Microsoft bought GitHub, development on the Atom editor unsurprisingly slowed – possibly because Microsoft has already put resources into Visual Studio Code and can live without homemade competition.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |