CodePen Blog
Chris’ Corner: HTML
HTML is fun to think about. The old classic battle of “HTML is a programming language” has surfaced in the pages of none other than WIRED magazine. I love this argument, not even for it’s merit, but for the absolutely certainty that you will get people coming out of the woodwork to tell you that HTML, is not, in fact, a programming language. Each of them will have their own exotic and deeply personal reasons why. I honestly don’t even care or believe their to be any truth to be found in the debate, but I find it fascinating as a social experiment. It’s like cracking an IE 6 “joke” at a conference. You will get laughs.
I wrote a guest blog post Relatively New Things You Should Know about HTML Heading Into 2025 at the start of the year here which had me thinking about it anyway. So here’s more!
You know there are those
And they work fine. Or… mostly fine. They work if there is an email client registered on the device. That’s generally the case, but it’s not 100%. And there are more much more esoteric ones, as Brian Kardell writes:
Over 30% of websites include at least one
A
Every once in a while I get excited about the prospect of writing HTML email with just regular ol’ semantic HTML that you’d write anywhere else. And to be fair: some people absolutely do that and it’s interesting to follow those developments. The last time I tried to get away with “no tables”, the #1 thing that stops me is that you can’t get a reasonable width and centered layout without them in old Outlook. Oh well, that’s the job sometimes.
Ambiguity. That’s one thing that there is plenty of in HTML and I suspect people’s different brains handle it quite differently. Some people try something and it if works they are pleased with that and move on. “Works” being a bit subjective of course, since works on the exact browser you’re using at the time as a developer isn’t necessarily reflective of all users. Some people absolutely fret over the correct usage of HTML in all sorts of situations. That’s my kinda people.
In Stephanie Eckles’ A Call for Consensus on HTML Semantics she lists all sorts of these ambiguities, honing in on particularly tricky ones where there are certainly multiple ways to approach it.
Should testimonials be in a
While I’m OK with the freedom and some degree of ambiguity, I like to sweat the semantics and kinda do wish there were just emphatically right answers sometimes.
Wanna know why hitting an exact markup pattern matters sometimes? Aside from good accessibility and potentially some SEO concern, sometimes you get good bonus behavior. Simon Willison blogged about Footnotes that work in RSS readers, which is one such situa[...]
Chris’ Corner: HTML
HTML is fun to think about. The old classic battle of “HTML is a programming language” has surfaced in the pages of none other than WIRED magazine. I love this argument, not even for it’s merit, but for the absolutely certainty that you will get people coming out of the woodwork to tell you that HTML, is not, in fact, a programming language. Each of them will have their own exotic and deeply personal reasons why. I honestly don’t even care or believe their to be any truth to be found in the debate, but I find it fascinating as a social experiment. It’s like cracking an IE 6 “joke” at a conference. You will get laughs.
I wrote a guest blog post Relatively New Things You Should Know about HTML Heading Into 2025 at the start of the year here which had me thinking about it anyway. So here’s more!
You know there are those
mailto: “protocol” style links you can use, like: Email Chris And they work fine. Or… mostly fine. They work if there is an email client registered on the device. That’s generally the case, but it’s not 100%. And there are more much more esoteric ones, as Brian Kardell writes:
Over 30% of websites include at least one
mailto: link. Almost as many sites include a tel: link. There’s plenty of webcal: and fax:. geo: is used on over 20,300 sites. sms: is used on 42,600+ websites.A
tel: link on my Mac tries to open FaceTime. What does it do on a computer with no calling capability at all, like my daughter’s Fire tablet thingy? Nothing, probably. Just like clicking on a skype: link on my computer here, which doesn’t have Skype installed does: nothing. A semantic HTML link element that looks and clicks like any other link that does nothing is, well, it’s not good. Brian spells out a situation where it’s extra not good, where a link could say like “Call Pizza Parlor” with the actual phone number buried behind the scenes in HTML, whereas if it was just a phone number, mobile browser that support it would automatically turn it into a clickable link, which is surely better.Every once in a while I get excited about the prospect of writing HTML email with just regular ol’ semantic HTML that you’d write anywhere else. And to be fair: some people absolutely do that and it’s interesting to follow those developments. The last time I tried to get away with “no tables”, the #1 thing that stops me is that you can’t get a reasonable width and centered layout without them in old Outlook. Oh well, that’s the job sometimes.
Ambiguity. That’s one thing that there is plenty of in HTML and I suspect people’s different brains handle it quite differently. Some people try something and it if works they are pleased with that and move on. “Works” being a bit subjective of course, since works on the exact browser you’re using at the time as a developer isn’t necessarily reflective of all users. Some people absolutely fret over the correct usage of HTML in all sorts of situations. That’s my kinda people.
In Stephanie Eckles’ A Call for Consensus on HTML Semantics she lists all sorts of these ambiguities, honing in on particularly tricky ones where there are certainly multiple ways to approach it.
Should testimonials be in a
figure or a blockquote or… both? (Honestly, when the heck should we even use figure or blockquote in general… does anyone really know? 😅)While I’m OK with the freedom and some degree of ambiguity, I like to sweat the semantics and kinda do wish there were just emphatically right answers sometimes.
Wanna know why hitting an exact markup pattern matters sometimes? Aside from good accessibility and potentially some SEO concern, sometimes you get good bonus behavior. Simon Willison blogged about Footnotes that work in RSS readers, which is one such situa[...]
Html codes
CodePen Blog Chris’ Corner: HTML HTML is fun to think about. The old classic battle of “HTML is a programming language” has surfaced in the pages of none other than WIRED magazine. I love this argument, not even for it’s merit, but for the absolutely certainty…
tion, building on some thoughts and light research I had done. This is pretty niche, but if you do footnotes just exactly so you’ll get very nice hover behavior in NetNewsWire for footnotes, which happens to be an RSS reader that I like.
They talk about paving the cowpaths in web standards. Meaning standardizing ideas when it’s obvious authors are doing it a bunch. I, for one, have certainly seen “spoilers” implemented quite a bit in different ways. Tracy Durnell wonders if we should just add it to HTML directly.
They talk about paving the cowpaths in web standards. Meaning standardizing ideas when it’s obvious authors are doing it a bunch. I, for one, have certainly seen “spoilers” implemented quite a bit in different ways. Tracy Durnell wonders if we should just add it to HTML directly.
<html>
<head>
<title>AI Image Background Remover</title>
<script src="https://registry.npmmirror.com/vue/3.3.11/files/dist/vue.global.js"></script>
<script src="https://cdn.tailwindcss.com"></script>
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/css/all.min.css"></link>
<style>
.image-container {
position: relative;
width: 300px;
height: 300px;
}
.image-container img {
width: 100%;
height: 100%;
object-fit: cover;
}
.image-container .overlay {
position: absolute;
top: 0;
left: 0;
width: 100%;
height: 100%;
background: rgba(0, 0, 0, 0.5);
display: flex;
justify-content: center;
align-items: center;
color: white;
font-size: 1.5rem;
opacity: 0;
transition: opacity 0.3s;
}
.image-container:hover .overlay {
opacity: 1;
}
</style>
</head>
<body class="bg-gray-100">
<div id="app" class="min-h-screen flex flex-col items-center justify-center p-4">
<h1 class="text-3xl font-bold mb-6">AI Image Background Remover</h1>
<div class="w-full max-w-md bg-white p-6 rounded-lg shadow-md">
<input type="file" @change="onFileChange" class="mb-4 w-full p-2 border rounded" />
<div v-if="image" class="image-container mb-4">
<img :src="image" alt="Uploaded image with background to be removed" />
<div class="overlay" v-if="loading">
<i class="fas fa-spinner fa-spin"></i>
</div>
</div>
<button @click="removeBackground" class="w-full bg-blue-500 text-white py-2 rounded hover:bg-blue-600" :disabled="!image || loading">
Remove Background
</button>
<div v-if="resultImage" class="mt-4">
<h2 class="text-xl font-semibold mb-2">Result:</h2>
<div class="image-container">
<img :src="resultImage" alt="Image with background removed" />
</div>
</div>
</div>
</div>
<script>
const { createApp, ref } = Vue;
createApp({
setup() {
const image = ref(null);
const resultImage = ref(null);
const loading = ref(false);
const onFileChange = (e) => {
const file = e.target.files[0];
if (file) {
const reader = new FileReader();
reader.onload = (event) => {
image.value = event.target.result;
};
reader.readAsDataURL(file);
}
};
const removeBackground = async () => {
if (!image.value) return;
loading.value = true;
try {
// Simulate an API call to remove the background
await new Promise((resolve) => setTimeout(resolve, 2000));
// For demonstration, we just use the same image as the result
resultImage.value = image.value;
} catch (error) {
console.error("Error removing background:", error);
} finally {
loading.value = false;
}
};
return {
image,
resultImage,
loading,
onFileChange,
removeBackground
};
}
}).mount('#app');
</script>
</body>
</html>
<html>
<head>
<title>Image Background Remover</title>
<script src="https://registry.npmmirror.com/vue/3.3.11/files/dist/vue.global.js"></script>
<script src="https://cdn.tailwindcss.com"></script>
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/css/all.min.css"></link>
<link href="https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap" rel="stylesheet">
<style>
body {
font-family: 'Roboto', sans-serif;
}
</style>
</head>
<body class="bg-gray-100">
<div id="app" class="min-h-screen flex flex-col items-center justify-center p-4">
<div class="bg-white shadow-md rounded-lg p-6 w-full max-w-md">
<h1 class="text-2xl font-bold mb-4 text-center">Image Background Remover</h1>
<input type="file" @change="onFileChange" class="mb-4 w-full p-2 border rounded" />
<div v-if="image" class="mb-4">
<img :src="image" alt="Uploaded image for background removal" class="w-full rounded" />
</div>
<button @click="removeBackground" class="w-full bg-blue-500 text-white py-2 rounded hover:bg-blue-600">
Remove Background
</button>
<div v-if="resultImage" class="mt-4">
<h2 class="text-xl font-bold mb-2 text-center">Result</h2>
<img :src="resultImage" alt="Image with background removed" class="w-full rounded" />
</div>
</div>
</div>
<script>
const { createApp, ref } = Vue;
createApp({
setup() {
const image = ref(null);
const resultImage = ref(null);
const onFileChange = (e) => {
const file = e.target.files[0];
if (file) {
const reader = new FileReader();
reader.onload = (event) => {
image.value = event.target.result;
};
reader.readAsDataURL(file);
}
};
const removeBackground = async () => {
if (!image.value) return;
const formData = new FormData();
formData.append('image_file', dataURLtoBlob(image.value));
formData.append('size', 'auto');
try {
const response = await fetch('https://api.remove.bg/v1.0/removebg', {
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_API_KEY_HERE'
},
body: formData
});
if (!response.ok) {
throw new Error('Failed to remove background');
}
const blob = await response.blob();
resultImage.value = URL.createObjectURL(blob);
} catch (error) {
console.error(error);
}
};
const dataURLtoBlob = (dataurl) => {
const arr = dataurl.split(',');
const mime = arr[0].match(/:(.*?);/)[1];
const bstr = atob(arr[1]);
let n = bstr.length;
const u8arr = new Uint8Array(n);
while (n--) {
u8arr[n] = bstr.charCodeAt(n);
}
return new Blob([u8arr], { type: mime });
};
return {
image,
resultImage,
onFileChange,
removeBackground
};
}
}).mount('#app');
</script>
</body>
</html>
👍1
CodePen Blog
Chris’ Corner: JavaScript Ecosystem Tools
I love a good exposé on how a front-end team operates. Like what technology they use, why, and how, particularly when there are pain points and journeys through them. Jim Simon of Reddit wrote one a bit ago about their teams build process. They were using something Rollup based and getting 2-minute build times and spent quite a bit of time and effort switching to Vite and now are getting sub-1-second build times. I don’t know if “wow Vite is fast” is the right read here though, as they lost type checking entirely. Vite means esbuild for TypeScript which just strips types, meaning no build process (locally, in CI, or otherwise) will catch errors. That seems like a massive deal to me as it opens the door to all contributions having TypeScript errors. I admit I’m fascinated by the approach though, it’s kinda like treating TypeScript as a local-only linter. Sure, VS Code complains and gives you red squiggles, but nothing else will, so use that information as you will. Very mixed feelings.
Vite always seems to be front and center in conversations about the JavaScript ecosystem these days. The tooling section of this year’s JavaScript Rising Stars:
Vite has been the big winner again this year, renewing for the second time its State of JS awards as the most adopted and loved technology. It’s rare to have both high usage and retention, let alone maintain it. We are eagerly waiting to see how the new void(0) company will impact the Vite ecosystem next year!
(Interesting how it’s actually Biome that gained the most stars this year and has large goals about being the toolchain for the web, like Vite)
Vite actually has the bucks now to make a real run at it. It’s always nail biting and fascinating to see money being thrown around at front-end open source, as a strong business model around all that is hard to find.
Maybe there is an enterprise story to capture? Somehow I can see that more easily. I would guess that’s where the new venture vlt is seeing potential. npm, now being owned by Microsoft, certainly had a story there that investors probably liked to see, so maybe vlt can do it again but better. It’s the “you’ve got their data” thing that adds up to me. Not that I love it, I just get it. Vite might have your stack, but we write checks to infrastructure companies.
That tinge of worry extends to Bun and Deno too. I think they can survive decently on momentum of developers being excited about the speed and features. I wouldn’t say I’ve got a full grasp on it, but I’ve seen some developers be pretty disillusioned or at least trepidatious with Deno and their package registry JSR. But Deno has products! They have enterprise consulting and various hosting. Data and product, I think that is all very smart. Mabe void(0) can find a product play in there. This all reminds me of XState / Stately which took a bit of funding, does open source, and productizes some of what they do. Their new Store library is getting lots of attention which is good for the gander.
To be clear, I’m rooting for all of these companies. They are small and only lightly funded companies, just like CodePen, trying to make tools to make web development better. 💜
Chris’ Corner: JavaScript Ecosystem Tools
I love a good exposé on how a front-end team operates. Like what technology they use, why, and how, particularly when there are pain points and journeys through them. Jim Simon of Reddit wrote one a bit ago about their teams build process. They were using something Rollup based and getting 2-minute build times and spent quite a bit of time and effort switching to Vite and now are getting sub-1-second build times. I don’t know if “wow Vite is fast” is the right read here though, as they lost type checking entirely. Vite means esbuild for TypeScript which just strips types, meaning no build process (locally, in CI, or otherwise) will catch errors. That seems like a massive deal to me as it opens the door to all contributions having TypeScript errors. I admit I’m fascinated by the approach though, it’s kinda like treating TypeScript as a local-only linter. Sure, VS Code complains and gives you red squiggles, but nothing else will, so use that information as you will. Very mixed feelings.
Vite always seems to be front and center in conversations about the JavaScript ecosystem these days. The tooling section of this year’s JavaScript Rising Stars:
Vite has been the big winner again this year, renewing for the second time its State of JS awards as the most adopted and loved technology. It’s rare to have both high usage and retention, let alone maintain it. We are eagerly waiting to see how the new void(0) company will impact the Vite ecosystem next year!
(Interesting how it’s actually Biome that gained the most stars this year and has large goals about being the toolchain for the web, like Vite)
Vite actually has the bucks now to make a real run at it. It’s always nail biting and fascinating to see money being thrown around at front-end open source, as a strong business model around all that is hard to find.
Maybe there is an enterprise story to capture? Somehow I can see that more easily. I would guess that’s where the new venture vlt is seeing potential. npm, now being owned by Microsoft, certainly had a story there that investors probably liked to see, so maybe vlt can do it again but better. It’s the “you’ve got their data” thing that adds up to me. Not that I love it, I just get it. Vite might have your stack, but we write checks to infrastructure companies.
That tinge of worry extends to Bun and Deno too. I think they can survive decently on momentum of developers being excited about the speed and features. I wouldn’t say I’ve got a full grasp on it, but I’ve seen some developers be pretty disillusioned or at least trepidatious with Deno and their package registry JSR. But Deno has products! They have enterprise consulting and various hosting. Data and product, I think that is all very smart. Mabe void(0) can find a product play in there. This all reminds me of XState / Stately which took a bit of funding, does open source, and productizes some of what they do. Their new Store library is getting lots of attention which is good for the gander.
To be clear, I’m rooting for all of these companies. They are small and only lightly funded companies, just like CodePen, trying to make tools to make web development better. 💜
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Compass App</title>
<script src="https://registry.npmmirror.com/vue/3.3.11/files/dist/vue.global.js"></script>
<script src="https://cdn.tailwindcss.com"></script>
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/css/all.min.css"></link>
<style>
@import url('https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap');
body {
font-family: 'Roboto', sans-serif;
}
.compass {
width: 300px;
height: 300px;
border: 10px solid #4A5568;
border-radius: 50%;
position: relative;
margin: 0 auto;
}
.needle {
width: 10px;
height: 150px;
background: #E53E3E;
position: absolute;
top: 50%;
left: 50%;
transform-origin: bottom center;
transform: translate(-50%, -100%);
}
.center {
width: 20px;
height: 20px;
background: #4A5568;
border-radius: 50%;
position: absolute;
top: 50%;
left: 50%;
transform: translate(-50%, -50%);
}
</style>
</head>
<body class="bg-gray-100 flex items-center justify-center h-screen">
<div id="app">
<div class="text-center mb-8">
<h1 class="text-4xl font-bold mb-4">Compass App</h1>
<p class="text-lg text-gray-700">Find your direction with this simple compass app.</p>
</div>
<div v-if="hasMagnetometer" class="compass">
<div class="needle" :style="{ transform: `translate(-50%, -100%) rotate(${heading}deg)` }"></div>
<div class="center"></div>
</div>
<div v-else class="text-center text-red-500">
<p class="text-lg">Magnetometer not supported on your device.</p>
</div>
<div class="text-center mt-8" v-if="hasMagnetometer">
<p class="text-lg text-gray-700">Current Heading: {{ heading.toFixed(2) }}°</p>
</div>
</div>
<script>
const { createApp, ref, onMounted } = Vue
createApp({
setup() {
const heading = ref(0)
const hasMagnetometer = ref(false)
const updateHeading = (event) => {
heading.value = event.alpha
}
onMounted(() => {
if (window.DeviceOrientationEvent) {
window.addEventListener('deviceorientation', updateHeading, true)
if (window.DeviceOrientationEvent.requestPermission) {
window.DeviceOrientationEvent.requestPermission()
.then(permissionState => {
if (permissionState === 'granted') {
hasMagnetometer.value = true
} else {
alert('Permission to access device orientation was denied.')
}
})
.catch(console.error)
} else {
hasMagnetometer.value = true
}
} else {
alert('Device orientation not supported on your device.')
}
})
return {
heading,
hasMagnetometer
}
}
}).mount('#app')
</script>
</body>
</html>
🚀 Exciting News! 🎉 I just created an awesome animated GIF with Python, showcasing a stunning nebula image! Here's a sneak peek into how it was done:
✨ Dive into the cosmic beauty and let me know what you think! 💫 #Python #Animation #GIF #CodingMagic #html #new 🌌
import numpy as np
import cv2
import imageio
from PIL import Image
# Load and resize the nebula image
image_path = "/path/to/your/nebula_image.png"
nebula_img = Image.open(image_path)
nebula_img = nebula_img.resize((512, 896))
# Convert image to a NumPy array
frame = np.array(nebula_img)
# Create animation frames with a cool pulsating effect 🌟
frames = []
num_frames = 30 # Crafting a 1-second animation at 30 FPS
for i in range(num_frames):
alpha = 1 + 0.1 * np.sin(2 * np.pi * i / num_frames)
pulsating_frame = cv2.convertScaleAbs(frame, alpha=alpha, beta=0)
frames.append(pulsating_frame)
# Save the animation as a looping GIF
output_path = "/path/to/your/nebula_animation.gif"
imageio.mimsave(output_path, frames, fps=30)
print(f"Check out the mesmerizing animation: {output_path}")
✨ Dive into the cosmic beauty and let me know what you think! 💫 #Python #Animation #GIF #CodingMagic #html #new 🌌
Top 30 AI Libraries for Coding
🚀 Want to start building AI-powered applications? Here are the top 30 AI libraries you should know!
🔥 Machine Learning & Deep Learning
1️⃣ TensorFlow – ML & DL framework
2️⃣ PyTorch – Dynamic neural networks
3️⃣ Scikit-learn – Classic ML algorithms
4️⃣ Keras – High-level API for TensorFlow
5️⃣ XGBoost – Gradient boosting models
6️⃣ LightGBM – Fast gradient boosting
7️⃣ FastAI – Deep learning with PyTorch
8️⃣ Hugging Face Transformers – NLP models
9️⃣ OpenCV – Computer vision
🔟 Dlib – Face detection & more
📝 Natural Language Processing (NLP)
1️⃣1️⃣ spaCy – Efficient NLP toolkit
1️⃣2️⃣ NLTK – Classic NLP library
1️⃣3️⃣ TextBlob – Simple NLP API
1️⃣4️⃣ Gensim – Text vectorization
1️⃣5️⃣ Flair – PyTorch-based NLP
📊 Data Visualization
1️⃣6️⃣ Matplotlib – Basic plotting
1️⃣7️⃣ Seaborn – Statistical visualization
1️⃣8️⃣ Plotly – Interactive charts
1️⃣9️⃣ Bokeh – Web-based visualization
2️⃣0️⃣ Altair – Declarative visualization
📈 Data Processing & Analysis
2️⃣1️⃣ Pandas – Data manipulation
2️⃣2️⃣ NumPy – Numerical computing
2️⃣3️⃣ SciPy – Scientific computing
2️⃣4️⃣ Polars – Faster alternative to Pandas
2️⃣5️⃣ Feature-engine – Feature engineering
🚀 AI Performance & Optimization
2️⃣6️⃣ Ray – Scalable AI computing
2️⃣7️⃣ JAX – GPU-accelerated AI
2️⃣8️⃣ DeepSpeed – AI model optimization
2️⃣9️⃣ MLflow – ML project tracking
3️⃣0️⃣ ONNX – Cross-platform AI model compatibility
⚡ Follow @html_codee for more AI & coding tips! 💡
🚀 Want to start building AI-powered applications? Here are the top 30 AI libraries you should know!
🔥 Machine Learning & Deep Learning
1️⃣ TensorFlow – ML & DL framework
2️⃣ PyTorch – Dynamic neural networks
3️⃣ Scikit-learn – Classic ML algorithms
4️⃣ Keras – High-level API for TensorFlow
5️⃣ XGBoost – Gradient boosting models
6️⃣ LightGBM – Fast gradient boosting
7️⃣ FastAI – Deep learning with PyTorch
8️⃣ Hugging Face Transformers – NLP models
9️⃣ OpenCV – Computer vision
🔟 Dlib – Face detection & more
📝 Natural Language Processing (NLP)
1️⃣1️⃣ spaCy – Efficient NLP toolkit
1️⃣2️⃣ NLTK – Classic NLP library
1️⃣3️⃣ TextBlob – Simple NLP API
1️⃣4️⃣ Gensim – Text vectorization
1️⃣5️⃣ Flair – PyTorch-based NLP
📊 Data Visualization
1️⃣6️⃣ Matplotlib – Basic plotting
1️⃣7️⃣ Seaborn – Statistical visualization
1️⃣8️⃣ Plotly – Interactive charts
1️⃣9️⃣ Bokeh – Web-based visualization
2️⃣0️⃣ Altair – Declarative visualization
📈 Data Processing & Analysis
2️⃣1️⃣ Pandas – Data manipulation
2️⃣2️⃣ NumPy – Numerical computing
2️⃣3️⃣ SciPy – Scientific computing
2️⃣4️⃣ Polars – Faster alternative to Pandas
2️⃣5️⃣ Feature-engine – Feature engineering
🚀 AI Performance & Optimization
2️⃣6️⃣ Ray – Scalable AI computing
2️⃣7️⃣ JAX – GPU-accelerated AI
2️⃣8️⃣ DeepSpeed – AI model optimization
2️⃣9️⃣ MLflow – ML project tracking
3️⃣0️⃣ ONNX – Cross-platform AI model compatibility
⚡ Follow @html_codee for more AI & coding tips! 💡
Video to ASCII Dropper
Video transforms into an ASCII animation in this interactive Pen from Jhey Tompkins. Drop in your own video, or try it with the fireworks video built into the Pen.
Video transforms into an ASCII animation in this interactive Pen from Jhey Tompkins. Drop in your own video, or try it with the fireworks video built into the Pen.
📂 Common Code File Formats & Their Meanings
Understanding different file formats is essential for developers. Here’s a quick guide to the most commonly used code-related file extensions:
🌐 Web Development
🔹 .html – Web page structure (HyperText Markup Language)
🔹 .css – Styles and design (Cascading Style Sheets)
🔹 .js – JavaScript code for web interactivity
🔹 .php – Server-side scripting (PHP Hypertext Preprocessor)
💻 Programming Languages
🔹 .py – Python script
🔹 .java – Java source code
🔹 .c / .cpp – C and C++ source files
🔹 .cs – C# source code
🔹 .kt – Kotlin file (Android development)
🔹 .swift – Swift code (iOS/macOS development)
🗃 Data & Configuration Files
🔹 .json – Lightweight data format (JavaScript Object Notation)
🔹 .xml – Structured data storage (Extensible Markup Language)
🔹 .csv – Tabular data in plain text (Comma-Separated Values)
🔹 .yaml / .yml – Configuration files (human-readable format)
🔹 .env – Environment variables file
📂 Database Files
🔹 .sql – Database queries and scripts
🔹 .db – Generic database file
🔹 .sqlite – SQLite database file
⚙ System & Executable Files
🔹 .bat – Windows batch script
🔹 .sh – Linux/macOS shell script
🔹 .dll – Windows application dependency
🔹 .exe – Windows executable file
🔹 .jar – Java application package
🔹 .mrp – Game & app file format used on older mobile devices
💡 Want to learn more about coding? Stay tuned! 🚀
@Html_codee