What kind of Internet connection would you prefer to have it use to download updates? You may trust your local network, but that network's connections to the wider Internet should not be inherently trustworthy. Even if you more or less trust your ISP, do you really know all the networks that packets traverse on their way to the server? This is why things like https and package signing were invented. As long as the update was properly signed (in this case by Microsoft, but most Linux distributions do the same thing for their packages) and the signature is verified before applying (and this is really important), then it doesn't matter what network it was used to download it.
At least as far as security is concerned. If it downloaded a large amount of data through a cell phone hotspot causing a large bill, that could certainly be a problem!
My corporate supplied computer at work doesn't have many settings to change.
And I have never associated Windows with performance. Unless it is "poor" performance. As a simple example, the software I develop at work takes about 4 hours to completely build and test on Linux. It takes about 60 hours to do the same on Windows. And that is after copying every single needed file to the local hard drive (while Linux gets almost everything from the network). By the time Linux is done, Windows is about half way through cleaning. Now a lot of this poor performance is probably from the shear amount of spyware installed on the system (by corporate) to monitor everything that goes on. But since you have to run that sort of monitoring software on Windows, even if it is only a virus scanner, Windows will always be slower than Linux. So "Ultimate Performance" of Windows just seems like a bad joke.
This is one of the most retarded things Trump has done. Of course it probably won't have any effect on industry...
So, in your own words, not spending 1.5 billion in tax payer money won't have "any effect", doesn't that imply that the spending was itself wasteful? If private interests will pick up the slack, shouldn't we be saving that money to spend somewhere else where it is more needed? Maybe that money could be spent improving infrastructure? Or other research? Or just plain not spending as much so our government doesn't have to borrow as much money every year. It doesn't sound so "retarded" to me in that light (and there's a bit of irony in an angry liberal using a derogatory word to describe mentally handicapped).
I agree with you about Trump's likely motivation here, but that doesn't mean that the outcome is actually bad. Don't go on angry rants about things that aren't really that bad -- it makes it much harder to take rants about actual bad things seriously.
JPEG 2000 is a complicated and slow (compared to JPEG) codec. I only work with it in software, but I'd imagine that it's easier (and thus cheaper) to design and implement JPEG encoders in hardware than JPEG 2000. So if the various cameras out there "settle" for JPEG, then that is what people will tend to use.
There's also browser support -- I don't think any modern browsers support JPEG 2000 images natively. That hurts.
JPEG 2000 has several "parts" in the spec, and only part 1 is available without licensing fees. That covers the still image format, but the more advanced things like JPIP streaming are locked away.
I'm not sure of the current level of support of JPEG2000 in FOSS. My employer chose to use the commercial Kakadu codec a while ago when it was the clear leader. Since we managed to get a perpetual license, there's not a lot of incentive to rip that out to go with something different. A lack of a clear FOSS library like libjpeg for JPEG has probably hurt JPEG 2000 adoption, too.
But JPEG 2000 is very popular in the remote sensing world. When the images are tens of thousands of pixels on each side and gigapixel images aren't uncommon, JPEG 2000 can make a big difference in size. Its bitrate limiting features help make predictable file sizes, which are important for some people. Its embedded res levels (a.k.a. image pyramid) allows for quick access to overviews, which is important for these large images (though I wish the PTB didn't set standards that limited res level generation to r5 -- even 1/32 of a large image can be pretty large). If you can get it working, JPIP streaming allows users to view the image by only downloading the parts that they need.
So JPEG 2000 hasn't really failed overall, it just became a niche format. I wouldn't be surprised if it is used behind the scenes in other industries that deal with large images, too.
So yeah, I totally get it - if it works perfectly, if it runs smooth every day, if I don't have to concentrate on my freaking setup every day...but can concentrate just on my job - then I'm all for it!
There's a lot of "if" coming off that statement. Perhaps Microsoft really improved Windows with version 10. At my employer I have a Windows 7 laptop which I use mostly for compiling software (my main desktop is Linux, thankfully). The Windows interface may be familiar to most people, but as a regular Linux user I find it fairly basic. There's no way to pin a window on top, for example, or even to have multiple virtual desktops. It doesn't even have symlink support!
On my Windows system, it's a rare day that it runs perfectly, or smoothly, or I don't have to concentrate on its setup. When something is wrong, the errors are often meaningless or misleading. For example, if a DLL needed by an EXE doesn't have execute permissions, you might get an error indicating that some other DLL couldn't be found. Or the system might skip that DLL and load a different one from later in that PATH. I waste much more of my time trying to keep the Windows build working than I do on Linux. And I mostly know what I'm doing -- I have no idea how average people fare. I gather they just ignore the problems as "that's Windows".
But worst of all, it is slow. Extremely slow. Mind bogglingly slow. The software I compile on it takes about 4 hours to completely build and test on Linux. And that's pulling all the data over the network (NFS and ClearCase). On Windows, it takes a minimum of 24 hours to build, and another 24 hours to test. And that's with everything copied to the local disk -- it takes twice as long if running over the network. I do daily builds on Linux, but only weekly builds on Windows. It's so slow it hinders my ability to use it.
Part of that slowness is likely related to all the dumb "security" software my employer installs on Windows. Lately, this software has made it so that about 2 out of 3 processes fail to start. You can imagine how much this would affect a build done using 'make'. I can't even get rsync to reliably start to copy the latest copy of the software from the network to the local drive.
This sort of dumbness is what the users of the Munich network can look forward to when they start getting their Windows clients. "Security" people (not real security people, but people who follow checklists and think that more security software always makes things better) will ruin whatever system shows up in Munich. They users will be longing for their Linux clients:)
For example, if I want to download bank statements from the bank, I should be able to automate and automate naming the given PDF the right name but I can't.
Why should I have to be disabled to be able to automate a thing like that? Downloading the bank statement and naming it right is an annoyingly long process, not least of which is because the bank's server doesn't suggest a name ending with ".pdf" so the save file dialog shows existing files that end in ".aspx' instead.
Other things like screen readers or screen magnifiers are useful for people with otherwise fine sight under some circumstances.
So basically, the things that are necessary for some disabled people to use the service are also often useful for able bodied people. Those developers you're arguing with should realize that they can make a better experience for EVERYONE by making their app/website/whatever more accessible.
Huh, they must have changed over time. About a decade ago, I ordered a pizza for carry out from their website and I had to create an account and I remember the password requirements were quite stringent. I don't remember the details, but it did impress on me that the requirements were much more than what was required to protect what amounted to my zip code. Maybe they got pushback from customers on how hard it was to come up with a password. Though having a short maximum length and not allowing symbols is bad practice in the other direction.
I bought an Insignia (Best Buy generic brand, I think) in late 2016 that doesn't have any smart features. Just a TV tuner and 3 HDMI ports. It works great, and I think it was cheaper than the smart equivalent. So it's definitely possible to get a non-smart TV.
He also had no references and didn't really make any reasonable attempt to actually support the central thesis, which was: "a. biological differences exist. b. differences exist in representation. c. a a causes b".
I'm not surprised he didn't have any references or make any attempt to support "a causes b" because that's not actually in Damore's document. Instead, he wrote (paraphrased) "a might be a contributing factor in b". And frankly, it's a stretch to assume that if a and b are both true (something you don't seem to dispute) that a doesn't play any role in b.
I'll quote from the section "Possible non-bias causes of the gender gap in techâ" [emphasis mine]:
I'm simply stating that the distribution of preferences and abilities of men and women differ in part due to biological causes and that these differences may explain why we don't see equal representation of women in tech and leadership. Many of these differences are small and there's significant overlap between men and women, so you can't say anything about an individual given these population level distributions.
[again, emphasis mine]
If you have categorical evidence that biological differences between men and women play no part in their preferences and that those preferences play no part in people's career choices, I suggest you post it.
Though to be back on topic, that evidence would probably do little good. And my introduction of facts will probably only harden your position. So I guess all hope of rational debate is lost.
Change the SecureBoot requirements so that it cannot be disabled on consumer computers. Revoke the SecureBoot certificate that allows (some) Linux distributions to boot with it enabled. Linux effectively extinguished in the consumer space. And Microsoft will say that's OK because now you can run your Linux programs under the gentle oversight of Windows, and whatever marketing data it is collecting.
1. WeatherBug used to be the best weather app by far, but a recent upgrade made it unusable so I switched to weatherunderground
Ha! Weather Underground used to be a great site before the Weather Channel (I think) purchased them and really bloated it up. It's really unfortunate because they have great information, especially for tropical storms.
I use Pidgin at work to connect to the Skype for Business server. One of the things I like about it is that it keeps a log of all the conversations. It is named something odd, though, and it usually takes me a second to go though all the context menu options to remember which one to use.
I also like it because it lets me disable the emoticons, which makes reading pasted code much easier. Too much code syntax has things that look like some form of smiley:)
This isn't a new idea at all. I actually own several plants that are powered by renewable sources that turn atmospheric carbon dioxide into solid carbon and oxygen. They work great and are completely off-grid! The only downside is that every so often I have to collect the solid carbon and put it on the curb to be taken to the local sequestration area or the homeowner's association will complain about my bushes and trees needing trimming.
And how soon would it be until those places start offering more expensive services and allowing residents to borrow against future UBI payments? Even if it is outlawed, borrowing against future UBI would very likely end up being a big thing in the underground market. It'd be risky, since the borrower could die, but criminals often take large risks.
Proponents of UBI often push their own rationalism onto everyone without thinking about the fact that many people make irrational decisions all the time.
You're proposing a flat tax, which is a tax rate that is the same regardless of income. People who talk about the rich paying their "fair share" are not talking about a flat tax. They generally want an extremely progressive tax rate structure. So maybe the 50k earner pays 5k in taxes (or maybe even no taxes) while the 500k earner pays 400k (or more) in taxes. Sure, the "rich" guy ends up taking home more (100k vs. 45k), but it's no longer quite as much. If earning 500k over 50k takes 10 times the effort (which is a big if) but only really nets twice the reward, it could discourage some people. And others just get disgusted about having so much money taken from them.
That's the argument, at least. At the extreme where taxes make more salary be no additional take home pay it makes sense. It makes less sense the less progressive the tax system is. But it probably is a real danger and why we should have a progressive system, but not TOO progressive a system.
The problem is they are losing customers and one wants to sue! Basically all the computers with XP worked fine before YOU came and cost us $5000 in lost business! They are now viewed as incompetent all thanks to Windows 10.
Maybe they should recommend that their customers migrate to systems that are more in their control. The one who wants to sue would hurt MS a lot more if he was able to move customers to Linux. And while there would be short term costs, the long term costs (especially in TCO) would probably be lower. Microsoft won't change their behavior until people start leaving their platform. That's how our economy works -- if you don't like vendor A, you take your business to a competitor.
The Thesolonians verses are saying that God will punish those people -- there is no need for any people to do it. Some would argue that also means people explicltly should not do any punishing, as that is God's perrogotive.
The Ephasians verse needs more context. Look at verses surrounding it:
And do not get drunk with wine, for that is debauchery, but be filled with the Spirit, addressing one another in psalms and hymns and spiritual songs, singing and making melody to the Lord with your heart, giving thanks always and for everything to God the Father in the name of our Lord Jesus Christ, submitting to one another out of reverence for Christ.
Wives, submit to your own husbands, as to the Lord. For the husband is the head of the wife even as Christ is the head of the church, his body, and is himself its Savior. Now as the church submits to Christ, so also wives should submit in everything to their husbands.
Husbands, love your wives, as Christ loved the church and gave himself up for her, that he might sanctify her, having cleansed her by the washing of water with the word, so that he might present the church to himself in splendor, without spot or wrinkle or any such thing, that she might be holy and without blemish. In the same way husbands should love their wives as their own bodies.
Christians are encouraged to submit to one another, and husbands are encouraged to love their wives, and give up everything for them. True, this passage is describing different roles for men and women, but it is not so one sided as you presented.
The Leviticus verse is from the Old Testament, which is law oriented, and does have many harsh punsihments. But Christianity teaches that "the wages of sin is death" (Romans 6:23) and "all have sinned and fallen short of the glory of God" (Romans 3:23). Basically, we ALL deserve to die by the standards of the Bible. Singling out one sin isn't really relevant. Christianity teaches that Christ sacrificed himself in our place for forgiveness of sins.
There are difficult and confusing passages in the Bible, but when the Old Testament is combined with the New, it is clear that the overall message of Christianity is love and forgiveness.
The advantage to -l is that it defines things like s() and c(), sine and cosine. It also sets the scale to be long. Passing all the arguments makes it easier to do things like:
bcc 1 + 2 + 3 + 4 + 5
without having to put it in quotes. The only time I have to use quotes is if I want to use parenthesis in the expression, since the shell would otherwise interpret those. You do have to be careful not to have any bare * arguments, though, since the shell will interpret that, too.
This isn't a government mandated block. A private company took the largest ISPs to court and got an injunction requiring them to block a long list of web sites.
Isn't the court a part of the government? And doesn't it interpret laws passed by the government? Just because the mandate didn't come from the Prime Minister (or the Queen) doesn't mean it isn't government mandated. Those ISPs wouldn't be blocking any sites just because a private company told them to.
Because every font created would have to (or is at least supposed to) support all of those glyphs! Not only is that more work for the font designers, it increases the size of the font files themselves. Throw in kerning tables which have to pair every glyph with every other glyph, and you have a O(n^2) increasing size.
Clearly not all glyphs are supported in all fonts (which is why I see boxes with hex characters in them all over the web). And there are probably ways to leave out kerning entries, too. But still, every additional glyph added causes more work for fonts. Essentially, instead of having a Wingdings font, we have put Wingdings into ALL fonts. That's why it is bad.
This news will have Canadians rioting in the streets for more expensive dairy products
Sounds like a joke, but a coworker of my ex had a miscarriage because she drank milk that had too much antibiotics in it.
That doesn't sound like a joke, but it does sound a lot like the people here in the U.S. that think vaccines cause autism becuase they heard about a case where a child developed autism after getting a vaccine.
Slashdot Mirror
What kind of Internet connection would you prefer to have it use to download updates? You may trust your local network, but that network's connections to the wider Internet should not be inherently trustworthy. Even if you more or less trust your ISP, do you really know all the networks that packets traverse on their way to the server? This is why things like https and package signing were invented. As long as the update was properly signed (in this case by Microsoft, but most Linux distributions do the same thing for their packages) and the signature is verified before applying (and this is really important), then it doesn't matter what network it was used to download it.
At least as far as security is concerned. If it downloaded a large amount of data through a cell phone hotspot causing a large bill, that could certainly be a problem!
Texas has a 6.25% state sales tax. Maybe you meant it has no state income tax?
My corporate supplied computer at work doesn't have many settings to change.
And I have never associated Windows with performance. Unless it is "poor" performance. As a simple example, the software I develop at work takes about 4 hours to completely build and test on Linux. It takes about 60 hours to do the same on Windows. And that is after copying every single needed file to the local hard drive (while Linux gets almost everything from the network). By the time Linux is done, Windows is about half way through cleaning. Now a lot of this poor performance is probably from the shear amount of spyware installed on the system (by corporate) to monitor everything that goes on. But since you have to run that sort of monitoring software on Windows, even if it is only a virus scanner, Windows will always be slower than Linux. So "Ultimate Performance" of Windows just seems like a bad joke.
Have you ever seen a bull in a china shop? I'm just saying, don't denigrate bulls by comparing them to incompetent people :)
So, in your own words, not spending 1.5 billion in tax payer money won't have "any effect", doesn't that imply that the spending was itself wasteful? If private interests will pick up the slack, shouldn't we be saving that money to spend somewhere else where it is more needed? Maybe that money could be spent improving infrastructure? Or other research? Or just plain not spending as much so our government doesn't have to borrow as much money every year. It doesn't sound so "retarded" to me in that light (and there's a bit of irony in an angry liberal using a derogatory word to describe mentally handicapped).
I agree with you about Trump's likely motivation here, but that doesn't mean that the outcome is actually bad. Don't go on angry rants about things that aren't really that bad -- it makes it much harder to take rants about actual bad things seriously.
JPEG 2000 is a complicated and slow (compared to JPEG) codec. I only work with it in software, but I'd imagine that it's easier (and thus cheaper) to design and implement JPEG encoders in hardware than JPEG 2000. So if the various cameras out there "settle" for JPEG, then that is what people will tend to use.
There's also browser support -- I don't think any modern browsers support JPEG 2000 images natively. That hurts.
JPEG 2000 has several "parts" in the spec, and only part 1 is available without licensing fees. That covers the still image format, but the more advanced things like JPIP streaming are locked away.
I'm not sure of the current level of support of JPEG2000 in FOSS. My employer chose to use the commercial Kakadu codec a while ago when it was the clear leader. Since we managed to get a perpetual license, there's not a lot of incentive to rip that out to go with something different. A lack of a clear FOSS library like libjpeg for JPEG has probably hurt JPEG 2000 adoption, too.
But JPEG 2000 is very popular in the remote sensing world. When the images are tens of thousands of pixels on each side and gigapixel images aren't uncommon, JPEG 2000 can make a big difference in size. Its bitrate limiting features help make predictable file sizes, which are important for some people. Its embedded res levels (a.k.a. image pyramid) allows for quick access to overviews, which is important for these large images (though I wish the PTB didn't set standards that limited res level generation to r5 -- even 1/32 of a large image can be pretty large). If you can get it working, JPIP streaming allows users to view the image by only downloading the parts that they need.
So JPEG 2000 hasn't really failed overall, it just became a niche format. I wouldn't be surprised if it is used behind the scenes in other industries that deal with large images, too.
There's a lot of "if" coming off that statement. Perhaps Microsoft really improved Windows with version 10. At my employer I have a Windows 7 laptop which I use mostly for compiling software (my main desktop is Linux, thankfully). The Windows interface may be familiar to most people, but as a regular Linux user I find it fairly basic. There's no way to pin a window on top, for example, or even to have multiple virtual desktops. It doesn't even have symlink support!
On my Windows system, it's a rare day that it runs perfectly, or smoothly, or I don't have to concentrate on its setup. When something is wrong, the errors are often meaningless or misleading. For example, if a DLL needed by an EXE doesn't have execute permissions, you might get an error indicating that some other DLL couldn't be found. Or the system might skip that DLL and load a different one from later in that PATH. I waste much more of my time trying to keep the Windows build working than I do on Linux. And I mostly know what I'm doing -- I have no idea how average people fare. I gather they just ignore the problems as "that's Windows".
But worst of all, it is slow. Extremely slow. Mind bogglingly slow. The software I compile on it takes about 4 hours to completely build and test on Linux. And that's pulling all the data over the network (NFS and ClearCase). On Windows, it takes a minimum of 24 hours to build, and another 24 hours to test. And that's with everything copied to the local disk -- it takes twice as long if running over the network. I do daily builds on Linux, but only weekly builds on Windows. It's so slow it hinders my ability to use it.
Part of that slowness is likely related to all the dumb "security" software my employer installs on Windows. Lately, this software has made it so that about 2 out of 3 processes fail to start. You can imagine how much this would affect a build done using 'make'. I can't even get rsync to reliably start to copy the latest copy of the software from the network to the local drive.
This sort of dumbness is what the users of the Munich network can look forward to when they start getting their Windows clients. "Security" people (not real security people, but people who follow checklists and think that more security software always makes things better) will ruin whatever system shows up in Munich. They users will be longing for their Linux clients :)
Why should I have to be disabled to be able to automate a thing like that? Downloading the bank statement and naming it right is an annoyingly long process, not least of which is because the bank's server doesn't suggest a name ending with ".pdf" so the save file dialog shows existing files that end in ".aspx' instead.
Other things like screen readers or screen magnifiers are useful for people with otherwise fine sight under some circumstances.
So basically, the things that are necessary for some disabled people to use the service are also often useful for able bodied people. Those developers you're arguing with should realize that they can make a better experience for EVERYONE by making their app/website/whatever more accessible.
Huh, they must have changed over time. About a decade ago, I ordered a pizza for carry out from their website and I had to create an account and I remember the password requirements were quite stringent. I don't remember the details, but it did impress on me that the requirements were much more than what was required to protect what amounted to my zip code. Maybe they got pushback from customers on how hard it was to come up with a password. Though having a short maximum length and not allowing symbols is bad practice in the other direction.
I bought an Insignia (Best Buy generic brand, I think) in late 2016 that doesn't have any smart features. Just a TV tuner and 3 HDMI ports. It works great, and I think it was cheaper than the smart equivalent. So it's definitely possible to get a non-smart TV.
I'm not surprised he didn't have any references or make any attempt to support "a causes b" because that's not actually in Damore's document. Instead, he wrote (paraphrased) "a might be a contributing factor in b". And frankly, it's a stretch to assume that if a and b are both true (something you don't seem to dispute) that a doesn't play any role in b.
I'll quote from the section "Possible non-bias causes of the gender gap in techâ" [emphasis mine]:
[again, emphasis mine]
If you have categorical evidence that biological differences between men and women play no part in their preferences and that those preferences play no part in people's career choices, I suggest you post it.
Though to be back on topic, that evidence would probably do little good. And my introduction of facts will probably only harden your position. So I guess all hope of rational debate is lost.
Change the SecureBoot requirements so that it cannot be disabled on consumer computers. Revoke the SecureBoot certificate that allows (some) Linux distributions to boot with it enabled. Linux effectively extinguished in the consumer space. And Microsoft will say that's OK because now you can run your Linux programs under the gentle oversight of Windows, and whatever marketing data it is collecting.
Ha! Weather Underground used to be a great site before the Weather Channel (I think) purchased them and really bloated it up. It's really unfortunate because they have great information, especially for tropical storms.
I use Pidgin at work to connect to the Skype for Business server. One of the things I like about it is that it keeps a log of all the conversations. It is named something odd, though, and it usually takes me a second to go though all the context menu options to remember which one to use.
I also like it because it lets me disable the emoticons, which makes reading pasted code much easier. Too much code syntax has things that look like some form of smiley :)
This isn't a new idea at all. I actually own several plants that are powered by renewable sources that turn atmospheric carbon dioxide into solid carbon and oxygen. They work great and are completely off-grid! The only downside is that every so often I have to collect the solid carbon and put it on the curb to be taken to the local sequestration area or the homeowner's association will complain about my bushes and trees needing trimming.
And how soon would it be until those places start offering more expensive services and allowing residents to borrow against future UBI payments? Even if it is outlawed, borrowing against future UBI would very likely end up being a big thing in the underground market. It'd be risky, since the borrower could die, but criminals often take large risks.
Proponents of UBI often push their own rationalism onto everyone without thinking about the fact that many people make irrational decisions all the time.
You're proposing a flat tax, which is a tax rate that is the same regardless of income. People who talk about the rich paying their "fair share" are not talking about a flat tax. They generally want an extremely progressive tax rate structure. So maybe the 50k earner pays 5k in taxes (or maybe even no taxes) while the 500k earner pays 400k (or more) in taxes. Sure, the "rich" guy ends up taking home more (100k vs. 45k), but it's no longer quite as much. If earning 500k over 50k takes 10 times the effort (which is a big if) but only really nets twice the reward, it could discourage some people. And others just get disgusted about having so much money taken from them.
That's the argument, at least. At the extreme where taxes make more salary be no additional take home pay it makes sense. It makes less sense the less progressive the tax system is. But it probably is a real danger and why we should have a progressive system, but not TOO progressive a system.
Maybe they should recommend that their customers migrate to systems that are more in their control. The one who wants to sue would hurt MS a lot more if he was able to move customers to Linux. And while there would be short term costs, the long term costs (especially in TCO) would probably be lower. Microsoft won't change their behavior until people start leaving their platform. That's how our economy works -- if you don't like vendor A, you take your business to a competitor.
Gay marriage. Brendan Eich.
Easily done. All you have to do is vote for one.
The Thesolonians verses are saying that God will punish those people -- there is no need for any people to do it. Some would argue that also means people explicltly should not do any punishing, as that is God's perrogotive.
The Ephasians verse needs more context. Look at verses surrounding it:
Christians are encouraged to submit to one another, and husbands are encouraged to love their wives, and give up everything for them. True, this passage is describing different roles for men and women, but it is not so one sided as you presented.
The Leviticus verse is from the Old Testament, which is law oriented, and does have many harsh punsihments. But Christianity teaches that "the wages of sin is death" (Romans 6:23) and "all have sinned and fallen short of the glory of God" (Romans 3:23). Basically, we ALL deserve to die by the standards of the Bible. Singling out one sin isn't really relevant. Christianity teaches that Christ sacrificed himself in our place for forgiveness of sins.
There are difficult and confusing passages in the Bible, but when the Old Testament is combined with the New, it is clear that the overall message of Christianity is love and forgiveness.
That's very similar to my 'bcc' function:
Great minds, huh? :)
The advantage to -l is that it defines things like s() and c(), sine and cosine. It also sets the scale to be long. Passing all the arguments makes it easier to do things like:
without having to put it in quotes. The only time I have to use quotes is if I want to use parenthesis in the expression, since the shell would otherwise interpret those. You do have to be careful not to have any bare * arguments, though, since the shell will interpret that, too.
Isn't the court a part of the government? And doesn't it interpret laws passed by the government? Just because the mandate didn't come from the Prime Minister (or the Queen) doesn't mean it isn't government mandated. Those ISPs wouldn't be blocking any sites just because a private company told them to.
Because every font created would have to (or is at least supposed to) support all of those glyphs! Not only is that more work for the font designers, it increases the size of the font files themselves. Throw in kerning tables which have to pair every glyph with every other glyph, and you have a O(n^2) increasing size.
Clearly not all glyphs are supported in all fonts (which is why I see boxes with hex characters in them all over the web). And there are probably ways to leave out kerning entries, too. But still, every additional glyph added causes more work for fonts. Essentially, instead of having a Wingdings font, we have put Wingdings into ALL fonts. That's why it is bad.
That doesn't sound like a joke, but it does sound a lot like the people here in the U.S. that think vaccines cause autism becuase they heard about a case where a child developed autism after getting a vaccine.
Correlation != Causation.