# rss_item

guid: tag:blog.golang.org,2013:blog.golang.org/survey2024-h2-results
title: Go Developer Survey 2024 H2 Results
author: Alice Merrick
url: https://go.dev/blog/survey2024-h2-results
feedurl: https://go.dev/blog/feed.atom
content_mime_type: text/html
content:
<div id="blog"><div id="content">
  <div id="content">

    <div class="Article" data-slug="/blog/survey2024-h2-results">
    
    <h1 class="small"><a href="/blog/">The Go Blog</a></h1>
    

    <h1>Go Developer Survey 2024 H2 Results</h1>
      
      <p class="author">
      Alice Merrick<br>
      20 December 2024
      </p>
      
      <style type="text/css" scoped>
  .chart {
    margin-left: 1.5rem;
    margin-right: 1.5rem;
    width: 800px;
  }
  blockquote p {
    color: var(--color-text-subtle) !important;
  }

  .quote_source {
    font-style: italic;
  }

  @media (prefers-color-scheme: dark) {
    .chart {
      border-radius: 8px;
    }
  }
</style>
<h2 id="background">Background</h2>
<p>Go was designed with a focus on developer experience, and we deeply value the
feedback we receive through proposals, issues, and community interactions.
However, these channels often represent the voices of our most experienced or
engaged users, a small subset of the broader Go community. To ensure we&rsquo;re
serving developers of all skill levels, including those who may not have strong
opinions on language design, we conduct this survey once or twice a year to
gather systematic feedback and quantitative evidence. This inclusive approach
allows us to hear from a wider range of Go developers, providing valuable
insights into how Go is used across different contexts and experience levels.
Your participation is critical in informing our decisions about language changes
and resource allocation, ultimately shaping the future of Go. Thank you to
everyone who contributed, and we strongly encourage your continued participation
in future surveys. Your experience matters to us.</p>
<p>This post shares the results of our most recent Go Developer Survey, conducted
from September 9–23, 2024. We recruited participants from the Go blog and
through randomized prompts in the <a href="https://code.visualstudio.com/" rel="noreferrer" target="_blank">VS Code</a> Go
plug-in and <a href="https://www.jetbrains.com/go/" rel="noreferrer" target="_blank">GoLand IDE</a>, allowing us to recruit
a more representative sample of Go developers. We received a total of 4,156
responses. A huge thank you to all those who contributed to making this
possible.</p>
<p>Along with capturing sentiments and challenges around using Go and Go tooling,
our primary focus areas for this survey were on uncovering sources of toil,
challenges to performing best practices, and how developers are using AI
assistance.</p>
<h2 id="highlights">Highlights</h2>
<ul>
<li><strong>Developer sentiment towards Go remains extremely positive</strong>, with 93% of
survey respondents saying they felt satisfied while working with Go during the
prior year.</li>
<li><strong>Ease of deployment and an easy to use API/SDK</strong> were respondents’ favorite
things about using Go on the top three cloud providers. First-class Go support
is critical to keeping up with developer expectations.</li>
<li>70% of respondents were using AI assistants when developing with Go. The most
common uses were <strong>LLM-based code completion</strong>, writing tests, generating Go
code from natural language descriptions, and brainstorming. There was a
significant discrepancy between what respondents said they wanted to use AI
for last year, and what they currently use AI for.</li>
<li>The biggest challenge for teams using Go was <strong>maintaining consistent coding
standards</strong> across their codebase. This was often due to team members having
different levels of Go experience and coming from different programming
backgrounds, leading to inconsistencies in coding style and adoption of
non-idiomatic patterns.</li>
</ul>
<h2 id="contents">Contents</h2>
<ul>
<li><a href="#sentiment">Overall satisfaction</a></li>
<li><a href="#devenv">Development environments and tools</a></li>
<li><a href="#cloud">Go in the clouds</a></li>
<li><a href="#ai-assistance">AI assistance</a></li>
<li><a href="#team-challenges">Challenges for teams using Go</a></li>
<li><a href="#simd">Single Instruction, Multiple Data (SIMD)</a></li>
<li><a href="#demographics">Demographics</a></li>
<li><a href="#firmographics">Firmographics</a></li>
<li><a href="#methodology">Methodology</a></li>
<li><a href="#how-to-read-these-results">How to read these results</a></li>
<li><a href="#closing">Closing</a></li>
</ul>
<h3 id="sentiment">Overall satisfaction</h3>
<p>Overall satisfaction remains high in the survey with 93% of respondents saying
they were somewhat or very satisfied with Go during the last year. Although the
exact percentages fluctuate slightly from cycle to cycle, we do not see any
statistically significant differences from our <a href="/blog/survey2023-h2-results">2023
H2</a> or <a href="/blog/survey2024-h1-results">2024 H1
</a>Surveys when the satisfaction rate
was 90% and 93%, respectively.</p>
<p><img src="survey2024h2/csat.svg" alt="Chart of developer satisfaction with Go"
class="chart" /></p>
<p>The open comments we received on the survey continue to highlight what
developers like most about using Go, for example, its simplicity, the Go
toolchain, and its promise of backwards compatibility:</p>
<p><em>“I am a programming languages enjoyer (C-like) and I always come back to Go for
its simplicity, fast compilation and robust toolchain. Keep it up!”</em></p>
<p><em>“Thank you for creating Go! It is my favorite language, because it is pretty
minimal, the development cycle has rapid build-test cycles, and when using a
random open source project written in Go, there is a good chance that it will
work, even 10 years after. I love the 1.0 compatibility guarantee.”</em></p>
<h3 id="devenv">Development environments and tools</h3>
<h4 id="developer-os">Developer OS</h4>
<p>Consistent with previous years, most survey respondents develop with Go on Linux
(61%) and macOS (59%) systems. Historically, the proportion of Linux and macOS
users has been very close, and we didn’t see any significant changes from the
last survey. The randomly sampled groups from JetBrains and VS Code were more
likely (33% and 36%, respectively) to develop on Windows than the self-selected
group (16%).</p>
<p><img src="survey2024h2/os_dev.svg" alt="Chart of operating systems respondents
use when developing Go software" class="chart" /> <img
src="survey2024h2/os_dev_src.svg" alt="Chart of operating systems respondents
use when developing Go software, split by difference sample sources"
class="chart" /></p>
<h4 id="deployment-environments">Deployment environments</h4>
<p>Given the prevalence of Go for cloud development and containerized workloads,
it’s no surprise that Go developers primarily deploy to Linux environments
(96%).</p>
<p><img src="survey2024h2/os_deploy.svg" alt="Chart of operating systems
respondents deploy to when developing Go software" class="chart" /></p>
<p>We included several questions to understand what architectures respondents are
deploying to when deploying to Linux, Windows or WebAssembly. The x86-64 /
AMD64 architecture was by far the most popular choice for those deploying to
both Linux (92%) and Windows (97%). ARM64 was second at 49% for Linux and 21%
for Windows.</p>
<p><img src="survey2024h2/arch_linux.svg" alt="Linux architecture usage"
class="chart" /> <img src="survey2024h2/arch_win.svg" alt="Windows architecture
usage" class="chart" /></p>
<p>Not many respondents deployed to Web Assembly (only about 4% of overall
respondents), but 73% that do said they deploy to JS and 48% to WASI Preview 1.</p>
<p><img src="survey2024h2/arch_wa.svg" alt="Web assembly architecture usage"
class="chart" /></p>
<h4 id="editor-awareness-and-preferences">Editor awareness and preferences</h4>
<p>We introduced a new question on this survey to assess awareness and usage of
popular editors for Go. When interpreting these results, keep in mind that 34%
of respondents came to the survey from VS Code and 9% of respondents came from
GoLand, so it is more likely for them to use those editors regularly.</p>
<p>VS Code was the most widely used editor, with 66% of respondents using it
regularly, and GoLand was the second most used at 35%. Almost all respondents
had heard of both VS Code and GoLand, but respondents were much more likely to
have at least tried VS Code. Interestingly, 33% of respondents said they
regularly use 2 or more editors. They may use different editors for different
tasks or environments, such as using Emacs or Vim via SSH, where IDEs aren’t
available.</p>
<p><img src="survey2024h2/editor_aware.svg" alt="Level of familiarity with each
editor" class="chart" /></p>
<p>We also asked a question about editor preference, the same as we have asked on
previous surveys. Because our randomly sampled populations were recruited from
within VS Code or GoLand, they are strongly biased towards preferring those
editors. To avoid skewing the results, we show the data for the most preferred
editor here from the self-selected group only. 38% preferred VS Code and 35%
preferred GoLand. This is a notable difference from the last survey in H1, when
43% preferred VS Code and 33% preferred GoLand. A possible explanation could be
in how respondents were recruited this year. This year the VS Code notification
began inviting developers to take the survey before the Go blog entry was
posted, so a larger proportion of respondents came from the VS Code prompt this
year who might have otherwise come from the blog post. Because we only show the
self-selected respondents in this chart, data from respondents from the VS Code
prompt data are not represented here. Another contributing factor could be the
slight increase in those who prefer &ldquo;Other&rdquo; (4%). The write-in responses suggest
there is increased interest in editors like <a href="https://zed.dev/" rel="noreferrer" target="_blank">Zed</a>, which made
up 43% of the write-in responses.</p>
<p><img src="survey2024h2/editor.svg" alt="Code editors respondents most prefer to
use with Go" class="chart" /></p>
<h4 id="code-analysis-tools">Code analysis tools</h4>
<p>The most popular code analysis tool was <code>gopls</code>, which was knowingly used by 65%
of respondents. Because <code>gopls</code> is used under-the-hood by default in VS Code,
this is likely an undercount. Following closely behind, <code>golangci-lint</code> was used
by 57% of respondents, and <code>staticcheck</code> was used by 34% of respondents. A much
smaller proportion used custom or other tools, which suggests that most
respondents prefer common established tools over custom solutions. Only 10% of
respondents indicated they don&rsquo;t use any code analysis tools.</p>
<p><img src="survey2024h2/code_analysis.svg" alt="Code analysis tools respondents
use with Go" class="chart" /></p>
<h4 id="cloud">Go in the Clouds</h4>
<p>Go is a popular language for modern cloud-based development, so we typically
include survey questions to help us understand which cloud platforms and
services Go developers are using. In this cycle, we sought to learn about
preferences and experiences of Go developers across cloud providers, with a
particular focus on the largest cloud providers: Amazon Web Services (AWS),
Microsoft Azure, and Google Cloud. We also included an additional option for
“Bare Metal Servers” for those who deploy to servers without virtualization.</p>
<p>Similar to previous years, almost half of respondents (50%) deploy Go programs
to Amazon Web Services. AWS is followed by self-owned or company-owned servers
(37%), and Google Cloud (30%). Respondents who work at large organizations are a
little more likely to deploy to self-owned or company-owned servers (48%) than
those who work at small-to-medium organizations (34%). They‘re also a little
more likely to deploy to Microsoft Azure (25%) than small-to-medium
organizations (12%).</p>
<p><img src="survey2024h2/cloud_platform.svg" alt="Cloud providers where
respondents deploy Go software" class="chart" /></p>
<p>The most commonly used cloud services were AWS Elastic Kubernetes Service (41%),
AWS EC2 (39%), and Google Cloud GKE (29%). Although we’ve seen Kubernetes usage
increase over time, this is the first time we’ve seen EKS become more widely
used than EC2. Overall, Kubernetes offerings were the most popular services for
AWS, Google Cloud, and Azure, followed by VMs and then Serverless offerings.
Go&rsquo;s strengths in containerization and microservices development naturally align
with the rising popularity of Kubernetes, as it provides an efficient and
scalable platform for deploying and managing these types of applications.</p>
<p><img src="survey2024h2/cloud_service.svg" alt="Cloud platforms where respondents
deploy Go software" class="chart" /></p>
<p>We asked a followup question to respondents who deployed Go code to the top
three cloud providers, Amazon Web Services, Google Cloud, and Microsoft Azure on
what they like most about deploying Go code to each cloud. The most popular
response across different providers was actually Go&rsquo;s performance and language
features rather than something about the cloud provider.</p>
<p>Other common reasons were:</p>
<ul>
<li>Familiarity with the given cloud provider compared to other clouds</li>
<li>Ease of deployment of Go applications on the given cloud provider</li>
<li>The cloud provider&rsquo;s API/SDK for Go is easy to use</li>
<li>The API/SDK is well documented</li>
</ul>
<p>Other than familiarity, the top favorite things highlight the importance of
having first class support for Go to keep up with developer expectations.</p>
<p>It was also fairly common for respondents to say they don&rsquo;t have a favorite
thing about their cloud provider. From a previous version of the survey that
involved write-in responses, this often meant that they did not interact
directly with the Cloud. In particular, respondents who use Microsoft Azure were
much more likely to say that “Nothing” was their favorite thing (51%) compared
to AWS (27%) or Google Cloud (30%).</p>
<p><img src="survey2024h2/cloud_fave_all.svg" alt= "What respondents liked most
about each of the top 3 Clouds" class="chart" /></p>
<h3 id="ai-assistance">AI assistance</h3>
<p>The Go team hypothesizes that AI assistance has the potential to alleviate
developers from tedious and repetitive tasks, allowing them to focus on more
creative and fulfilling aspects of their work. To gain insights into areas where
AI assistance could be most beneficial, we included a section in our survey to
identify common developer toil.</p>
<p>The majority of respondents (70%) are using AI assistants when developing with
Go. The most common usage of AI assistants was in LLM-based code completion
(35%). Other common responses were writing tests (29%), generating Go code from
a natural language description (27%), and brainstorming ideas (25%). There was
also a sizable minority (30%) of respondents who had not used any LLM for
assistance in the last month.</p>
<p><img src="survey2024h2/ai_assist_tasks.svg" alt= "Most common tasks used with AI
assistance" class="chart" /></p>
<p>Some of these results stood out when compared to findings from our 2023 H2
survey, where we asked respondents for the top 5 use cases they would like to
see AI/ML support Go developers. Although a couple new responses were introduced
in the current survey, we can still do a rough comparison between what
respondents said they wanted AI support for, and what their actual usage was
like. In that previous survey, writing tests was the most desired use case
(49%). In our latest 2024 H2 survey, about 29% of respondents had used AI
assistants for this in the last month. This suggests that current offerings are
not meeting developer needs for writing tests. Similarly, in 2023, 47%
respondents said they would like suggestions for best practices while coding,
while only 14% a year later said they are using AI assistance for this use case.
46% said they wanted help catching common mistakes while coding, and only 13%
said they were using AI assistance for this. This could indicate that current AI
assistants are not well-equipped for these kinds of tasks, or they&rsquo;re not well
integrated into developer workflows or tooling.</p>
<p>It was also surprising to see such high usage of AI for generating Go code from
natural language and brainstorming, since the previous survey didn&rsquo;t indicate
these as highly desired use cases. There could be a number of explanations for
these differences. While previous respondents might not have explicitly <em>wanted</em>
AI for code generation or brainstorming initially, they might be gravitating
towards these uses because they align with the current strengths of generative
AI—natural language processing and creative text generation. We should also keep
in mind that people<a href="https://www.nngroup.com/articles/first-rule-of-usability-dont-listen-to-users/" rel="noreferrer" target="_blank"> are not necessarily the best predictors of their own
behavior</a>.</p>
<p><img src="survey2024h2/ai_assist_tasks_yoy.svg" alt= "Tasks used AI assistance
in 2024 compared to those wanted in 2023" class="chart" /></p>
<p>We also saw some notable differences in how different groups responded to this
question. Respondents at small to medium sized organizations were a little more
likely to have used LLMs (75%) compared to those at large organizations (66%).
There could be a number of reasons why, for example, larger organizations may
have stricter security and compliance requirements and concerns about the
security of LLM coding assistants, the potential for data leakage, or compliance
with industry-specific regulations. They also may have already invested in
other developer tools and practices that already provide similar benefits to
developer productivity.</p>
<p><img src="survey2024h2/ai_assist_tasks_org.svg" alt= "Most common tasks used
with AI assistance by org size" class="chart" /></p>
<p>Go developers with less than 2 years of experience were more likely to use AI
assistants (75%) compared to Go developers with 5+ years of experience (67%).
Less experienced Go developers were also more likely to use them for more tasks,
on average 3.50. Although all experience levels tended to use LLM-based code
completion, less experienced Go developers were more likely to use Go for more
tasks related to learning and debugging, such as explaining what a piece of Go
code does, resolving compiler errors and debugging failures in their Go code.
This suggests that AI assistants are currently providing the greatest utility to
those who are less familiar with Go. We don&rsquo;t know how AI assistants affect
learning or getting started on a new Go project, something we want to
investigate in the future. However, all experience levels had similar rates of
satisfaction with their AI assistants, around 73%, so new Go developers are not
more satisfied with AI assistants, despite using them more often.</p>
<p><img src="survey2024h2/ai_assist_tasks_exp.svg" alt= "Most common tasks used
with AI assistance by experience with Go" class="chart" /></p>
<p>To respondents who reported using AI assistance for at least one task related to
writing Go code, we asked some follow up questions to learn more about their AI
assistant usage. The most commonly used AI assistants were ChatGPT (68%) and
GitHub Copilot (50%). When asked which AI assistant they used <em>most</em> in the last
month, ChatGPT and Copilot were about even at 36% each, so although more
respondents used ChatGPT, it wasn’t necessarily their primary assistant.
Participants were similarly satisfied with both tools (73% satisfied with
ChatGPT, vs. 78% with GitHub CoPilot). The highest satisfaction rate for any AI
assistant was Anthropic Claude, at 87%.</p>
<p><img src="survey2024h2/ai_assistants_withother.svg" alt= "Most common AI
assistants used" class="chart" /> <img src="survey2024h2/ai_primary.svg" alt=
"Most common primary AI assistants used" class="chart" /></p>
<h3 id="team-challenges">Challenges for teams using Go</h3>
<p>In this section of the survey, we wanted to understand which best practices or
tools should be better integrated into developer workflows. Our approach was to
identify common problems for teams using Go. We then asked respondents which
challenges would bring them the most benefit if they were “magically” solved for
them. (This was so that respondents would not focus on particular solutions.)
Common problems that would provide the most benefit if they were solved would be
considered candidates for improvement.</p>
<p>The most commonly reported challenges for teams were maintaining consistent coding
standards across our Go codebase (58%), identifying performance issues in a
running Go program (58%) and identifying resource usage inefficiencies in a
running Go program (57%).</p>
<p><img src="survey2024h2/dev_challenges.svg" alt= "Most common challenges for
teams" class="chart" /></p>
<p>21% of respondents said their team would benefit most from maintaining
consistent coding standards across their Go codebase. This was the most common
response, making it a good candidate to address. In a follow-up question, we got
more details as to why specifically this was so challenging.</p>
<p><img src="survey2024h2/dev_challenges_most_benefit.svg" alt= "Most benefit to
solve" class="chart" /></p>
<p>According to the write-in responses, many teams face challenges maintaining
consistent coding standards because their members have varying levels of
experience with Go and come from different programming backgrounds. This led to
inconsistencies in coding style and the adoption of non-idiomatic patterns.</p>
<p><em>“There&rsquo;s lots of polyglot engineers where I work. So the Go written is not
consistent. I do consider myself a Gopher and spend time trying to convince my
teammates what is idiomatic in Go”—Go developer with 2–4 years of experience.</em></p>
<p><em>“Most of the team members are learning Go from scratch. Coming from the
dynamically typed languages, it takes them a while to get used to the new
language. They seem to struggle maintaining the code consistency following the
Go guidelines.”—Go developer with 2–4 years of experience.</em></p>
<p>This echoes some feedback we’ve heard before about teammates who write &ldquo;Gava&rdquo; or
&ldquo;Guby&rdquo; due to their previous language experiences. Although static analysis was
a class of tool we had in mind to address this issue when we came up with this
question, we are currently exploring different ways we might address this.</p>
<h3 id="simd">Single Instruction, Multiple Data (SIMD)</h3>
<p>SIMD, or Single Instruction, Multiple Data, is a type of parallel processing
that allows a single CPU instruction to operate on multiple data points
simultaneously. This facilitates tasks involving large datasets and repetitive
operations, and is often used to optimize performance in fields like game
development, data processing, and scientific computing. In this section of the
survey we wanted to assess respondents&rsquo; needs for native SIMD support in Go.</p>
<p>The majority of respondents (89%) say that work on projects where performance
optimizations are crucial at least some of the time. 40% said they work on such
projects at least half the time. This held true across different organization
sizes and experience levels, suggesting that performance is an important issue
for most developers.</p>
<p><img src="survey2024h2/perf_freq.svg" alt= "How often respondents work on
performance critical software" class="chart" /></p>
<p>About half of respondents (54%), said they are at least a little familiar with
the concept of SIMD. Working with SIMD often requires a deeper understanding of
computer architecture and low-level programming concepts, so unsurprisingly we
find that less experienced developers were less likely to be familiar with SIMD.
Respondents with more experience and who worked on performance-crucial
applications at least half the time were the most likely to be familiar with
SIMD.</p>
<p><img src="survey2024h2/simd_fam.svg" alt= "Familiarity with SIMD" class="chart"
/></p>
<p>For those who were at least slightly familiar with SIMD, we asked some follow
-up questions to understand how respondents were affected by the absence of
native SIMD support in Go. Over a third, about 37%, said they had been impacted.
17% of respondents said they had been limited in the performance they could
achieve in their projects, 15% said they had to use another language instead of
Go to achieve their goals, and 13% said they had to use non-Go libraries when
they would have preferred to use Go libraries. Interestingly, respondents who
were negatively impacted by the absence of native SIMD support were a little
more likely to use Go for data processing and AI/ML. This suggests that adding
SIMD support could make Go a better option for these domains.</p>
<p><img src="survey2024h2/simd_impact.svg" alt= "Impacts of lack of native Go support
for SIMD" class="chart" /> <img src="survey2024h2/what_simd_impact.svg" alt=
"What impacted respondents build with Go" class="chart" /></p>
<h3 id="demographics">Demographics</h3>
<p>We ask similar demographic questions during each cycle of this survey so we can
understand how comparable the year-over-year results may be. For example, if we
saw changes in who responded to the survey in terms of Go experience, it’d be
very likely that other differences in results from prior cycles were due to this
demographic shift. We also use these questions to provide comparisons between
groups, such as satisfaction according to how long respondents have been using
Go.</p>
<p>We didn’t see any significant changes in levels of experience among respondents
during this cycle.</p>
<p><img src="survey2024h2/go_exp.svg" alt= "Experience levels of respondents"
class="chart" /></p>
<p>There are differences in the demographics of respondents according to whether
they came from The Go Blog, the VS Code extension, or GoLand. The population
who responded to survey notifications in VS Code skews toward less experience
with Go; we suspect this a reflection of VS Code’s popularity with new Go
developers, who may not be ready to invest in an IDE license while they’re still
learning. With respect to years of Go experience, the respondents randomly
selected from GoLand are more similar to our self-selected population who found
the survey through the Go Blog. Seeing consistencies between samples allows us
to more confidently generalize findings to the rest of the community.</p>
<p><img src="survey2024h2/go_exp_src.svg" alt= "Experience with Go by survey
source" class="chart" /></p>
<p>In addition to years of experience with Go, we also measured years of
professional coding experience. Our audience tends to be a pretty experienced
bunch, with 26% of respondents having 16 or more years of professional coding
experience.</p>
<p><img src="survey2024h2/dev_exp.svg" alt= "Overall levels of professional
developer experience" class="chart" /></p>
<p>The self-selected group was even more experienced than the randomly selected
groups, with 29% having 16 or more years of professional experience. This
suggests that our self-selected group is generally more experienced than our
randomly selected groups and can help explain some of the differences we see in
this group.</p>
<p><img src="survey2024h2/dev_exp_src.svg" alt= "Levels of professional developer
experience by survey source" class="chart" /></p>
<p>We found that 81% of respondents were fully employed. When we look at our
individual samples, we see a small but significant difference within our
respondents from VS Code, who are slightly more likely to be students. This
makes sense given that VS Code is free.</p>
<img src="survey2024h2/employment.svg" alt= "Employment status" class="chart" />
<img src="survey2024h2/employment_src.svg" alt= "Employment status by survey
source" class="chart" />
<p>Similar to previous years, the most common use cases for Go were API/RPC
services (75%) and command line tools (62%). More experienced Go developers
reported building a wider variety of applications in Go. This trend was
consistent across every category of app or service. We did not find any notable
differences in what respondents are building based on their organization size.
Respondents from the random VS Code and GoLand samples did not display
significant differences either.</p>
<p><img src="survey2024h2/what.svg" alt= "What respondents build with Go"
class="chart" /></p>
<h3 id="firmographics">Firmographics</h3>
<p>We heard from respondents at a variety of different organizations. About 29%
worked at large organizations with 1,001 or more employees, 25% were from
midsize organizations of 101–1,000 employees, and 43% worked at smaller
organizations with fewer than 100 employees. As in previous years, the most
common industry people work in was technology (43%) while the second most common
was financial services (13%).</p>
<p><img src="survey2024h2/org_size.svg" alt= "Organization sizes where respondents
work" class="chart" /> <img src="survey2024h2/industry.svg" alt= "Industries
respondents work in" class="chart" /></p>
<p>As in previous surveys, the most common location for survey respondents was the
United States (19%). This year we saw a significant shift in the proportion of
respondents coming from Ukraine, from 1% to 6%, making it the third most common
location for survey respondents. Because we only saw this difference among our
self-selected respondents, and not in the randomly sampled groups, this suggests
that something affected who discovered the survey, rather than a widespread
increase in Go adoption across all developers in Ukraine. Perhaps there was
increased visibility or awareness of the survey or the Go Blog among developers
in Ukraine.</p>
<p><img src="survey2024h2/location.svg" alt= "Where respondents are located"
class="chart" /></p>
<h2 id="methodology">Methodology</h2>
<p>We announce the survey primarily through the Go Blog, where it is often picked
up on various social channels like Reddit, or Hacker News. We also recruit
respondents by using the VS Code Go plugin to randomly select users to whom we show
a prompt asking if they’d like to participate in the survey. With some help from
our friends at JetBrains, we also have an additional random sample from
prompting a random subset of GoLand users to take the survey. This gave us two
sources we used to compare the self-selected respondents from our traditional
channels and help identify potential effects of <a href="https://en.wikipedia.org/wiki/Self-selection_bias" rel="noreferrer" target="_blank">self-selection
bias</a>.</p>
<p>57% of survey respondents “self-selected” to take the survey, meaning they found
it on the Go blog or other social Go channels. People who don’t follow these
channels are less likely to learn about the survey from them, and in some cases,
they respond differently than people who do closely follow them. For example,
they might be new to the Go community and not yet aware of the Go blog. About
43% of respondents were randomly sampled, meaning they responded to the survey
after seeing a prompt in VS Code (25%) or GoLand (11%). Over the period of
September 9–23, 2024, there was roughly a 10% chance users of the VS Code plugin
would have seen this prompt. The prompt in GoLand was similarly active between
September 9–20. By examining how the randomly sampled groups differ from the
self-selected responses, as well as from each other, we’re able to more
confidently generalize findings to the larger community of Go developers.</p>
<p><img src="survey2024h2/source.svg" alt="Chart of different sources of survey
respondents" class="chart" /></p>
<h4 id="how-to-read-these-results">How to read these results</h4>
<p>Throughout this report we use charts of survey responses to provide supporting
evidence for our findings. All of these charts use a similar format. The title
is the exact question that survey respondents saw. Unless otherwise noted,
questions were multiple choice and participants could only select a single
response choice; each chart’s subtitle will tell the reader if the question
allowed multiple response choices or was an open-ended text box instead of a
multiple choice question. For charts of open-ended text responses, a Go team
member read and manually categorized all of the responses. Many open-ended
questions elicited a wide variety of responses; to keep the chart sizes
reasonable, we condensed them to a maximum of the top 10-12 themes, with
additional themes all grouped under “Other”. The percentage labels shown in
charts are rounded to the nearest integer (e.g., 1.4% and 0.8% will both be
displayed as 1%), but the length of each bar and row ordering are based on the
unrounded values.</p>
<p>To help readers understand the weight of evidence underlying each finding, we
included error bars showing the 95% <a href="https://en.wikipedia.org/wiki/Confidence_interval" rel="noreferrer" target="_blank">confidence
interval</a> for responses;
narrower bars indicate increased confidence. Sometimes two or more responses
have overlapping error bars, which means the relative order of those responses
is not statistically meaningful (i.e., the responses are effectively tied). The
lower right of each chart shows the number of people whose responses are
included in the chart, in the form “n = [number of respondents]”. In cases where
we found interesting differences in responses between groups, (e.g., years of
experience, organization size, or sample source) we showed a color-coded
breakdown of the differences.</p>
<h3 id="closing">Closing</h3>
<p>Thanks for reviewing our semi-annual Go Developer Survey! And many thanks to
everyone who shared their thoughts on Go and everyone who contributed to making
this survey happen. It means the world to us and truly helps us improve Go.</p>
<p>&mdash; Alice (on behalf of the Go team at Google)</p>

    </div>

    
    <div class="Article prevnext">
    
    
      
        <p>
        
        
          
            <b>Previous article: </b><a href="/blog/protobuf-opaque">Go Protobuf: The new Opaque API</a><br>
          
        
        <b><a href="/blog/all">Blog Index</a></b>
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
      
    
    </div>
    

  </div>
</div>

<script src="/js/play.js"></script>


guid: yt:video:9JJDy8x5APM
title: Does What We Do Even Matter? - WAN Show January 31, 2025
author: Linus Tech Tips
url: https://www.youtube.com/watch?v=9JJDy8x5APM
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCXuqSBlHAE6Xw-yeJA0Tunw
enclosure_url: https://www.youtube.com/v/9JJDy8x5APM?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Say yes to every opportunity in 2025 with Vessi. Explore https://vessi.com/Wanshow to keep your feet dry and start your year with 15% off your first order.

Get a free 15-day trial of Odoo’s all-in-one business solution and see how it can make your life easier! Check it out at https://www.odoo.com/wan

Ready for a puzzle like no other? Get 15% off your first order at https://oddpieces.com/wanshow

Buy something from dbrand so they have an excuse to keep messing with Linus. Visit http://dbrand.com/WAN

Pick up a Secretlab Titan Evo Ergonomic Gaming Chair today at: https://lmg.gg/secretlabwan

Get a special deal on Private Internet Access VPN today at https://www.piavpn.com/LinusWan

Purchases made through some store links may provide some compensation to Linus Media Group.

Podcast Download: https://pdst.fm/e/chrt.fm/track/C76EG6/mgln.ai/e/94/claritaspod.com/measure/verifi.podscribe.com/rss/p/chtbl.com/track/289382/pfx.vpixl.com/j0JIg/traffic.megaphone.fm/ROOSTER8928505904.mp3?updated=1738385596
Timestamps (courtesy of NoKi1119): 
0:00 Chapters
1:00 Intro
1:30 Topic #1: RTX 5080 reviews, paper launch
2:55 Scalping, price hike, was the work on the reviews worth it?
7:31 Reviews, upgrading, upcoming 8K gaming video, Plouffe's 4090
12:48 Linus on upgrading, Luke on local LLMs, on-prem storage
14:52 1080P charts on LTT Labs, RTX 5080 video analytics
16:54 Topic #2: Major tech stock crashes due to DeepSeek
18:02 DeepSeek accused of data distilling, AI scraper bots
21:15 Utilizing local LLMs, open source & forks, interests spiking
26:58 Mac Mini & Studio, second hand RTX 3090 GPU prices
33:40 Linus on buying RTX from launch then flipping it today
35:06 GeForce NOW membership
38:21 OpenAI & efficiency, "more gaming PCs," most boring consoles
42:46 Linus on 4:2:2 encoding for streaming, ANNO 1800 on Deck
46:56 Luke's plans for open source LLMs, closing thoughts
47:33 LTTStore's new sport button-up shirt
49:37 Help make LTTStore better
50:06 Merch Messages - Fixing mistypes with mechanical keyboards?
53:05 Single thing in tech that made you feel the oldest?
58:08 Topic #3: Pebble makes a return with open source OS
1:03:06 Topic #4: Making AI scraping difficult by poisoning them
1:05:52 Topic #5: SteamOS to be used on other handhelds
1:07:28 Topic #6: Sony removes PSN requirements for some PC games
1:09:47 WAN Show played on a school's jumbotron
1:10:38 Rugby, US fields, past schools, kickball, "shuttle"
1:18:16 Vessi
1:19:21 Odoo
1:20:27 Odd Pieces
1:21:49 Merch Message - Morning routine? ft. "Big boi," Allen HS
1:27:55 Topic #7: Protonmail "politically neutral" under fire
1:29:36 Topic #8: Meta AI uses your FB messages & data, MS 365 has Copilot
1:30:24 Facebook marketplace, Linus likes the ads
1:33:15 Topic #9: Gobi cameras use proprietary cables?
1:34:48 FP's executives week, Linus's post surgery, why is WAN late?
1:35:59 Merch Mesages ft. Missing dark after dark, narcissists
1:37:38 LTT pants to go with the new shirt? ft. Prototype' "issues"
1:40:23 Does Linus still find Dennis's stickers in his house?
1:40:48 Cool tech that influenced your badminton spot?
1:43:46 Is the way Linus talks in videos on purpose?
1:45:10 If it's the 20th century, what tech would you revisit?
1:46:42 Would X86 CPUs be able to scale beyond 128 cores?
1:47:51 How come we've seen +30% performance for ARM but not X86?
1:51:18 How to restore the LTT screwdriver's black finish?
1:52:29 Should I insist on my warranty for RMA or switch brands?
1:54:26 How do you think development will evolve with AI?
1:59:48 Using rattle can for car hood painting?
2:00:48 Thoughts on companies that struggle due to misinformation?
2:04:12 Has Linus heard of Manor Lords?
2:07:22 Technology or equipment you liked that never released?
2:10:10 Would Linus replace his limbs or organs to become a cyborg?
2:14:33 Insights on logistics of huge tech releases?
2:17:21 "GTA VI will release before Linus paints his bike"
2:19:00 Advice for a takeover of a company? ft. "Review body parts"
2:22:52 Linus's bike painting update ft. Cake
2:23:52 How do you measure input latency?
2:24:55 Linus watched a bit of Louis Rossmann's video
2:26:09 "Intentionally messaged Steve's wrong number"
2:26:34 Outro ft. Luke's cybernetic arm


guid: https://simonwillison.net/2025/Jan/31/o3-mini/#atom-entries
title: OpenAI o3-mini, now available in LLM
author: Simon Willison
url: https://simonwillison.net/2025/Jan/31/o3-mini/#atom-entries
feedurl: https://simonwillison.net/atom/entries/
content_mime_type: text/html
content:
<p>OpenAI's <a href="https://openai.com/index/openai-o3-mini/">o3-mini is out today</a>. As with other o-series models it's a slightly difficult one to evaluate - we now need to decide if a prompt is best run using GPT-4o, o1, o3-mini or (if we have access) o1 Pro.</p>
<p>Confusing matters further, the benchmarks in <a href="https://openai.com/index/o3-mini-system-card/">the o3-mini system card</a> (PDF) aren't a universal win for o3-mini across all categories. It generally benchmarks higher than GPT-4o and o1 but not across everything.</p>
<p>The biggest win for o3-mini is on the Codeforces ELO competitive programming benchmark, which I think is <a href="https://arxiv.org/abs/2501.01257">described by this 2nd January 2025 paper</a>, with the following scores:</p>
<ul>
<li>o3-mini (high) 2130</li>
<li>o3-mini (medium) 2036</li>
<li>o1 1891</li>
<li>o3-mini (low) 1831</li>
<li>o1-mini 1650</li>
<li>o1-preview 1258</li>
<li>GPT-4o 900</li>
</ul>
<p>Weirdly, that GPT-4o score was in an older copy of the System Card PDF which has been replaced by an updated document that doesn't mention Codeforces ELO scores at all.</p>
<p>One note from the System Card that stood out for me concerning intended applications of o3-mini for OpenAI themselves:</p>
<blockquote>
<p>We also plan to allow users to use o3-mini to search the internet and summarize the results in ChatGPT. We expect o3-mini to be a useful and safe model for doing this, especially given its performance on the jailbreak and instruction hierarchy evals detailed in Section 4 below.</p>
</blockquote>
<p>This is notable because the existing o1 models on ChatGPT have not yet had access to their web search tool - despite the mixture of search and "reasoning" models having very clear benefits.</p>
<p>o3-mini does not and <a href="https://twitter.com/nikunjhanda/status/1885415728624656481">will not</a> support vision. We will have to wait for future OpenAI reasoning models for that.</p>
<p>I released <a href="https://llm.datasette.io/en/stable/changelog.html#v0-21">LLM 0.21</a> with support for the new model, plus its <code>-o reasoning_effort high</code> (or <code>medium</code> or <code>low</code>) option for tweaking the reasoning effort - details <a href="https://github.com/simonw/llm/issues/728">in this issue</a>.</p>
<p>Note that the new model is currently only available for <a href="https://platform.openai.com/docs/guides/rate-limits/usage-tiers#tier-3-rate-limits">Tier 3</a> and higher users, which requires you to have spent at least $100 on the API.</p>
<p>o3-mini <a href="https://openai.com/api/pricing/">is priced</a> at $1.10/million input tokens, $4.40/million output tokens - less than half the price of GPT-4o (currently $2.50/$10) and massively cheaper than o1 ($15/60).</p>
<p>I tried using it to summarize <a href="https://news.ycombinator.com/item?id=42890627">this conversation about o3-mini on Hacker News</a>, using <a href="https://til.simonwillison.net/llms/claude-hacker-news-themes#user-content-adding-a--m-model-option">my hn-summary.sh script</a>.</p>

<div class="highlight highlight-source-shell"><pre>hn-summary.sh 42890627 -o o3-mini</pre></div>

<p>Here's <a href="https://gist.github.com/simonw/09e5922be0cbb85894cf05e6d75ae050">the result</a> - it used 18,936 input tokens and 2,905 output tokens for a total cost of 3.3612 cents.</p>

<p>Another characteristic worth noting is o3-mini's token output limit - the measure of how much text it can output in one go.  That's 100,000 tokens, compared to 16,000 for GPT-4o and just 8,000 for both DeepSeek R1 and Claude 3.5.</p>

<p>Invisible "reasoning tokens" come out of the same budget, so it's likely not possible to have it output the full 100,000.</p>

<p>The model accepts up to 200,000 tokens of input, an improvement on GPT-4o's 128,000.</p>

<p>An application where output limits really matter is translation between human languages, where the output can realistically be expected to have a similar length to the input. It will be interesting seeing how well o3-mini works for that, especially given its low price.</p>
<p>Update: Here's a <a href="https://news.ycombinator.com/item?id=42894215#42895610">fascinating comment</a> on this by professional translator Tom Gally on Hacker News:</p>
<blockquote>
<p>I just did a test in which both R1 and o3-mini got worse at translation in the latter half of a long text. [...]</p>
<p>An initial comparison of the output suggested that, while R1 didn’t seem bad, o3-mini produced a writing style closer to what I asked for in the prompt—smoother and more natural English.
But then I noticed that the output length was 5,855 characters for R1, 9,052 characters for o3-mini, and 11,021 characters for my own polished version. Comparing the three translations side-by-side with the original Japanese, I discovered that R1 had omitted entire paragraphs toward the end of the speech, and that o3-mini had switched to a strange abbreviated style (using slashes instead of “and” between noun phrases, for example) toward the end as well. The vanilla versions of ChatGPT, Claude, and Gemini that I ran the same prompt and text through a month ago had had none of those problems.</p>
</blockquote>


guid: yt:video:h6ws1znxvF4
title: I walked the length of a state (ish)
author: Stand-up Maths
url: https://www.youtube.com/watch?v=h6ws1znxvF4
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCSju5G2aFaWMqn-_0YBtq5A
enclosure_url: https://www.youtube.com/v/h6ws1znxvF4?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Join me on the medium seas, 7-10 November: https://stemconatsea.com/STANDUP

Boundary Stones of the District of Columbia https://boundarystones.org/

Rectangular States and Kinky Borders https://mathtourist.blogspot.com/2007/08/rectangular-states-and-kinky-borders.html?m=1

"Chart showing the original boundary milestones of the District of Columbia." Fred E. Woodward, 1906. Geography and Map Division, Library of Congress. https://blogs.loc.gov/maps/2017/05/modest-monuments-the-district-of-columbia-boundary-stones/

Huge thanks to my Patreon supporters. They be there and be square. https://www.patreon.com/standupmaths

CORRECTIONS
- None yet, let me know if you spot anything! 

Filming by Truman Hanks
Editing by Gus Melton
Written and performed by Matt Parker
Additional material by Truman Hanks and Nicole Jacobus
Produced by Nicole Jacobus
Music by Howard Carter
Design by Simon Wright and Adam Robinson
Additional technical support by Adam Fineberg and David Benji Weiner

MATT PARKER: Stand-up Mathematician
Website: http://standupmaths.com/

PS The Smithsonian video is about a calculator prototype they have in their archives. It's very exciting.


guid: yt:video:nnGEvWqTaO8
title: Trump & Elon Force Government Programmers to Disable DEI Language Chat Bot
author: The Lunduke Journal
url: https://www.youtube.com/watch?v=nnGEvWqTaO8
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCkK9UDm_ZNrq_rIXCz3xCGA
enclosure_url: https://www.youtube.com/v/nnGEvWqTaO8?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Plus: US Government Devs are quickly deleting DEl material off GitHub, let's see what they're removing. (Spoiler: It's super racist and ridiculous!)

More from The Lunduke Journal:
https://lunduke.com/


guid: yt:video:X6zKIcumWQ4
title: Arch Linux Discord Voting to Ban Links to X / Twitter (Because "Nazis")
author: The Lunduke Journal
url: https://www.youtube.com/watch?v=X6zKIcumWQ4
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCkK9UDm_ZNrq_rIXCz3xCGA
enclosure_url: https://www.youtube.com/v/X6zKIcumWQ4?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Following Debian's lead, the Arch community is preparing to take a stand against Elon Musk, Conservatives, & X. And they're banning anyone who disagrees.

More from The Lunduke Journal:
https://lunduke.com/


guid: yt:video:rt6Z_N82tYk
title: The Most Important Tech News of January 2025 (That Only The Lunduke Journal Covered)
author: The Lunduke Journal
url: https://www.youtube.com/watch?v=rt6Z_N82tYk
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCkK9UDm_ZNrq_rIXCz3xCGA
enclosure_url: https://www.youtube.com/v/rt6Z_N82tYk?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
H1-B Visas, Non-Woke Operating Systems, Facebook ending DEl, Memory Leaking Rust, Godot Went Woke Went Broke, Debian Linux Doubles Down on Wokeness, & more.

More from The Lunduke Journal:
https://lunduke.com/


guid: yt:video:KtItxpghFaA
title: Arch Linux Discord: "I think we should kill Lunduke"
author: The Lunduke Journal
url: https://www.youtube.com/watch?v=KtItxpghFaA
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCkK9UDm_ZNrq_rIXCz3xCGA
enclosure_url: https://www.youtube.com/v/KtItxpghFaA?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
How does the Arch Linux Discord server respond to me covering their plan to "Ban Links to X"? By threatening to murder me. Because they are definitely very sane.

More from The Lunduke Journal:
https://lunduke.com/


guid: yt:video:s8BgXaBAr8c
title: Red Hat Adding AI to Fedora Linux & GNOME
author: The Lunduke Journal
url: https://www.youtube.com/watch?v=s8BgXaBAr8c
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCkK9UDm_ZNrq_rIXCz3xCGA
enclosure_url: https://www.youtube.com/v/s8BgXaBAr8c?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Red Hat's Director of Desktop, outlines plans for 2025: "Big item on our list is looking at ways Fedora can make use of Artificial Intelligence" from IBM.

More from The Lunduke Journal:
https://lunduke.com/


guid: yt:video:RJ_6KZRg-HE
title: C Must Die
author: ThePrimeTime
url: https://www.youtube.com/watch?v=RJ_6KZRg-HE
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCUyeluBRhGPCW4rPe_UvBZQ
enclosure_url: https://www.youtube.com/v/RJ_6KZRg-HE?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Twitch https://twitch.tv/ThePrimeagen
Discord https://discord.gg/ThePrimeagen

Become Backend Dev: https://boot.dev/prime
(plus i make courses for them)

This is also the best way to support me is to support yourself becoming a better backend engineer.  

### LINKS 
https://veresov.pro/cmustdie/

Great News?  Want me to research and create video????: https://www.reddit.com/r/ThePrimeagen

Kinesis Advantage 360: https://bit.ly/Prime-Kinesis

Get production ready SQLite with Turso: https://turso.tech/deeznuts


guid: yt:video:X-lsquJq5yU
title: Making Memory Safer in my C
author: Tsoding Daily
url: https://www.youtube.com/watch?v=X-lsquJq5yU
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCrqM0Ym_NbK1fqeQG2VIohg
enclosure_url: https://www.youtube.com/v/X-lsquJq5yU?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Streamed Offline

Related Playlists:
- https://www.youtube.com/playlist?list=PLpM-Dvs8t0VYkIVqDPCa63XiFA-ycqmOe

References:
- https://github.com/tsoding/coroutines
- https://stackoverflow.com/questions/56888725/why-is-map-growsdown-mapping-does-not-grow
- The SVG of the thumbnail logo: https://gist.github.com/rexim/4f1651fff0f02f0f1786850ca03353c8

Support:
- https://github.com/tsoding/donate#support-tsoding

Coroutines Ep.4 - Allocating stack using mmap with MAP_GROWSDOWN flag


guid: yt:video:3DEEqxtxXFk
title: Leaking Memory is Safe
author: Tsoding Daily
url: https://www.youtube.com/watch?v=3DEEqxtxXFk
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCrqM0Ym_NbK1fqeQG2VIohg
enclosure_url: https://www.youtube.com/v/3DEEqxtxXFk?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Streamed Offline

Related Playlists:
- https://www.youtube.com/playlist?list=PLpM-Dvs8t0VYkIVqDPCa63XiFA-ycqmOe

References:
- https://github.com/tsoding/coroutines
- Previous Session: https://www.youtube.com/watch?v=X-lsquJq5yU

Support:
- https://github.com/tsoding/donate#support-tsoding

Coroutines Ep.4.5 - A follow up to Coroutines Ep.4 that address the leaked pages due to MAP_GROWSDOWN


guid: yt:video:1X3dV3D5EJg
title: Grafana is the goat... Let's deploy the LGTM stack
author: Fireship
url: https://www.youtube.com/watch?v=1X3dV3D5EJg
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCsBjURrPoezykLs9EqgamOA
enclosure_url: https://www.youtube.com/v/1X3dV3D5EJg?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Get up to 67% off VPS at Hostinger. Use code FIRESHIP for an extra discount at https://hostinger.com/fireship

#linux #programming #softwareengineer 

💬 Chat with Me on Discord

https://discord.gg/fireship

🔗 Resources

Docker 101 https://youtu.be/rIrNIzy6U_g
Full Deno Course https://fireship.io/courses/deno
Grafana on GitHub https://github.com/grafana/grafana

🔥 Get More Content - Upgrade to PRO

Upgrade at https://fireship.io/pro
Use code YT25 for 25% off PRO access 

🎨 My Editor Settings

- Atom One Dark 
- vscode-icons
- Fira Code Font

🔖 Topics Covered

What is Grafana? 
How to get started with software observability?
What is Open Telemetry?
How to deploy LGTM stack?
How monitor Linux server performance?


guid: yt:video:PoeFxGzPpXE
title: OpenAI o3 tries to curb stomp DeepSeek...
author: Fireship
url: https://www.youtube.com/watch?v=PoeFxGzPpXE
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCsBjURrPoezykLs9EqgamOA
enclosure_url: https://www.youtube.com/v/PoeFxGzPpXE?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Stay updated with the best dev content at https://daily.dev/fireship

Let's take a first look at OpenAI o3-mini and its new deep research feature. In addition, we will examine the recent bans on DeepSeek R1 and it compare it to other AI tools.  

#tech #ai #thecodereport 

💬 Chat with Me on Discord

https://discord.gg/fireship

🔗 Resources

OpenAI Deep Research https://openai.com/index/introducing-deep-research/
OpenAI accuses DeepSeek of IP theft https://youtu.be/hpwoGjpYygI
Tech Trends 2025 https://youtu.be/v4H2fTgHGuc
Godot in 100 Seconds https://youtu.be/QKgTZWbwD1U

🔥 Get More Content - Upgrade to PRO

Upgrade at https://fireship.io/pro
Use code YT25 for 25% off PRO access 

🎨 My Editor Settings

- Atom One Dark 
- vscode-icons
- Fira Code Font

🔖 Topics Covered

- OpenAI Deep Research First Look
- Why is DeepSeek banned?
- Latest AI features in tech
- o3-mini vs DeepSeek R1 vs Claude Sonnet


guid: yt:video:8FcbexcoW4E
title: More Thoughts On Game Marketing
author: Timothy Cain
url: https://www.youtube.com/watch?v=8FcbexcoW4E
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCTAfm-YD2M9xzvbYvRc5ttA
enclosure_url: https://www.youtube.com/v/8FcbexcoW4E?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
I give constructive feedback on how to be a game marketer.

Videos I reference:
Marketing: https://www.youtube.com/watch?v=LDSF7Ek4wec
Giving Good Feedback: https://www.youtube.com/watch?v=-72btgrwKzA
Game Production Stages: https://www.youtube.com/watch?v=IADSh_P05As


guid: yt:video:A3csqlk8kFw
title: Useful Terminal Commands For Distro-Hoppers
author: DistroTube
url: https://www.youtube.com/watch?v=A3csqlk8kFw
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCVls1GmFKf6WlTraIb_IaJg
enclosure_url: https://www.youtube.com/v/A3csqlk8kFw?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
I love using the terminal.  This video highlights some of the commands that I often use when I'm installing a new Linux distro or checking out a new distro release.

WANT TO SUPPORT THE CHANNEL? 
💰 Patreon: https://www.patreon.com/distrotube 
💳 Paypal: https://www.youtube.com/redirect?event=channel_banner&redir_token=QUFFLUhqazNocEhiaGFBT1l1MnRHbnlIcHFKbXJWVnpQd3xBQ3Jtc0tsLVZJc19YeFlwZ2JqbXVOa3g0Skw4TVhTV2otNm1tM3A1bUNnamh3S2V6OGQtLTBnSjBxYTlvUXMxeEVIS3o4US10NENHMUQ3STk2a01FOFBhUnZjZFctMEhFUTg1TVctQmFfVUdxZXJ4TDl0azlYNA&q=https%3A%2F%2Fwww.paypal.com%2Fcgi-bin%2Fwebscr%3Fcmd%3D_donations%26business%3Dderek%2540distrotube%252ecom%26lc%3DUS%26item_name%3DDistroTube%26no_note%3D0%26currency_code%3DUSD%26bn%3DPP%252dDonationsBF%253abtn_donateCC_LG%252egif%253aNonHostedGuest
🛍️ Amazon: https://amzn.to/2RotFFi
👕 Teespring: https://teespring.com/stores/distrotube

DT ON THE WEB:
🕸️ Website: http://distrotube.com/
📁 GitLab: https://gitlab.com/dwt1  
🗨️ Mastodon: https://fosstodon.org/@distrotube
👫 Reddit: https://www.reddit.com/r/DistroTube/
📽️ LBRY/Odysee: https://odysee.com/@DistroTube:2

FREE AND OPEN SOURCE SOFTWARE THAT I USE:
🌐 Brave Browser - https://brave.com/dis872 
📽️ Open Broadcaster Software: https://obsproject.com/
🎬 Kdenlive: https://kdenlive.org
🎨 GIMP: https://www.gimp.org/
💻 VirtualBox: https://www.virtualbox.org/
🗒️ Doom Emacs: https://github.com/hlissner/doom-emacs

Your support is very much appreciated. Thanks, guys!


guid: yt:video:FoAP9eqeVBg
title: Varia Is A Download Manager On Steroids
author: DistroTube
url: https://www.youtube.com/watch?v=FoAP9eqeVBg
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCVls1GmFKf6WlTraIb_IaJg
enclosure_url: https://www.youtube.com/v/FoAP9eqeVBg?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Varia is a download manager that supports videos and torrents on top of just regular files, and with a variety of advanced features wrapped inside an easy to use interface.

REFERENCED:
► https://flathub.org/apps/io.github.giantpinkrobots.varia

WANT TO SUPPORT THE CHANNEL? 
💰 Patreon: https://www.patreon.com/distrotube 
💳 Paypal: https://www.youtube.com/redirect?event=channel_banner&redir_token=QUFFLUhqazNocEhiaGFBT1l1MnRHbnlIcHFKbXJWVnpQd3xBQ3Jtc0tsLVZJc19YeFlwZ2JqbXVOa3g0Skw4TVhTV2otNm1tM3A1bUNnamh3S2V6OGQtLTBnSjBxYTlvUXMxeEVIS3o4US10NENHMUQ3STk2a01FOFBhUnZjZFctMEhFUTg1TVctQmFfVUdxZXJ4TDl0azlYNA&q=https%3A%2F%2Fwww.paypal.com%2Fcgi-bin%2Fwebscr%3Fcmd%3D_donations%26business%3Dderek%2540distrotube%252ecom%26lc%3DUS%26item_name%3DDistroTube%26no_note%3D0%26currency_code%3DUSD%26bn%3DPP%252dDonationsBF%253abtn_donateCC_LG%252egif%253aNonHostedGuest
🛍️ Amazon: https://amzn.to/2RotFFi
👕 Teespring: https://teespring.com/stores/distrotube

DT ON THE WEB:
🕸️ Website: http://distrotube.com/
📁 GitLab: https://gitlab.com/dwt1  
🗨️ Mastodon: https://fosstodon.org/@distrotube
👫 Reddit: https://www.reddit.com/r/DistroTube/
📽️ LBRY/Odysee: https://odysee.com/@DistroTube:2

FREE AND OPEN SOURCE SOFTWARE THAT I USE:
🌐 Brave Browser - https://brave.com/dis872 
📽️ Open Broadcaster Software: https://obsproject.com/
🎬 Kdenlive: https://kdenlive.org
🎨 GIMP: https://www.gimp.org/
💻 VirtualBox: https://www.virtualbox.org/
🗒️ Doom Emacs: https://github.com/hlissner/doom-emacs

Your support is very much appreciated. Thanks, guys!


guid: yt:video:9lXCqePhJ4g
title: 2025 EEVblog Viewer Survey and GIVEAWAY
author: EEVblog
url: https://www.youtube.com/watch?v=9lXCqePhJ4g
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UC2DjFE7Xf11URZqWBigcVOQ
enclosure_url: https://www.youtube.com/v/9lXCqePhJ4g?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
I'd really appreciate if you could fill in the 2025 viewer survey and tell me what you like and don't like about the channel, and what changes I can make. It is ANONYMOUS unless you want to enter the giveaway.
LINK:
https://docs.google.com/forms/d/e/1FAIpQLSdLeQRdLRmbwyLT4yn4d9BZU3kzxjOoFAq-XpqS4g8VL1hXpw/viewform?usp=dialog

I will be giving away three new BM2257 multimeters to random people who fill it out. Thanks.

Forum: https://www.eevblog.com/forum/blog/2025-eevblog-viewer-survey-and-giveaway/

Web Site: http://www.eevblog.com
Hardware Store: https://eevblog.store/
Merch Store: https://www.teepublic.com/stores/eevblog?ref_id=37825

If you find my videos useful you may consider supporting the EEVblog on Patreon: http://www.patreon.com/eevblog
Or with crypto:
BTC: 33BsprBQNBtHuVzVwDmqWkpDjYnCouwASM
ETH: 0x68114e40ff4dcdd384750500501e20acf3875f8c
BCH: 35n9KBPw9T7M3NGzpS3t4nUYEf9HbRmkm4
USDC: 0x68114e40ff4dcdd384750500501e20acf3875f8c
LTC: MJfK57ujxy55su4XicVGQc9wcEJf6mAoXF

Other channels:
EEVblog2: http://www.youtube.com/EEVblog2
EEVdiscover: https://www.youtube.com/eevdiscover

#ElectronicsCreators #Survey


guid: yt:video:D3c3UVDSKTg
title: EEVblog 1664 - REPAIR with Junk Bin Parts! Keithley 2302
author: EEVblog
url: https://www.youtube.com/watch?v=D3c3UVDSKTg
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UC2DjFE7Xf11URZqWBigcVOQ
enclosure_url: https://www.youtube.com/v/D3c3UVDSKTg?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Repair of a Keithley 2302 battery simulator with junk bin parts. But it did put up a fight!

Teardown video: https://www.youtube.com/watch?v=5LK8wduZsy0

Forum: https://www.eevblog.com/forum/blog/eevblog-1664-repair-with-junk-bin-parts!-keithley-2302/

00:00 - Faulty VFD display in a Keithley 2302 Battery Simulator
01:22 - Teardown
03:14 - The Display driver PCB
04:30 - Solder Sucking Sucks
05:26 - The VFD display module, a Newhaven Display VFM162SDAR8 
06:50 - Probing Pro Tip
07:28 - Probing the VFD signals on the oscilloscope
09:42 - Searching for a replacement 16x2 VFD display
15:03 - Potential replacement LCD 
16:38 - Identical replacement found
17:44 - Lets check the junk bin...
18:33 - Pinout trap for young players
19:25 - First test FAIL, but hold on a second, lets try something...
21:09 - Winner Winner Chicken Dinner
22:12 - WOAH, now it's not working?
24:09 - Lets try THIS...

Web Site: http://www.eevblog.com
Hardware Store: https://eevblog.store/
Merch Store: https://www.teepublic.com/stores/eevblog?ref_id=37825

If you find my videos useful you may consider supporting the EEVblog on Patreon: http://www.patreon.com/eevblog
Or with crypto:
BTC: 33BsprBQNBtHuVzVwDmqWkpDjYnCouwASM
ETH: 0x68114e40ff4dcdd384750500501e20acf3875f8c
BCH: 35n9KBPw9T7M3NGzpS3t4nUYEf9HbRmkm4
USDC: 0x68114e40ff4dcdd384750500501e20acf3875f8c
LTC: MJfK57ujxy55su4XicVGQc9wcEJf6mAoXF

Other channels:
EEVblog2: http://www.youtube.com/EEVblog2
EEVdiscover: https://www.youtube.com/eevdiscover

#ElectronicsCreators #Repair #keithley


guid: yt:video:e-EG3B5Uj78
title: Run Deepseek R1 at Home on Hardware from $250 to $25,000: From Installation to Questions
author: Dave's Garage
url: https://www.youtube.com/watch?v=e-EG3B5Uj78
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCNzszbnvQeFzObW0ghk0Ckw
enclosure_url: https://www.youtube.com/v/e-EG3B5Uj78?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Dave installs Deepseek on a Jetson Orin Nano and a Threadripper and explores the self-hosted editions of Deepseek R1 and evaluates their performance on a wide range of hardware.  Free Sample of my Book on the Spectrum: https://amzn.to/3zBinWM

Secrets of the Autistic Millionaire: https://amzn.to/3WNDDkJ

Watch ShopTalk Now on Dave's Attic: https://youtu.be/5Emgx0lhllE

Follow me on X: https://x.com/davepl1968
Facebook: https://www.facebook.com/davepl

Introduction to the Affordable NVIDIA Jetson Orin Nano Super: 00:00
Why Run AI Locally?: 00:31
Advantages of Self-Hosted AI: 01:02
Jetson Nano Specifications: 01:33
Setting Up DeepSeek R1 with Olama: 02:04
Privacy Benefits of Local AI: 03:06
Running Queries Locally: 03:57
Use Cases for Home Automation: 05:09
Cost-Effectiveness of Jetson Nano: 05:40
Reasoning Models vs Traditional LLMs: 06:42
7B Parameter Model Performance Review On Affordable Jetson Orin Nano: 8:53
Running the full DeepSeek-R1 671B on $10,000+ machine 9:20
Outro - 11:58


guid: yt:video:TihoKTILOrs
title: Find the FAKE PC Gamer
author: Linus Tech Tips
url: https://www.youtube.com/watch?v=TihoKTILOrs
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCXuqSBlHAE6Xw-yeJA0Tunw
enclosure_url: https://www.youtube.com/v/TihoKTILOrs?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Power your PC with confidence! Check out Seasonic’s Core GX and Focus GX ATX 3 power supplies at https://seasonic.com/core-gx-atx-3-2024/ and https://seasonic.com/focus-gx-white-atx-3/

Five people CLAIM they are PC gamers, but one of them is LYING. In this reality tv style format, 2 people compete to identify the imposter by asking the hard questions and slowly eliminating them 1 by 1. Are they in Jeopardy? Who is going to be the Weakest Link? And will YOU be able to identify the Console Gamer before the Hosts do? PLAY ALONG AT HOME!

Discuss on the forum: https://linustechtips.com/topic/1599714-find-the-fake-pc-gamer/

► GET OUR MERCH: https://lttstore.com
► GET EXCLUSIVE CONTENT ON FLOATPLANE: https://lmg.gg/lttfloatplane
► GET A VPN: http://www.piavpn.com/linus
► SPONSORS, AFFILIATES, AND PARTNERS: https://lmg.gg/partners

CHAPTERS
---------------------------------------------------
0:00 What is happening?
1:23 Choice NUMBER 1
3:04 The second selection
4:35 The THIRD number
6:31 Will we have our first ELIMINATION?
8:51 TWO IN A ROW????
12:17 The Final Guess


guid: yt:video:8FeiXml-U6c
title: The $300 GAMING PC Challenge - The Original Scrapyard Wars COMPLETE
author: Linus Tech Tips
url: https://www.youtube.com/watch?v=8FeiXml-U6c
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCXuqSBlHAE6Xw-yeJA0Tunw
enclosure_url: https://www.youtube.com/v/8FeiXml-U6c?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Our FIRST reality competition series AND NOW ITS ONE BIG FREAKING VIDEO! Luke and Linus go head 2 head to build the ultimate gaming PC for $300 bucks in 48 hours, meaning they gotta be cheap with all their components, like GPU and CPU. Find the deals to claim the crown. But things never go as expected, do they? It's hard to remember when we shot this like 10 years ago… so retro.

Discuss on the forum: https://linustechtips.com/topic/1600073-the-300-gaming-pc-challenge-the-original-scrapyard-wars-complete/

► GET OUR MERCH: https://lttstore.com
► GET EXCLUSIVE CONTENT ON FLOATPLANE: https://lmg.gg/lttfloatplane
► GET A VPN: http://www.piavpn.com/linus
► SPONSORS, AFFILIATES, AND PARTNERS: https://lmg.gg/partners

Purchases made through some store links may provide some compensation to Linus Media Group.

CHAPTERS
---------------------------------------------------
0:00 Intro
1:17 Part 1
17:14 Part 2
29:16 Part 3
47:48 Outro


guid: yt:video:YX29Hk08lAY
title: The Ultimate Sleeper Gaming TV
author: Linus Tech Tips
url: https://www.youtube.com/watch?v=YX29Hk08lAY
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCXuqSBlHAE6Xw-yeJA0Tunw
enclosure_url: https://www.youtube.com/v/YX29Hk08lAY?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Join us and over 70 million players in one of the most comprehensive vehicle combat games EVER MADE! Check out War Thunder for free today on PC, Console, and Mobile using our links!

PC/Console: https://playwt.link/linustechtips

Mobile: https://wtm.game/linustechtips

Old TVs are huge.. But what if you used that space for modern hardware? Well that is exactly what we did, cramming every relevant console into an old rear projection TV.. and 1200W of speakers for good measure.

Discuss on the forum: https://linustechtips.com/topic/1600198-the-ultimate-sleeper-gaming-tv/

Buy SVS Prime Elevation Speakers: https://geni.us/XDZ2
Buy a Streacom STDA6B Open ITX Case: https://geni.us/WWPc
Buy a Sony A95L 65" 4K OLED TV: https://geni.us/S9noO
Buy a SVS Prime Wireless Pro SoundBase Streaming Box: https://geni.us/dMTS

► GET OUR MERCH: https://lttstore.com
► GET EXCLUSIVE CONTENT ON FLOATPLANE: https://lmg.gg/lttfloatplane
► GET A VPN: http://www.piavpn.com/linus
► SPONSORS, AFFILIATES, AND PARTNERS: https://lmg.gg/partners

Purchases made through some store links may provide some compensation to Linus Media Group.

CHAPTERS
---------------------------------------------------
0:00 Intro
0:51 Sponsor
1:07 What is a rear projection TV?
2:50 Disassembling the TV
4:30 Fresnel lens shenanigans
5:14 Planning the layout
7:10 Building the layout
9:35 Installing the Wii and speakers
12:13 Listening to the speakers
12:28 The PC
13:35 Buttoning it back up
15:10 Linus does a handstand
15:26 The PS5
15:49 The Switch
17:05 The OLED panel
18:14 Closing it up
19:36 Trying it out
21:03 Sponsor
21:57 Credits


guid: yt:video:fsJR0g40-RU
title: Is It Time To Leave BCacheFS In The Past
author: Brodie Robertson
url: https://www.youtube.com/watch?v=fsJR0g40-RU
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCld68syR8Wi-GY_n4CaoJGA
enclosure_url: https://www.youtube.com/v/fsJR0g40-RU?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
Bcachefs has had a fairly rocky time in the kernel over the years and as it's going it's unclear whether or not it'll actually stick around in the kernel or now and one dev has decided to leave it behind.

==========Support The Channel==========
► Patreon: https://brodierobertson.xyz/patreon
► Paypal: https://brodierobertson.xyz/paypal
► Liberapay: https://brodierobertson.xyz/liberapay
► Amazon USA: https://brodierobertson.xyz/amazonusa

==========Resources==========
Blog Post: https://blog.sesse.net/blog/tech/2025-01-20-21-45_migrating_away_from_bcachefs.html

=========Video Platforms==========
🎥 Odysee: https://brodierobertson.xyz/odysee
🎥 Podcast: https://techovertea.xyz/youtube
🎮 Gaming: https://brodierobertson.xyz/gaming

==========Social Media==========
🎤 Discord: https://brodierobertson.xyz/discord
🐦 Twitter: https://brodierobertson.xyz/twitter
🌐 Mastodon: https://brodierobertson.xyz/mastodon
🖥️ GitHub: https://brodierobertson.xyz/github

==========Credits==========
🎨 Channel Art:
Profile Picture:
https://www.instagram.com/supercozman_draws/

#Linux #kernel #FOSS #OpenSource #bcachefs

🎵 Ending music
Track: Debris & Jonth - Game Time [NCS Release]
Music provided by NoCopyrightSounds.
Watch:  https://www.youtube.com/watch?v=yDTvvOTie0w 
Free Download / Stream: http://ncs.io/GameTime

DISCLOSURE: Wherever possible I use referral links, which means if you click one of the links in this video or description and make a purchase I may receive a small commission or other compensation.


guid: yt:video:GIqhJLbOaOk
title: Just Delete The Fedora Flatpak Repo Already
author: Brodie Robertson
url: https://www.youtube.com/watch?v=GIqhJLbOaOk
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCld68syR8Wi-GY_n4CaoJGA
enclosure_url: https://www.youtube.com/v/GIqhJLbOaOk?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
The Fedora Flatpak repo is a weird thing that unless you're on Fedora you probably never think about but for those who are especially on Workstation the ordering of the repos has caused a lot of issues for people over the years and still does today.

==========Support The Channel==========
► Patreon: https://brodierobertson.xyz/patreon
► Paypal: https://brodierobertson.xyz/paypal
► Liberapay: https://brodierobertson.xyz/liberapay
► Amazon USA: https://brodierobertson.xyz/amazonusa

==========Resources==========
Flatpak 2023 Change: https://fosstodon.org/@fedora/109802129126311440
Fedora Flatpak: https://pagure.io/fedora-workstation/issue/463

=========Video Platforms==========
🎥 Odysee: https://brodierobertson.xyz/odysee
🎥 Podcast: https://techovertea.xyz/youtube
🎮 Gaming: https://brodierobertson.xyz/gaming

==========Social Media==========
🎤 Discord: https://brodierobertson.xyz/discord
🐦 Twitter: https://brodierobertson.xyz/twitter
🌐 Mastodon: https://brodierobertson.xyz/mastodon
🖥️ GitHub: https://brodierobertson.xyz/github

==========Credits==========
🎨 Channel Art:
Profile Picture:
https://www.instagram.com/supercozman_draws/

🎵 Ending music
Track: Debris & Jonth - Game Time [NCS Release]
Music provided by NoCopyrightSounds.
Watch:  https://www.youtube.com/watch?v=yDTvvOTie0w 
Free Download / Stream: http://ncs.io/GameTime

#Fedora #Linux #LinuxDistro #FOSS #Flatpak #FedoraLinux

DISCLOSURE: Wherever possible I use referral links, which means if you click one of the links in this video or description and make a purchase I may receive a small commission or other compensation.


guid: yt:video:6XTQPsnSu5E
title: "Everything Is Open Source If You Know Assembly"
author: Brodie Robertson
url: https://www.youtube.com/watch?v=6XTQPsnSu5E
feedurl: https://www.youtube.com/feeds/videos.xml?channel_id=UCld68syR8Wi-GY_n4CaoJGA
enclosure_url: https://www.youtube.com/v/6XTQPsnSu5E?version=3
enclosure_type: application/x-shockwave-flash
content_mime_type: text/plain
content:
There's a common phrase people in the FOSS world say "Everything Is Open Source If You Know Assembly" and whilst this is obviously a joke there's some truth to it if you play some mental gymnastics

==========Support The Channel==========
► Patreon: https://brodierobertson.xyz/patreon
► Paypal: https://brodierobertson.xyz/paypal
► Liberapay: https://brodierobertson.xyz/liberapay
► Amazon USA: https://brodierobertson.xyz/amazonusa

=========Video Platforms==========
🎥 Odysee: https://brodierobertson.xyz/odysee
🎥 Podcast: https://techovertea.xyz/youtube
🎮 Gaming: https://brodierobertson.xyz/gaming

==========Social Media==========
🎤 Discord: https://brodierobertson.xyz/discord
🐦 Twitter: https://brodierobertson.xyz/twitter
🌐 Mastodon: https://brodierobertson.xyz/mastodon
🖥️ GitHub: https://brodierobertson.xyz/github

==========Credits==========
🎨 Channel Art:
Profile Picture:
https://www.instagram.com/supercozman_draws/

🎵 Ending music
Track: Debris & Jonth - Game Time [NCS Release]
Music provided by NoCopyrightSounds.
Watch:  https://www.youtube.com/watch?v=yDTvvOTie0w 
Free Download / Stream: http://ncs.io/GameTime

#FOSS #Linux #OpenSource #LinuxDestkop #Assembly

DISCLOSURE: Wherever possible I use referral links, which means if you click one of the links in this video or description and make a purchase I may receive a small commission or other compensation.


guid: https://www.computerenhance.com/p/q-and-a-71-2025-02-03
title: Q&A #71 (2025-02-03)
url: https://www.computerenhance.com/p/q-and-a-71-2025-02-03
feedurl: https://www.computerenhance.com/feed
enclosure_type: image/jpeg
content_mime_type: text/html
content:
<p><em>In each Q&amp;A video, I answer questions from the comments on the previous Q&amp;A video, which can be from any part of the course.</em></p><p>I felt compelled to annotate this post with the following amusing anecdote:</p><p>In this Q&amp;A, one of the questions was about &#8220;64k aliasing&#8221;. I happened to know about 64k aliasing because Michael Abrash and Mike Sartain ran into this problem when optimizing the Pixomatic software renderer. Since I was also working at RAD Game Tools at the time, I specifically remember them tracking it down. I want to say it even involved having Intel run their code on the internal Intel simulator, whose output we were allowed to see a screenshot of, but which is otherwise a closely-guarded secret<a class="footnote-anchor" data-component-name="FootnoteAnchorToDOM" id="footnote-anchor-1" href="#footnote-1" target="_self">1</a>.</p><p>When answering the question in the Q&amp;A, I assumed that this would have been a documented issue with (old) Intel hardware, and that it&#8217;d be easy to post a link here for anyone who wanted to investigate further. However, 64k aliasing turned out to be more esoteric than I thought.</p>
      <p>
          <a href="https://www.computerenhance.com/p/q-and-a-71-2025-02-03">
              Read more
          </a>
      </p>
   

enclosure_url:
https://substack-video.s3.amazonaws.com/video_upload/post/156414046/06dcddc1-d49e-43cb-a13a-305dbaceb63f/transcoded-143137.png


guid: https://lwn.net/Articles/1007438/
title: Stable kernel updates for Saturday
author: corbet
url: https://lwn.net/Articles/1007438/
feedurl: https://lwn.net/headlines/rss
content:
The
<a href="https://lwn.net/Articles/1007439/">6.13.1</a>,
<a href="https://lwn.net/Articles/1007440/">6.12.12</a>,
<a href="https://lwn.net/Articles/1007441/">6.6.75</a>,
<a href="https://lwn.net/Articles/1007442/">6.1.128</a>,
<a href="https://lwn.net/Articles/1007443/">5.15.178</a>,
<a href="https://lwn.net/Articles/1007444/">5.10.234</a>, and
<a href="https://lwn.net/Articles/1007445/">5.4.290</a>
stable kernel updates have all been released; each contains another set of
important fixes.


guid: https://lwn.net/Articles/1007541/
title: GNU Binutils 2.44 Released
author: corbet
url: https://lwn.net/Articles/1007541/
feedurl: https://lwn.net/headlines/rss
content:
Version 2.44 of the GNU Binutils package has been released.  Perhaps the
most significant change is the absence of the "gold" linker, which is
deprecated and about to disappear entirely.  Gold <a
href="https://lwn.net/Articles/274859/">appeared in 2008</a> with some fanfare as a faster
linker, but it has suffered from a lack of maintenance in recent years.
This release also includes some architecture-specific assembler
improvements, and some (non-gold) linker enhancements.


guid: https://lwn.net/Articles/1007547/
title: Kernel prepatch 6.14-rc1
author: corbet
url: https://lwn.net/Articles/1007547/
feedurl: https://lwn.net/headlines/rss
content:
Linus has released <a href="https://lwn.net/Articles/1007546/">6.14-rc1</a> and closed the
merge window for this release.
<p>
<blockquote class="bq">
	This is actually a _tiny_ merge window, and that's ok. The holidays
	clearly meant that people did less development than during a normal
	cycle, and that then shows up as a much smaller-than-average
	release.  I really felt like this year we got the whole holiday
	season release timing right, and this is just another sign of that.
</blockquote>


guid: https://lwn.net/Articles/1007646/
title: Security updates for Monday
author: jake
url: https://lwn.net/Articles/1007646/
feedurl: https://lwn.net/headlines/rss
content:
Security updates have been issued by <b>AlmaLinux</b> (git-lfs, libsoup, and unbound), <b>Debian</b> (dcmtk, ffmpeg, openjdk-11, pam-u2f, and python-aiohttp), <b>Fedora</b> (buku, chromium, jpegxl, nodejs18, nodejs20, and rust-routinator), <b>Mageia</b> (clamav, kernel, kmod-virtualbox, kmod-xtables-addons &amp; dwarves, and kernel-linus), <b>SUSE</b> (apptainer, bind, buildah, chromedriver, clamav, dovecot24, ignition, kubelogin, libjxl, libQt5Bluetooth5-32bit, orc, owasp-modsecurity-crs, python-pydantic, python311-ipython, and stb), and <b>Ubuntu</b> (linux-azure and netdata).


guid: https://lwn.net/Articles/1007677/
title: What’s new in GTK, winter 2025 edition
author: jzb
url: https://lwn.net/Articles/1007677/
feedurl: https://lwn.net/headlines/rss
content:
<p>Matthias Clasen has written <a href="https://blog.gtk.org/2025/02/01/whats-new-in-gtk-winter-2025-edition/">a short update</a> on a GTK hackfest that
took place at <a href="https://fosdem.org/">FOSDEM</a> and what's
coming in GTK 4.18. This includes fixes for pointer sizes in Wayland
when fractional scaling is enabled, removal of the old GL renderer in
favor of the <a
href="https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/">GL
renderer</a> introduced in <a
href="https://download.gnome.org/sources/gtk/4.13/gtk-4.13.6.news">GTK
4.13.6</a>, and deprecation of X11 and Broadway backends with intent
to remove them in GTK 5.</p>

<p>The deprecated backends will remain available until then, and no
action is required by developers at this time, Clasen wrote: "<q>There
is no need to act on deprecations until you are actively porting your
app to the next major version of GTK, which is not on the horizon
yet</q>".</p>

<p></p>


guid: https://lwn.net/Articles/1006378/
title: [$] The rest of the 6.14 merge window
author: corbet
url: https://lwn.net/Articles/1006378/
feedurl: https://lwn.net/headlines/rss
content:
By the time that Linus Torvalds <a href="https://lwn.net/Articles/1007546/">released
6.14-rc1</a> and closed the merge window for this development cycle, some
9,307 non-merge changesets had been pulled into the mainline
repository — the lowest level of merge-window activity seen in years.
There were, nonetheless, a number of interesting changes in the
5,000 commits pulled since <a href="https://lwn.net/Articles/1005651/">the
first-half merge-window summary</a> was written.


guid: https://lwn.net/Articles/1007886/
title: Security updates for Tuesday
author: corbet
url: https://lwn.net/Articles/1007886/
feedurl: https://lwn.net/headlines/rss
content:
Security updates have been issued by <b>Debian</b> (openjdk-17), <b>Fedora</b> (chromium, fastd, ovn, and yq), <b>Mageia</b> (libxml2 and redis), <b>Oracle</b> (gstreamer1-plugins-base, gstreamer1-plugins-good), <b>Red Hat</b> (buildah, bzip2, galera, mariadb, grafana, keepalived, libsoup, mariadb:10.11, mariadb:10.5, mingw-glib2, podman, python-jinja2, and rsync), <b>SUSE</b> (bind, ignition, java-11-openjdk, java-17-openjdk, krb5, libxml2, openssl-1_1, orc, python-asteval, rsync, and xrdp), and <b>Ubuntu</b> (harfbuzz, libndp, libvpx, and opencv).


guid: https://lwn.net/Articles/1007887/
title: Firefox 135.0 released
author: corbet
url: https://lwn.net/Articles/1007887/
feedurl: https://lwn.net/headlines/rss
content:
<a href="https://www.mozilla.org/en-US/firefox/135.0/releasenotes/">Version
135.0</a> of the Firefox web browser has been released.  Changes include
more languages for the translations feature, increasing roll-out of the
credit-card autofill and AI chatbot features, and (perhaps most welcome):
<p>
<blockquote class="bq">
	Firefox now includes safeguards to prevent sites from abusing the
	history API by generating excessive history entries, which can make
	navigating with the back and forward buttons difficult by
	cluttering the history. This intervention ensures that such
	entries, unless interacted with by the user, are skipped when using
	the back and forward buttons.
</blockquote>


guid: https://lwn.net/Articles/1006375/
title: [$] An update on sealed system mappings
author: daroc
url: https://lwn.net/Articles/1006375/
feedurl: https://lwn.net/headlines/rss
content:
<p>
Jeff Xu has been working on
<a href="https://lwn.net/ml/all/20241125202021.3684919-1-jeffxu@google.com/">
a patch set</a> that makes certain mappings in a process's address space
impossible to change, sealing them against tampering. This has some potential
security benefits — mainly, making
sure that someone cannot relocate the
<a href="https://lwn.net/Articles/446528/">vsyscall and
vDSO mappings</a> — but some kernel developers haven't
been impressed with the patches.
While the core functionality (sealing the mappings) is sound, some of the
supporting code for enabling and disabling the new feature caused concern by
going against the normal design for such things. Reviewers also questioned
how this feature would interact with checkpointing and with sandboxing.
</p>


