It could, but it could also cause a resurgence of better casual typefaces, such as Comic Neue, JollyGood Sans, or Filmotype Apache/August/Beaver (digitized as Jester, Cochise, URW Apache, and Panache Stanley/Sixpack).
But in Windows-land, people just sit around and bitch and complain, while continuing to send their money to Microsoft.
This is probably because a lot of businesses are so invested in Windows that sending a small amount of money to Microsoft would be less expensive than either A. sending a larger amount of money to the ReactOS project to bring it up to parity with Windows in the areas about which the business cares, or B. spending a larger amount of money switching to an existing non-Microsoft stack on all of its own systems while somehow retaining interoperability with its suppliers that use a Microsoft stack (e.g. files in.xlsm,.mdb, or.accdb format).
In practice, how hard is it to avoid circular references using a combination of std::shared_ptr and std::weak_ptr? Besides, if you have circular references in any other language, in what order should the language call the objects' finalizers? Not calling them at all breaks the RAII idiom. Or what idiom is superior to RAII for ownership whose lifetime exceeds that of a single try statement?
Let me try to address it from a different angle: Does any fiat or cryptographic currency have a use value apart from its exchange value? Gold does. In real life, it's used to plate electrical connectors. But I'll grant that use value isn't the only thing that lends stability to exchange value.
Back in 2008, before the Twitter.com microblog service took off, Slashdot had an active user named twitter. This twitter was notorious for using alternate "sockpuppet" accounts to post his pro-GNU/Linux, anti-"M$" screeds and attack some who disagreed with his message or methods.
If you don't remember twitter, you must be new here. [notices UID 2881349 and login through Twitter.com] Now I understand. Twitter the sockpuppeteer mostly stopped posting before you joined.
Perform early testing, while the program is under rapid development, with smaller translation units, and later testing, after most of the functionality has become stable, with larger translation units. That's not the same as shipping untested binaries. Also run both the program with smaller translation units and the program with larger translation units in parallel, and consider it a defect if there is any difference in behavior between the two other than execution time.
The fact that you have to install a cross-compiler for that particular (language, architecture) pair. For some less popular architectures, compilers accepting languages other than a handful (C++, C, and possibly Fortran) happen not to exist.
Then use smaller translation units for debug builds and larger ones for release builds. If you use a laptop or compact desktop for your debug builds, you may have to use a full-size desktop or server for release builds.
Until the headers themselves change, causing a cascade throughout all source files that instantiate a class or its subclasses because of C++'s fragile base class tendency.
and set up your makefiles for multiple cores.
There are known limits of GNU Make when you have a single program that spits out more than one file. For example, a graphic may be converted for use on a particular platform by decomposing it into a tile file and a map file. Or a collection of documents may be compressed into a static dictionary and a (separate) archive of the compressed documents. The problem is that Make will often try to run the program twice at once, once to produce the tile file and once for the map file, wasting CPU. What's the typical workaround? Is it a good practice to have the program generate an archive file containing both files, and then generate the tile file and map file by extracting them from the archive file?
Besides, link-time whole-program optimization doesn't parallelize nearly as well.
So instead of compiling and linking the entire application repeatedly as you track down a bug, you only integrate after all your unit tests are written and passed in isolation.
Which doesn't help when the bug is in the integration.
I say run the meter when the connection is congested and stop running it when it's underutilized. That's what satellite does, with cap-free early mornings.
Between Amazon Prime Video, Netflix, Hulu, etc. there is no longer a reason to pirate anything
Anything? Let me know when the film Song of the South, the film Pinocchio and the Emperor of the Night, or the TV series Spartakus and the Sun Beneath the Sea becomes lawfully available in the United States on streaming or even on DVD.
A "get onto our cloud" jingle sounds plausible given the music choice Microsoft made for the Windows 95 ad campaign two decades ago. It makes a grown man cry.
I comment on about three different Twitter handles
You should have been around back in 2008. There was this one twitter guy who was commenting on a dozen handles, praising GNU/Linux and slamming what he called "M$".
From a usability engineering perspective, people who sign up for a Twitter account are its users. This includes @Erris, @gnutoo, @inTheLoo, @westbake, @Odder, @ibane, @deadzero, @freenix, @right_handed, and @trimmer.* But from a business perspective, they are not its customers; advertisers are.
But have you managed to get this far without Erris, Mactrope, gnutoo, inTheLoo, willeyhill, westbake, Odder, ibane, deadzero, freenix, myCopyWrong, right handed, GNUChop, and the rest of the gang?
Slashdot Mirror
It could, but it could also cause a resurgence of better casual typefaces, such as Comic Neue, JollyGood Sans, or Filmotype Apache/August/Beaver (digitized as Jester, Cochise, URW Apache, and Panache Stanley/Sixpack).
But in Windows-land, people just sit around and bitch and complain, while continuing to send their money to Microsoft.
This is probably because a lot of businesses are so invested in Windows that sending a small amount of money to Microsoft would be less expensive than either A. sending a larger amount of money to the ReactOS project to bring it up to parity with Windows in the areas about which the business cares, or B. spending a larger amount of money switching to an existing non-Microsoft stack on all of its own systems while somehow retaining interoperability with its suppliers that use a Microsoft stack (e.g. files in .xlsm, .mdb, or .accdb format).
In practice, how hard is it to avoid circular references using a combination of std::shared_ptr and std::weak_ptr? Besides, if you have circular references in any other language, in what order should the language call the objects' finalizers? Not calling them at all breaks the RAII idiom. Or what idiom is superior to RAII for ownership whose lifetime exceeds that of a single try statement?
Let me try to address it from a different angle: Does any fiat or cryptographic currency have a use value apart from its exchange value? Gold does. In real life, it's used to plate electrical connectors. But I'll grant that use value isn't the only thing that lends stability to exchange value.
Back in 2008, before the Twitter.com microblog service took off, Slashdot had an active user named twitter. This twitter was notorious for using alternate "sockpuppet" accounts to post his pro-GNU/Linux, anti-"M$" screeds and attack some who disagreed with his message or methods.
If you don't remember twitter, you must be new here.
[notices UID 2881349 and login through Twitter.com]
Now I understand. Twitter the sockpuppeteer mostly stopped posting before you joined.
Perform early testing, while the program is under rapid development, with smaller translation units, and later testing, after most of the functionality has become stable, with larger translation units. That's not the same as shipping untested binaries. Also run both the program with smaller translation units and the program with larger translation units in parallel, and consider it a defect if there is any difference in behavior between the two other than execution time.
The fact that you have to install a cross-compiler for that particular (language, architecture) pair. For some less popular architectures, compilers accepting languages other than a handful (C++, C, and possibly Fortran) happen not to exist.
you just cannot implement an efficient garbage collector in C/++.
Then what's std::shared_ptr if not an efficient reference counting garbage collector?
For any type with a size less than 29 bits the behavior is undefined. [...] For signed types it is implementation defined.
But what is it for uint32_t x = 0xdeadbeef;?
First focus on quickly achieving correctness, and then add efficiency once the program is correct.
Sadly, there are many tests that pass when software is built with GCC but fail (sometimes even segfault) when the same software is built with clang.
Have you reported each such test to the respective project's bug tracker?
Then use smaller translation units for debug builds and larger ones for release builds. If you use a laptop or compact desktop for your debug builds, you may have to use a full-size desktop or server for release builds.
You should be using precompiled headers
Until the headers themselves change, causing a cascade throughout all source files that instantiate a class or its subclasses because of C++'s fragile base class tendency.
and set up your makefiles for multiple cores.
There are known limits of GNU Make when you have a single program that spits out more than one file. For example, a graphic may be converted for use on a particular platform by decomposing it into a tile file and a map file. Or a collection of documents may be compressed into a static dictionary and a (separate) archive of the compressed documents. The problem is that Make will often try to run the program twice at once, once to produce the tile file and once for the map file, wasting CPU. What's the typical workaround? Is it a good practice to have the program generate an archive file containing both files, and then generate the tile file and map file by extracting them from the archive file?
Besides, link-time whole-program optimization doesn't parallelize nearly as well.
So instead of compiling and linking the entire application repeatedly as you track down a bug, you only integrate after all your unit tests are written and passed in isolation.
Which doesn't help when the bug is in the integration.
Oh, Internet. What has happened to you?
Oh Internet tried to kill Encyclopædia Dramatica, but it failed as it was stricken down to the ground.
I say run the meter when the connection is congested and stop running it when it's underutilized. That's what satellite does, with cap-free early mornings.
Between Amazon Prime Video, Netflix, Hulu, etc. there is no longer a reason to pirate anything
Anything? Let me know when the film Song of the South, the film Pinocchio and the Emperor of the Night, or the TV series Spartakus and the Sun Beneath the Sea becomes lawfully available in the United States on streaming or even on DVD.
A "get onto our cloud" jingle sounds plausible given the music choice Microsoft made for the Windows 95 ad campaign two decades ago. It makes a grown man cry.
Seattle, Washington, has outdated wiring plus excessive red tape for access to rights of way.
The issue expressed in the comic to which you refer has since been addressed through the HBO Now service.
Can we please stop using the "uhhhhh" sound to replace the word "you"?
Sure, if you can get nearly 17 million Dutch to agree to it.
I comment on about three different Twitter handles
You should have been around back in 2008. There was this one twitter guy who was commenting on a dozen handles, praising GNU/Linux and slamming what he called "M$".
How much does it cost to make my post more important?
At the bottom of every page on Twitter is a link to Ads info, which teaches how Promoted Tweets work.
From a usability engineering perspective, people who sign up for a Twitter account are its users. This includes @Erris, @gnutoo, @inTheLoo, @westbake, @Odder, @ibane, @deadzero, @freenix, @right_handed, and @trimmer.* But from a business perspective, they are not its customers; advertisers are.
* Why these accounts?
I think the idea is to put your microblog on Pump or GNU Social and mirror that to Twitter. It's what @fsf does.
But have you managed to get this far without Erris, Mactrope, gnutoo, inTheLoo, willeyhill, westbake, Odder, ibane, deadzero, freenix, myCopyWrong, right handed, GNUChop, and the rest of the gang?