text:
List of computing and IT abbreviations

This is a list of computing and IT acronyms, initialisms and abbreviations.

0–9

 * 1GL—First-Generation Programming Language
 * 1NF—First Normal Form
 * 10B2—10BASE-2
 * 10B5—10BASE-5
 * 10B-F—10BASE-F
 * 10B-FB—10BASE-FB
 * 10B-FL—10BASE-FL
 * 10B-FP—10BASE-FP
 * 10B-T—10BASE-T
 * 100B-FX—100BASE-FX
 * 100B-TX—100BASE-TX
 * 100BVG—100BASE-VG
 * 286—Intel 80286 processor
 * 2B1Q—2 Binary 1 Quaternary
 * 2FA—Two-factor authentication
 * 2GL—Second-Generation Programming Language
 * 2NF—Second Normal Form
 * 3GL—Third-Generation Programming Language
 * 3GPP—3rd Generation Partnership Project – 3G comms
 * 3GPP2—3rd Generation Partnership Project 2
 * 3NF—Third Normal Form
 * 386—Intel 80386 processor
 * 486—Intel 80486 processor
 * 4B5BLF—4-bit 5-bit Local Fiber
 * 4GL—Fourth-Generation Programming Language
 * 4NF—Fourth Normal Form
 * 5GL—Fifth-Generation Programming Language
 * 5NF—Fifth Normal Form
 * 6NF—Sixth Normal Form
 * 8B10BLF—8-bit 10-bit Local Fiber
 * 802.11—Wireless LAN

A

 * A11Y—Accessibility
 * AAA—Authentication Authorization, Accounting
 * AABB—Axis Aligned Bounding Box
 * AAC—Advanced Audio Coding
 * AAL—ATM Adaptation Layer
 * AALC—ATM Adaptation Layer Connection
 * AARP—AppleTalk Address Resolution Protocol
 * ABAC—Attribute-Based Access Control
 * ABCL—Actor-Based Concurrent Language
 * ABI—Application Binary Interface
 * ABM—Asynchronous Balanced Mode
 * ABR—Area Border Router
 * ABR—Auto Baud-Rate detection
 * ABR—Available Bitrate
 * ABR—Average Bitrate
 * ABR—Adaptive Bitrate (Streaming)
 * AC—Acoustic Coupler
 * AC—Alternating Current
 * ACD—Automatic Call Distributor
 * ACE—Advanced Computing Environment
 * ACID—Atomicity Consistency Isolation Durability
 * ACK—ACKnowledgement
 * ACK—Amsterdam Compiler Kit
 * ACL—Access Control List
 * ACL—Active Current Loop
 * ACM—Association for Computing Machinery
 * ACME—Automated Classification of Medical Entities
 * ACP—Airline Control Program
 * ACPI—Advanced Configuration and Power Interface
 * ACR—Allowed Cell Rate
 * ACR—Attenuation to Crosstalk Ratio
 * AD—Active Directory
 * AD—Administrative Domain
 * ADC—Analog-to-Digital Converter
 * ADC—Apple Display Connector
 * ADB—Apple Desktop Bus
 * ADCCP—Advanced Data Communications Control Procedures
 * ADO—ActiveX Data Objects
 * ADSL—Asymmetric Digital Subscriber Line
 * ADT—Abstract Data Type
 * AE—Adaptive Equalizer
 * AES—Advanced Encryption Standard
 * AF—Anisotropic Filtering
 * AFP—Apple Filing Protocol
 * AGI—Artificial General Intelligence
 * AGP—Accelerated Graphics Port
 * AH—Active Hub
 * AI—Artificial Intelligence
 * AIX—Advanced Interactive eXecutive
 * Ajax—Asynchronous JavaScript and XML
 * AL—Active Link
 * AL—Access List
 * ALAC—Apple Lossless Audio Codec
 * ALGOL—Algorithmic Language
 * ALSA—Advanced Linux Sound Architecture
 * ALU—Arithmetic and Logical Unit
 * AM—Access Method
 * AM—Active Matrix
 * AMOLED—Active-Matrix Organic Light-Emitting Diode
 * AM—Active Monitor
 * AM—Allied Mastercomputer
 * AM—Amplitude Modulation
 * AMD—Advanced Micro Devices
 * AMQP—Advanced Message Queuing Protocol
 * AMR—Audio Modem Riser
 * ANN—Artificial Neural Network
 * ANSI—American National Standards Institute
 * ANT—Another Neat Tool
 * AoE—ATA over Ethernet
 * AOP—Aspect-Oriented Programming
 * AOT—Ahead-Of-Time
 * APCI—Application-Layer Protocol Control Information
 * API—Application Programming Interface
 * APIC—Advanced Programmable Interrupt Controller
 * APIPA—Automatic Private IP Addressing
 * APL—A Programming Language
 * APR—Apache Portable Runtime
 * ARC—Adaptive Replacement Cache
 * ARC—Advanced RISC Computing
 * ARIN—American Registry for Internet Numbers
 * ARM—Advanced RISC Machines
 * AROS—AROS Research Operating System
 * ARP—Address Resolution Protocol
 * ARPA—Address and Routing Parameter Area
 * ARPA—Advanced Research Projects Agency
 * ARPANET—Advanced Research Projects Agency Network
 * AS—Access Server
 * ASCII—American Standard Code for Information Interchange
 * AuthIP—Authenticated Internet Protocol
 * ASG—Abstract Semantic Graph
 * ASIC—Application-Specific Integrated Circuit
 * ASIMO—Advanced Step in Innovative Mobility
 * ASLR—Address Space Layout Randomization
 * ASM—Algorithmic State Machine
 * ASMP—Asymmetric Multiprocessing
 * ASN.1—Abstract Syntax Notation 1
 * ASP—Active Server Pages
 * ASP—Application Service Provider
 * ASR—Asynchronous Signal Routine
 * AST—Abstract Syntax Tree
 * AT—Advanced Technology
 * AT—Access Time
 * AT—Active Terminator
 * ATA—Advanced Technology Attachment
 * ATAG—Authoring Tool Accessibility Guidelines
 * ATAPI—Advanced Technology Attachment Packet Interface
 * ATM—Asynchronous Transfer Mode
 * AuthN—Authentication
 * AuthZ—Authorization
 * AV—Antivirus
 * AVC—Advanced Video Coding
 * AVI—Audio Video Interleaved
 * AWK—Aho Weinberger Kernighan
 * AWS—Amazon Web Services
 * AWT—Abstract Window Toolkit

B

 * B2B—Business-to-Business
 * B2C—Business-to-Consumer
 * B2E—Business-to-Employee
 * BAL—Basic Assembly Language
 * BAM—Block Availability Map
 * Bash—Bourne-again shell
 * BASIC—Beginner's All-Purpose Symbolic Instruction Code
 * BBP—Baseband Processor
 * BBS—Bulletin Board System
 * BC—Business Continuity
 * BCC—Blind Carbon Copy
 * BCD—Binary Coded Decimal
 * BCD—Boot Configuration Data
 * BCNF—Boyce–Codd normal form
 * BCP—Business Continuity Planning
 * BCP—Best Current Practice
 * BE—Backend
 * BEEP—Blocks Extensible Exchange Protocol
 * BER—Bit Error Rate
 * BFD—Bidirectional Forwarding Detection
 * BFD—Binary File Descriptor
 * BFS—Breadth-First Search
 * BFT—Byzantine Fault Tolerant
 * BGP—Border Gateway Protocol
 * BI—Business Intelligence
 * BiDi—Bi-Directional
 * bin—binary
 * BINAC—Binary Automatic Computer
 * BIND—Berkeley Internet Name Domain
 * BIOS—Basic Input Output System
 * BJT—Bipolar Junction Transistor
 * bit—binary digit
 * Blob—Binary large object
 * Blog—Web Log
 * BMP—Basic Multilingual Plane
 * BNC—Baby Neill Constant
 * BOINC—Berkeley Open Infrastructure for Network Computing
 * BOM—Byte Order Mark
 * BOOTP—Bootstrap Protocol
 * BPDU—Bridge Protocol Data Unit
 * BPEL—Business Process Execution Language
 * BPL—Broadband over Power Lines
 * BPM—Business Process Management
 * BPM—Business Process Modeling
 * bps—bits per second
 * BRM—Business Reference Model
 * BRMS—Business Rule Management System
 * BRR—Business Readiness Rating
 * BRS—Broadband Radio Service
 * BSA—Business Software Alliance
 * BSB—Backside Bus
 * BSD—Berkeley Software Distribution
 * BSoD—Blue Screen of Death
 * BSS—Block Started by Symbol
 * BT—BitTorrent
 * BT—Bluetooth
 * B TAM—Basic Telecommunications Access Method
 * BW—Bandwidth
 * BYOD—Bring Your Own Device
 * Byte—By eight (group of 8 bits)

C

 * CA—Computer Accountancy
 * CAD—Computer-Aided Design
 * CAE—Computer-Aided Engineering
 * CAID—Computer-Aided Industrial Design
 * CAI—Computer-Aided Instruction
 * CAM—Computer-Aided Manufacturing
 * CAP—Consistency Availability Partition tolerance (theorem)
 * CAPTCHA—Completely Automated Public Turing Test to tell Computers and Humans Apart
 * CAT—Computer-Aided Translation
 * CAQ—Computer-Aided Quality Assurance
 * CASE—Computer-Aided Software Engineering
 * cc—C Compiler
 * CC—Carbon Copy
 * CD—Compact Disc
 * CDE—Common Desktop Environment
 * CDFS—Compact Disk File System
 * CDMA—Code-Division Multiple Access
 * CDN—Content Delivery Network
 * CDP—Cisco Discovery Protocol
 * CDP—Continuous Data Protection
 * CD-R—CD-Recordable
 * CD-ROM—CD Read-Only Memory
 * CD-RW—CD-Rewritable
 * CDSA—Common Data Security Architecture
 * CERT—Computer Emergency Response Team
 * CES—Consumer Electronics Show
 * CF—Compact Flash
 * CFD—Computational Fluid Dynamics
 * CFG—Context-Free Grammar
 * CFG—Control-Flow Graph
 * CG—Computer Graphics
 * CGA—Color Graphics Array
 * CGI—Common Gateway Interface
 * CGI—Computer-Generated Imagery
 * CGT—Computational Graph Theory
 * CHAP—Challenge-Handshake Authentication Protocol
 * CHS—Cylinder-Head-Sector
 * CIDR—Classless Inter-Domain Routing
 * CIFS—Common Internet Filesystem
 * CIM—Common Information Model
 * CIM—Computationally Independent Model
 * CIO—Chief Information Officer
 * CIR—Committed information rate
 * CISC—Complex Instruction Set Computer
 * CJK—Chinese, Japanese, and Korean
 * CJKV—Chinese, Japanese, Korean, and Vietnamese
 * CLI—Command Line Interface
 * CLR—Common Language Runtime
 * CM—Configuration Management
 * CM—Content Management
 * CMDB—Configuration Management Database
 * CMMI—Capability Maturity Model Integration
 * CMOS—Complementary Metal-Oxide Semiconductor
 * CMO—Current Mode of Operation
 * CMS—Content Management System
 * CN—Canonical Name
 * CN—Common Name
 * CNC—Computer Numerical Control
 * CNG—Cryptographic Next Generation
 * CNG—Cryptography Next Generation
 * CNR—Communications and Networking Riser
 * COBOL—Common Business-Oriented Language
 * COM—Component Object Model or communication
 * CORBA—Common Object Request Broker Architecture
 * CORS—Cross-Origin Resource Sharing
 * COTS—Commercial Off-The-Shelf
 * CPA—Cell Processor Architecture
 * CPAN—Comprehensive Perl Archive Network
 * CP/M—Control Program/Monitor
 * CPRI—Common Public Radio Interface
 * CPS—characters per second
 * CPU—Central Processing Unit
 * CQS—Command–query separation
 * CQRS—Command Query Responsibility Segregation
 * CR—Carriage Return
 * CRAN—Comprehensive R Archive Network
 * CRC—Cyclic Redundancy Check
 * CRLF—Carriage Return Line Feeds
 * CRM—Customer Relationship Management
 * CRS—Computer Reservations System
 * CRT—Cathode-Ray Tube
 * CRUD—Create, Read, Update and Delete
 * CS—Cable Select
 * CS—Computer Science
 * CSE—Computer Science and Engineering
 * CSI—Common System Interface
 * CSM—Compatibility Support Module
 * CSMA/CD—Carrier-sense multiple access with collision detection
 * CSP—Cloud Service Provider
 * CSP—Communicating Sequential Processes
 * CSRF—Cross-Site Request Forgery
 * CSS—Cascading Style Sheets
 * CSS—Content-Scrambling System
 * CSS—Closed Source Software
 * CSS—Cross-Site Scripting
 * CSV—Comma-Separated Values
 * CT—Computerized Tomography
 * CTAN—Comprehensive TeX Archive Network
 * CTCP—Client-To-Client Protocol
 * CTI—Computer Telephony Integration
 * CTFE—Compile-time function execution
 * CTL—Computational Tree Logic
 * CTM—Close To Metal
 * CTS—Clear To Send
 * CTSS—Compatible Time-Sharing System
 * CUA—Common User Access
 * CVE—Common Vulnerabilities and Exposures
 * CVS—Concurrent Versioning System
 * CX—Customer Experience

D

 * DAC—Digital-To-Analog Converter
 * DAC—Discretionary Access Control
 * DAL—Database Abstraction Layer
 * DAO—Data Access Object
 * DAO—Data Access Objects
 * DAO—Disk-At-Once
 * DAP—Directory Access Protocol
 * DARPA—Defense Advanced Research Projects Agency
 * DAS—Direct Attached Storage
 * DAT—Digital Audio Tape
 * DB—Database
 * DSKT—Desktop
 * DBA—Database Administrator
 * DBCS—Double Byte Character Set
 * DBMS—Database Management System
 * DCC—Direct Client-to-Client
 * DCCP—Datagram Congestion Control Protocol
 * DCCA—Debian Common Core Alliance
 * DCL—Data Control Language
 * DCS—Distributed Control System
 * DCMI—Dublin Core Metadata Initiative
 * DCOM—Distributed Component Object Model
 * DD—Double Density
 * DDE—Dynamic Data Exchange
 * DDI—DNS DHCP & IP address management
 * DDL—Data Definition Language
 * DDoS—Distributed Denial of Service
 * DDR—Double Data Rate
 * DEC—Digital Equipment Corporation
 * DES—Data Encryption Standard
 * dev—development
 * DFA—Deterministic Finite Automaton
 * DFD—Data Flow Diagram
 * DFS—Depth-First Search
 * DFS—Distributed File System
 * DGD—Dworkin's Game Driver
 * DHCP—Dynamic Host Configuration Protocol
 * DHTML—Dynamic Hypertext Markup Language
 * DIF—Data Integrity Field
 * DIMM—Dual Inline Memory Module
 * DIN—Deutsches Institut für Normung
 * DIP—Dual In-line Package
 * DISM—Deployment Image and Service Management Tool
 * DIVX—Digital Video Express
 * DKIM—Domain Keys Identified Mail
 * DL—Download
 * DLL—Dynamic Link Library
 * DLNA—Digital Living Network Alliance
 * DMA—Direct Memory Access
 * DMCA—Digital Millennium Copyright Act
 * DMI—Direct Media Interface
 * DML—Data Manipulation Language
 * DML—Definitive Media Library
 * DMR—Dennis M. Ritchie
 * DMZ—Demilitarized Zone
 * DN—Distinguished Name
 * DND—Drag-and-Drop
 * DNS—Domain Name System
 * DOA—Dead on Arrival
 * DOCSIS—Data Over Cable Service Interface Specification
 * DOM—Document Object Model
 * DORA—Discover, Offer, Request, Acknowledge
 * DoS—Denial of Service
 * DOS—Disk Operating System
 * DP—Dot Pitch
 * DPC—Deferred Procedure Call
 * DPI—Deep Packet Inspection
 * DPI—Dots Per Inch
 * DPMI—DOS Protected Mode Interface
 * DPMS—Display Power Management Signaling
 * DR—Disaster Recovery
 * DRAM—Dynamic Random-Access Memory
 * DR-DOS—Digital Research – Disk Operating System
 * DRI—Direct Rendering Infrastructure
 * DRM—Digital Rights Management
 * DRM—Direct Rendering Manager
 * DSA—Digital Signature Algorithm
 * DSDL—Document Schema Definition Languages
 * DSDM—Dynamic Systems Development Method
 * DSL—Digital Subscriber Line
 * DSL—Domain-Specific Language
 * DSLAM—Digital Subscriber Line Access Multiplexer
 * DSN—Database Source Name
 * DSN—Data Set Name
 * DSP—Digital Signal Processor
 * DSSSL—Document Style Semantics and Specification Language
 * DTD—Document Type Definition
 * DTE—Data Terminal Equipment or data transfer rate
 * DTO—Data Transfer Object
 * DTP—Desktop Publishing
 * DTR—Data Terminal Ready or Data transfer rate
 * DVD—Digital Versatile Disc or Digital Video Disc
 * DVD-R—DVD-Recordable
 * DVD-ROM—DVD-Read-Only Memory
 * DVD-RW—DVD-Rewritable
 * DVI—Digital Visual Interface
 * DVR—Digital Video Recorder
 * DW—Data Warehouse

E

 * EAI—Enterprise Application Integration
 * EAP—Extensible Authentication Protocol
 * EAS—Exchange ActiveSync
 * EBCDIC—Extended Binary Coded Decimal Interchange Code
 * EBML—Extensible Binary Meta Language
 * ECC—Elliptic Curve Cryptography
 * ECMA—European Computer Manufacturers Association
 * ECN—Explicit Congestion Notification
 * ECOS—Embedded Configurable Operating System
 * ECRS—Expense and Cost Recovery System
 * ECS—Entity-Component-System
 * EDA—Electronic Design Automation
 * EDGE—Enhanced Data rates for GSM Evolution
 * EDI—Electronic Data Interchange
 * EDO—Extended Data Out
 * EDSAC—Electronic Delay Storage Automatic Calculator
 * EDVAC—Electronic Discrete Variable Automatic Computer
 * EEPROM—Electronically Erasable Programmable Read-Only Memory
 * EFF—Electronic Frontier Foundation
 * EFI—Extensible Firmware Interface
 * EFM—Eight-to-Fourteen Modulation
 * EFM—Ethernet in the First Mile
 * EFS—Encrypting File System
 * EGA—Enhanced Graphics Array
 * E-mail—Electronic mail
 * EGP—Exterior Gateway Protocol
 * eID—electronic ID card
 * EIDE—Enhanced IDE
 * EIGRP—Enhanced Interior Gateway Routing Protocol
 * EISA—Extended Industry Standard Architecture
 * ELF—Extremely Low Frequency
 * ELF—Executable and Linkable Format
 * ELM—ELectronic Mail
 * EMACS—Editor MACroS
 * EMS—Expanded Memory Specification
 * ENIAC—Electronic Numerical Integrator And Computer
 * EOD—End of Day
 * EOF—End of File
 * EOL—End of Life
 * EOL—End of Line
 * EOM—End of Message
 * EOS—End of Support
 * EPIC—Explicitly Parallel Instruction Computing
 * EPROM—Erasable Programmable Read-Only Memory
 * ERD—Entity–Relationship Diagram
 * ERM—Entity–Relationship Model
 * ERP—Enterprise Resource Planning
 * eSATA—external SATA
 * ESB—Enterprise service bus
 * ESCON—Enterprise Systems Connection
 * ESD—Electrostatic Discharge
 * ESI—Electronically Stored Information
 * ESR—Eric Steven Raymond
 * ETL—Extract, Transform, Load
 * ETW—Event Tracing for Windows
 * EUC—Extended Unix Code
 * EULA—End User License Agreement
 * EWM—Enterprise Work Management
 * EWMH—Extended Window Manager Hints
 * EXT—EXTended file system
 * ETA—Estimated Time of Arrival

F

 * FAP—FORTRAN Assembly Program
 * FASM—Flat ASseMbler
 * FAT—File Allocation Table
 * FAQ—Frequently Asked Questions
 * FBDIMM—Fully Buffered Dual Inline Memory Module
 * FC-AL—Fibre Channel Arbitrated Loop
 * FCB—File Control Block
 * FCS—Frame Check Sequence
 * FDC—Floppy-Disk Controller
 * FDS—Fedora Directory Server
 * FDD—Frequency-Division Duplexing
 * FDD—Floppy Disk Drive
 * FDDI—Fiber Distributed Data Interface
 * FDM—Frequency-Division Multiplexing
 * FDMA—Frequency-Division Multiple Access
 * FE—Frontend
 * FEC—Forward Error Correction
 * FEMB—Front-End Motherboard
 * FET—Field Effect Transistor
 * FHS—Filesystem Hierarchy Standard
 * FICON—FIber CONnectivity
 * FIFO—First In First Out
 * FIPS—Federal Information Processing Standards
 * FL—Function Level
 * FLAC—Free Lossless Audio Codec
 * FLOPS—FLoating-Point Operations Per Second
 * FLOSS—Free/Libre/Open-Source Software
 * FMC—Fixed Mobile Convergence "Mobile UC or Unified Communications over Wireless"
 * FMO—Future Mode of Operation
 * FOLDOC—Free On-line Dictionary of Computing
 * FORTRAN—Formula Translation
 * FOSDEM—Free and Open-source Software Developers' European Meeting
 * FOSI—Formatted Output Specification Instance
 * FOSS—Free and Open-Source Software
 * FP—Function Programming
 * FP—Functional Programming
 * FPGA—Field Programmable Gate Array
 * FPS—Floating Point Systems
 * FPU—Floating-Point Unit
 * FRU—Field-Replaceable Unit
 * FS—File System
 * FSB—Front-Side Bus
 * fsck—File System Check
 * FSF—Free Software Foundation
 * FSM—Finite State Machine
 * FTTA—Fiber To The Antenna
 * FTTC—Fiber To The Curb
 * FTTH—Fiber To The Home
 * FTTP—Fiber To The Premises
 * FTP—File Transfer Protocol
 * FQDN—Fully Qualified Domain Name
 * FUD—Fear Uncertainty Doubt
 * FWS—Folding White Space
 * FXP—File eXchange Protocol
 * FYI—For Your Information
 * FVEK—Full Volume Encryption Key

G

 * G11N—Globalization
 * Gas—GNU Assembler
 * Gb—Gigabit
 * GB—Gigabyte
 * Gbps—Gigabits per second
 * GCC—GNU Compiler Collection
 * GCJ—GNU Compiler for Java
 * GCP—Google Cloud Platform
 * GCR—Group Coded Recording
 * GDB—GNU Debugger
 * GDI—Graphics Device Interface
 * GFDL—GNU Free Documentation License
 * GIF—Graphics Interchange Format
 * GIGO—Garbage In, Garbage Out
 * GIMP—GNU Image Manipulation Program
 * GIMPS—Great Internet Mersenne Prime Search
 * GIS—Geographic Information System
 * GLUT—OpenGL Utility Toolkit
 * GML—Geography Markup Language
 * GNOME—GNU Network Object Model Environment
 * GNU—GNU's Not Unix
 * GOMS—Goals, Operators, Methods, and Selection rules
 * GPASM—GNU PIC ASseMbler
 * GPFS—General Parallel File System
 * GPG—GNU Privacy Guard
 * GPGPU—General-Purpose Computing on Graphics Processing Units
 * GPIB—General-Purpose Instrumentation Bus
 * GPL—General Public License
 * GPL—General-Purpose Language
 * GPRS—General Packet Radio Service
 * GPT—GUID Partition Table
 * GPU—Graphics Processing Unit
 * GRUB—Grand Unified Boot-Loader
 * GERAN—GSM EDGE Radio Access Network
 * GSM—Global System for Mobile Communications
 * GTK/GTK+—GIMP Toolkit
 * GUI—Graphical User Interface
 * GUID—Globally Unique IDentifier
 * GWT—Google Web Toolkit
 * GYR—IT Networking

H

 * HA—High availability
 * HAL—Hardware Abstraction Layer
 * HARD—HTML Application Rapid Development
 * HASP—Houston Automatic Spooling Priority
 * HBA—Host Bus Adapter
 * HCI—Human—Computer Interaction
 * HD—High Density
 * HDD—Hard Disk Drive
 * HCL—Hardware Compatibility List
 * HD DVD—High Definition DVD
 * HDL—Hardware Description Language
 * HDMI—High-Definition Multimedia Interface
 * HECI—Host Embedded Controller Interface
 * HF—High Frequency
 * HFS—Hierarchical File System
 * HHD—Hybrid Hard Drive
 * HID—Human Interface Device
 * HIG—Human Interface Guidelines
 * HIRD—Hurd of Interfaces Representing Depth
 * HLASM—High Level ASseMbler
 * HLS—HTTP Live Streaming
 * HMA—High Memory Area
 * HP—Hewlett-Packard
 * HPC—High-Performance Computing
 * HPFS—High Performance File System
 * HSDPA—High-Speed Downlink Packet Access
 * HTC—High-Throughput Computing
 * HSM—Hierarchical Storage Management
 * HT—Hyper Threading
 * HTM—Hierarchical Temporal Memory
 * HTML—Hypertext Markup Language
 * HTTP—Hypertext Transfer Protocol
 * HTTPd—Hypertext Transport Protocol Daemon
 * HTTPS—HTTP Secure
 * HTX—HyperTransport eXpansion
 * HURD—Hird of Unix-Replacing Daemons
 * HVD—Holographic Versatile Disc
 * Hz—Hertz

I

 * I²C—Inter-Integrated Circuit
 * I²S—Integrated Interchip Sound
 * I18N—Internationalization
 * IANA—Internet Assigned Numbers Authority
 * IaaS—Infrastructure as a Service
 * IaC—Infrastructure as Code
 * iBCS—Intel Binary Compatibility Standard
 * IBM—International Business Machines
 * IC—Integrated Circuit
 * ICANN—Internet Corporation for Assigned Names and Numbers
 * ICE—In-Circuit Emulator
 * ICE—Intrusion Countermeasure Electronics
 * ICH—I/O Controller Hub
 * ICMP—Internet Control Message Protocol
 * ICP—Internet Cache Protocol
 * ICS—Internet Connection Sharing
 * ICT—Information and Communication Technology
 * IDE—Integrated Development Environment
 * IDE—Integrated Drive Electronics
 * IDF—Intermediate Distribution Frame
 * IDF—Intermediate Data Format
 * IDL—Interactive Data Language
 * IDL—Interface Definition Language
 * IdP—Identity Provider (cybersecurity)
 * IDS—Intrusion Detection System
 * IE—Internet Explorer
 * IEC—International Electrotechnical Commission
 * IEEE—Institute of Electrical and Electronics Engineers
 * IETF—Internet Engineering Task Force
 * IFL—Integrated Facility for Linux
 * IGMP—Internet Group Management Protocol
 * IGRP—Interior Gateway Routing Protocol
 * IHV—Independent Hardware Vendor
 * IIOP—Internet Inter-Orb Protocol
 * IIS—Internet Information Services
 * IKE—Internet Key Exchange
 * IL—Intermediate Language
 * IM—Instant Message or Instant Messaging
 * IMAP—Internet Message Access Protocol
 * IME—Input Method Editor
 * INFOSEC—Information Systems Security
 * I/O—Input/output
 * IoT—Internet of Things
 * IP—Intellectual Property
 * IP—Internet Protocol
 * IPAM—IP Address Management
 * IPC—Inter-Process Communication
 * IPL—Initial Program Load
 * IPMI—Intelligent Platform Management Interface
 * IPO—Inter Procedural Optimization
 * IPP—Internet Printing Protocol
 * IPS—In-Plane Switching
 * IPS—Instructions Per Second
 * IPS—Intrusion Prevention System
 * IPsec—Internet Protocol security
 * IPTV—Internet Protocol Television
 * IPv4—Internet Protocol version 4
 * IPv6—Internet Protocol version 6
 * IPX—Internetwork Packet Exchange
 * IR—Intermediate Representation
 * IRC—Internet Relay Chat
 * IrDA—Infrared Data Association
 * IRI—Internationalized Resource Identifier
 * IRP—I/O Request Packet
 * IRQ—Interrupt Request
 * IS—Information Systems
 * IS-IS—Intermediate System to Intermediate System
 * ISA—Industry Standard Architecture
 * ISA—Instruction Set Architecture
 * ISAM—Indexed Sequential Access Method
 * ISATAP—Intra-Site Automatic Tunnel Addressing Protocol
 * ISC—Internet Storm Center
 * iSCSI—Internet Small Computer System Interface
 * ISDN—Integrated Services Digital Network
 * ISO—International Organization for Standardization
 * iSNS—Internet Storage Name Service
 * ISP—Internet Service Provider
 * ISPF—Interactive System Productivity Facility
 * ISR—Interrupt Service Routine
 * ISV—Independent Software Vendor
 * IT—Information Technology
 * ITIL—Information Technology Infrastructure Library
 * ITL—Interval Temporal Logic
 * ITU—International Telecommunication Union
 * IVR(S)—Interactive Voice Response (System)

J

 * J2EE—Java 2 Enterprise Edition
 * J2ME—Java 2 Micro Edition
 * J2SE—Java 2 Standard Edition
 * JAXB—Java Architecture for XML Binding
 * JAX-RPC—Jakarta XML (formerly Java XML) for Remote Procedure Calls
 * JAXP—Java API for XML Processing
 * JBOD—Just a Bunch of Disks
 * JCE— Java Cryptography Extension
 * JCL—Job Control Language
 * JCP—Java Community Process
 * JDBC—Java Database Connectivity
 * JDK—Java Development Kit
 * JEE—Java Enterprise Edition
 * JES—Job Entry Subsystem
 * JDS—Java Desktop System
 * JFC—Java Foundation Classes
 * JFET—Junction Field-Effect Transistor
 * JFS—IBM Journaling File System
 * JINI—Jini Is Not Initials
 * JIT—Just-In-Time
 * JME—Java Micro Edition
 * JMX—Java Management Extensions
 * JMS—Java Message Service
 * JNDI—Java Naming and Directory Interface
 * JNI—Java Native Interface
 * JNZ—Jump non-zero
 * JPEG—Joint Photographic Experts Group
 * JRE—Java Runtime Environment
 * JS—JavaScript
 * JSE—Java Standard Edition
 * JSON—JavaScript Object Notation
 * JSP—Jackson Structured Programming
 * JSP—JavaServer Pages
 * JTAG—Joint Test Action Group
 * JVM—Java Virtual Machine

K

 * K&R—Kernighan and Ritchie
 * K8s—Kubernetes
 * KB—Keyboard
 * Kb—Kilobit
 * KB—Kilobyte
 * KB—Knowledge Base
 * Kbps—Kilobits per second
 * KiB—Kibibyte
 * KDE—K Desktop Environment
 * kHz—Kilohertz
 * KM—Knowledge Machine
 * KRL—Knowledge Representation Language
 * KVM—Keyboard, Video, Mouse

L

 * L10N—Localization
 * L2TP—Layer two Tunneling Protocol
 * LACP—Link Aggregation Control Protocol
 * LAMP—Linux Apache MySQL Perl
 * LAMP—Linux Apache MySQL PHP
 * LAMP—Linux Apache MySQL Python
 * LAN—Local Area Network
 * LBA—Logical Block Addressing
 * LB—Load Balancer
 * LCD—Liquid Crystal Display
 * LCR—Least Cost Routing
 * LCOS—Liquid Crystal On Silicon
 * LDAP—Lightweight Directory Access Protocol
 * LE—Logical Extents
 * LED—Light-Emitting Diode
 * LF—Line Feed
 * LF—Low Frequency
 * LFS—Linux From Scratch
 * LGA—Land Grid Array
 * LGPL—Lesser General Public License
 * LIB—LIBrary
 * LIF—Low Insertion Force
 * LIFO—Last In First Out
 * LILO—Linux Loader
 * LIP—Loop Initialization Primitive
 * LISP—LISt Processing
 * LKML—Linux Kernel Mailing List
 * LM—Lan Manager
 * LOC—Lines of Code
 * LPC—Lars Pensjö C
 * LPI—Lines Per Inch
 * LPI—Linux Professional Institute
 * LPT— Line Print Terminal
 * LRU—Least Recently Used
 * LSB—Least Significant Bit
 * LSB—Linux Standard Base
 * LSI—Large-Scale Integration
 * LTE—Long Term Evolution
 * LTL—Linear Temporal Logic
 * LTR—Left-to-Right
 * LUG—Linux User Group
 * LUN—Logical Unit Number
 * LV—Logical Volume
 * LVD—Low Voltage Differential
 * LVM—Logical Volume Management
 * LZW—Lempel-Ziv-Welch

M

 * MAC—Mandatory Access Control
 * MAC—Media Access Control
 * MAC—Message authentication code
 * MANET—Mobile Ad-Hoc Network
 * MAN—Metropolitan Area Network
 * MAPI—Messaging Application Programming Interface
 * MBCS—Multi Byte Character Set
 * MBD—Model-Based Design
 * MBR—Master Boot Record
 * Mb—Megabit
 * MB—Megabyte
 * Mbps—Megabits per second
 * MCAD—Microsoft Certified Application Developer
 * MCAS—Microsoft Certified Application Specialist
 * MCA—Micro Channel Architecture
 * MCA—Microsoft Certified Architect
 * MCDBA—Microsoft Certified DataBase Administrator
 * MCDST—Microsoft Certified Desktop Support Technician
 * MCITP—Microsoft Certified Information Technology Professional
 * MCM—Microsoft Certified Master
 * MCPC—Multiple Channels Per Carrier
 * MCPD—Microsoft Certified Professional Developer
 * MCP—Microsoft Certified Professional
 * MCSA—Microsoft Certified Systems Administrator
 * MCSD—Microsoft Certified Solution Developer
 * MCSE—Microsoft Certified Systems Engineer
 * MCTS—Microsoft Certified Technology Specialist
 * MCT—Microsoft Certified Trainer
 * MDA—Monochrome Display Adapter
 * MDA—Mail Delivery Agent
 * MDA—Model-Driven Architecture
 * MDD/MDSD—Model-Driven (Software) Development
 * MDF—Main Distribution Frame
 * MDI—Multiple-Document Interface
 * MDM—Master Data Management
 * ME—Microsoft Edge
 * ME—[Windows] Millennium Edition
 * MFA—Multi-factor authentication
 * MFC—Microsoft Foundation Classes
 * MFT—Master File Table
 * MFM—Modified Frequency Modulation
 * MF—Medium Frequency
 * MGCP—Media Gateway Control Protocol
 * MHz—Megahertz
 * MIB—Management Information Base
 * MICR—Magnetic Ink Character Recognition or Magnetic Ink Character Reader
 * MIDI—Musical Instrument Digital Interface
 * MIMD—Multiple Instruction, Multiple Data
 * MIME—Multipurpose Internet Mail Extensions
 * MIMO—Multiple-Input Multiple-Output
 * MINIX—MIni-uNIX
 * MIPS—Microprocessor without Interlocked Pipeline Stages
 * MIPS—Million Instructions Per Second
 * MISD—Multiple Instruction, Single Data
 * MIS—Management Information Systems
 * MIT—Massachusetts Institute of Technology
 * ML—Machine Learning
 * MMC—Microsoft Management Console
 * MMDS—Mortality Medical Data System
 * MMDS—Multichannel Multipoint Distribution Service
 * MMF—Multi-Mode (optical) Fiber
 * MMIO—Memory-Mapped I/O
 * MMI—Man Machine Interface.
 * MMORPG—Massively Multiplayer Online Role-Playing Game
 * MMS—Multimedia Message Service
 * MMU—Memory Management Unit
 * MMX—Multi-Media Extensions
 * MNG—Multiple-image Network Graphics
 * MoBo—Motherboard
 * MOM—Message-Oriented Middleware
 * MOO—MUD Object Oriented
 * MOP—Meta-Object Protocol
 * MOSFET—Metal-Oxide Semiconductor Field Effect Transistor
 * MOS—Microsoft Office Specialist
 * MOTD—Message Of The Day
 * MOUS—Microsoft Office User Specialist
 * MOV—Apple QuickTime Multimedia File
 * MPAA—Motion Picture Association of America
 * MPEG—Motion Pictures Experts Group
 * MPLS—Multiprotocol Label Switching
 * MPL—Mozilla Public License
 * MPU—Microprocessor Unit
 * MS-DOS—Microsoft DOS
 * MSA—Mail Submission Agent
 * MSB—Most Significant Bit
 * MSDN—Microsoft Developer Network
 * MSI—Medium-Scale Integration
 * MSI—Message Signaled Interrupt
 * MSI—Microsoft Installer
 * MSN—Microsoft Network
 * MS—Microsoft
 * MS—Memory Stick
 * MTA—Mail Transfer Agent
 * MTA—Microsoft Technology Associate
 * MTBF—Mean Time Between Failures
 * MTU—Maximum Transmission Unit
 * MT—Machine Translation
 * MUA—Mail User Agent
 * MUD—Multi-User Dungeon
 * MU—Memory Unit
 * MVC—Model-View-Controller
 * MVP—Most Valuable Professional
 * MVS—Multiple Virtual Storage
 * MWC—Mobile World Congress
 * MXF—Material Exchange Format
 * MX—Mail exchange

N

 * NAC—Network Access Control
 * NACK—Negative ACKnowledgement
 * NAK—Negative AcKnowledge Character
 * NaN—Not a Number
 * NAP—Network Access Protection
 * NAS—Network-Attached Storage
 * NASM—Netwide ASseMbler
 * NAT—Network Address Translation
 * NCP—NetWare Core Protocol
 * NCQ—Native Command Queuing
 * NCSA—National Center for Supercomputing Applications
 * NDIS—Network Driver Interface Specification
 * NDPS—Novell Distributed Print Services
 * NDS—Novell Directory Services
 * NEP—Network Equipment Provider
 * NetBIOS—Network Basic Input/Output System
 * NetBT—NetBIOS over TCP/IP
 * NEXT—Near-End CrossTalk
 * NFA—Nondeterministic Finite Automaton
 * NFC—Near-field communication
 * NFS—Network File System
 * NFT—Non-Fungible Token
 * NGL—aNGeL
 * NGSCB—Next-Generation Secure Computing Base
 * NI—National Instruments
 * NIC—Network Interface Controller or Network Interface Card
 * NIM—No Internal Message
 * NIO—Non-blocking I/O
 * NIST—National Institute of Standards and Technology
 * NLE—Non-Linear Editing system
 * NLP—Natural Language Processing
 * NLS—Native Language Support
 * NMI—Non-Maskable Interrupt
 * NNTP—Network News Transfer Protocol
 * NOC—Network Operations Center
 * NOP—No OPeration
 * NOS—Network Operating System
 * NP—Nondeterministic Polynomial time
 * NPL—Netscape Public License
 * NPTL—Native POSIX Thread Library
 * NPU—Network Processing Unit
 * NS—Netscape
 * NSA—Network Security Appliance
 * NSI—Network Service Interface
 * NSIS—Nullsoft Scriptable Install System
 * NSPR—Netscape Portable Runtime
 * NSS—Novell Storage Service
 * NSS—Network Security Services
 * NSS—Name Service Switch
 * NT—New Technology
 * NTFS—NT Filesystem
 * NTLM—NT Lan Manager
 * NTP—Network Time Protocol
 * NUMA—Non-Uniform Memory Access
 * NURBS—Non-Uniform Rational B-Spline
 * NVR—Network Video Recorder
 * NVRAM—Non-Volatile Random-Access Memory

O

 * OASIS—Organization for the Advancement of Structured Information Standards
 * OAT—Operational Acceptance Testing
 * OBSAI—Open Base Station Architecture Initiative
 * OCR—Optical Character Recognition
 * ODBC—Open Database Connectivity
 * OEM—Original Equipment Manufacturer
 * OES—Open Enterprise Server
 * OFDM—Orthogonal Frequency-Division Multiplexing
 * OFTC—Open and Free Technology Community
 * OID—Object Identifier
 * OLAP—Online Analytical Processing
 * OLE—Object Linking and Embedding
 * OLED—Organic Light Emitting Diode
 * OLPC—One Laptop per Child
 * OLTP—Online Transaction Processing
 * OMF—Object Module Format
 * OMG—Object Management Group
 * OMR—Optical Mark Reader
 * OO—Object-Oriented
 * OO—OpenOffice
 * OOE—Out-of-Order Execution
 * OOM—Out Of Memory
 * OOo—OpenOffice.org
 * OoOE—Out-of-Order Execution
 * OOP—Object-Oriented Programming
 * OOTB—Out of the box
 * OPML—Outline Processor Markup Language
 * ORB—Object Request Broker
 * ORM—Object–Relational Mapping
 * OS—Open Source
 * OS—Operating System
 * OSCON—O'Reilly Open Source CONvention
 * OSDN—Open Source Development Network
 * OSI—Open Source Initiative
 * OSI—Open Systems Interconnection
 * OSPF—Open Shortest Path First
 * OSS—Open Sound System
 * OSS—Open-Source Software
 * OSS—Operations Support System
 * OSTG—Open Source Technology Group
 * OTP—One-time password
 * OUI—Organizationally Unique Identifier

P

 * P2P—Peer-To-Peer
 * PaaS—Platform as a Service
 * PAM—Privileged Access Management
 * PAN—Personal Area Network
 * PAP—Password Authentication Protocol
 * PARC—Palo Alto Research Center
 * PATA—Parallel ATA
 * PBS—Portable Batch System
 * PC—Personal Computer
 * PCB—Printed Circuit Board
 * PCB—Process Control Block
 * PC DOS—Personal Computer Disc Operating System
 * PCI—Peripheral Component Interconnect
 * PCIe—PCI Express
 * PCI-X—PCI Extended
 * PCL—Printer Command Language
 * PCMCIA—Personal Computer Memory Card International Association
 * PCM—Pulse-Code Modulation
 * PCRE—Perl Compatible Regular Expressions
 * PD—Public Domain
 * PDA—Personal Digital Assistant
 * PDF—Portable Document Format
 * PDH—Plesiochronous Digital Hierarchy
 * PDP—Programmed Data Processor
 * PE—Physical Extents
 * PE—Portable Executable
 * PERL—Practical Extraction and Reporting Language
 * PFA—Please Find Attachment
 * PG—Peripheral Gateway
 * PGA—Pin Grid Array
 * PGA—Programmable Gate Array
 * PGO—Profile-Guided Optimization
 * PGP—Pretty Good Privacy
 * PHP—Hypertext Preprocessor
 * PIC—Peripheral Interface Controller
 * PIC—Programmable Interrupt Controller
 * PID—Proportional-Integral-Derivative
 * PID—Process ID
 * PIM—Personal Information Manager
 * PINE—Program for Internet News and Email
 * PIM—Platform Independent Model
 * PING—Packet Internet Gopher
 * PIO—Programmed Input/Output
 * Pixel—Picture element
 * PKCS—Public Key Cryptography Standards
 * PKI—Public Key Infrastructure
 * PLC—Power Line Communication
 * PLC—Programmable Logic Controller
 * PLD—Programmable Logic Device
 * PL/I—Programming Language One
 * PL/M—Programming Language for Microcomputers
 * PL/P—Programming Language for Prime
 * PLT—Power Line Telecommunications
 * PMM—POST Memory Manager
 * PNG—Portable Network Graphics
 * PnP—Plug-and-Play
 * PNRP—Peer Name Resolution Protocol
 * PoE—Power over Ethernet
 * PoS—Point of Sale
 * POCO—Plain Old Class Object
 * POID—Persistent Object Identifier
 * POJO—Plain Old Java Object
 * POP—Point of Presence
 * POP3—Post Office Protocol v3
 * POSIX—Portable Operating System Interface, formerly IEEE-IX
 * POST—Power-On Self Test
 * PPC—PowerPC
 * PPI—Pixels Per Inch
 * PPM—Pages Per Minute
 * PPP—Point-to-Point Protocol
 * PPPoA—PPP over ATM
 * PPPoE—PPP over Ethernet
 * PPTP—Point-to-Point Tunneling Protocol
 * PR—Pull Request
 * PROM—Programmable Read-Only Memory
 * PS—PostScript
 * PS/2—Personal System/2
 * PSA—Professional Services Automation
 * PSM—Platform Specific Model
 * PSTN—Public Switched Telephone Network
 * PSU—Power Supply Unit
 * PSVI—Post-Schema-Validation Infoset
 * PTS-DOS—PhysTechSoft – Disk Operating System
 * PV—Physical Volume
 * PVG—Physical Volume Group
 * PVR—Personal Video Recorder
 * PXE—Preboot Execution Environment
 * PXI—PCI eXtensions for Instrumentation
 * PRC—Procedure Remote Call

Q

 * QDR—Quad Data Rate
 * QA—Quality Assurance
 * QFP—Quad Flat Package
 * QoS—Quality of Service
 * QOTD—Quote of the Day
 * Qt—Quasar Toolkit
 * QTAM—Queued Teleprocessing Access Method
 * QSOP—Quarter Small Outline Package
 * qWave—Quality Windows Audio/Video Experience

R

 * RACF—Resource Access Control Facility
 * RAD—Rapid Application Development
 * RADIUS—Remote Authentication Dial In User Service
 * RAID—Redundant Array of Independent Disks
 * RAII—Resource Acquisition Is Initialization
 * RAIT—Redundant Array of Inexpensive Tapes
 * RAM—Random-Access Memory
 * RARP—Reverse Address Resolution Protocol
 * RAS—Reliability, Availability and Serviceability
 * RAS—Remote access service
 * RC—Region Code
 * RC—Release Candidate
 * RC—Run Commands
 * RCA—Root Cause Analysis
 * RCS—Revision Control System
 * RD—Remote Desktop
 * rd—remove directory
 * RDBMS—Relational Database Management System
 * RDC—Remote Desktop Connection
 * RDF—Resource Description Framework
 * RDM—Relational Data Model
 * RDOS—Real-time Disk Operating System
 * RDP—Remote Desktop Protocol
 * RDS—Remote Data Services
 * REFAL—Recursive Functions Algorithmic Language
 * REP—RAID Error Propagation
 * REST—Representational State Transfer
 * RESV—Reservation Message
 * regex—Regular Expression
 * regexp—Regular Expression
 * RF—Radio Frequency
 * RFC—Request For Comments
 * RFI—Radio Frequency Interference
 * RFID—Radio Frequency Identification
 * RGB—Red, Green, Blue
 * RGBA—Red, Green, Blue, Alpha
 * RHL—Red Hat Linux
 * RHEL—Red Hat Enterprise Linux
 * RIA—Rich Internet Application
 * RIAA—Recording Industry Association of America
 * RIP—Raster Image Processor
 * RIP—Routing Information Protocol
 * RIR—Regional Internet registry
 * RISC—Reduced Instruction Set Computer
 * RISC OS—Reduced Instruction Set Computer Operating System
 * RJE—Remote Job Entry
 * RLE—Run-Length Encoding
 * RLL—Run-Length Limited
 * rmdir—remove directory
 * RMI—Remote Method Invocation
 * RMS—Richard Matthew Stallman
 * ROM—Read-Only Memory
 * ROMB—Read-Out Motherboard
 * ROM-DOS—Read-Only Memory – Disk Operating System
 * RPA—Robotic Process Automation
 * RPC—Remote Procedure Call
 * RPG—Report Program Generator
 * RPM—RPM Package Manager
 * RRAS—Routing and Remote Access Service
 * RSA—Rivest Shamir Adleman
 * RSI—Repetitive Strain Injury
 * RSS—Radio Service Software
 * RSS—Rich Site Summary, RDF Site Summary, or Really Simple Syndication
 * RSVP—Resource Reservation Protocol
 * RTAI—Real-Time Application Interface
 * RTC—Real-Time Clock
 * RTE—Real-Time Enterprise
 * RTEMS—Real-Time Executive for Multiprocessor Systems
 * RTF—Rich Text Format
 * RTL—Right-to-Left
 * RTMP—Real Time Messaging Protocol
 * RTOS—Real-Time Operating System
 * RTP—Real-time Transport Protocol
 * RTS—Ready To Send
 * RTSP—Real Time Streaming Protocol
 * RTTI—Run-time Type Information
 * RTU—Remote Terminal Unit
 * RWD—Responsive Web Design

S

 * SaaS—Software as a Service
 * SASS—Syntactically Awesome Style Sheets
 * SAM—Security Account Manager
 * SAN—Storage Area Network
 * SAS—Serial attached SCSI
 * SATA—Serial ATA
 * SAX—Simple API for XML
 * SBOD—Spinning Beachball of Death
 * SBP-2—Serial Bus Protocol 2
 * sbin—superuser binary
 * sbs—Small Business Server
 * SBU—Standard Build Unit
 * SCADA—Supervisory Control And Data Acquisition
 * SCID—Source Code in Database
 * SCM—Software Configuration Management
 * SCM—Source Code Management
 * SCP—Secure Copy
 * SCPC—Single Channel Per Carrier
 * SCPI—Standard Commands for Programmable Instrumentation
 * SCSA—Secure Content Storage Association
 * SCSI—Small Computer System Interface
 * SCTP—Stream Control Transmission Protocol
 * SD—Secure Digital
 * SDDL—Security Descriptor Definition Language
 * SDH—Synchronous Digital Hierarchy
 * SDI—Single-Document Interface
 * SEC—Single Edge Contact
 * SDIO—Secure Digital Input Output
 * SDK—Software Development Kit
 * SDL—Simple DirectMedia Layer
 * SDN—Service Delivery Network
 * SDP—Session Description Protocol
 * SDR—Software-Defined Radio
 * SDRAM—Synchronous Dynamic Random-Access Memory
 * SDSL—Symmetric DSL
 * SE—Single Ended
 * SEI—Software Engineering Institute
 * SEO—Search Engine Optimization
 * SFTP—Secure FTP
 * SFTP—Simple File Transfer Protocol
 * SFTP—SSH File Transfer Protocol
 * SGI—Silicon Graphics, Incorporated
 * SGML—Standard Generalized Markup Language
 * SGR—Select Graphic Rendition
 * SHA—Secure Hash Algorithm
 * SHDSL—Single-pair High-speed Digital Subscriber Line
 * SIEM—Security information and event management
 * SIGCAT—Special Interest Group on CD-ROM Applications and Technology
 * SIGGRAPH—Special Interest Group on Graphics
 * SIMD—Single Instruction, Multiple Data
 * SIM—Subscriber Identification Module
 * SIMM—Single Inline Memory Module
 * SIP—Session Initiation Protocol
 * SIP—Supplementary Ideographic Plane
 * SISD—Single Instruction, Single Data
 * SISO—Single-Input and Single-Output
 * SLA—Service Level Agreement
 * SLED—SUSE Linux Enterprise Desktop
 * SLES—SUSE Linux Enterprise Server
 * SLI—Scalable Link Interface
 * SLIP—Serial Line Internet Protocol
 * SLM—Service Level Management
 * SLOC—Source Lines of Code
 * SME—Subject Matter Expert
 * SMF—Single-Mode (optical) Fiber
 * SPM—Software project management
 * SPMD—Single Program, Multiple Data
 * SPOF—Single point of failure
 * SMA—SubMiniature version A
 * SMB—Server Message Block
 * SMBIOS—System Management BIOS
 * SMIL—Synchronized Multimedia Integration Language
 * S/MIME—Secure/Multipurpose Internet Mail Extensions
 * SMP—Supplementary Multilingual Plane
 * SMP—Symmetric Multi-Processing
 * SMPS—Switch Mode Power Supply
 * SMS—Short Message Service
 * SMS—System Management Server
 * SMT—Simultaneous Multithreading
 * SMTP—Simple Mail Transfer Protocol
 * SNA—Systems Network Architecture
 * SNMP—Simple Network Management Protocol
 * SNTP—Simple Network Time Protocol
 * SOA—Service-Oriented Architecture
 * SOAP—Simple Object Access Protocol
 * SOAP—Symbolic Optimal Assembly Program
 * SOPA—Stop Online Piracy Act
 * SoC—System-on-a-Chip
 * SO-DIMM—Small Outline DIMM
 * SOE—Standard Operating Environment
 * SOHO—Small Office/Home Office
 * SOI—Silicon On Insulator
 * SOLID—Single-responsibility, Open-closed, Liskov substitution, Interface segregation, Dependency Inversion
 * SP—Service Pack
 * SPA—Single Page Application
 * SPF—Sender Policy Framework
 * SPI—Serial Peripheral Interface
 * SPI—Stateful Packet Inspection
 * SPARC—Scalable Processor Architecture
 * SQL—Structured Query Language
 * SRAM—Static Random-Access Memory
 * SSA—Static Single Assignment
 * SSD—Software Specification Document
 * SSD—Solid-State Drive
 * SSDP—Simple Service Discovery Protocol
 * SSE—Streaming SIMD Extensions
 * SSH—Secure Shell
 * SSI—Server Side Includes
 * SSI—Single-System Image
 * SSI—Small-Scale Integration
 * SSID—Service Set Identifier
 * SSL—Secure Socket Layer
 * SSO—Single Sign On
 * SSP—Supplementary Special-purpose Plane
 * SSR—Server Side Rendering
 * SSSE—Supplementary Streaming SIMD Extensions
 * SSSP—Single Source Shortest Path
 * SSTP—Secure Socket Tunneling Protocol
 * su—superuser
 * SUS—Single UNIX Specification
 * SUSE—Software und System-Entwicklung
 * SVC—Scalable Video Coding
 * SVG—Scalable Vector Graphics
 * SVGA—Super Video Graphics Array
 * SVD—Structured VLSI Design
 * SWF—Shock Wave Flash
 * SWT—Standard Widget Toolkit
 * Sysop—System operator

T

 * TAO—Track-At-Once
 * TAPI—Telephony Application Programming Interface
 * TASM—Turbo ASseMbler
 * TB—TeraByte
 * Tcl—Tool Command Language
 * TCP—Transmission Control Protocol
 * TCP/IP—Transmission Control Protocol/Internet Protocol
 * TCU—Telecommunication Control Unit
 * TDMA—Time-Division Multiple Access
 * TDP—Thermal Design Power
 * TFT—Thin-Film Transistor
 * TFTP—Trivial File Transfer Protocol
 * TI—Texas Instruments
 * TIFF—Tagged Image File Format
 * TLA—Three-Letter Acronym
 * TLD—Top-Level Domain
 * TLS—Thread-Local Storage
 * TLS—Transport Layer Security
 * TLV—Type—length—value
 * tmp—temporary
 * TNC—Terminal Node Controller
 * TNC—Threaded Neill-Concelman connector
 * TPF—Transaction Processing Facility
 * TPM—Trusted Platform Module
 * TROFF—Trace Off
 * TRON—Trace On
 * TRON—The Real-time Operating system Nucleus
 * TRSDOS—Tandy Radio Shack – Disk Operating System
 * TSO—Time Sharing Option
 * TSP—Traveling Salesman Problem
 * TSR—Terminate and Stay Resident
 * TTA—True Tap Audio
 * TTF—TrueType Font
 * TTL—Transistor—Transistor Logic
 * TTL—Time To Live
 * TTS—Text-to-Speech
 * TTY—Teletype
 * TUCOWS—The Ultimate Collection of Winsock Software
 * TUG—TeX Users Group
 * TWAIN—Technology Without An Interesting Name

U

 * UAAG—User Agent Accessibility Guidelines
 * UAC—User Account Control
 * UART—Universal Asynchronous Receiver/Transmitter
 * UAT—User Acceptance Testing
 * UB—Undefined Behavior
 * UCS—Universal Character Set
 * UDDI—Universal Description, Discovery, and Integration
 * UDMA—Ultra DMA
 * UDP—User Datagram Protocol
 * UEFI—Unified Extensible Firmware Interface
 * UHF—Ultra High Frequency
 * UI—User Interface
 * UL—Upload
 * ULA—Uncommitted Logic Array
 * ULSI—Ultra Large Scale Integration
 * UMA—Upper Memory Area
 * UMB—Upper Memory Block
 * UML—Unified Modeling Language
 * UML—User-Mode Linux
 * UMPC—Ultra-Mobile Personal Computer
 * UMTS—Universal Mobile Telecommunications System
 * UNC—Universal Naming Convention
 * UNIVAC—Universal Automatic Computer (By MKS)
 * UPS—Uninterruptible Power Supply or Uninterrupted Power Supply
 * URI—Uniform Resource Identifier
 * URL—Uniform Resource Locator
 * URN—Uniform Resource Name
 * USB—Universal Serial Bus
 * usr—User System Resources
 * USR—U.S. Robotics
 * UTC—Coordinated Universal Time
 * UTF—Unicode Transformation Format
 * UTP—Unshielded Twisted Pair
 * UTRAN—Universal Terrestrial Radio Access Network
 * UUCP—Unix to Unix Copy
 * UUID—Universally Unique Identifier
 * UUN—Universal User Name
 * UVC—Universal Virtual Computer
 * UWP—Universal Windows Platform
 * UX—User Experience

V

 * var—variable
 * VoLTE—Voice Over Long Term Evolution
 * VAX—Virtual Address eXtension
 * VCPI—Virtual Control Program Interface
 * VB—Visual Basic
 * VBA—Visual Basic for Applications
 * VBS—Visual Basic Script
 * VDI—Virtual Desktop Infrastructure
 * VDU—Visual Display Unit
 * VDM—Virtual DOS machine
 * VDSL—Very High Bitrate Digital Subscriber Line
 * VESA—Video Electronics Standards Association
 * VFAT—Virtual FAT
 * VHD—Virtual Hard Disk
 * VFS—Virtual File System
 * VG—Volume Group
 * VGA—Video Graphics Array
 * VHF—Very High Frequency
 * VIRUS—Vital Information Resource Under Seize
 * VLAN—Virtual Local Area Network
 * VLSM—Variable Length Subnet Mask
 * VLB—Vesa Local Bus
 * VLF—Very Low Frequency
 * VLIW—Very Long Instruction Word
 * VLSI—Very-Large-Scale Integration
 * VM—Virtual Machine
 * VM—Virtual Memory
 * VMM—Virtual Machine Monitor
 * VNC—Virtual Network Computing
 * VOD—Video On Demand
 * VoIP—Voice over Internet Protocol
 * VPN—Virtual Private Network
 * VPS—Virtual Private Server
 * VPU—Visual Processing Unit
 * VR—Virtual Reality
 * VRML—Virtual Reality Modeling Language
 * VSAM—Virtual Storage-Access Method
 * VSAT—Very Small Aperture Terminal
 * VT—Video Terminal
 * VTL—Virtual Tape Library
 * VTAM—Virtual Telecommunications Access Method
 * VRAM—Video Random-Access Memory

W

 * W3C—World Wide Web Consortium
 * WWDC—Apple World Wide Developer Conference
 * WAFS—Wide Area File Services
 * WAI—Web Accessibility Initiative
 * WAIS—Wide Area Information Server
 * WAN—Wide Area Network
 * WAP—Wireless Access Point
 * WAP—Wireless Application Protocol
 * WASM—Watcom ASseMbler
 * WBEM—Web-Based Enterprise Management
 * WCAG—Web Content Accessibility Guidelines
 * WCF—Windows Communication Foundation
 * WDM—Wavelength-Division Multiplexing
 * WebDAV—WWW Distributed Authoring and Versioning
 * WEP—Wired Equivalent Privacy
 * WFI—Wait For Interrupt
 * Wi-Fi—Wireless Fidelity
 * WiMAX—Worldwide Interoperability for Microwave Access
 * WinFS—Windows Future Storage
 * WinRT—Windows RunTime
 * WINS—Windows Internet Name Service
 * WLAN—Wireless Local Area Network
 * WMA—Windows Media Audio
 * WMI—Windows Management Instrumentation
 * WMV—Windows Media Video
 * WNS—Windows Push Notification Service
 * WOL—Wake-on-LAN
 * WOR—Wake-on-Ring
 * WORA—Write once, run anywhere
 * WORE—Write once, run everywhere
 * WORM—Write Once Read Many
 * WPA—Wi-Fi Protected Access
 * WPAD—Web Proxy Autodiscovery Protocol
 * WPAN—Wireless Personal Area Network
 * WPF—Windows Presentation Foundation
 * WS-D—Web Services-Discovery
 * WSDL—Web Services Description Language
 * WSFL—Web Services Flow Language
 * WUSB—Wireless Universal Serial Bus
 * WWAN—Wireless Wide Area Network
 * WWID—World Wide Identifier
 * WWN—World Wide Name
 * WWW—World Wide Web
 * WYSIWYG—What You See Is What You Get
 * WZC—Wireless Zero Configuration

X

 * XAG—XML Accessibility Guidelines
 * XAML—eXtensible Application Markup Language
 * XDM—X Window Display Manager
 * XDMCP—X Display Manager Control Protocol
 * XCBL—XML Common Business Library
 * XHTML—eXtensible Hypertext Markup Language
 * XILP—X Interactive ListProc
 * XML—eXtensible Markup Language
 * XMMS—X Multimedia System
 * XMPP—eXtensible Messaging and Presence Protocol
 * XMS—Extended Memory Specification
 * XNS—Xerox Network Systems
 * XP—Cross-Platform
 * XP—Extreme Programming
 * XPCOM—Cross Platform Component Object Model
 * XPI—XPInstall
 * XPIDL—Cross-Platform IDL
 * XPS—XML Paper Specification
 * XSD—XML Schema Definition
 * XSL—eXtensible Stylesheet Language
 * XSL-FO—eXtensible Stylesheet Language Formatting Objects
 * XSLT—eXtensible Stylesheet Language Transformations
 * XSS—Cross-Site Scripting
 * XTF—eXtensible Tag Framework
 * XTF—eXtended Triton Format
 * XUL—XML User Interface Language
 * XVGA—Extended Video Graphics Adapter

Y

 * Y2K—Year Two Thousand
 * Y2K38—Year Two Thousand Thirty Eight
 * YAAF—Yet Another Application Framework
 * YACC—Yet Another Compiler Compiler
 * YAGNI—You Aren't Gonna Need It
 * YAML—YAML Ain't Markup Language
 * YARN—Yet Another Resource Negotiator
 * YaST—Yet another Setup Tool

Z

 * ZCAV—Zone Constant Angular Velocity
 * ZCS—Zero Code Suppression
 * ZIF—Zero Insertion Force
 * ZIFS—Zero Insertion Force Socket
 * ZIP—ZIP file archive
 * ZISC—Zero Instruction Set Computer
 * ZOI—Zero One Infinity
 * ZOPE—Z Object Publishing Environment
 * ZMA—Zone Multicast Address
 * ZPL—Z-level Programming Language

title: List of computing and IT abbreviations


text:
Talk:BASIC

Peter Fedorow

 * I removed the following sentence from the article: Based on an article originally written for Nupedia by Peter Fedorow <fedorowpATyahoo.com>, licensed under the GNU Free Documentation License. As far as I can tell there has never been an article on BASIC on Nupedia (neither finished, in-progress or on the chalkboard). —R. Koot 21:30, 5 December 2005 (UTC)
 * Yeah thats true since there's no mention of BASIC at http://nupedia.8media.org/newest.phtml, I also removed this reference from Nupedia_and_Wikipedia article. 202.65.149.2 13:40, 17 January 2006 (UTC)
 * Oops, my apologies for reverting you since it seems you may be right; however, the claim of a link goes back as far as it's possible to know: the earliest (surviving) version of this page. OTOH, that version only claims it was written for Nupedia, not on it - maybe it was never actually submitted, and it was the author who put it here, rather than someone using the GFDL? All a bit academic, I know, but kinda interesting, in a vague way... - IMSoP 13:51, 17 January 2006 (UTC)
 * This seems to be the most likely explanaition. I'll try to contact him. —Ruud 13:59, 17 January 2006 (UTC)

Pictures
This page looks like a tetris game. The images are all either blue or black blocks, in a uniform size. It could do with some morevaried sizes, and more main sections with less subsections. MichaelBillington 05:23, 12 June 2006 (UTC)

Hello World
Does anyone besides me think there should be a Hello World program listed on this article that is not just an image?

10 PRINT "Hello World"

Or for some people:

10 PRINT "Hello World" 20 GOTO 10

FL a RN (talk) 18:17, 24 November 2006 (UTC)

About a footnote
Footnote 1 says "The acronym is tied to the name of an unpublished paper by Thomas Kurtz and is not a backronym, as is sometimes suggested." Says who? We can't just make an assertion like that without a verifiable source. 81.159.56.96 01:53, 8 May 2007 (UTC)
 * Oh we can as long as no one contests it. However since you have now done so we'll need to provide one. -- Derek Ross | Talk 06:06, 8 May 2007 (UTC)

Object-oriented versus High-Level
Correct me if I'm wrong, But BASIC is not Object-oriented although it is a high level language? Complex-Algorithm-Interval 02:45, 11 August 2007 (UTC)

 * Dartmouth BASIC was originally devised as a "high-level language" in 1964. During the early 1970s, structuring keywords were added to it and Dartmouth BASIC version 7 became a "structured programming language" (although you might not have noticed since a lot of clones of mid-1960s BASIC were written during the late 1970s and 1980s). During the 1990s, object-programming keywords were added to (Visual) BASIC and it became an object-based (somewhat object-oriented) language. Since 2003, VB.NET has appeared. It is a fully object-oriented version of BASIC. So we are now in the position where some dialects of BASIC are object-oriented, some are object-based, some are structured, and some are just high-level. So your statement is right for some versions of BASIC and wrong for others. -- Derek Ross | Talk 06:20, 11 August 2007 (UTC)
 * Just an aside: Languages become object-oriented when they provide language support for object-oriented programming, so that the programmer doesn't have to build the structures. It was possible to do Object-Oriented or Structured or Functional programming in BASIC,C or Pascal. And people did so: OO languages weren't created Ex-Novo.
 * There were many large commercial projects written in BASIC when the language was popular, and some of them used complex program structures and techniques. For example, a v-table is a data structure used to support dynamic dispatch in some object-oriented languages. Programmers used to create their own v-tables in C,Pascal or BASIC, to support their v-table based objected-oriented programs. Before object oriented languages became available, BASIC was particularly suited for building Object-Oriented or Functional programs because most BASICS inherently supported Dynamic Dispatch.
 * I think that BASIC was particularly un-suited for bulding Object-Oriented or Functional programs because the resulting program was almost un-inteligable without external documentation. But I think that C++ programs are uninteligable too, so maybe it's just me, not the programs.  —Preceding unsigned comment added by 203.206.162.148 (talk) 03:10, 18 August 2010 (UTC)
 * Good points which I agree with. -- Derek Ross | Talk 06:23, 18 August 2010 (UTC)

Popularity Today
The article states that BASIC "remains popular to this day in a handful of heavily evolved dialects". If you mean VB AND VB.NET this is obvious. For other “modern versions” such as Quickbasic that still have line numbers etc this needs documentation. COBOL is still around a lot in large corporate mainframe type machines. The article needs to state outside of the VB world where and how BASIC is used in 2007 Edkollin 16:21, 20 August 2007 (UTC)
 * Only place that I can think of outwith the VB dialects, is PIC microcontrollers eg the BASIC Stamp. -- Derek Ross | Talk 18:48, 20 August 2007 (UTC)

 * Lotus Notes (installed base 130,000,000 seats) incorporates a BASIC dialect that is called LotusScript. In addition to being the basis for countless applications written by IBM Lotus' customers, a great deal of the front-end functionality of Notes' built-in mail and calendaring system is implemented in it. Rhsatrhs 00:40, 21 August 2007 (UTC)

Y'all apparently forgotten about the various timesharing BASICs that were developed in the 1970's for minicomputer use (e.g., MAI Business Basic, Wang Basic, etc.). A lot of that code is still in use and probably will continue to be so for many years. BTW, in the 1980's, companies such as Basis International and Thoroughbred were founded to port the MAI style business BASIC into UNIX. I still do some development with Thoroughbred's package (which is "semi-compiled" T-code). —Preceding unsigned comment added by 70.228.163.254 (talk) 06:02, August 28, 2007 (UTC)
 * Visual Basic also has line numbers.--Dojarca 14:43, 1 October 2007 (UTC)
 * As does QuickBASIC ... but having used the latter and assuming the former to be similar (as AFAIK its somewhat of a continuation of the same product line), they're not essential. I've seen enough QB programs, including nearly all of the included example files, that forego them completely, and just use text labels and seperate modules if they need to jump to a certain section 82.46.180.56 (talk) 16:41, 12 April 2008 (UTC)

Visual Basic
Does it include the different/similarities between Basic and Visual Basic? Visual Basic has totally different commands, although the first BASIC versions had relatively the same keywords. Complex-Algorithm 00:49, 5 September 2007 (UTC)

 * Not totally different - this is easy to overstate. Visual Basic includes If, Then, For, Next, Goto, Dim, Int, Asc, Len, End, Stop, Rem.  VB 1-6 had no console-mode support, so it's natural enough that Print and Input were missing (having said that, Print was still possible for files, for the debug object, and if used with a form object, Form1.Print, and Input was also possible with a file number).  VB.NET (version 7 onwards) reintroduced console mode but without Print and Input (although again, they can be used for file I/O, but with slightly different syntax from before).  All versions of VB, even .NET, allow optional type-declaration characters such as % and $ to be appended to variables.  VB 1-6 allow Str$, Chr$, Left$ alongside Str, Chr, Left - in .NET the $ is dropped completely.  All versions have VB have exactly the same mathematical operators (+, -, *, /, \, Mod, ^) as earlier versions of MS Basic.  All versions of VB, even 2008 beta, allow optional line numbers to be entered at the start of lines, albeit VB only allows them on certain lines, not all.  VB 1-6 include While, Wend, Gosub, Return.  VB 7 onwards have While / End While and drop Gosub. -- 86.137.136.182 (talk), 22:37, 9 September 2007 (UTC)
 * VBA 5 and 6 have console support and "print" coommand as well. Probably and VB have.--Dojarca 14:37, 1 October 2007 (UTC)

 * Well said. VB and other BASIC dialects have far more in common with each other than they do with other languages. It still makes sense to think of VB as one more dialect of BASIC -- even the .NET variant. -- Derek Ross | Talk 22:44, 9 September 2007 (UTC)

 * VB3 has "console-not-console" support: Print prints to the surface of a form. I don't think that Win 3.x had any console support, so this was a resonable approach.150.101.166.15 (talk) 04:51, 13 December 2007 (UTC)

 * VB before .NET never really had true console support, even under Win32 where it was avaiable. PRINT in VB6 still printed to a form (unless otherwise specified, and stdout was not an option). -- int19h (talk) 21:02, 15 December 2007 (UTC)

Modern BASIC
The example shown here as an example of "modern Basic" is not a modern basic in fact. It is a Basic of second generation (structured) while VisualBasic and StarBasic are basic systems of 3rd genegarion (object).--Dojarca 14:34, 1 October 2007 (UTC)

Alternate version of Visual Basic .NET version of example
Madlobster 15:53, 1 December 2007 (UTC)
 * You do not need to separate line numbers with colon. VB supports line numbers as well.--Certh 13:33, 3 December 2007 (UTC)

I didn't type them. Visual Studio 2008 put them there automatically.Madlobster 21:26, 3 December 2007 (UTC)

Historical Context?
I believe that the entire premise of this section is factually incorrect.

I.e., The key sentences are:

- "Because memory chips were very expensive, 8-bit computers did not have the capacity to run a memory intensive compiler-linker program."

- "The only compilers in existence for microprocessors were cross-compilers"

- "Native compilers became feasible only in the late days of the heyday of the IBM/AT machines when memory ceilings of around 512 kilobytes became affordable."

Those assertions are simply not true. In 1980 (i.e., before the first IBM PC was available, not to mention years before the AT), I was using Leor Zolman's C compiler known as BDS C, running it on a microcomputer known as the Intertec Superbrain. This was a dual Z-80 system (the second Z-80 was used as an i/o controller) with just 64K of RAM. I also recall using the Digital Research PL/1 compiler (known as "PL/1-80") on that same machine. And although I was not a user of it, I think that the Mark Williams Company C compiler was also used on IBM PCs well before the AT was available, and possibly the Lattice and Whitesmiths compilers. And Microsoft C was certainly available before the "late days" of the AT, if not even before the AT shipped.

Frankly, I'm leaning toward deleting this entire section. Perhaps it can be re-worked to emphasize that compilers were infeasible on microcomputers in lower-end configurations used by many typical hobbiests... but I don't really see what value that fact adds to this article. Rhsatrhs (talk) 03:06, 28 December 2007 (UTC)

 * I think deletion is the best idea. I was not happy with this section either. -- Derek Ross | Talk 04:57, 28 December 2007 (UTC)

 * Done. Text pasted here in case anyone wants to try to make something better from it.Rhsatrhs (talk) 02:41, 29 December 2007 (UTC)

A Bit of History sidebar
In addition to the "Historical Context", I removed this box from the article and dropped it here. The first sentence makes no sense. In fact it should be several sentences, but how they relate to each other and what point they are trying to make is a mystery.

Dartmouth College
I have given a fuller description of the location so as to avoid confusion with http://www.dartmouthcollege.co.uk/bayard/int/ —Preceding unsigned comment added by 86.147.253.126 (talk) 16:29, 6 January 2008 (UTC)
 * If they want to know where it is, they can click on the link. It's, at best, a parenthetical description, and probably should not be in the article at all.  — Arthur Rubin |  (talk) 16:43, 6 January 2008 (UTC)
 * I disagree. If it remains there is nothing wrong with a proper description, in fact it helps. —Preceding unsigned comment added by 86.147.253.126 (talk) 16:46, 6 January 2008 (UTC)

What's the difference between RAM and memory?
"Newer computer systems supported time-sharing, a system which allows multiple users or processes to use the RAM and memory"

But... RAM stands for Random Access Memory. In other words, RAM is Memory.

Shouldn't it be "processor and memory" (or "CPU and RAM")? —Preceding unsigned comment added by 216.218.41.190 (talk) 17:58, 9 September 2009 (UTC)
 * Yes, RAM is memory... and ROM is memory, and Core is memory, and disc is memory and drum is memory. Computers of that era had an extremely limited amount of electronic RAM, a slightly larger amount of Core (magnetic RAM) and a much larger amount of disc- or drum-based virtual memory. Disc and drum can simulate RAM when used with paging hardware but they're not exactly RAM themselves. So RAM is always memory but memory is not always RAM. -- Derek Ross | Talk 05:28, 12 September 2009 (UTC)

Text Clash
On my computer, at the top of the History section the "[Edit]" text overlaps the word "special-", pushed there I think, by the image. I don't know how to fix this, so I'm mentioning it here. Dinoceras (talk) 09:32, 9 November 2009 (UTC)

Screenshots
Why does the first screenshot show Atari Basic and not the famous C64 Basic start screen? 92.105.10.244 (talk) 10:13, 6 December 2009 (UTC)

 * They're all famous. We tossed a coin and picked one. -- Derek Ross | Talk 16:25, 6 December 2009 (UTC)

Discussion of revert to "Basic Culture and Computing Culture"
"The threshold for inclusion in Wikipedia is verifiability, not truth—that is, whether readers are able to check that material added to Wikipedia has already been published by a reliable source, not whether we think it is true."

The Dijkstra quote is well-known, and verifiable; the evolution of Basic culture and its nonuse for most systems programming is verifiable in many histories of the field (a "cite" should not be provided for well-documented material that is verified elsewhere).

The Nilges book, which describes a compiler-interpreter for Quick Basic written in .Net Basic, is I think worthy for inclusion because it's the exception that proves the rule. But it needs a cite, and a cite was provided.

 * Trouble is you're repeating stuff that's already in the article. We already mention Dijkstra's quote. So why mention it again ? As for the non-use of BASIC for systems programming, well, everyone used or uses C for systems programming don't they ? So BASIC is only one of many languages (most of them in fact) not intended for systems programming. So again, why mention it? Surely it makes more sense to mention that a language is intended for systems programming than that it isn't since that is the exceptional case. In any case, whatever the initial intention, BASIC has been and still is used for systems programming in a very few situations, including the occasional creation of systems programming tools. For instance STAMP controllers have been around for twenty years plus, PowerBASIC for almost that long. The use of BASIC for systems programming is easily verifiable. QuickBASIC itself has been used for systems programming including for writing its own compiler (check out XBASIC or Freebasic both of which are extended QuickBASIC compilers written in extended QuickBASIC), so the fact that somebody has used .NET Basic to compile a subset of QuickBASIC isn't particularly interesting, far less some sort of exception. It actually sounds to me as if you're spamming the article to plug the Nilges book (although I realise that that's unlikely given the age of the book) and I'd support removing your additions from the article on that basis alone, never mind the duplication of already existing info. -- Derek Ross | Talk 07:12, 3 January 2010 (UTC)

 * By the way, I just checked and you got the Dijkstra quote wrong. He said that "The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offence". So, wrong language. Please try reading the article and all of its footnotes before making any more changes. If you had already done so, you would have been able to discover what Dijkstra really said about BASIC. -- Derek Ross | Talk 08:34, 3 January 2010 (UTC)

Birth Date
The article contradicts itself on the year BASIC was first developed: 1963 vs. 1964. Kdammers (talk) 10:26, 3 April 2010 (UTC)

NON-FREE Image use in this article.
There is an overuse of non-free images. Considering 3 of the 4 images only have 1 letter difference in the entire image, I doubt these all qualify for non-free use in the article, and the last is just a different version name. One image would be enough to give a basic idea of the IBM BASIC. Unless anyone can point out an outstanding reason for having four images which can be condensed in to one image, 3 of the 4 can be removed. Spigot Who?  14:28, 7 May 2010 (UTC)

VB.NET-Sample
The VB.NET sample is not very good. It could be compacter. But editing the sample is not possible. A lot of HTML commands (see wiki source) makes editing the sample impossible. :-( --Filzstift (talk) 10:23, 11 April 2011 (UTC)

The early days of BASIC
I think GE Commercial Time-Sharing deserves at least an acknowledgement. I was involved in it at the very beginning. The Dartmouth BASIC ran on what was called a GE-265 computer which was, in fact, a GE-235 computer working with a device called, if memory does not fail me, a Datanet 30. I believe that the Datanet was developed for telephone switching. It made the time-sharing possible. GE bought the rights to use the Dartmouth design and went into the commercial time-sharing businees. But before they went public they rebuilt the system to make it sturdy enough to use commercially.

The original setup was a compiler. The input-output system was punched paper tape. So people would write their programs offline and put them on punched paper tape. Then paper tape was fed in at the user's console (a teletype), compiled and run. Output, if any, was punched out at the teletype.

After GE got the program four of us entirely rewrote it in a couple of months. I did the computational part of the compiler. The GE-235 was a very weird computer and programming for it (in its machine language, of course) was a strange experience. The original Dartmouth implementation was, to put it politely, student term papers. I cannot believe the time trials mentioned in the text were run on the real original BASIC - I suspect nobody knew that GE had completely rewritten it. GE kept calling their BASIC Dartmouth BASIC for quite some time. It is entirely possible that GE management was not aware it had been rewritten.

DKleinecke (talk) 20:28, 4 July 2011 (UTC)

Maturity: the personal computer era
The section Maturity: the personal computer era is far below any acceptable standard:
 * 1. BASIC's fortunes reversed once again with the introduction of Visual Basic by Microsoft.
 * yeah! (Except a little too heroically written: "fortunes")
 * 2. It is somewhat difficult to consider this language to be BASIC[neutrality is disputed], because of the major shift in its orientation towards an object-oriented and event-driven perspective[citation needed].
 * no and no: it wasn't object-oriented and so it is in fact very easy to consider,
 * 3. The only significant similarity to older BASIC dialects was familiar syntax.
 * which uses to define a programming language, and as far as I can remember, it executed as a BASIC too, and so was a good-old BASIC, except cleaned up and tidied for some structured programming,
 * 4. Syntax itself no longer "fully defined" the language, since much development was done using "drag and drop" methods without exposing all code for commonly used objects such as buttons and scrollbars to the developer.
 * which is the worst garbage in the section: a programming language is defined by its syntax, not by any happenstance IDE - if it were, gcc perusing emacs and gmake would be quite another language than gcc perusing gedit and another make, but in fact gcc is C, whatever IDE/editor/make system that is used.

There's certainly more, but the text needs to be on level with computer science, not an amateur BASIC-only heroic saga. Rursus dixit. ( m bork3 !) 20:45, 16 September 2011 (UTC)

 * Forgot to say: this refers to VB before VB.NET, which was what the section was about. VB.NET is allegedly better, so maybe it is. Rursus dixit. ( m bork3 !) 20:47, 16 September 2011 (UTC)

 * The VB compiler understands the syntax of FRM files. The QuickBASIC compiler doesn't. The VBDOS compiler had the same variable scoping rules as QuickBASIC, so it could also compile QuickBASIC code. However the VBwin compilers treated variable scope differently, so they could not compile QuickBASIC code. In addition the events associated with VB forms led to a very different programming style from the one used for QuickBASIC. There is more to a programming language than syntax. Scoping, events and available data types are also key. Syntax of Algol, Pascal and Modula are all fairly similar. The big differences lie elsewhere. The same is true of different generations of BASIC. And yes, agreed. The IDE has nothing to do with anything. The VB IDE hides the true syntax of FRM files but there is nothing stopping anyone from using Notepad to see their real nature or indeed to edit them provided that they have been saved as text. -- Derek Ross | Talk 00:04, 17 September 2011 (UTC)

Trim
Hi, I've just hacked out a fair bit of text. If it belongs anywhere, it should be in Dartmouth BASIC article. I'll be looking at tidying up the rest of the article too in the coming days. Snori (talk) 17:36, 12 November 2011 (UTC)

More important to whom?
"More important were the facilities for structured programming..." Sez who?! In an encyclopedia, what's a value-judgment doing in the article?! What if I'm someone who thinks graphics extensions are far more important than satisfying the "kerrect programming" requirements according to Dickstra? Just like Wikipedia to reflect the opinions of Unixtoxicated text-only "correct"-programming weenies... 46.117.126.215 (talk) 01:13, 11 December 2011 (UTC)

Typing
This article before I fixed it claimed that BASIC was strongly typed. This is a false claim. There are versions of BASIC which are not typed at all. The runtime machine determins the type on the fly and it can switch it back and forth as needed. So a string can become a numeric and then back to a string, a file pointer can be examined as a text string, a list pointer can be as well. That's not a strongly typed language. Although I agree there are some versions of BASIC which are in fact strongly typed, not all of them are, and this article is on all of them, not some.Wjhonson (talk) 21:39, 12 December 2011 (UTC)
 * The original language was strongly typed. It differentiated between string variables and floating point numeric variables. Conversions between the two types required conversion functions and the results had to be stored in a variable of the correct type. Later dialects added integer variables of various sizes and assorted types such as Boolean. However I'm not aware of any weakly typed or untyped dialects until VB for Windows was introduced in the mid 1990s. Perhaps you can name some that existed in the 1980s or before. Even today when a few untyped variants exist, the majority of implementations are strongly typed. So I don't think that it's a completely false claim. Merely one which is no longer as true as it was. -- Derek Ross | Talk 22:12, 12 December 2011 (UTC)

 * And the ANSI/ISO definition of the language specifies it as a strongly typed language. So it might be more accurate to say that the language is strongly typed but that non-conformant implementations that allow untyped variables exist. -- Derek Ross | Talk 22:23, 12 December 2011 (UTC)

BASIC used in business
This article also does not seem to cover BASIC as a language running thousands of small businesses in the 1970s and 1980s. Instead it focusing on home computer use. That section should be introduced.Wjhonson (talk) 21:44, 12 December 2011 (UTC)
 * I Second the motion, I would like to hear from people who created hundreds (I think) of Business programs used world-wide in Basic-like lang...Gcavazos (talk) 02:58, 15 September 2012 (UTC)

Need an improved/expanded criticism section
Yes, the article has Dijkstra's famous "mentally mutilated" comment. But, 24.229.124.203 (talk) 06:00, 18 October 2012 (UTC)
 * What, specifically, about BASIC causes the mutilation?
 * Have computer science pedagogues reached any sort of consensus about better tools and methods for introducing young students to programming?
 * We discussed the "mental mutilation" years ago. Check the archives for this talk page for a possible reason. -- Derek Ross | Talk 13:36, 18 October 2012 (UTC)

Confused
The earliest date given here is 1964. But I was introduced to something that was called Basic before I entered "Adavanced Level" grades - which can be no later than July 1962. This was part of an ICT educational outreach programme. The language structure of the subsection I saw was very similar to the Basic from Dartmouth College. In principle this should be referenceable and therefore included - but I could find nothing. Can anyone help? PhysicistQuery (talk) 16:11, 2 January 2015 (UTC)

Sister Keller
Keller may have been one of the students (apparently a grad student) who implemented Basic under the direction of Professors Kemeny and Kurtz. The "Encyclopedia Dubuque" ref in Keller's article says "Sister Keller had assisted in the development of BASIC computer language while at Dartmouth College." The ACM GCSE Bulletin article by Denise Gurer says "At Dartmouth, the university broke the “men only” rule and allowed her to work in the computer science center, where she participated in the development of BASIC." "Assisting" and "participating in the development" do not warrant equal billing. No reliable source has been presented to say she deserves equal billing. Articles I found at Google Book Search say things like "Professors Kemeny and Kurtz, working with students at Dartmouth College in 1963 and 1964, developed the Basic programming language." The Encyclopedia of information Technology says "The original Basic language was invented in 1963 by John Kemeny (1926-1993) and Thomas Kurz at Dartmouth College and implemented by a team of Dartmouth students under their direction. None of these articles single out Keller as being of particular importance in that development. The only sources presented so far say that she was one of the students working under the direction of Kemeny and Kurtz, and it may be that the Keller article needs a bit of editing to avoid overstating her role. If she was the co-developer, then lets see the reliable sources which can verify it. Until then, she should not be listed as the co-developer. Edison (talk) 19:36, 13 March 2015 (UTC)
 * I did the same searches and I agree. This dispute seems to be over changes to the lede and to the infobox. The argument in the infobox is "Designed by"—does that mean the language, or the implementation? The lede clearly says "designed the original BASIC language". But implementing is not the same as designing the language (which to me, as an occasional designer of "little languages", means designing its syntax). From what I gather, Kemeny and Kurtz designed the syntax, and Keller was among the group that helped implement it. The article body says "The original BASIC language was designed on May 1, 1964 by" by Kemeny and Kurtz, and the ref for that does not mention Keller. The lede should not have anything not in the body. (I doubt that the entire design job was done in one day, but that's another subject. The ref given for the latter claim actually says that the first BASIC program ran on that day.) Jeh (talk) 23:18, 13 March 2015 (UTC)
 * I'm in full agreement with Edison (and Jeh) on this matter. I wouldn't particularly object to mentioning her in the History section, but this needs to be phrased carefully, as there do appear be other students that worked on the development. Her specific claim to fame seems to be being (one of) the first woman/women to receive a PhDs in computer science, not having been a developer of BASIC. —Ruud 22:30, 14 March 2015 (UTC)
 * I support 's recent edit. However I suggest that it should be possible to nail this down by looking up Kemeney and Kurtz's early papers describing the language and its implementation, and/or Keller's list of publications. If Keller is listed as an equal-status co-author with Ke and Ku, as opposed to "the work was assisted by" or similar, then she can go back in the article as co-creator. If not, then that is further support for the current status. Jeh (talk) 08:34, 16 March 2015 (UTC)

 * Regardless of all this, it seems that it was perfectly reasonable for the reversion of the IP address edits to be challenged when they were because the referenced claim is in the Mary Kenneth Keller article where it has stood unchallenged since the article was created back in July 2012. The reversion offered no competing evidence.  This discussion was not available at that time. –  Live Rail    < Talk >  11:34, 16 March 2015 (UTC)

 * I disagree. But that's not a topic for this talk page. Jeh (talk) 14:25, 16 March 2015 (UTC)

 * You don't state which bit(s) of my post you disagree with or why. So here goes:
 * There is no evidence that the first first edit from an IP address editor was made in bad faith. You are therefore required by Wikipedia policy to assume that the edit was made in good faith.  The second edit from another IP address editor merely correctly and properly added a wikilink to another article.  If you are disagreeing that either of these edits was made in good faith then you are as guilty as  of not assuming the required good faith.
 * That the Mary Kenneth Keller article had both the claim and the supporting reference when the article was first written cannot be in doubt as the article's edit history clearly shows this to be so.
 * This was the talk page of this aricle as it was when the first IP address edit was made. There is not yet any discussion on the role Mary Keller did or did not have in the development of BASIC.
 * So which bit are you disagreeing with, why and where is your evidence? –  Live Rail    < Talk >  08:56, 17 March 2015 (UTC)
 * Article talk pages are for improving article content. I see no way that your questions here are about improving the article. So as I said above, "that's not a topic for this talk page". Since I was apparently not clear above, I'll be more clear here: I won't respond further to such questions. Jeh (talk) 11:22, 17 March 2015 (UTC)
 * , you may like to note that has consistently defended Wtshymanski's policy of reverting all IP edits made to any engineering based article.  He has also consistently posted an argument defending Wtshymanski's reverts.  However, all have been non arguments based on fatuous material.  You have summed up his last post but one perfectly.  No surprise whatsoever that he has refused to justify it.
 * You (and Jeh) may care to note that Wtshymanski has already confirmed that he does operate a policy of reverting all IP edits in articles that he routinely watches with the exception of one per year. Wtshymanski used the one per year to claim that he does not revert all IP edits - a claim that impressed few including the admins.  DieSwartzPunkt (talk) 18:46, 17 March 2015 (UTC)

 * The 1964-1965 development of Basic was a very notable event in the history of computer software, and is certainly within living memory for any of the participants at Dartmouth). It seems very likely that someone in the field of the history of technology would have tracked down participants and documented their recollections, or would have done in depth interviews of Kemeny and Kurtz, then written up reliable secondary sources which could be used to improve this article, and to shed light on the contributions of participants other than Kurtz and Kemeny. I just did not find such writings in my recent Google Book search. In  histories of other technology, the contributions of the "little people" to the successes of famous inventors have often been written up, such as Dickson's contribution to motion picture technology in Edison's lab. We are not on deadline, so I hope that someone will dig into reliable sources about the development of Basic. If Keller shows up as a major contributor, similar to Kemeny and Kurtz, I have no objection to appropriate coverage. The sources that say she was there and participated are not justification for the edits listing her as the co-inventor.  An article in Time magazine in 2014 on the 50th anniversary of the development of Basic said of Kemeny and Kurtz " They lead a team of a dozen undergraduate students - young men who were still in the process of learning about computers themselves. (Dartmouth was a male-only institution at the time: Kemeny himself took it co-ed in 1972 as president of the college, a position he held from 1970-1981)" So was Keller really a student of any kind at Dartmouth when Basic was being developed? Was she an auditor or visiting student? In her favor, there was a long standing tradition of leaving women out of official histories of early computing. During WW2,female mathematicians did the work of programming the first computers, and were conspicuously absent from photos and accounts of how men got the computers working.  Edison (talk) 19:13, 16 March 2015 (UTC)

 * The proceedings of ACM SIGPLAN HOPL-I had a whole section devoted to BASIC. I scanned the article by Kurtz. It seems to mention a few students by name, but not Keller. —Ruud 19:50, 16 March 2015 (UTC)

 * Indeed. As I wrote somewhere, to anyone who was following the microcomputer industry, Kemeny and Kurtz were, for at least a period of time, as well known re. Basic as Admiral Hopper was re. Cobol. This was due to a resurgence of awareness of their names: after seemingly every microcomputer maker came out with their own unique extension to Basic, they formed a company that sold a product called "True BASIC" - "extended BASIC as it should be, from the original inventors of BASIC". They made much of their status as "original inventors" and got much attention in the trade press, so their names were spoken of a lot. I haven't thought about those names in a long time, but when this discussion came up I immediately remembered "Kemeney and Kurtz"; this took no great expert-level involvement in the industry. And I never heard anybody say "there is another." (Personal note: My "survey of programming languages" class was taught by a staunch feminist and if there had been any hint of a woman who was truly Basic's co-inventor but who had been ignored due to gender bias, I'm quite certain she'd have mentioned it.)
 * Investigation should continue but I think what we have here is completely sufficient to support this page as it is. And also to bring the matter to the Mary Kenneth Keller page... to its talk page at least. Jeh (talk) 22:32, 17 March 2015 (UTC)
 * Further investigation may well be warranted, but not based on your post. It's wall-to-wall original research in that you have cited absolutely nothing.  DieSwartzPunkt (talk) 13:11, 18 March 2015 (UTC)
 * I didn't suggest, nor would I support, that any of that be used in the article as is and with no citations. I even highlighted my "personal note" so as to make damn sure it was clear that I wasn't claiming anything citable there. So I'm not sure what your complaint is. Jeh (talk) 16:12, 18 March 2015 (UTC)

The widespread claim that Sister Keller played a role in the development of Basic is an urban myth. Some sources place her at the computer center at Dartmouth in 1958. Yet Dartmouth did not acquire its first computer until 1959, three months before I arrived as a freshman. Dianne P. O'Leary spent some time investigating Sister Keller's involvement with computer science. She found
 * Sister Mary Kenneth Keller (MKK) was at Dartmouth in the summer of 1961, between the time she taught math at St Mary's High School in Chicago and at Heelan High School in Sioux City, Iowa. She continued to teach high school until 1964, and there was no reason for her to need an exception to participate in Dartmouth's summer program.
 * MKK went to Clarke College in 1965, after receiving her PhD. This was 4 years after the Dartmouth summer program, so since you mention the Clarke affiliation, I guess you must have stayed in contact with her. Some of her notes suggest that she did maintain contact with Dartmouth, perhaps through ASCUE, or perhaps through her activity in writing a book with Dorn and Greenberg on Mathematical Logic and Probability with BASIC Programming.

I remember seeing Sister Keller at Dartmouth, perhaps in the summer of 1961, which was several years before Kemeny and Kurtz invented Basic. At best, she observed our work on the Dartmouth ALGOL 30 compiler, whose successful use in education was a precursor to the development of Basic. SJGarland (talk) 19:51, 31 December 2021 (UTC)SJGarland

Time Sharing vs Batch
In this article Time sharing and batch systems are explained as the same type of system.

Multitasking does not equal time sharing system. Time Sharing is multiple interactive users sharing a computers respurces. True multitasking is required. However a multitasking batch system does not support user interaction with batch jobs.

The issue may be clouded on the DEC-System-Ten for example. On the TOPS-10 operatoring system BATCH jobs were run by a program. The batch control program usually ran privileged on the operators terminal.Steamerandy (talk) 08:44, 15 October 2015 (UTC)
 * I've just tidied up the history section to clarify in a way that makes sense for this article. Snori (talk) 23:37, 15 October 2015 (UTC)

Business BASIC
There is hardly any mention in this article of the use of BASIC on the timesharing minicomputers of the 1970s and 1980s. Systems such as the MAI Basic Four and Point 4 had a highly optimized form of BASIC that was designed for interaction with a timesharing operating system, and hundreds of thousands of these systems were sold worldwide.

In the early 1980s, companies like Basis International (BBx) and Concept Omega (Thoroughbred) developed timesharing BASIC implementations that would run on UNIX. These UNIX implementations remain in use to this day, often running code that was developed back when Ronald Reagan was president of the USA.

As for Visual Basic, that is an aberration and not at all representative of what BASIC is all about.

38.69.12.5 (talk) 23:19, 27 January 2016 (UTC)
 * Well go ahead and add it then. Sounds like it would be a good addition to the article and you obviously know more about it than most of us. -- Derek Ross | Talk 01:05, 28 January 2016 (UTC)

 * Yes, go ahead and add it... As long as there are good references.

 * BASIC also enjoyed widespread use on the PDP-11 under RSTS/E. Jeh (talk) 01:24, 28 January 2016 (UTC)

Micro-Soft
"In 1975 MITS released Altair BASIC, developed by Bill Gates and Paul Allen as the company Micro-Soft," Shouldn't this be "... at  the company..."? Kdammers (talk) 22:46, 8 June 2016 (UTC)

 * No. Initially Gates and Allen were the company. Jeh (talk) 23:00, 8 June 2016 (UTC)

Trivia section
Hi boys, hello girls! I removed the trivia section as is recommended here.--Jimmy Olano (talk) 20:34, 24 August 2019 (UTC)

Legal Status
Accordingly Wiki type of Pages refer to programming languages that are programmed in basic to allow for an asnii shell using homonyms and ciphers to correlate "their" information using hacker software compatible with Google Translator. This software does not come from anything else other than Canopy, a derivative of Filmhouse located in Ohio. — Preceding unsigned comment added by 2605:A000:1301:877E:96C0:E216:4649:62A9 (talk) 23:53, 5 April 2020 (UTC)
 * Ummm... This resembles English but English generated by a random text generator. It has syntax but seems to be devoid of meaning. -- Derek Ross | Talk 03:31, 7 April 2020 (UTC)

please add this quote to balance it
"I think Dijkstra, God rest his soul, was entirely wrong about that. I know so many really good programmers who got their start programming BASIC because that’s what was available to them." -Joshua Bloch in Coders at Work (page 170)

-

Top programmers such as Jamie Zawinski and Brad Fitzpatrick started with BASIC.

Joshua Bloch himself did lots of BASIC: "I was programming in BASIC, like everybody else back then, from about 1973 through 1976. That’s when I got seriously into it (programming)." -Same book

Alfredo Valente (talk) 15:24, 13 April 2020 (UTC)

Am I missing something here?
Beginners' All-purpose Symbolic Instruction Code[2] or Beginners All-purpose Symbolic Instruction Code

The only difference between these two appears to be a single-quote after the S. I don't believe that requires both to be written out~ Maury Markowitz (talk) 19:47, 3 June 2020 (UTC)

tokenization
Is there a Wikipedia article that discusses the kind of tokenization used many BASIC dialects? My understanding is:

 * (a) When typing in lines of a program or loading a program from disk/cassette, common keywords such as "PRINT", "IF(" (including the opening parenthesis), "GOSUB", etc. are recognized and stored as a single byte or two in RAM, some or all spaces were discarded, line numbers and internal decimal numbers are converted to internal binary format(s), etc.
 * (b) When listing the program with LIST or storing a program to disk/cassette, those tokens are expanded back to the full human-readable name of the keyword, spaces were inserted as necessary, those binary values are printed out in decimal, etc.

Some articles (such as the "Applesoft BASIC" article) link to tokenization (lexical analysis), which is closely related but not exactly the same -- that article covers the sort of thing done in compilers similar to (a), but that article says nothing about (b), which compilers never do, but practically every BASIC dialect mentioned in the "List of computers with on-board BASIC" article does.

The source-code editor article briefly mentions "tokenizing editors" that do both (a) and (b).

Should *this* "BASIC" article have a section on tokenization, or is there already some other article that discusses it? --DavidCary (talk) 17:40, 7 July 2020 (UTC)

 * I now see that BASIC interpreter discusses such tokenization, but I still wonder -- do any other non-BASIC languages do such tokenization? --DavidCary (talk) 04:29, 3 September 2020 (UTC)

Any such discussion should make it clear that the "tokenization" done by such BASICS, at least in the Microsoft versions, is not the lexical analysis, or at least not all of it. The final lexical analysis is done by the interpreter on the result of the "CRUNCH" routine, and many lexical units are still multiple characters at that point. I've done some original research in this area; feel free to contact me for further information on this if you like. Cjs (talk) 03:27, 21 November 2020 (UTC)

The tokenization was really just a microcomputer interpreter thing, owing to the lack of memory on early micros. I don't think that minicomputer or mainframe BASICs used it. And although BASIC compilers could handle it, they didn't require it. -- Derek Ross | Talk 16:48, 22 November 2020 (UTC)

Yes, to this day, most BASICs support (but frown on) the use of the '?' for "PRINT". — Preceding unsigned comment added by 2001:8003:E41C:1C01:8416:B98E:59:E8A8 (talk) 11:53, 18 October 2022 (UTC)

Typo
There is a typo in a note. '(of even' should read '(or even' -- I don't know how to make the correction, since the notes section does not show the notes. Kdammers (talk) 14:54, 30 August 2020 (UTC)
 * ✅. Hint: The edit has to be done where the note is added, not in the notes section. NJD-DE (talk) 15:03, 30 August 2020 (UTC)

MIT, Minsky and McCarthy
In the "Origin" section, the statement "While Kurtz was visiting MIT, Marvin Minsky suggested that time-sharing offered a solution" is not supported by the reference (the Time magazine article). I can't find any support that it was Minsky Kurtz met, but the Rankin reference from DTSS does state that Kurtz met John McCarthy, also working in AI at MIT at the time. I will update the article to correct this apparent error and add the reference. Cjs (talk) 03:32, 21 November 2020 (UTC)

Infobox screenshot
This "Commodore BASIC v2.0 (1977) on the Commodore 64" looks like ATARI Basic to me. Either the screenshot or the caption is wrong. Griggorio2 (talk) 17:49, 24 January 2021 (UTC)

I am adding some links
In this article (as often elsewhere) terms are used that are thought to be common knowledge by contributors, but might be unknown to newbies (and might become unknown to general public of later generations ;-), so I am adding links to apropriate articles to some that catch my eye. --Marjan Tomki SI (talk) 07:45, 30 March 2021 (UTC)

It's timeline
I want to find it's timeline 103.255.6.77 (talk) 16:39, 30 November 2021 (UTC)

"Basic" was not intended to be an acronym
I remember reading an article many, MANY, years ago, (in Byte magazine?) where the person/people who invented the Basic language mentioned that "Basic" is NOT an acronym but a proper noun - a language that was intended to be "basic" when compared to things like FORTRAN and COBOL.

At the time, (the 70's) it was the vogue for programming languages to be acronyms - FORTRAN, COBOL, APL, LISP, etc. - and people kept asking what "Basic" was an acronym for - and the folks at Dartmouth kept saying "It's not an acronym!" until someone decided to make it an acronym. The existing acronym has nothing to do with the origins of the language or its original name.

Unfortunately, I read this many years ago and I have not found a citation for this, but I can assure you it's gospel truth. Jharris1993 (talk) 16:20, 14 March 2022 (UTC)

MAT statements
The article mentions the MAT INPUT statement. I can recall at university, in 1973, there was an HP calculator that supported this. It also had a MAT PRINT function, that would print out the array. We used it to generate and then print out 3 X 3 magic squares. Wow, that was nearly 50 years ago. 2001:8003:E41C:1C01:8416:B98E:59:E8A8 (talk) 11:52, 18 October 2022 (UTC)

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Talk:BASIC