Back in July, Paint.NET creator Rick Brewster said he was bringing the app to the Windows Store. That day has arrived.
“Paint.NET version 4.0.18, which I just announced, is now available on the Windows Store,” Mr. Brewster writes on the Paint.NET blog. “The standard price is currently $8.99, but I’ve put it on sale for $5.99 until the end of October. You can also make use of the 30-day free trial to get started.”
Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!
"*" indicates required fields
That there is a price at all has disappointed some: Paint.NET is available for free on the web, though Brewster requests that users show their appreciation for his work and support future development by donating.
“The Store release of Paint.NET is not distributed free-of-charge,” he explains. “This allows many things to converge and solves a lot of problems, while still providing value for new and existing users (err, customers?). The ‘Classic’ release will still be available and kept up-to-date on the same schedule as the Store release.”
So there you go. But as he notes, there are some important advantages to using the Store version of the app, aside from the usual karma-related stuff around paying for what you use and appreciate:
Background updating. Software updates are now “fully automatic and transparent,” Brewster says, ensuring that you will always be on the latest version of the app. The Classic version, by comparison, checks only once every 10 days.
Easier install. Once you own Paint.NET via the Store, it’s super-easy to get it installed on all your PCs. “Store apps also come with the wonderful advantage that they can’t install browser toolbars,” Brewster adds. “They can’t change your web browser’s homepage. They can’t do all sorts of things that would pollute your system. Store apps don’t get to provide their own installers full of sneaky check boxes that may or may not install various crapware. Paint.NET has never and will never do anything like that, but for many other apps it has been a very slippery slope over the years.”
Better reliability. Likewise, the Store version of Paint.NET uses the more reliable and modern Microsoft package manager and application model, and not the old-school MSI technology he uses for web distribution.
Aside from the Store advantages, Paint.NET version 4.0.18 offers 25 percent faster startup performance, per-user plug-in support, and other improvements.
You can find Paint.NET in the Windows Store. I highly recommend buying it: It’s a top-notch graphics app. And, remember, it’s only $5.99 right now, a $3 savings over the normal pricing.
skane2600
<blockquote><a href="#186312"><em>In reply to hrlngrv:</em></a></blockquote><p>Linux's installation approach is hardly a panacea for users or for developers.</p>
skane2600
<blockquote><a href="#186562"><em>In reply to hrlngrv:</em></a></blockquote><p>Cruft: "badly designed, unnecessarily complicated, or unwanted code or software"</p><p><br></p><p>Sure, none of those characteristics could ever apply to Linux or Linux programs, right? </p>
skane2600
<blockquote><a href="#186469"><em>In reply to William_Kempf:</em></a></blockquote><p>MS still charges a one-time registration fee. </p><p><br></p><p>Obviously we are going to discuss the broader issue of UWP vs Win32 here. Rick opened the door by discussing not just his own app, but by making general comments promoting UWP.</p>
skane2600
<blockquote><a href="#186259"><em>In reply to VancouverNinja:</em></a></blockquote><p>You have to consider both the middle man cost and the potential profits. MS is charging the same percentage as the other companies despite the fact that it's a less successful store. </p>
skane2600
<p>"Store apps also come with the wonderful advantage that they can’t install browser toolbars…" etc</p><p><br></p><p>I don't see the relevance of what some other Win32 programs do to the decision to buy or not buy the store version of Paint.NET</p>
skane2600
<blockquote><a href="#186309"><em>In reply to hrlngrv:</em></a></blockquote><p>It would still require manual examination. In general the OS doesn't know whether a component is being installed to affect other applications or its own because it doesn't know what all the applications are and what they do. They are also legitimate cases where changing settings of other applications is exactly the purpose of the program and the user intended it to do so. It would be dumb to have multiple UACs triggered in that case.</p><p><br></p><p>Besides the users who don't pay attention to default checkboxes in an installer are also likely to just click through any UACs that pop up.</p>
skane2600
<blockquote><a href="#186242"><em>In reply to hrlngrv:</em></a></blockquote><p>Totally impractical. They'd either have to eliminate installers entirely or manually review each and every installer in the world to determine if it installs "crapware" (which has no crisp technical definition).</p><p><br></p><p>In any case, still irrelevant to Paint.NET unless the Win32 version is designed to perform these negative behaviors on installation.</p>
skane2600
<blockquote><a href="#186310"><em>In reply to hrlngrv:</em></a></blockquote><p>As I said, it could trigger additional annoyance UACs for programs that are designed to legitimately change those settings. I know, I've written such programs for clients to perform the function who paid me to implement.</p>