safari source code github

• Trying the Latest
• Reporting Bugs
• Staying in Touch

WebKit Overview ¶

WebKit is a cross-platform web browser engine. On iOS and macOS, it powers Safari, Mail, iBooks, and many other applications.

Getting Up and Running ¶

Downloading the source code ¶, building webkit ¶.

Compilation instructions are for macOS. For other platforms additional instructions may be found here .

Running Minibrowser ¶

(optional) add scripts directory to your path ¶, contribute ¶.

Congratulations! You’re up and running. Now you can begin coding in WebKit and contribute your fixes and new features to the project. For details on submitting your code to the project, read Contributing Code .

Trying the Latest ¶

On macOS, download Safari Technology Preview to test the latest version of WebKit. On Linux, download Epiphany Technology Preview . On Windows, you will have to build it yourself.

Reporting Bugs ¶

• Search WebKit Bugzilla to see if there is an existing report for the bug you've encountered.
• Create a Bugzilla account to to report bugs (and to comment on them) if you haven't done so already.
• File a bug in accordance with our guidelines .

Once your bug is filed, you will receive email when it is updated at each stage in the bug life cycle . After the bug is considered fixed, you may be asked to download the latest nightly and confirm that the fix works for you.

Staying in Touch ¶

Before getting in touch with WebKit developers using any of the avenues below, make sure that you have checked our page on how to ask questions about WebKit .

You can find WebKit developers, testers, and other interested parties on the #WebKit Slack workspace . Join the WebKit slack , and stay in touch.

Sourcegraph for Safari 4+

Sourcegraph.

• 5.0 • 1 Rating

Screenshots

Description.

The open-source Sourcegraph extension adds code navigation and code intelligence to GitHub, GitHub Enterprise, GitLab, Bitbucket Server, Phabricator, and Gerrit. • Code intelligence on your code host: * Hover tooltips with documentation and type information * Go to definition * Find references • Integrations with third-party services like Codecov coverage overlays, open-in-editor buttons and many more with Sourcegraph extensions It works for 20+ languages on public and private code on popular code hosts (see below). MAKE IT WORK ON YOUR CODE HOST: • GitHub - Navigate to GitHub and click the Sourcegraph toolbar button to grant website permissions. • GitHub Enterprise, GitLab, Bitbucket Server and Phabricator - grant additional permissions in the extension menu Browser extension docs: https://docs.sourcegraph.com/integration/browser_extension MAKE IT WORK FOR PRIVATE CODE: To use the browser extension with your private repositories, you need to set up a private Sourcegraph instance and connect it to the extension. Installation docs: https://docs.sourcegraph.com/admin/install WHERE TO START? After adding the extension you install it, try it out on any of these public repositories: • Go: https://github.com/gorilla/mux/blob/9e1f59/mux.go or https://github.com/dgrijalva/jwt-go/pull/152/files#diff-f615844d3497ff38db57e459d6ef657bL48 • Java: https://github.com/google/guava/blob/581ba1/guava/src/com/google/common/collect/ImmutableList.java • TypeScript: https://github.com/angular/angular/blob/a2878b/packages/benchpress/src/reporter/console_reporter.ts or https://github.com/sindresorhus/got/pull/917/files#diff-02301bc46e8b878f10e9a8339efb7de7R176 • C#: https://github.com/paiden/Nett/pull/76/files#diff-e969e1315b2cb01bab80b2860be0d87eR52 • Python: https://github.com/ageitgey/face_recognition/blob/b8fed6/examples/facerec_on_raspberry_pi.py This extension is open source: https://github.com/sourcegraph/sourcegraph/tree/main/client/browser

Version 1.24

- Updated the info text when accessing an unindexed repository [pull/42509](https://github.com/sourcegraph/sourcegraph/pull/42509) - Fix an issue that caused the native code host integration to not work on gitlab.com [pull/42748](https://github.com/sourcegraph/sourcegraph/pull/42748)

Ratings and Reviews

App privacy.

The developer, Sourcegraph , indicated that the app’s privacy practices may include handling of data as described below. For more information, see the developer’s privacy policy .

Data Not Linked to You

The following data may be collected but it is not linked to your identity:

• Diagnostics

Privacy practices may vary, for example, based on the features you use or your age. Learn More

Information

• Developer Website
• App Support
• Privacy Policy

Downloading source code archives

You can download a snapshot of the code in your repository.

In this article

Overview of source code archives.

You can download a snapshot of any branch, tag, or specific commit from GitHub.com. These snapshots are generated by the git archive command in one of two formats: tarball or zipball. Snapshots don't contain the entire repository history. If you want the entire history, you can clone the repository. For more information, see " Cloning a repository ."

You can download the source code archives in three ways.

Downloading source code archives from the repository view

On GitHub.com, navigate to the main page of the repository.

Above the list of files, click Code .

Click Download ZIP .

Downloading source code archives from a release

To the right of the list of files, click Releases .

Scroll down to the "Assets" section of the release.

To download the source code, click Source code (zip) or Source code (tar.gz) .

Downloading source code archives from a tag

At the top of the Releases page, click Tags .

To download the source code, click zip or tar.gz .

Source code archive URLs

Source code archives are available at specific URLs for each repository. For example, consider the repository github/codeql . There are different URLs for downloading a branch, a tag, or a specific commit ID.

Note : You can use either .zip or .tar.gz in the URLs above to request a zipball or tarball respectively.

Stability of source code archives

Source code archives are generated on request, cached for a while, and then deleted. If the same archive is requested again in the future, it'll be regenerated. It's important to understand what guarantees GitHub makes about source code archives.

• An archive of a commit ID will always have the same file contents whenever it's requested, assuming the commit ID is still in the repository and the repository's name has not changed.
• Because branches and tags can move to different commit IDs, future downloads of an archive may have different contents than previously downloaded archives of the same branch or tag. Assuming the branch or tag still points at the same commit ID, it will have the same file contents.
• The exact compression settings used to generate a zipball or tarball may change over time. The extracted contents won't change if the branch or tag doesn't change, but the outer compressed archive may have a different byte layout. GitHub will give at least six months' notice before changing compression settings.
• The name of the repository is part of the directory structure inside the archive. Therefore, if the repository name changes, the root directory name will change as well.

If you rely on stability of source code archives for reproducibility (ensuring you always get identical files inside the archive), we recommend using the archives REST API with a commit ID for :ref . Using the commit ID ensures you'll always get the same file contents inside the archive and you’ll be immune to repositories rewriting tags or moving branch heads.

If you rely on stability of archives for security (for example: to ensure you don't attempt to unzip a maliciously-crafted file), we recommend using releases instead of using source downloads. For more information, see " About releases ."

You can use something like this third-party GitHub action to create and push these files as part of your release process. The Release Assets REST API can later be used to retrieve them.

5 Ways to View Page Source on iPhone or iPad [Inspect]

It is quite easy to view HTML page source code on Windows PC or Mac, but you don’t always hold your computer. For iOS users, you always have your iPhone around. It would be more convenient to view page source on iPhone or iPad. Actually, you can do it without third-party apps.

In this post, I will show you 5 ways to show webpage source code on iOS devices and even inspect elements. Sounds great? Keep reading to learn how. 

Method 1: Create a View Source Shortcut 

The first I recommend is to create a View Source shortcut that is available in Share Sheet, so you can easily access it from Safari. Shortcuts is a stock app in iOS 13 or new versions for automation. There are many amazing pre-made shortcuts that you can get from the internet. 

Here I will show you how to make one to view HTML source code step by step. You can refer to the steps below or the video.  If you don’t want to make it by yourself, you can also click this link to add it to your Shortcuts Library. 

Step 1. Open the Shortcuts on your iPhone or iPad. Tap on the “+” icon to create a new one. 

Step 2. Tap on the three-dot icon and enable the option “Show in Share Sheet”. Tap Done to go back to the new shortcut. 

Step 3. Type “html” in the search bar and drag the “Make HTML from Rich Text” action from the search results to the shortcut.

Step 4. Type “quick look” in the search bar and drag the “Quick Look” action to the shortcut. 

Step 5. Tap “Done” to save the shortcut and change the shortcut name to “View Source”.

Step 6. Go to Safari and open the web page where you want to view the source code. Tap the Safari Share button and select the “View Source” shortcut that you just created. 

Shortcuts only accept Safari web pages, so if you want to view source code on Chrome or other web browsers, keep reading to find other alternative methods. 

Method 2: Safari Bookmark Trick

Another way to view source code is via Safari bookmark. You can use bookmark to run a javascript and it will show the source code of any web page. 

Step 1. Copy the script. You can go to this Github page and copy the script or copy the script below. 

Step 2. Tap your browser (Chrome or Safari) Share button and select Add Bookmark. It doesn’t matter which web page you add. You just need to create a new bookmark for further usage. 

Step 3. Tap on the Bookmark icon and locate the new bookmark that you just created.

Step 4. From there, tap Edit and change the new bookmark name to “View Page Source” and the URL to the script that you copied before. 

Step 5. Go to the webpage where you want to view source code. Tap the Bookmark icon and select the View Page Source bookmark that you just saved. 

Then it will display the source code of that web page. If you use Chrome, it is even simpler because you can change the bookmark URL on Step 2. 

Method 3: DevTools Extension for Safari

If you also need to inspect elements, you can use a Safari extension for iPhone or iPad. There are a few of extensions that allows you to inspeact elements, including DevTools Extension, Web Inspector, and Achoo HTML Viewer & Inspector (Paid).

Let me take DevTools Extension as an example to show you how:

Step 1. Open AppStore and search for “DevToools Extension” or simply click on this link to install it.

Step 2. Once installed, go to Settings Safari > Extensions to enable DevTools Extension.

Step 3. Open Safari and visit any web page that you want to inspect. Tap on the AA icon from the address bar and select DevTools Extension.

Step 4. You will see a gear icon on the page. Tap on it and you will see the Developer Tools like on Desktop browser. When done, you can always click on the gear icon again to close Developer Tools.

Method 4: A Nice Browser That Spports View Source

Unfortunately, Chrome for iOS does not allow viewing page source. Alternatively, You can use Via Browser. It is a nice browser for iPhone and iPad that allows you to view page source and inspect elements.

Via Browser is also available for Android, so you can also use it to view page source on Android . Once you have the browser, you can tap the three bars icon on the bottom right and select Tools > View Source. It will open a new tab with the source code of your current page.

In addition, Via browser enables you to run userscripts and change user agent. As you know, some web apps only works on Desktop. If you use Via browser to change user agent to MacOS or Windows, then you can use Desktop web app on your iPhone or iPad.

Method 5: View Source App for iOS

You can also download a dedicated app for viewing HTML source code. For that, I recommend the free app View Source , which is designed for iPhone. Once you installed this app, you will see an option View Source in your Web Browser (Safari or Chrome) Share Sheet. You can simply tap on it to see the source code. 

In addition, it can also work as a standalone app. Within the app, you can input any webpage URL and the app will load its source code automatically. 

These 5 methods all work great on iOS devices. You can use any of them to view page source on iPhone or iPad based on your preference. For me, I prefer the Shortcuts method because Shortcuts allows you to customize it for all kinds of possibilities. 

1 thought on “ 5 Ways to View Page Source on iPhone or iPad [Inspect] ”

Thanks for this, shortcut now created, most useful.

Leave a Reply

Your email address will not be published. Required fields are marked *

You cannot copy content of this page

• a. Send us an email
• b. Anonymous form
• Buyer's Guide
• Upcoming Products
• Tips / Contact Us
• Podcast Instagram Facebook Twitter Mastodon YouTube Notifications RSS Newsletter

How to Use Safari's Built-in 2FA Code Generator

With online account hacking becoming increasingly widespread, Mac users should make sure they're taking every security measure available to them. In other words, consider using Apple verification codes to protect your accounts. Keep reading to learn how it works.

In macOS Monterey and later versions of its Mac operating system software, Apple's Safari browser (version 15 and later) includes a built-in two-factor authenticator that can generate verification codes for additional sign-in security. This means if a site offers 2FA, you can set up verification codes for it without downloading a third-party app.

Verification codes are backed up via iCloud , and once set up, the codes will autofill when you sign into the site using any Apple device linked to your Apple ID . This makes using 2FA on iPhone and iPad much more streamlined.

Enabling 2FA on the Account or Service

First, make sure you have the latest version of Safari (Safari 17). Once you've done that, you'll need to enable the use of a 2FA app on whichever website or service you are trying to secure. Note that if you've already enrolled an account with 2FA on a mobile app, you'll either have to unenroll from 2FA or use the current 2FA code from your mobile app.

Using Setup Keys

Once you've enabled 2FA on the account or service in question, you'll be asked to either enter a setup key on your device or scan a QR code using your device's camera. Note that you'll need to ensure that Safari's AutoFill feature is enabled (Safari ➝ Settings ➝ AutoFill) and the website's login credentials are saved in Safari for the 2FA code generator to work properly.

• Open Safari, then select Safari ➝ Settings... from the menu bar.
• Choose the Passwords tab, then either type your user password or use Touch ID to authenticate.
• Find and open the entry for the site you want to add 2FA to, then click Set Up next to "Verification Code," under Account Options.
• If the site offers a setup key, enter it in the Setup Key field. If it offers a QR code, Control-click it and choose "Set Up Verification Code". (Alternatively, you can download the QR code image and choose it using the option.)

Using Safari's Generated 2FA Code

• Open Safari and navigate to the website that requires two-factor authentication (2FA).
• Enter your username and password for the website as usual.
• When the site asks for a 2FA code, look for Safari's built-in suggestion that appears above the input field.
• Click on the 2FA code suggestion. Safari will automatically generate and fill in a 2FA code.
• Complete the login process by verifying the 2FA code, and you're done.

In future, when you come to log in to the site or service and you're prompted for a verification code, Safari will automatically display the latest code as an AutoFill option – all you need to do is click the code to enter it into the input field, and away you go.

Get weekly top MacRumors stories in your inbox.

Popular Stories

Delta Game Emulator Now Available From App Store on iPhone

All iPhone 16 Models to Feature Action Button, But Usefulness Debated

Hands-On With the New App Store Delta Game Emulator

NES Emulator for iPhone and iPad Now Available on App Store [Removed]

PlayStation, GameCube, Wii, and SEGA Emulator for iPhone and Apple TV Coming to App Store

Next article.

Our comprehensive guide highlighting every major new addition in iOS 17, plus how-tos that walk you through using the new features.

App Store changes for the EU, new emoji, Podcasts transcripts, and more.

Get the most out your iPhone 15 with our complete guide to all the new features.

A deep dive into new features in macOS Sonoma, big and small.

Revamped models with OLED displays, M3 chip, and redesigned Magic Keyboard accessory.

Updated 10.9-inch model and new 12.9-inch model, M2 chip expected.

Apple's annual Worldwide Developers Conference will kick off with a keynote on June 10.

Expected to see new AI-focused features and more. Preview coming at WWDC in June with public release in September.

Other Stories

9 hours ago by MacRumors Staff

12 hours ago by MacRumors Staff

1 day ago by MacRumors Staff

2 days ago by MacRumors Staff

Instantly share code, notes, and snippets.

unRob / index.html

• Download ZIP
• Star 0 You must be signed in to star a gist
• Fork 0 You must be signed in to fork a gist
• Embed Embed this gist in your website.
• Share Copy sharable link for this gist.
• Clone via HTTPS Clone using the web URL.
• Learn more about clone URLs
• Save unRob/3bd07a012597aa959c92 to your computer and use it in GitHub Desktop.

alecat88 commented Mar 31, 2020

does this works?

Sorry, something went wrong.

unRob commented Mar 31, 2020

@alecat88 I'm not sure, it was last updated nearly 5 years ago, and browsers change really fast. Try it out locally to know for sure!

I did a quick search with the title of this gist ( Safari vs video.source = Blob ) and found this working example: https://bl.ocks.org/unRob/3bd07a012597aa959c92

Yeah, that refreshed my memory, searching for that url i came up with a bug about it in webkit , and a stack overflow post I wrote about it.

Hope that helps!

Google launches Code Assist, its latest challenger to GitHub’s Copilot

At its Cloud Next conference, Google on Tuesday unveiled Gemini Code Assist , its enterprise-focused AI code completion and assistance tool.

If this sounds familiar, that’s likely because Google previously offered a similar service under the now-defunct Duet AI branding. That one became generally available in late 2023, but even then, Google already hinted that it would move the service away from its Codey model to Gemini in the near future. Code Assist is both a rebrand of the older service as well as a major update.

Code Assist, which Google Cloud demoed at its 30,000-attendee conference in Las Vegas, will be available through plug-ins for popular editors like VS Code and JetBrains.

Even more so than the Duet AI version, Code Assist is also a direct competitor to GitHub’s Copilot Enterprise  and not so much the basic version of Copilot. That’s because of a few Google-specific twists.

Among those is support for Gemini 1.5 Pro , which famously has a million-token context window, allowing Google’s tool to pull in a lot more context than its competitors. Google says this means more-accurate code suggestions, for example, but also the ability to reason over and change large chunks of code.

“This upgrade brings a massive 1 million-token context window, which is the largest in the industry. This allows customers to perform large-scale changes across your entire code base, enabling AI-assisted code transformations that were not possible before,” Brad Calder, Google’s VP and GM for its cloud platform and technical infrastructure, explained in a press conference ahead of Tuesday’s announcement.

Image Credits: Google

Like GitHub Enterprise, Code Assist can also be fine-tuned based on a company’s internal code base.

“Code customization using RAG with Gemini Code Assist significantly increased the quality of Gemini’s assistance for our developers in terms of code completion and generation,” said Kai Du, Director of Engineering and Head of Generative AI at Turing. “With code customization in place, we are expecting a big increase in the overall code-acceptance rate.”

This functionality is currently in preview.

Image Credits: Frederic Lardinois/TechCrunch

Another feature that makes Code Assist stand out is its ability to support codebases that sit on-premises, in GitLab, GitHub and Atlassian’s BitBucket, for example, as well as those that may be split between different services. That’s something Google’s most popular competitors in this space don’t currently offer.

Google is also partnering with a number of developer-centric companies to bring their knowledge bases to Gemini. Stack Overflow already announced its partnership with Google Cloud earlier this year. Datadog, Datastax, Elastic, HashiCorp, Neo4j, Pinecone, Redis, Singlestore and Snyk are now also partnering with Google through similar partnerships.

The real test, of course, is how developers will react to Code Assist and how useful its suggestions are to them. Google is making the right moves here by supporting a variety of code repositories and offering a massive context window, but if the latency is too high or the results simply aren’t that good, none of those features matter. And if it’s not significantly better than Copilot, which had quite a headstart, it may end up suffering the fate of AWS’ CodeWhisperer , which seems to have close to zero momentum .

It’s worth noting that in addition to Code Assist, Google today also announced the launch of CodeGemma, a new open model in its Gemma family that was fine-tuned for code generation and assistance. CodeGemma is now available through Vertex AI.

Cloud Assist

In addition to Code Assist, Google also today announced Gemini Cloud Assist to help “ cloud teams design, operate, and optimize their application lifecycle.” The tool can generate architecture configuration that are tailored to a company’s needs, for example, based on a description of the desired design outcome. It can also help diagnose issues and find their root causes, as well as optimize a company’s cloud usage to reduce cost or improve performance.

Cloud Assist will be available through a chat interface and embedded directly into a number of Google Cloud products.

Google brings Stack Overflow’s knowledge base to Gemini for Google Cloud

GitHub’s Copilot Enterprise is now generally available at $39 a month

Amazon launches CodeWhisperer, a GitHub Copilot-like AI pair programming tool

• United States
• United Kingdom

Beyond Git: How version control systems are evolving for devops

Version control is critical for managing changes to source code over time. here's how platforms like github are evolving to meet the demand for agility, scalability, performance, and more..

Contributing writer, InfoWorld |

Demand for version control systems

What to look for in a vcs, orienting around git and devops, generative ai in version control, cloud-based version control, popular version control systems.

Tools that manage changes to source code, programs, documents, or other collections of information are known by a variety of names: version control, revision control, source control, or source code management are all common descriptors. Regardless of what we call them, these systems have become increasingly vital in a world where software and data are essential commodities.

Version control systems (VCS) are used to track every change to source code. They help development teams and others manage these changes over time. As market pressures accelerate development efforts to bring products to market faster, version control has become more important than ever.

"As demand for more software increases, whether it be traditional software or emerging and growing areas of demand such as infrastructure as code , policy as code, and low-code generated code, there is a direct impact on the demand for version control,” says Christopher Condo, a principal analyst at Forrester Research.

“Since all code needs to be version controlled, any increased demand [for] software will result in an increased demand for version control systems,” he adds.

A report by research firm Acumen Research and Consulting expects the version control systems market to grow as more organizations adopt agile development methodologies , and as collaboration and code management become more important.

The market for these types of products will expand by an estimated 12 percent compound annual growth rate to reach $2.68 billion by 2030, according to the report. The increasing adoption of cloud-based version control systems is also driving market growth, it says.

“Version control or source control management was originally designed for developer source code,” says International Data Corp. Program Vice President, Software Development, DevOps & DevSecOps Jim Mercer. “But as we have evolved into an everything-as-code approach with things such as infrastructure as code, security as code, networking as code, and so forth, there are more consumers of version control.”

With everything as code, “this has paved the way for GitOps , a development and deployment methodology that uses Git version control to manage the entire application infrastructure and configurations as code in version control,” Mercer says. “Further, code has become the crown jewel for modern digital businesses, and therefore version control requires more functionality and security rigor to support and secure the code.”

Version control systems are evolving to meet the changing technical landscape and market demand. At a basic level, a version control system lets developers manage different versions of source code, configurations, and any other artifact that will change over time, says Condo. Teams also look for a variety of additional key features depending on the size and priorities of the organizations.

One such feature is scalability. These systems should be able to manage code across domains and platforms, enabling developers and others within an organization to use the same version control system, notes Mercer. Scalability is especially important for a growing company with expanding development initiatives.

Performance is another important benchmark. Version control software should be able to perform well wherever it is used within an organization, Mercer says.

A version control system should also have branching capabilities. Branching allows an object under version control to be duplicated so that each object thereafter can be modified separately and in parallel.

“As work is performed it’s a common practice to create [a] temporary branch for new work, to avoid disrupting work on the main branch,” Condo says. “Likewise, when new work is ready to be merged back into a main branch, the ability to merge a branch into a trunk is a critical capability.”

Collaboration is also essential for modern version control systems. Development teams oftentimes are working in different regions, and need to effectively collaborate on projects. Collaboration ensures that everyone is working from the same source, whether it’s with a single codebase or multiple branches.

Extensibility via secure APIs is another feature to look for. “Increasingly, version control systems are the system-of-record for orchestrating automations for triggering testing, deployment, and release automation into production,” Condo says. “Therefore, having secure APIs that can integrate version control with deployment and release management tools is necessary to achieve continuous delivery.”

Finally, these systems should provide data integrity and history, Mercer says. Users should be able to rely on the code version history to roll backward and forward as needed.

Many version control systems have been developed over the past 20+ years, Mercer says, including Subversion, ClearCase, Mercurial, and others.

“However, most teams favor a Git-based solution based on the Git open source project , so the primary options are GitHub, GitLab, and Bitbucket,” Mercer says. “Most other version control systems have created bridges or integrations into Git, given its dominance.”

Most of the version control systems, including GitLab and GitHub , have added features to evolve into full-featured devops platforms, Mercer says. “Other developments tend to be around scalability, performance, security, and the ability to create policies to ensure source code is protected from things such as code leakage, enforcement of digital provenance, etc.,” he says.

GitHub, GitLab, and Bitbucket “have evolved dramatically to be more the ‘modern developer environment,’” says Thomas Murphy, senior director analyst at research firm Gartner. “They run the build, they manage the project, they manage documentation, they can package, test, deploy software.”

Murphy notes that these platforms are now using generative AI assistants to help create and update code and perform other tasks. AI-powered assistants will help with common tasks such as creating commit messages or helping with branching and merging, which can sometimes become complicated, Condo says.

GitHub is one of the leaders when it comes to version control system innovation, Condo says. GitHub Copilot is a genAI application that uses data from GitHub to train large language models (LLMs), which then can assist developers with coding suggestions. GitLab is taking a similar approach with AI-powered assistants and is working hard to differentiate itself from GitHub, he says.

But the emergence of genAI and how LLMs are trained is a particular concern for some organizations, Condo says. “It’s public information that tools like GitHub Copilot use source code from public [version control] systems they host to train their model,” he says. “Buyers need to decide if they are comfortable with that or if they would prefer their code not be used for that purpose.”

Organizations with sensitive algorithms or concerns that intellectual property (IP) will be leaked need to look for safeguards to protect their IP from being used as training data, Condo says. “If the goal is to share the IP as an open-sourced project, it might be perfectly fine, as long as the customer can decide,” he says.

Another trend is the shift toward cloud-based version control systems in recent years, Acumen says. These services offer benefits such as real-time collaboration, accessibility from anywhere, and lower upfront costs compared with on-premises systems, the firm says.

GitHub, GitLab, and other online repositories allow organizations to use their software-as-a-service products without the hassle of operating a self-hosted version control system, Condo says. “This makes it easier for distributed teams to collaborate across geographies in ways that self-hosted systems may find more challenging,” he says.

Organizations that choose to run their own on-premises version control system have their own set of concerns, and must have the necessary skills and resources to do so successfully and securely, Condo says.

“They must have the resources to effectively operate a secure VCS while still enabling access and collaboration with teams in other regions,” Condo says. “Even companies based solely in the US and [that] do business in the US must take this into consideration, as increasingly they are using remote developers or leveraging systems integrators that have developers in other global regions.”

On top of that, running a version control system also means keeping pace with change, says Condo. Version control platforms “are constantly evolving and being updated,” he says. “It will do an enterprise absolutely no good if it lacks the bandwidth or skillset to maintain the keys to their kingdom.”

What are the leading version control systems today and how do they stack up? Here's a quick look at the field.

Apache Subversion (SVN)

A software versioning and revision control system distributed as open source under the Apache License. Developers can use SVN to maintain current and historical versions of files including source code, web pages, and documentation.

A Git-based source code repository hosting and collaboration service owned by Atlassian. Bitbucket offers both commercial plans and free accounts with an unlimited number of private repositories. It is mostly used for code and code reviews.

The most widely used version control system. Git is a free, open-source devops tool used for source code management. It can handle small to extremely large development projects. Using Git to track changes in source code allows multiple developers to collaborate on a non-linear development project.

A platform from Microsoft’s subsidiary GitHub that allows developers to create, manage, and share code. GitHub delivers the distributed version control of Git as well as access control, bug tracking, task management, and other capabilities. The platform offers a large open-source repository, has tools for managing the software project and community, and has a broad set of partners that support it with add-in functions.

Based on Git, GitLab is an open-source repository manager used for collaboration and version control. Teams can use it to manage projects, track issues, and review code.

A free, distributed source control management tool for software developers that can handle projects of any size. Mercurial was created with platform independence in mind.

Supports Git but offers a proprietary product, Helix Core. Perforce is a version control platform for developers that tracks and manages changes to source code, digital assets, and large binary files.

Team Foundation Version Control (TFVC)

This platform from Microsoft is a centralized version control system, as opposed to distributed version control such as Git. TFVC lets users apply granular permissions and restrict access down to a file level.

Next read this:

• Why companies are leaving the cloud
• 5 easy ways to run an LLM locally
• Coding with AI: Tips and best practices from developers
• Meet Zig: The modern alternative to C
• What is generative AI? Artificial intelligence that creates
• The best open source software of 2023
• Version Control Systems
• Software Development
• Enterprise Buyer’s Guides

Copyright © 2024 IDG Communications, Inc.

• Español – América Latina
• Português – Brasil
• Tiếng Việt
• Chrome for Developers

New in Chrome 124

Here are the highlights in Chrome 124:

There are two new APIs that allow the declarative shadow DOM to be used from JavaScript.

• You can use streams in Web Sockets .
• View Transitions get a little better.
• And there's plenty more .

Want the full run down? Check out the Chrome 124 Release Notes .

Use declarative shadow DOM in JavaScript

setHTMLUnsafe() is similar to innerHTML , and lets you set the inner HTML of an element to the string provided. This helps when you have some HTML that includes a declarative shadow DOM, like this.

If you just use innerHTML , the browser won't parse it properly, and there's no shadow DOM. But with setHTMLUnsafe() , your shadow DOM is created, and the element is parsed as you'd expect.

The other API is parseHTMLUnsafe() , and it works similarly to DOMParser.parseFromString() .

Both of these APIs are unsafe , which means they don't do any input sanitization. So you'll want to make sure that whatever you feed them, is safe. In an upcoming release, we expect see a version that does provide sanitization of the input.

Finally, both of these APIs are already supported in the latest version of Firefox and Safari!

WebSocket Stream API

WebSockets are a great way to send data back and forth between the user's browser and the server without having to rely on polling. This is great for things like chat apps, where you want to deal with information as soon as it comes in.

But what if the data arrives faster than you can handle?

That's called back pressure, and can cause some serious headaches for you. Unfortunately, the WebSocket API doesn't have a nice way to deal with back pressure.

The WebSocket Stream API gives you the power of streams, and web sockets, which means back pressure can be applied without any extra cost.

Start by constructing a new WebSocketStream and passing it the URL of the WebSocket server.

Next, you wait for the connection to be opened, which results in a ReadableStream and a WritableStream . By calling the ReadableStream.getReader() method, you get a ReadableStreamDefaultReader which you can then read() data from until the stream is done.

To write data, call the WritableStream.getWriter() method, which gives you a WritableStreamDefaultWriter , that you can then write() data to.

View transitions improvements

I'm excited about the View Transitions features, and there are two new features in Chrome 124 designed to make view transitions easier.

The pageswap event is fired on a document's window object when a navigation will replace the document with a new document.

And document render-blocking which lets you block rendering of a document until the critical content has been parsed, ensuring a consistent first paint across all browsers.

Of course there's plenty more.

disallowReturnToOpener hints to the browser that it shouldn't show a button in the picture-in-picture window that allows the user to go back to the opener tab.

Keyboard-focusable scroll containers improves accessibility by making scroll containers focusable using sequential focus navigation.

And universal install allows users to install any page, even those not meeting the current PWA criteria .

Further reading

This covers only some key highlights. Check the following links for additional changes in Chrome 124.

• Chrome 124 Release Notes
• What's new in Chrome DevTools (124)
• ChromeStatus.com updates for Chrome 124
• Chromium source repository change list
• Chrome release calendar

To stay up to date, subscribe to the Chrome Developers YouTube channel , and you'll get an email notification whenever we launch a new video.

I'm Pete LePage, and as soon as Chrome 125 is released, we'll be right here to tell you what's new in Chrome!

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2024-04-16 UTC.