They should study to see if athiests are lacking an intuitive thinking.
I'd be interested in such a study as well, though I predict an opposite result. There is no evidence God does not exist, just as there is no evidence he does exist; therefore, atheism requires just as much faith as any other religion.
Whoops. Should have read the next sentence on the front page of julialang.org:
The core of the Julia implementation is licensed under the MIT license. Various libraries used by the Julia environment include their own licenses such as the GPL, LGPL, and BSD (therefore the environment, which consists of the language, user interfaces, and libraries, is under the GPL).
So the issue of canonical brace style and automatic semi-colon insertion kind of go hand in hand. If you know you're going to have a canonical brace style, then choose the one that allows you to simplify the rules of the automatic semi-colon insertion and allows easy line-at-a-time parsing for interactive implementations.
I suppose I can respect that you don't think it's a problem worth solving. But I think that if you're going through all the trouble of designing a new language, you might as well fix as many problems as you can, no matter how small. Certainly compound declarations with function pointers are complex, but I think the ability to read the declaration from left to right is a major improvement over the Clockwise-Spiral Rule of C.
The syntax is obviously C-inspired, but with some changes, many of which seemed like experimentation -- doing something different just because it's different. Although I don't object to the philosophy, I'd like to see how those changes work out before investing a lot of time into them. In particular, the declaration syntax feels very strange to people who are used to C-style languages.
Perhaps this section of the FAQ might be useful in explaining some of those changes. Another page explaining the declaration syntax in particular can be found here.
The most important person who cares what style he prefers is him. Really, that's all that matters.
Every person who ever reads your code disagrees. Programming is not a solitary activity.
I'm sure a smart preprocessor could deal with many indent styles just fine, but what's scary is when the language developers say, "here is how you will use our language." Because other people always find more clever things to do with flexible languages than the designers intended.
How does having a canonical brace format in any way limit what you are able to do with the language?
As mentioned below, in the Go community there isn't much discussion of formatting. If you prefer a technical reason, then the canon format can be easily enforced using the "go fmt" command. Using a separate brace style means you must either manually enforce it, or fork gofmt and make the changes yourself. In the end, is it really worth the extra effort?
One thing I'd like to add that most people miss is that the language was designed for easy dependency management, and it's built into the go tool. For instance, if you download library A that depends on library B that you don't have installed, when you build library A the tools will download, install, and build library B automatically.
Don't forget vitess, which is a Google project aimed at making MySQL databases scale better, and is used in YouTube. The Thanksgiving Google Doodle was also written in Go, and developed in 24 hours. Google does eat their own dogfood.
Imagine you're watching a really good movie and your parents tell you to switch it off halfway through. Wouldn't you be angry? That has nothing to do with addiction.
Of course, the real problem with this statement is video games are much longer than movies. Zelda games can last 50 hours or more, depending on completion and whether you've played the game before or not. It's certainly not healthy to play games like that in a single sitting (this coming from a guy who played Mass Effect 2 in a single 24-hour session).
But the problem is not that you take away their super powers or anything like that, it's a bit more basic: They just want to know how the story ends! With games like Wii Sports and Mario Kart, the "stories" only last a few minutes, at which point it's easy to break away from the game.
Of course, game developers aren't stupid. Most games of the length of Zelda and Final Fantasy aren't written such that they have to be played in one sitting. The real trick, of course, is that you, as a parent, have to be able to find points in the story to switch off the game. This is not something you can do unless you are very familiar with the game itself, so my suggestion is this: Watch your child play the games. You don't have to watch every second; if you have a laptop you could get some work done during battles and puzzles and stuff like that. The point is to follow the story and find the best point to say "okay, that's enough for today" rather than just limiting it to half an hour a day.
Don't expect me to port existing code to your new language. Either make it compatible - i.e. an old language with new features - or provide me with an automated conversion tool.
One of Go's advantages are the features deliberately left out of the language, such as the typical class hierarchy, multiple inheritance, and operator overloading. Similar to conditional compilation in C, those features, while useful, are too easy to abuse and make code harder to read in the long run. So the Go devs left them out. You can't do something like that and keep backwards compatibility.
If backwards compatibility was necessary for a successful language, then every new language would C++.
K = 1/2 * m * v^2 (kinetic energy; integral of momentum with respect to velocity)
x = 1/2 * a * t^2 (position from acceleration; integral of velocity w.r.t. time)
U = 1/2 * k * x^2 (potential energy of a spring; integral of force w.r.t. distance)
E = 1/2 * C * V^2 (energy stored in a capacitor; integral of charge w.r.t. voltage)
E = 1/2 * L * I^2 (energy stored in an inductor; integral of voltage w.r.t. current)
A = 1/2 * tau* r^2 (area of a circle, integral of circumference w.r.t. radius)
Changing the formula actually brings it into line with the others. This is explained in both the "Pi is Wrong!" article and the Tau Manifesto.
As for spheres, remember that the volume of a sphere is 2/3 of that of a circumscribed cylinder. The volume of said cylinder is 1/2 * tau * r^2 * 2 * r = tau * r^3. The tau formula clearly shows this relationship, while the pi formula obfuscates it.
The Australian Government should surely be looking at, for instance, how much of the decoration and formatting, how much of the Powerpoint, are actually wasted effort.
Almost all of it. The entire purpose of typesetting systems such as (La)TeX is to make it so the users didn't have to worry about such things.
As has been mentioned before, splash screens do serve a useful purpose in letting users know the app is actually loading. As has been mentioned before, Photoshop does a lot of stuff, so it's more or less impossible to get the program down to a reasonable size in a single executable. As such, you're pretty much left with a single option. Go back to the philosophy of making each program doing one thing well; in this case, a separate program for each photo effect. Now your huge, monolithic program becomes not much more than a simple shell that calls a number of smaller programs only when their needed.
Imagine if, to boot Linux, everything in $PATH had to be loaded into memory. That's pretty much what Photoshop does; no wonder it takes forever.
"No *atmospheric* warning in the last decade or two! IT'S A HOAX!"
Except they don't claim it's a hoax. There was nothing in the article claiming that global warming doesn't exist. In fact, they don't even debate the existence of global warming. They even mentioned Climategate without calling them frauds.
The specific claims:
The lack of warming for more than a decade—indeed, the smaller-than-predicted warming over the 22 years since the U.N.'s Intergovernmental Panel on Climate Change (IPCC) began issuing projections—suggests that computer models have greatly exaggerated how much warming additional CO2 can cause.
Better plant varieties, chemical fertilizers and agricultural management contributed to the great increase in agricultural yields of the past century, but part of the increase almost certainly came from additional CO2 in the atmosphere.
Although the number of publicly dissenting scientists is growing, many young scientists furtively say that while they also have serious doubts about the global-warming message, they are afraid to speak up for fear of not being promoted—or worse.
There is no compelling scientific argument for drastic action to "decarbonize" the world's economy.
A recent study of a wide variety of policy options by Yale economist William Nordhaus showed that nearly the highest benefit-to-cost ratio is achieved for a policy that allows 50 more years of economic growth unimpeded by greenhouse gas controls.
And it is likely that more CO2 and the modest warming that may come with it will be an overall benefit to the planet.
If elected officials feel compelled to "do something" about climate, we recommend supporting the excellent scientists who are increasing our understanding of climate with well-designed instruments on satellites, in the oceans and on land, and in the analysis of observational data.
For all those people commenting asking about why we need a new language, Rob Pike, one of the developers of Go, gave a talk a couple years back that included some of the reasoning behind why the Go developers felt that a new language was needed, rather than just a new library. The rationale was mostly intended for Go, but Rust fills a very similar niche, so the rationale works for it as well. The video is here for those interested.
I have ADHD. I am most certainly offended by being equated with that.
AD(H)D (like most psychological disorders) is exactly what it says on the tin: Attention Deficit Disorder (with Hyperactivity). Having a small attention span does not make you an asshole.
Maintaining your beliefs whether or not they are correct is not integrity; it's simply stubbornness. Integrity includes being able to admit you were wrong before, which is seems to be looked down on in our society; consider how many politicians have been accused of "flip-flopping" on a controversial subject.
The problem with this simplification is that it is rarely obvious that one's belief is incorrect.
If the facts are not clear, then everyone is entitled to their own opinion. In science it's called a hypothesis; In mathematics, a conjecture; in religion, faith. I don't see much of a problem with using opinion in place of unknown facts, as long as they are clearly (and correctly) labeled as such.
Maintaining your beliefs whether or not they are correct is not integrity; it's simply stubbornness.
No. It's not that simple. Saying it is stubbornness implies that the believer understands they are wrong, or understands that looking at the data will enlighten them into a new outlook. It's more like this (and I'm still simplifying there.)
I chose my words poorly. What I meant was exactly what you describe; when one continues to believe something which has been proven false. Sorry for the confusion.
Slashdot Mirror
There are many more ways to have bad grammar than there are to have good grammar.
They should study to see if athiests are lacking an intuitive thinking.
I'd be interested in such a study as well, though I predict an opposite result. There is no evidence God does not exist, just as there is no evidence he does exist; therefore, atheism requires just as much faith as any other religion.
The core of the Julia implementation is licensed under the MIT license. Various libraries used by the Julia environment include their own licenses such as the GPL, LGPL, and BSD (therefore the environment, which consists of the language, user interfaces, and libraries, is under the GPL).
The core Julia implementation uses the MIT License, not the GPL. See the license information here.
Nice to see the police didn't turn a blind eye to a citizen in need.
So the issue of canonical brace style and automatic semi-colon insertion kind of go hand in hand. If you know you're going to have a canonical brace style, then choose the one that allows you to simplify the rules of the automatic semi-colon insertion and allows easy line-at-a-time parsing for interactive implementations.
I suppose I can respect that you don't think it's a problem worth solving. But I think that if you're going through all the trouble of designing a new language, you might as well fix as many problems as you can, no matter how small. Certainly compound declarations with function pointers are complex, but I think the ability to read the declaration from left to right is a major improvement over the Clockwise-Spiral Rule of C.
The syntax is obviously C-inspired, but with some changes, many of which seemed like experimentation -- doing something different just because it's different. Although I don't object to the philosophy, I'd like to see how those changes work out before investing a lot of time into them. In particular, the declaration syntax feels very strange to people who are used to C-style languages.
Perhaps this section of the FAQ might be useful in explaining some of those changes. Another page explaining the declaration syntax in particular can be found here.
Really... *nobody* cares what style *you* prefer.
The most important person who cares what style he prefers is him. Really, that's all that matters.
Every person who ever reads your code disagrees. Programming is not a solitary activity.
I'm sure a smart preprocessor could deal with many indent styles just fine, but what's scary is when the language developers say, "here is how you will use our language." Because other people always find more clever things to do with flexible languages than the designers intended.
How does having a canonical brace format in any way limit what you are able to do with the language?
As mentioned below, in the Go community there isn't much discussion of formatting. If you prefer a technical reason, then the canon format can be easily enforced using the "go fmt" command. Using a separate brace style means you must either manually enforce it, or fork gofmt and make the changes yourself. In the end, is it really worth the extra effort?
One thing I'd like to add that most people miss is that the language was designed for easy dependency management, and it's built into the go tool. For instance, if you download library A that depends on library B that you don't have installed, when you build library A the tools will download, install, and build library B automatically.
Um... what problems are caused by the automatic semi-colon insertion?
Don't forget vitess, which is a Google project aimed at making MySQL databases scale better, and is used in YouTube. The Thanksgiving Google Doodle was also written in Go, and developed in 24 hours. Google does eat their own dogfood.
Imagine you're watching a really good movie and your parents tell you to switch it off halfway through. Wouldn't you be angry? That has nothing to do with addiction.
Of course, the real problem with this statement is video games are much longer than movies. Zelda games can last 50 hours or more, depending on completion and whether you've played the game before or not. It's certainly not healthy to play games like that in a single sitting (this coming from a guy who played Mass Effect 2 in a single 24-hour session).
But the problem is not that you take away their super powers or anything like that, it's a bit more basic: They just want to know how the story ends! With games like Wii Sports and Mario Kart, the "stories" only last a few minutes, at which point it's easy to break away from the game.
Of course, game developers aren't stupid. Most games of the length of Zelda and Final Fantasy aren't written such that they have to be played in one sitting. The real trick, of course, is that you, as a parent, have to be able to find points in the story to switch off the game. This is not something you can do unless you are very familiar with the game itself, so my suggestion is this: Watch your child play the games. You don't have to watch every second; if you have a laptop you could get some work done during battles and puzzles and stuff like that. The point is to follow the story and find the best point to say "okay, that's enough for today" rather than just limiting it to half an hour a day.
Don't expect me to port existing code to your new language. Either make it compatible - i.e. an old language with new features - or provide me with an automated conversion tool.
One of Go's advantages are the features deliberately left out of the language, such as the typical class hierarchy, multiple inheritance, and operator overloading. Similar to conditional compilation in C, those features, while useful, are too easy to abuse and make code harder to read in the long run. So the Go devs left them out. You can't do something like that and keep backwards compatibility.
If backwards compatibility was necessary for a successful language, then every new language would C++.
K = 1/2 * m * v^2 (kinetic energy; integral of momentum with respect to velocity)
x = 1/2 * a * t^2 (position from acceleration; integral of velocity w.r.t. time)
U = 1/2 * k * x^2 (potential energy of a spring; integral of force w.r.t. distance)
E = 1/2 * C * V^2 (energy stored in a capacitor; integral of charge w.r.t. voltage)
E = 1/2 * L * I^2 (energy stored in an inductor; integral of voltage w.r.t. current)
A = 1/2 * tau* r^2 (area of a circle, integral of circumference w.r.t. radius)
Changing the formula actually brings it into line with the others. This is explained in both the "Pi is Wrong!" article and the Tau Manifesto.
As for spheres, remember that the volume of a sphere is 2/3 of that of a circumscribed cylinder. The volume of said cylinder is 1/2 * tau * r^2 * 2 * r = tau * r^3. The tau formula clearly shows this relationship, while the pi formula obfuscates it.
The Australian Government should surely be looking at, for instance, how much of the decoration and formatting, how much of the Powerpoint, are actually wasted effort.
Almost all of it. The entire purpose of typesetting systems such as (La)TeX is to make it so the users didn't have to worry about such things.
As has been mentioned before, splash screens do serve a useful purpose in letting users know the app is actually loading. As has been mentioned before, Photoshop does a lot of stuff, so it's more or less impossible to get the program down to a reasonable size in a single executable. As such, you're pretty much left with a single option. Go back to the philosophy of making each program doing one thing well; in this case, a separate program for each photo effect. Now your huge, monolithic program becomes not much more than a simple shell that calls a number of smaller programs only when their needed.
Imagine if, to boot Linux, everything in $PATH had to be loaded into memory. That's pretty much what Photoshop does; no wonder it takes forever.
I am not aware of any.
Allow me to enlighten you then.
Aka, for the neckbearded virgins.
Hey, I resemble that remark!
"No *atmospheric* warning in the last decade or two! IT'S A HOAX!"
Except they don't claim it's a hoax. There was nothing in the article claiming that global warming doesn't exist. In fact, they don't even debate the existence of global warming. They even mentioned Climategate without calling them frauds.
The specific claims:
The lack of warming for more than a decade—indeed, the smaller-than-predicted warming over the 22 years since the U.N.'s Intergovernmental Panel on Climate Change (IPCC) began issuing projections—suggests that computer models have greatly exaggerated how much warming additional CO2 can cause.
Better plant varieties, chemical fertilizers and agricultural management contributed to the great increase in agricultural yields of the past century, but part of the increase almost certainly came from additional CO2 in the atmosphere.
Although the number of publicly dissenting scientists is growing, many young scientists furtively say that while they also have serious doubts about the global-warming message, they are afraid to speak up for fear of not being promoted—or worse.
There is no compelling scientific argument for drastic action to "decarbonize" the world's economy.
A recent study of a wide variety of policy options by Yale economist William Nordhaus showed that nearly the highest benefit-to-cost ratio is achieved for a policy that allows 50 more years of economic growth unimpeded by greenhouse gas controls.
And it is likely that more CO2 and the modest warming that may come with it will be an overall benefit to the planet.
If elected officials feel compelled to "do something" about climate, we recommend supporting the excellent scientists who are increasing our understanding of climate with well-designed instruments on satellites, in the oceans and on land, and in the analysis of observational data.
If ten thousand plaintiffs sue a large company and win $1,000 each, that's $10 million that the company has to explain to its shareholders.
If.
For all those people commenting asking about why we need a new language, Rob Pike, one of the developers of Go, gave a talk a couple years back that included some of the reasoning behind why the Go developers felt that a new language was needed, rather than just a new library. The rationale was mostly intended for Go, but Rust fills a very similar niche, so the rationale works for it as well. The video is here for those interested.
I have ADHD. I am most certainly offended by being equated with that .
AD(H)D (like most psychological disorders) is exactly what it says on the tin: Attention Deficit Disorder (with Hyperactivity). Having a small attention span does not make you an asshole.
Maintaining your beliefs whether or not they are correct is not integrity; it's simply stubbornness. Integrity includes being able to admit you were wrong before, which is seems to be looked down on in our society; consider how many politicians have been accused of "flip-flopping" on a controversial subject.
The problem with this simplification is that it is rarely obvious that one's belief is incorrect.
If the facts are not clear, then everyone is entitled to their own opinion. In science it's called a hypothesis; In mathematics, a conjecture; in religion, faith. I don't see much of a problem with using opinion in place of unknown facts, as long as they are clearly (and correctly) labeled as such.
No. It's not that simple. Saying it is stubbornness implies that the believer understands they are wrong, or understands that looking at the data will enlighten them into a new outlook. It's more like this (and I'm still simplifying there.)
I chose my words poorly. What I meant was exactly what you describe; when one continues to believe something which has been proven false. Sorry for the confusion.