According to Microsoft, GitHub has 28 million users and hosts 85 million codebases.
|
|
Some apps had codebases just too complex to be automatically translated and emulated for Intel.
|
|
That makes it hard to get third-party opinions on anything but the most simple codebases.
|
|
It's unclear whether the NSA has found vulnerabilities in those protocols because it's harder to audit big codebases.
|
|
It analyzes codebases, offers data about which APIs are being used and provides general information about developer productivity and other metrics.
|
|
In a sprint to merge the codebases of their engines, they camped out in Helgason's apartment for several days while he was out of town.
|
|
Ex-Uber employee Jacobs: Uber team "successes" included acquiring leaked codebases of competitors on GitHub, getting info on drivers overseas, also general metrics around competitors overseas.
|
|
The service boasts about 28 million users and hosts 85 million codebases for a wide variety of organizations, including Apple, Amazon, Facebook, Google, Walmart, and the US government.
|
|
While many companies have been able to get away with poor or unusable codebases, I doubt developers will let future companies get away with so much smoke and mirrors.
|
|
Zuckerberg built the system in Python, PHP and Objective C — but like most programming problems, the bulk of the work seems to have been stitching together existing systems and codebases.
|
|
But if you do so with a native app, be aware you're implicitly deciding to have two development teams, and two separate and out-of-sync codebases to maintain, somewhere down the road.
|
|
The startup is launching out of Y Combinator's latest class with a product that integrates directly into customer codebases and that lets engineers easily flag features to roll out to targeted groups of users.
|
|
The company also tells me that the enterprise version can handle larger codebases so that even complex queries over a large data set only takes a few seconds (or minutes if it's a really large codebase).
|
|
It's also a whole new way of managing software in a cloud-native environment, which means that developers and managers are increasingly needing to work together to migrate legacy codebases from old models to cloud and Git-native ones.
|
|
As vibrators with shoddy encryption and hastily put together codebases begin to flood the market, bedrooms around the world could quickly become filled with vulnerable entry points (and not the ones those dildos and butt plugs were originally intended to pleasure).
|
|
Reorganizing the codebases for Facebook's messaging services so that they are essentially one application with three different interfaces could make it much harder for a court or regulator to order a breakup of Facebook's properties, as some critics are proposing.
|
|
" Trail of Bits added that "The quantity of findings discovered during this assessment, the complexity of the system, and the lack of access to both a running test environment as well as certain codebases leads us to believe that other vulnerabilities are latent.
|
|
"I can't feel good about my job if the profits I help generate and the codebases I contribute to can be leveraged to accelerate fossil fuel extraction or fund groups that delay or deny urgent climate action," Sam Kern, a UX engineer at Google, told the Guardian.
|
|
And it was not just brain power that was indelibly interwoven in the development of the Event Horizon Telescope; like many codebases, the "eht-imaging" repository at the center of this debate is indebted to open source technologies, starting with Python, the language for the project.
|
|
Some of the codebases below are incredibly popular, with many servers based on them; other codebases may only be found on archive sites, making them available but effectively extinct. For a list of specific servers using some of these codebases, see the Chronology of MUDs article.
|
|
Although, the codebases for Quake and Quake II were separate GPL releases.
|
|
A separate codebase or a distributed codebase keeps individual repositories smaller and more manageable, enforcing at the same time separation between components, but it also requires integration between codebases (or with the main repository), and complicates changes that span multiple codebases. In terms of standards, referring to multiple codebases as "distinct" declares that there are independent implementations without shared source code and that, historically, these implementations did not evolve from a common project. This may be a way of demonstrating interoperability by showing two independent pieces of software that implement a given standard.
|
|
The MUD trees below depict hierarchies of derivation among MUD codebases. Solid lines between boxes indicate code relationships, while dotted lines indicate conceptual relationships. Dotted boxes indicate that the codebase is outside the family depicted. Note that codebases are different from individual servers, in the same way that a biological family/genus/species is different from a specific bird at a zoo or fossil imprint in a museum.
|
|
KDevelop is part of the KDE project, and is based on KDE Frameworks and Qt. The C/C++ backend uses Clang to provide accurate information even for very complex codebases.
|
|
Puns on the "wet dirt" meaning of "mud" are endemic, as with, for example, the names of the ROM (Rivers of MUD), MUCK, MUSH, and CoffeeMUD codebases and the MUD Muddy Waters.
|
|
Still supported in Delphi and Free Pascal. FPC also packages its own substitutes for the libraries/units. Delphi doesn't. The Free Pascal 1.0 series and the FPC textmode IDE are the largest open codebases in this dialect.
|
|
During the early 1990s, LPMud was one of the most popular MUD codebases. Descendants of the original LPMud include MudOS, DGD, SWLPC, FluffOS, and the Pike programming language, the latter the work of long-time LPMud developer Fredrik "Profezzorn" Hübinette.
|
|
Includes his opinions about Dashboard. Includes a response to the "Desk Accessories argument". The codebases for Konfabulator and Dashboard are also different: Konfabulator uses XML and JavaScript to generate Widgets, whereas Dashboard uses HTML, CSS, JavaScript, and Objective-C.Dashboard vs.
|
|
AberMUD4 was improved by Alf Salte and Gjermund "Nicknack" Sørseth to create Dirt. Their May 1993 final release of Dirt 3.1.2 is used by most of the remaining AberMUD games on the internet. AberMUD's legacy lives on in the three major codebases it inspired: TinyMUD, LPMud and DikuMUD.
|
|
In his book Designing Virtual Worlds, Richard Bartle (co-creator of the original MUD) cited DikuMUD as one of the five "major codebases used for (textual) virtual worlds". Bartle further described how DikuMUD went in the opposite direction to TinyMUD and LPMud, by providing a very well organised hard-coded game that ran "out of the box". It has been proposed by Raph Koster (lead designer of Ultima Online and chief creative officer of EverQuest II) that Diku has resulted in the greatest proliferation of gameworlds due to being the easiest to set up and use. He further pointed out that "Diku codebases did eventually popularize many of the major developments in muds", and that the Diku gameplay provided inspiration for numerous MMORPGs, including EverQuest, World of Warcraft and Ultima Online.
|
|
In October 2007, PWLib was renamed to PTLib. The OPAL and PTLib repositories were migrated to Subversion and maintenance of these codebases was moved to the SourceForge opalvoip project. A fork of OpenH323 called H323Plus was created at the same time and was moved to the SourceForge H323Plus project. There is no known development currently active on the OpenH323 codebase.
|
|
There are alternatives to the DirectX family of APIs, with OpenGL, its successor Vulkan, Metal and Mantle having the most features comparable to Direct3D. Examples of other APIs include SDL, Allegro, OpenMAX, OpenML, OpenAL, OpenCL, FMOD, SFML etc. Many of these libraries are cross-platform or have open codebases. There are also alternative implementations that aim to provide the same API, such as the one in Wine.
|
|
Though the Merc MUD codebases usually come with a set of 52 stock areas, all of A.V.A.T.A.R.'s areas are non-stock. Some areas retain the theme of the stock areas they replaced. The MUD continues to grow, with 327 areas online as of January 2014. In addition to these permanent additions, temporary areas and quests are regularly added to the MUD, and older, less-visited areas are either revamped or removed.
|
|
OpenSIPS, a fork of SER which has diverged—deciding to "go their own way" from the SER and OpenSER codebases—is a free software implementation of SIP for voice over IP (VoIP) that can be used to handle voice, text and video communication. OpenSIPS is intended for installations serving thousands of calls and is IETF RFC 3261 compliant. The software was recognized by Google in 2017 with their Open Source Peer Bonus award.
|
|
From a programming standpoint, there was nearly nothing as easy to use as PDO. However, PDO was also reliant entirely on Objective-C to function. This was a price most were unwilling to pay, as at the time C++ was more widely used and the effort to shift codebases to an entirely new language and paradigm was considered too onerous. PDO never saw much use, and NeXT's emphasis shifted to its new WebObjects framework in 1995.
|
|
Foswiki is an enterprise wiki, typically used to run a collaboration platform, knowledge base or document management system. Users can create wiki applications using the Topic Markup Language (TML), and developers can extend its functionality with plugins. The Foswiki project was launched in October 2008 when a dispute about the future direction of TWiki could not be settled, resulting in the decision of nearly all key TWiki contributors to fork. Since then the codebases have diverged significantly.
|
|
While WMC 3.0 and WMC 4.0 offer similar feature-set, they are built using different codebases. With WMP integration, WMC can make available the entire media library managed by WMP. When a shared library is browsed by the WMP client, it can be browsed, filtered and sorted like a regular WMP media library. On Windows XP by default, Windows Media Connect 2.0 does not work after Windows Media Player 11 has been installed, although Windows Media Player 11 only includes the UPnP AV server and does not include the client.
|
|
Kamailio's roots go back to 2001, when the first line of SIP Express Router (SER) was written; at the time, the working group published results at iptel.org—in September 2002 the code itself was published under the GPL. The first fork of SER came in 2005—OpenSER—which would later merge back into the code that would become Kamailio. The codebases of SER and OpenSER (by then known as Kamailio) converged in December 2012, and it was decided to continue to use Kamailio as the main name of the project, which remains open source.
|
|
In 1990, the release of DikuMUD, which was inspired by AberMUD, led to a virtual explosion of hack and slash MUDs based upon its code. DikuMUD inspired numerous derivative codebases, including CircleMUD, Merc, ROM, SMAUG, and GodWars. The original Diku team comprised Sebastian Hammer, Tom Madsen, Katja Nyboe, Michael Seifert, and Hans Henrik Staerfeldt. DikuMUD had a key influence on the early evolution of the MMORPG genre, with EverQuest (created by avid DikuMUD player Brad McQuaid) displaying such Diku- like gameplay that Verant developers were made to issue a sworn statement that no actual DikuMUD code was incorporated.
|
|
XEmacs 21.5 on GNU/Linux Lucid Emacs, based on an early version of GNU Emacs 19, was developed beginning in 1991 by Jamie Zawinski and others at Lucid Inc. One of the best- known forks in free software development occurred when the codebases of the two Emacs versions diverged and the separate development teams ceased efforts to merge them back into a single program. After Lucid filed for bankruptcy, Lucid Emacs was renamed XEmacs and remains the second most popular variety of Emacs, after GNU Emacs. XEmacs development has slowed, with the most recent stable version 21.4.
|
|
Multiple projects can have separate, distinct codebases, or can have a single, shared or . This is particularly the case for related projects, such as those developed within the same company. In more detail, a monolithic codebase typically entails a single repository (all the code in one place), and often a common build system or common libraries. Whether the codebase is shared or split does not depend on the system architecture and actual build results; thus, a monolithic codebase, which is related to the actual development, does not entail a monolithic system, which is related to software architecture or a single monolithic binary.
|
|
Infer performs checks for null pointer exceptions, resource leaks, annotation reachability, missing lock guards, and concurrency race conditions in Android and Java code. It checks for null pointer problems, memory leaks, coding conventions and unavailable API’s in C, C++ and Objective C. Infer uses a technique called bi- abduction Separation logic and bi-abduction, page, Infer project site. to perform a compositional program analysis that interprets program procedures independently of their callers. It is claimed that this enables Infer to scale to large codebases and to run quickly on code-changes in an incremental fashion, while still performing an inter-procedural analysis that reasons across procedure boundaries.
|
|
The project will integrate independent open protocols and standards by means of a framework for use-specific modules, including blockchains with their own consensus and storage routines, as well as services for identity, access control and smart contracts. Early on there was some confusion that Hyperledger would develop its own bitcoin-type cryptocurrency, but Behlendorf has unreservedly stated that the Hyperledger Project itself will never build its own cryptocurrency. In early 2016, the project began accepting proposals for incubation of codebases and other technologies as core elements. One of the first proposals was for a codebase combining previous work by Digital Asset, Blockstream's libconsensus and IBM's OpenBlockchain.
|
|
It can then "play back" the same actions by executing the same command objects again in sequence. If the program embeds a scripting engine, each command object can implement a method, and user actions can then be easily recorded as scripts. ; Mobile Code : Using languages such as Java where code can be streamed/slurped from one location to another via URLClassloaders and Codebases the commands can enable new behavior to be delivered to remote locations (EJB Command, Master Worker). ; Multi-level undo : If all user actions in a program are implemented as command objects, the program can keep a stack of the most recently executed commands.
|
|
The source code for most widely used MUSH servers is open source and available from its current maintainers. A primary feature of MUSH codebases that tends to distinguish it from other multi-user environments is the ability, by default, of any player to extend the world by creating new rooms or objects and specifying their behavior in the MUSH's internal scripting language. Another is the default lack of much player or administrative hierarchy imposed by the server itself. Over the years, both of these traits have become less pronounced, as many server administrators choose to eliminate or heavily restrict player-controlled building, and several games have custom coded systems to restore more of a hierarchal system.
|
|
In formal methods logic is used to specify and prove properties of computer programs. Abduction has been used in mechanized reasoning tools to increase the level of automation of the proof activity. A technique known as bi-abduction, which mixes abduction and the frame problem, was used to scale reasoning techniques for memory properties to millions of lines of code; logic-based abduction was used to infer pre-conditions for individual functions in a program, relieving the human of the need to do so. It led to a program-proof startup company which was acquired by Facebook, and the Infer program analysis tool which led to thousands of bugs being prevented in industrial codebases.
|
|
Apache Incubator is the gateway for open-source projects intended to become fully fledged Apache Software Foundation projects. The Incubator project was created in October 2002 to provide an entry path to the Apache Software Foundation for projects and codebases wishing to become part of the Foundation's efforts. All code donations from external organizations and existing external projects wishing to move to Apache must enter through the Incubator. The Apache Incubator project serves on the one hand as a temporary container project until the incubating project is accepted and becomes a top- level project of the Apache Software Foundation or becomes subproject of a proper project such as the Jakarta Project or Apache XML.
|
|
The reliance on Adobe for decoding Flash makes its use on the World Wide Web a concern—the completeness of its public specifications are debated, and no complete implementation of Flash is publicly available in source code form with a license that permits reuse. Generally, public specifications are what makes a format re- implementable (see future proofing data storage), and reusable codebases can be ported to new platforms without the endorsement of the format creator. Adobe's restrictions on the use of the SWF/FLV specifications were lifted in February 2009 (see Adobe's Open Screen Project). However, despite efforts of projects like Gnash, Swfdec, and Lightspark, a complete free Flash player is yet to be seen, as of September 2011.
|
|
In November 2013, speaking about Windows RT at the UBS Global Technology Conference, Julie Larson-Green made comments discussing the future of Microsoft's mobile strategy surrounding the Windows platform. Larson-Green stated that in the future (accounting for Windows, Windows RT, and Windows Phone), Microsoft was "[not] going to have three [mobile operating systems]." The fate of Windows RT was left unclear by her remarks; industry analysts interpreted them as signs that Microsoft was preparing to discontinue Windows RT due to its poor adoption, while others suggested that Microsoft was planning to unify Windows with Windows Phone. Microsoft ultimately announced its "Universal Windows Apps" platform at Build 2014, which would allow developers to create WinRT apps for Windows, Windows Phone, and Xbox One that share common codebases.
|
|
Portion of a Quattro Pro for Windows spreadsheet Quattro Pro began as a DOS program (like Lotus 1-2-3) but with the growing popularity of Windows from Microsoft, a Windows version of Quattro needed to be written. There was almost nothing from the DOS code that could be moved to the Windows project, so the Quattro Pro for Windows (QPW) was written from scratch. Both the QPW and Paradox for Windows codebases (the latter being another Borland database application) were based on Borland's internal pilot project with object oriented UI code for Windows. This project ran simultaneously with the Borland language group investigating the desirability of a C++ compiler, and the company decided to make a bet on C++.
|
|
Dave's own version of Citadel (DOC) is a variant of the Citadel/UX Bulletin board system (BBS) software which was developed specifically to run ISCA BBS in the late 1980s. It is based on Citadel/UX 3.0 but very heavily modified to suit the specific needs of ISCA BBS, which at its peak was a massive system supporting hundreds of simultaneous users. DOC and its descendants are now used by a number of Internet BBSes, including some in Latin America, which have been heavily modified, support 8-bit characters, and are presented in Spanish. Along with its offshoots DOC has inspired at least four clone codebases, including YAWC, which is likely the oldest, Jammin (code), which has since become WeIrDo, bbs100 (which is licensed under GPL), and A better Citadel (ABC).
|
|
VA Software continued to say that a new source code release would be made at some point, but it never was. Some time later, 2002, Tim Perdue left VA and started GForge LLC which released both an open source and commercial version of GForge. Both codebases were forked from the last publicly released version, 2.6, and merged the debian-sf fork, previously maintained by Roland Mas and Christian Bayle, into the project. In February 2009 there was a break-up of the original open source (GPL) version of GForge with some of the developers of GForge releasing the continued development of the old open source code under the new name of FusionForge while Perdue and his new company focused on a commercial offering (GForge Advanced Server and later GForgeNext).
|
|
The increasing computing power and decreasing cost of processors such as the Intel 80386, Intel 80486, and Motorola 68030, caused the rise of 3D graphics, and multimedia abilities through sound cards and CD-ROMs. Early 3D games began with flat shading graphics (Elite, Starglider 2 or Alpha Waves), and then simple forms of texture mapping. 1989 and the early 1990s saw the release and spread of the Multi-User Dungeon (MUD) codebases DikuMUD and LPMud, leading to a tremendous increase in the proliferation and popularity of MUDs. Before the end of the decade, the evolution of the genre continued through graphical MUDs into the first massively multiplayer online role-playing games (MMORPGs), which freed users from the limited number of simultaneous players in other games and brought persistent worlds to the mass market.
|
|
As a result, a monolithic codebase may and (for large codebases) often will consist of separate components, instead of carrying only a single system or single binary; a distributed codebase (with multiple components) can be used to build a single monolithic system or even a single binary. For example, the Linux kernel is architecturally a single monolithic kernel, but it consists of separate binaries (loadable components), and is developed in multiple distributed repositories. There are both advantages and disadvantages to a monolithic codebase, when it is compared to a distributed codebase. Most simply, a monolithic codebase simplifies integrationchanges to different components or refactoring of code between components can be done easily and atomicallyand allows operations across the entire codebase, but requires a larger repository and makes it easier to introduce wide-ranging technical debt.
|
|
The majority of such games owe their achievement to simplistic software development kits such as the Japanese RPG Maker series. ;MUDs and MMORPGs 1989 and the early 1990s saw the release and spread of the MUD codebases DikuMUD and LPMud, leading to a tremendous increase in the proliferation and popularity of MUDs. Before the end of the decade, the evolution of the genre continued through "graphical MUDs" into the first massively multiplayer online role-playing games (MMORPGs), a term coined by Richard Garriott in 1997. That genre, as currently defined, began with Meridian 59 in 1995, but first truly came into its own with Ultima Online in 1997, a game that provided a core idea of what later MMORPGs would become, featuring a massive continent on which players could interact with others from around the world, fight mythical creatures, and cast spells.
|
|