FreshRSS

🔒
❌ About FreshRSS
There are new available articles, click to refresh the page.
Before yesterdayYour RSS feeds

Samsung Software Engineers Busted For Pasting Proprietary Code Into ChatGPT

By: BeauHD
Multiple employees of Samsung's Korea-based semiconductor business plugged lines of confidential code into ChatGPT, effectively leaking corporate secrets that could be included in the chatbot's future responses to other people around the world. PCMag reports: One employee copied buggy source code from a semiconductor database into the chatbot and asked it to identify a fix, according to The Economist Korea. Another employee did the same for a different piece of equipment, requesting "code optimization" from ChatGPT. After a third employee asked the AI model to summarize meeting notes, Samsung executives stepped in. The company limited each employee's prompt to ChatGPT to 1,024 bytes. Just three weeks earlier, Samsung had lifted its ban on employees using ChatGPT over concerns around this issue. After the recent incidents, it's considering re-instating the ban, as well as disciplinary action for the employees, The Economist Korea says. "If a similar accident occurs even after emergency information protection measures are taken, access to ChatGPT may be blocked on the company network," reads an internal memo. "As soon as content is entered into ChatGPT, data is transmitted and stored to an external server, making it impossible for the company to retrieve it." The OpenAI user guide warns users against this behavior: "We are not able to delete specific prompts from your history. Please don't share any sensitive information in your conversations." It says the system uses all questions and text submitted to it as training data.

Read more of this story at Slashdot.

'Docker is Deleting Open Source Organisations'

By: msmash
Alex Ellis: Earlier this month, Docker sent an email to any Docker Hub user who had created an "organisation", telling them their account will be deleted including all images, if they do not upgrade to a paid team plan. The email contained a link to a tersely written PDF (since, silently edited) which was missing many important details which caused significant anxiety and additional work for open source maintainers. As far as we know, this only affects organisation accounts that are often used by open source communities. There was no change to personal accounts. Free personal accounts have a a 6 month retention period. Why is this a problem? 1. Paid team plans cost 420 USD per year (paid monthly) 2. Many open source projects including ones I maintain have published images to the Docker Hub for years 3. Docker's Open Source program is hostile and out of touch Why should you listen to me? I was one of the biggest advocates around for Docker, speaking at their events, contributing to their projects and being a loyal member of their voluntary influencer program "Docker Captains". I have written dozens if not hundreds of articles and code samples on Docker as a technology. I'm not one of those people who think that all software and services should be free. I pay for a personal account, not because I publish images there anymore, but because I need to pull images like the base image for Go, or Node.js as part of my daily open source work. When one of our OpenFaaS customers grumbled about paying for Docker Desktop, and wanted to spend several weeks trying to get Podman or Rancher Desktop working, I had to bite my tongue. If you're using a Mac or a Windows machine, it's worth paying for in my opinion. But that is a different matter. Having known Docker's new CTO personally for a very long time, I was surprised how out of touch the communication was. More: Docker: We apologize. We did a terrible job announcing the end of Docker Free Teams..

Read more of this story at Slashdot.

Go Finally Returns to Top 10 of Programming Language Popularity List

"Google's Go language has re-entered the top 10 of the Tiobe index of programming language popularity, after a nearly six-year absence," reports InfoWorld: Go ranks 10th in the March edition of the index, after placing 11th the previous month. The language last appeared in the top 10 in July 2017. The re-emergence of Go in the March 2023 index is being attributed to its popularity with software engineers and its strength in combining the right features, namely built-in concurrency, garbage collection, static typing, and good performance. Google's backing also helps, improving long-term trust in the language, Tiobe said. The languages Go beat out include "assembly language" at #11, followed by MATLAB, Delphi/Object Pascal, Scratch, and Classic Visual Basic. Here's the complete top-ten most popular programming languages, according to TIOBE: Python C Java C++ C# Visual Basic JavaScript SQL PHP Go

Read more of this story at Slashdot.

Meet Zig: the Modern Alternative to the C Programming Language

Systems-oriented developers already have programming languages like C, C++, Rust, and Go, notes InfoWorld. But now, "we also have Zig, a newer language that seeks to absorb what's best about these languages and offer comparable performance with a better, more reliable developer experience." Zig is a very active project. It was started by Andrew Kelley in 2015 and now seems to be reaching critical mass. Zig's ambition is rather momentous in software history: to become the heir to C's longstanding reign as both the go-to portable low-level language and as a standard to which other languages are compared.... Currently, Zig is being used to implement the Bun.js JavaScript runtime as an alternative to Node.js. Bun's creator Jarred Sumner told me "Zig is sort of similar to writing C, but with better memory safety features in debug mode and modern features like defer (sort of similar to Go's) and arbitrary code can be executed at compile-time via comptime. It has very few keywords so it's a lot easier to learn than C++ or Rust." Zig differs from most other languages in its small feature footprint, which is the outcome of an explicit design goal: Only one obvious way to do things. Zig's developers take this goal so much to heart that for a time, Zig had no for loop, which was deemed an unnecessary syntactic elaboration upon the already adequate while loop. Kevin Lynagh, coming from a Rust background, wrote, "The language is so small and consistent that after a few hours of study I was able to load enough of it into my head to just do my work." Nathan Craddock, a C developer, echoed the sentiment. Programmers seem to really like the focused quality of Zig's syntax. While Zig is "approaching" production-ready status, the article notes its high degree of interoperability with C and C++, its unique error-handling system, and its elimination of a malloc keyword (leaving memory allocation to the standard library). "For now, the Zig team appears to be taking its time with the 1.0 release, which may drop in 2025 or later — but none of that stops us from building all sorts of things with the language today."

Read more of this story at Slashdot.

cURL, the omnipresent data tool, is getting a 25th birthday party this month

Two men curling in blurry motion photo

Enlarge / Curling, like the cURL project, requires precision and is underappreciated.

When you first start messing with the command line, it can feel like there's an impermeable wall between the local space you're messing around in and the greater Internet. On your side, you've got your commands and files, and beyond the wall, there are servers, images, APIs, webpages, and more bits of useful, ever-changing data. One of the most popular ways through that wall has been cURL, or "client URL," which turns 25 this month.

The cURL tool started as a way for programmer Daniel Stenberg to let Internet Chat Relay users quickly fetch currency exchange rates while still inside their chat window. As detailed in an archived history of the project, it was originally built off an existing command-line tool, httpget, built by Rafael Sagula. A 1.0 version was released in 1997, then changed names to urlget by 2.0, as it had added in GOPHER, FTP, and other protocols. By 1998, the tool could upload as well as download, and so version 4.0 was named cURL.

Over the next few years, cURL grew to encompass nearly every Internet protocol, work with certificates and encryption, offer bindings for more than 50 languages, and be included in most Linux distributions and other systems. The cURL project now encompasses both the command-line command itself and the libcurl library. In 2020, the project's history estimated the command and library had been installed in more than 10 billion instances worldwide.

Read 2 remaining paragraphs | Comments

By: ayjay

The Art of Computational Narrative – by Samuel Arbesman:

Perhaps there are specific features of computer programs that might be (a tiny bit) like prose. For example, just as literary texts have specific properties and rhythms, it could be useful to compare programming languages based on their literary properties. Is there a rhythm to a Python program, or something written in Lisp? And what are the nuances behind keyword choices within each programming language? For despite the limitations on syntax and vocabulary that each language contains, the resulting code may have a particular expressive power.

Ask Slashdot: What's the Best Podcast About Computer Science?

Long-time Slashdot reader destinyland writes: They say "always be learning" — but do podcasts actually help? I've been trying to find podcasts that discuss programming, and I've enjoyed Lex Fridman's interviews with language creators like Guido van Rossum, Chris Lattner, and Brendan Eich (plus his long interviews with Donald Knuth). Then I discovered that GitHub, Red Hat, Stack Overflow, and the Linux Foundation all have their own podcast. There's a developer podcast called "Corecursive" that I like with the tagline "the stories behind the code," plus a whole slew of (sometimes language-specific) podcasts at Changelog (including an interview with Brian Kernighan). And it seems like there's an entirely different universe of content on YouTube — like the retired Microsoft engineer doing "Dave's Garage," Software Engineering Daily, and the various documentaries by Honeypot.io. Computerphile has also scored various interviews with Brian Kernighan, and if you search YouTube enough you'll find stray interviews with Steve Wozniak. But I wanted to ask Slashdot's readers: Do you listen to podcasts about computer science? And if so, which ones? (Because I'm always stumbling across new programming podcasts, which makes me worry about what else I've been missing out on.) Maybe I should also ask if you ever watch coding livestreams on Twitch — although that gets into the more general question of just how much content we consume that's related to our profession. Fascinating discussions, or continuing work-related education? (And do podcasts really help keep your skills fresh? Are coding livestreams on Twitch just a waste of time?) Most importantly, does anyone have a favorite geek podcast that they're listening to? Share your own experience and opinions in the comments... What's the best podcast about computer science?

Read more of this story at Slashdot.

GCC Gets a New Frontend for Rust

Slashdot reader sleeping cat shares a recent FOSDEM talk by a compiler engineer on the team building Rust-GCC, "an alternative compiler implementation for the Rust programming language." "If gccrs interprets a program differently from rustc, this is considered a bug," explains the project's FAQ on GitHub. The FAQ also notes that LLVM's set of compiler technologies — which Rust uses — "is missing some backends that GCC supports, so a gccrs implementation can fill in the gaps for use in embedded development." But the FAQ also highlights another potential benefit: With the recent announcement of Rust being allowed into the Linux Kernel codebase, an interesting security implication has been highlighted by Open Source Security, inc. When code is compiled and uses Link Time Optimization (LTO), GCC emits GIMPLE [an intermediate representation] directly into a section of each object file, and LLVM does something similar with its own bytecode. If mixing rustc-compiled code and GCC-built code in the Linux kernel, the compilers will be unable to perform a full link-time optimization pass over all of the compiled code, leading to absent CFI (control flow integrity). If Rust is available in the GNU toolchain, releases can be built on the Linux kernel (for example) with CFI using LLVM or GCC. Started in 2014 (and revived in 2019), "The effort has been ongoing since 2020...and we've done a lot of effort and a lot of progress," compiler engineer Arthur Cohen says in the talk. "We have upstreamed the first version of gccrs within GCC. So next time when you install GCC 13 — you'll have gccrs in it. You can use it, you can start hacking on it, you can please report issues when it inevitably crashes and dies horribly." "One big thing we're doing is some work towards running the rustc test suite. Because we want gccrs to be an actual Rust compiler and not a toy project or something that compiles a language that looks like Rust but isn't Rust, we're trying really hard to get that test suite working." Read on for some notes from the talk...

Read more of this story at Slashdot.

Whatever Happened to the Ruby Programming Language?

Three years after Rails was introduced in 2005, InfoWorld asked whether it might the successor to Java. That didn't happen. So this week InfoWorld "spoke to current and former Ruby programmers to try to trace the language's rise and fall." Some responses: "Rails came along at the cusp of a period of transformation and growth for the web," says Matthew Boeh, a Ruby developer since 2006. "It both benefited from and fueled that growth, but it was a foregone conclusion that it wasn't going to be the only success story." Boeh recently took a job as a senior staff software engineer at Lattice, a TypeScript shop. "You could say that Ruby has been a victim of its own success, in that its community was a major driving force in the command-line renaissance of recent years," he says. "In the early '00s it was introducing REPL-driven development to people who had never heard of Lisp, package management to people who would have been scared off by Perl's CPAN, test-driven development to people outside the highly corporate Java world, and so on. This is all stuff that is considered table stakes today. Ruby didn't originate any of it, but it was all popularized and made accessible by Rubyists...." "The JavaScript ecosystem in its current form would have been unimaginable in 2004 — it needed both the command line renaissance and the takeoff of the web platform," adds Lattice's Boeh. "Did you know it took a full decade, 1999 to 2009, to release a single new version of the JavaScript standard? We get one yearly now. Rails became a big deal in the very last time period where it was possible to be a full-stack developer without knowing JavaScript...." [W]hen it comes to data science, Python has a leg up because of the ready availability of libraries like TensorFlow and Keras. "These frameworks make it easy for coders to build data visualizations and write programs for machine learning," says Pulkit Bhardwaj, e-commerce coach at BoutiqueSetup.net. JavaScript, meanwhile, has spawned seemingly endless libraries that developers can easily download and adapt for just about any purpose. "As a technologist, you can go on your own hero's journey following whatever niche thing you think is the right way to go," says Trowbridge. But when it comes to JavaScript, "these libraries are excellent. Why ignore all of that?" Many of those libraries were developed by community members, which inspired others to contribute in a snowball effect familiar to anyone involved in open source. But one big player has had an outsized influence here. Python's TensorFlow, which Bhardwaj called a "game-changer," was released by Google, which has followed academia's lead and made Python its internal scripting language. Google, as the maker of the dominant web browser, also has an obvious interest in boosting JavaScript, and Trowbridge gives Google much of the credit for making JavaScript much faster and more memory efficient than it once was: "In some ways it feels almost like a low level language," he says. Meanwhile, Ruby is widely acknowledged to be lagging in performance, in part because it lacks the same sort of corporate sponsor with resources for improving it.

Read more of this story at Slashdot.

A Developer is Reimplementing GNU's Core Utilities in Rust

A Rust-based re-implementation of GNU core utilities like cp and mv is "reaching closer to parity with the widely-used GNU upstream and becoming capable of taking on more real-world uses," reports Phoronix: Debian developer Sylvestre Ledru [also an engineering director at Mozilla] began working on uutils during the COVID-19 pandemic and presented last week at FOSDEM 2023 on his Coreutils replacement effort. With uutils growing into increasingly good shape, it's been packaged up by many Linux distributions and is also used now by "a famous social network via the Yocto project...." The goals with uutils are to try to create a drop-in replacement for GNU Coreutils, strive for good cross-platform support, and easy testing. Ledru's initial goals were about being able to boot Debian, running the most popular packages, building key open-source software, and all-around it's been panning out to be a great success.... [M]ore performance optimizations are to come along with other work for compatibility against the GNU tools and implementing some still missing options in different programs

Read more of this story at Slashdot.

Under Microsoft, GitHub Reaches 100M-Developer Milestone

"Code-hosting platform GitHub has announced that 100 million developers are now using the platform," reports TechCrunch: The figure represents a substantial hike on the 3 million users GitHub counted 10 years ago, the 28 million it claimed when Microsoft acquired it for $7.5 billion five years ago and the 90 million-plus it revealed just three months ago. GitHub has come a long way since its launch back in 2008, and now serves as the default hosting service for millions of open source and proprietary software projects, allowing developers to collaborate around shared codebases from disparate locations. GitHub's announcement argues that "From creating the pull request to empowering developers with AI through GitHub Copilot, everything we do has been to put the developer first." But TechCrunch notes that GitHub's various paid plans "now contribute around $1 billion annually to [Microsoft's] coffers."

Read more of this story at Slashdot.

The best midrange smartphones for 2023

As one of Engadget’s resident mobile geeks, I’ve reviewed dozens of midrange phones and have found that a great smartphone doesn’t have to cost a fortune. Years of commoditization have brought features once exclusive to high-end devices – including big batteries, multi-camera arrays and high refresh rate displays – down to their more affordable siblings. If your budget is less than $600, I can help you figure out what features to prioritize when trying to find the best midrange phone for the money.

What is a midrange phone, anyway?

While the term shows up frequently in articles and videos, there isn’t an agreed-upon definition for “midrange” beyond a phone that isn’t a flagship or an entry-level option. For this guide, our recommendations for the best phone in this category cost between $400 and $600. Any less and you should expect significant compromises. If your budget is higher, though, you should consider flagships like the Apple iPhone 13 and Samsung Galaxy S22.

What factors should you consider when buying a midrange smartphone?

Buying a new device can be intimidating, but a few questions can help guide you through the process. First: what platform do you want to use? If the answer is iOS, that narrows your options down to exactly one phone. (Thankfully, it’s great.) And if you’re an Android fan, there’s no shortage of compelling options. Both platforms have their strengths, so you shouldn’t rule either out.

Obviously, also consider how much you’re comfortable spending. Even increasing your budget by $100 more can get you a dramatically better product. And manufacturers tend to support their more expensive devices for longer. It’s definitely worth buying something toward the top limit of what you can afford.

Having an idea of your priorities will help inform your budget. Do you want a long battery life? Do you value speedy performance above all else? Or would you like the best possible cameras? While they continue to improve every year, midrange phones still involve some compromises, and knowing what’s important to you will make choosing one easier.

Lastly, pay attention to wireless bands and network compatibility. If you don’t want to worry about that, your best bet is to buy directly from your carrier. To make things easier, all the phones we recommend are compatible with every major US wireless provider and can be purchased unlocked. 

What won’t you get from a midrange smartphone?

Every year, the line between midrange and flagship phones gets blurrier as more upmarket features trickle down. When we first published this guide in 2020, it was difficult to find $500 devices with waterproofing or 5G. Now, the biggest thing you might miss out on is wireless charging. Just remember to budget for a power adapter too – many companies have stopped including them. Performance has improved in recent years, but can still be hit or miss as most midrange phones use slower processors that can struggle with multitasking. Thankfully, their cameras have improved dramatically, and you can typically expect at least a dual-lens system on most midrange smartphones below $600.

The best midrange Android phone: Pixel 6a

There’s a lot to like about Google's Pixel 6a. For one, the Pixel 6a features the best cameras at this price. It may not have as many lenses as some of the other options on this list, but thanks to Google’s expertise in computational photography, the 6a delivers pictures that are on par with phones that cost hundreds more. Nighttime photos in particular are stellar thanks in part to Night Sight, which helps brighten up dim environments and bring out more detail.

The Google Pixel 6a has a few other things going for it. Thanks to its large battery and efficient chipset, you won’t have to worry about running out of juice. It lasted just over 19 hours in our battery testing, and Google's Tensor chipset allows the 6a to run very similarly to the Pixel 6 and 6 Pro handsets. And those who plan to hang on to their smartphone for as long as possible will appreciate that Google plans to support the 6a with software updates for the next five years.

In addition to its solid battery life and performance, the Google Pixel 6a even has some advanced features you may not expect to see on a midrange phone. Its design looks very similar to the flagship models with the striking camera bar on the handset's rear top half, and it has a 2,400 x 1,080 resolution OLED touchscreen with an under-display fingerprint sensor. You'll only get a refresh rate of 60Hz on the 6a, but that's a small sacrifice to make when you're getting a number of other features at a killer price.

The best (and only) iPhone under $600: iPhone SE

If you can get past its dated design and small 5.4-inch display, the Apple iPhone SE is the fastest phone you can buy for less than $600. No other device on this list has a processor that comes close to the SE’s A15 Bionic. What’s more, you can expect Apple to support the 2022 model for years to come. The company is only just ending support for the first-generation SE after six years. The company hasn’t said how long it intends to furnish the latest SE with new software, but it’s likely to support the device for a similar length of time.

For all its strengths, the iPhone SE is held back by a dated display. Not only is the SE’s screen small and slow, but it also uses an IPS panel instead of an OLED, meaning it can’t deliver deep blacks. Additionally, that screen is surrounded by some of the largest bezels you’ll find on a modern phone. That’s not surprising. The SE uses the design of the iPhone 6, which will be a decade old in two years. And if the SE looks dated now, it will only feel more tired in a few years.

The midrange phone with the best screen: Samsung Galaxy A53 5G

For the best possible display at this price, look no further than Samsung’s $450 Galaxy A53 5G. It features a 6.5-inch Super AMOLED display that is ideal for watching TV shows and movies. Plus the 120Hz panel is the fastest on this list. Other standout features of this Samsung phone include a 5,000mAh battery and versatile camera system. The A53’s three cameras may not deliver photos with the same detail and natural colors as the Pixel 6a, but it can capture bigger scenes with its two wide-angle lenses.

Like the other Android smartphones on this list, the Samsung Galaxy A53 isn’t the fastest performer. At best, Samsung’s Exynos 1280 is a lateral move from the Qualcomm Snapdragon 750G found in the Galaxy A52 5G. And though the A53 is $50 cheaper than its predecessor, this Samsung phone no longer comes with a power adapter and headphone jack, so the difference may not end up being much.

An ultra-budget 5G option: OnePlus Nord N200 5G

If you only have around $200 to spend on your next phone, you could do a lot worse than the OnePlus Nord N200. To start, this budget phone features a big 5,000mAh battery that will easily last you a full day. The N200 also has a 90Hz display and 5G connectivity, which are tricky to find at this price. Best of all, it doesn’t look like a cheap phone.

But the N200 is also a good illustration of why you should spend more on a budget phone if you can. It's the slowest device on this list, due to its Snapdragon 480 chipset and paltry 4GB of RAM. Its triple main camera system is serviceable during the day but struggles in low light and doesn’t offer much versatility beyond a disappointing macro lens. OnePlus also doesn’t plan to update the phone beyond the soon-to-be-outdated Android 12. In short, the N200 is unlikely to last you as long as any of the other recommendations on this list.

Chris Velazco contributed to this report.

Pixel 6a colors

Top down view of the sage and white Pixel 6a next to each other, on top of book on a wooden surface.

Extensions are Easily Impersonated in Microsoft's VSCode Marketplace, Researchers Say

74.48% of developers use Microsoft's Visual Studio Code, according to one survey conducted by StackOverflow. And besides GitHub Copilot, there's over 40,000 other extensions in the VSCode Marketplace. Unfortunately, InfoWorld reports, "Researchers at Aqua Nautilus say they have found that attackers could easily impersonate popular extensions and trick unknowing developers into downloading them." It can be challenging to distinguish between malicious and benign extensions, and the lack of sandbox capabilities means that extensions could install ransomware, wipers, and other malicious code, Aqua security researcher Ilay Goldman wrote in a January 6 blog post. ["In fact, it can access and even alter all the code that you have locally and even use your SSH key to change the code in all your organization's repositories."] VS Code extensions, which provide capabilities ranging from Python language support to JSON file editing, can be downloaded from Microsoft's Visual Studio Code Marketplace. Aqua Nautilus uploaded an extension masquerading as the Prettier code formatter and saw more than 1,000 installs in less than 48 hours, from around the world. The spoof extension has been removed. Goldman noted that the Visual Studio Code Marketplace runs a virus scan for each new extension and subsequent updates, and removes malicious extensions when it finds them. Users can report suspicious-looking extensions via a Report Abuse link. "While the media is full of stories about malicious packages that have been uploaded to popular package managers such as NPM and PyPI, there is very little information about malicious VSCode extension," the blog post notes. Yet it points out that a blue checkmark on a VSCode extension "merely means that whoever the publisher is has proven the ownership of a domain. That means any domain." And even Microsoft acknowledged to InfoWorld that social engineering techniques have been used to persuade victims to download malicious extensions — though they point out that Microsoft confirms that each extension has a Marketplace certificate and verifiable signature before being installed. "To help make informed decisions, we recommend consumers review information, such as domain verification, ratings and feedback to prevent unwanted downloads."

Read more of this story at Slashdot.

Rust Safety Is Not Superior To C++, Bjarne Stroustrup Says

guest reader writes: The Open Standards site contains a new paper from Bjarne Stroustrup titled A call to action: Think seriously about "safety"; then do something sensible about it. Bjarne reacts to an NSA report about Software Memory Safety since the report excludes C and C++ as unsafe. Bjarne does not consider any of the report's choices for "safe" languages as superior to C++ for the range of uses he cares about. From Bjarne's response: I have worked for decades to make it possible to write better, safer, and more efficient C++. In particular, the work on the C++ Core Guidelines specifically aims at delivering statically guaranteed type-safe and resource-safe C++ for people who need that without disrupting code bases that can manage without such strong guarantees or introducing additional tool chains. For example, the Microsoft Visual Studio analyzer and its memory-safety profile deliver much of the CG support today and any good static analyzer (e.g., Clang tidy, that has some CG support) could be made to completely deliver those guarantees at a fraction of the cost of a change to a variety of novel "safe" languages. Bjarne also complains that in the NSA's document, "'safe' is limited to memory safety, leaving out on the order of a dozen other ways that a language could (and will) be used to violate some form of safety and security." There is not just one definition of "safety", and we can achieve a variety of kinds of safety through a combination of programming styles, support libraries, and enforcement through static analysis.... I envision compiler options and code annotations for requesting rules to be enforced. The most obvious would be to request guaranteed full type-and-resource safety. Bjarne notes that if you work in application domains which prioritize performance over type safety, you could "apply the safety guarantees only where required and use your favorite tuning techniques where needed." Partial adoption of some of the rules (e.g., rules for range checking and initialization) is likely to be important. Gradual adoption of safety rules and adoption of differing safety rules will be important. If for no other reason than the billions of lines of C++ code will not magically disappear, and even "safe" code (in any language) will have to call traditional C or C++ code or be called by traditional code that does not offer specific safety guarantees. Ignoring the safety issues would hurt large sections of the C++ community and undermine much of the other work we are doing to improve C++. The article also contains the following references for consideration:- Design Alternatives for Type-and-Resource Safe C++.- Type-and-resource safety in modern C++.- A brief introduction to C++'s model for type- and resource-safety.- C++ Core Guidelines, safety profiles.

Read more of this story at Slashdot.

❌