Developers offered browser-based fun in VSCode.dev and Java action in Visual Studio Code

Looking at code here, there and (almost) everywhere


Microsoft has whipped the covers off yet another take on code-in-the-browser with a lightweight version of Visual Studio Code, while unveiling the version 1.0 release of support for Red Hat Java in the freebie source wrangler.

It comes after last month's preview of the code editor that runs entirely in the browser, and will doubtless have some users pondering the difference between this and Microsoft-owned GitHub's github.dev, which also pops a development environment into the browser. One of the biggest of those differences is a lack of compulsory integration with the VS source-shack; this is unavoidable with github.dev (the clue is, after all, in the URL.)

VSCode.dev, on the other hand, will permit the opening up of a file from a local device (if the browser allows it and supports the File System Access API) in what looks for all the world like an instance of Visual Studio Code, except surrounded by the gubbins of a browser.

El Reg had a poke around

We fired it up on Chrome, Edge and Safari without issue. Developers will be unsurprised to learn that Internet Explorer was not happy with whatever was going on behind the scenes and vomited up a blank screen. The Chromium browser on a Raspberry Pi-400 worked well and even Safari on an iPhone produced a useable environment, if perhaps more suitable for a keen-eyed masochist.

As for what one can do, the answer is... not a huge amount by virtue of what is possible locally in the browser. For full-on remote development and debugging, something like Gitpod or the aforementioned GitHub Codespaces is a better bet (and, unsurprisingly, moving to the latter is relatively straightforward.)

That said, the convenience of being able to view and edit files, and review PRs without requiring a full install is undeniable. Particularly in places where the desktop version of Visual Studio Code fears to tread.

Java language support reaches 1.0 in Visual Studio Code

Very much requiring the desktop version of Visual Studio Code (if one wants to spit out apps) is the long-awaited version 1.0 of the Java extension, more than five years after Red Hat first announced it.

It has taken a while (and a good many iterations) and this week's emission, replete with Java 17 support, represents quite the milestone. Performance has been upped, and the language server is more responsive, according to Microsoft, and there's some basic Kotlin support.

In the future, the team plans to embed a Java runtime in the extension and continue working on the performance of language server. This would be handy, because when we took the extension for a spin, we wouldn't describe it as eye-poppingly quick. More "acceptable".

As for alternatives, the team is looking to "eventually reach feature parity" with what is on offer in the Eclipse Java IDE. However, for Java-wrangling Visual Studio Code users right now, this release 1.0 will be more than welcome. ®

Similar topics


Other stories you might like

  • Prisons transcribe private phone calls with inmates using speech-to-text AI

    Plus: A drug designed by machine learning algorithms to treat liver disease reaches human clinical trials and more

    In brief Prisons around the US are installing AI speech-to-text models to automatically transcribe conversations with inmates during their phone calls.

    A series of contracts and emails from eight different states revealed how Verus, an AI application developed by LEO Technologies and based on a speech-to-text system offered by Amazon, was used to eavesdrop on prisoners’ phone calls.

    In a sales pitch, LEO’s CEO James Sexton told officials working for a jail in Cook County, Illinois, that one of its customers in Calhoun County, Alabama, uses the software to protect prisons from getting sued, according to an investigation by the Thomson Reuters Foundation.

    Continue reading
  • Battlefield 2042: Please don't be the death knell of the franchise, please don't be the death knell of the franchise

    Another terrible launch, but DICE is already working on improvements

    The RPG Greetings, traveller, and welcome back to The Register Plays Games, our monthly gaming column. Since the last edition on New World, we hit level cap and the "endgame". Around this time, item duping exploits became rife and every attempt Amazon Games made to fix it just broke something else. The post-level 60 "watermark" system for gear drops is also infuriating and tedious, but not something we were able to address in the column. So bear these things in mind if you were ever tempted. On that note, it's time to look at another newly released shit show – Battlefield 2042.

    I wanted to love Battlefield 2042, I really did. After the bum note of the first-person shooter (FPS) franchise's return to Second World War theatres with Battlefield V (2018), I stupidly assumed the next entry from EA-owned Swedish developer DICE would be a return to form. I was wrong.

    The multiplayer military FPS market is dominated by two forces: Activision's Call of Duty (COD) series and EA's Battlefield. Fans of each franchise are loyal to the point of zealotry with little crossover between player bases. Here's where I stand: COD jumped the shark with Modern Warfare 2 in 2009. It's flip-flopped from WW2 to present-day combat and back again, tried sci-fi, and even the Battle Royale trend with the free-to-play Call of Duty: Warzone (2020), which has been thoroughly ruined by hackers and developer inaction.

    Continue reading
  • American diplomats' iPhones reportedly compromised by NSO Group intrusion software

    Reuters claims nine State Department employees outside the US had their devices hacked

    The Apple iPhones of at least nine US State Department officials were compromised by an unidentified entity using NSO Group's Pegasus spyware, according to a report published Friday by Reuters.

    NSO Group in an email to The Register said it has blocked an unnamed customers' access to its system upon receiving an inquiry about the incident but has yet to confirm whether its software was involved.

    "Once the inquiry was received, and before any investigation under our compliance policy, we have decided to immediately terminate relevant customers’ access to the system, due to the severity of the allegations," an NSO spokesperson told The Register in an email. "To this point, we haven’t received any information nor the phone numbers, nor any indication that NSO’s tools were used in this case."

    Continue reading

Biting the hand that feeds IT © 1998–2021