Am I the only one who find's Musk's version of scientism worryingly naive?
Musk says other folks "engage in wishful thinking. They ignore counterarguments. They form conclusions based on what others are doing and aren't doing." But then in advocating for his version of the scientific method, he repeats these same errors. He talks about "truth", "probability", "axioms", "correctness", "objectivity", and what's "right," sliding casually between epistemology, naturalism, metaphysics, and ethics, but without pausing to define terms, examine what is given and what has presupposed, or consider the counterarguments those presuppositions have already silenced... surely a case of wishful thinking.
Musk identifies AI as the "biggest threat that humanity faces this century," AI is a product of "the scientific method" he advocates. So how to reconcile the poison and the cure? Shouldn't folks like Musk cogitate on that with a bit more critical depth, before spouting stuff like "It's really helpful for figuring out the tricky things," which sounds like a page from Zuckerberg's playbook, before Russia and Fake News turned up and proved that the world is a lot more complex than that.
Maybe my sense of ire is raised because I've been spending time reading Alfred Whitehead's books (Science and the Modern World, The Concept of Nature, Process and Reality). Whitehead was the co-author with Bertrand Russell of Principia Mathematica, so a major figure in logic. His discussion of the narrow-band thinking that takes place under the name of the scientific method is almost 100 years old, but still just as damning. In Whitehead's view, inductive and axiomatic methods are specialist modes of thought, useful in certain parts of science, but easily prone to fallacies and dogmatism in wider discussions. To pull up a random quote:
"In its use of [methods of induction] natural science has shown a curious mixture of rationalism and irrationalism. Its prevalent tone of thought has been ardently rationalistic within its own borders, and dogmatically irrational beyond those borders. In practice such an attitude tends to become a dogmatic denial that there are any factors in the world not fully expressible in terms of its own primary notions devoid of further generalization. Such a denial is the self-denial of thought."
Here's hoping that industry figures like Zuckerberg and Musk find a way to up their game - I don't expect them to be Whitehead readers, but can we at least move away from disappointing and disingenuous dogma?
TLDR version: I spend a lot of time on Xenforo. On Slashdot I really miss the ability to edit comments, as well as a low-friction Like button. I think/. needs that.
The/. commenting system and Mod points (or God points as I call them) are antiquated and its hurting the community.
Here's why:
Slashdot's commenting system evolved in a time when a typical story had 1000-1500 comments. The comment moderation system was both necessary and innovative. Today it isn.t. There isn't a story on the front page of/. right now with more than 130 comments. A rare story spikes with several thousand comments, but that is atypical. We have lost commenters. The needs of the comment moderation system have changed. Web conventions have shifted but/. has not kept pace.
New Voices
I believe contributors come to/., write a comment or two, don't receive any mod points, nobody responds, their comment disappears, they get disappointed and leave. (this is a guess - it would be interesting to back this with actual data).
A low-friction Like button would be a way to acknowledge or reward a post without needing M[G]od privileges - it would be a way to encourage users to participate, and to recognize new voices.. A "Like" could be treated as e.g. 1/4 of a Mod point for filtering purposes. Fleshing out a Like feature could be part of a way of making/. more social, along with building out better Profile page feature (come on - when was the last time any of you read another users profile page here? They are very broken.) I'd also love Alerts, so you can see when a comment has been responded to. Showing a users karma / level next to their comments would be valuable. Heck, why not just port/. to Xenforo! Ok, that's going too far, but you asked for ideas.
The Long Read
The fact that you cannot edit a comment or delete it means users have to get a comment just right first time. You cannot fix typos, add new ideas, refine your argument, or withdraw a point. It promotes rapid fire one-liners and trolling --- but this is already well served by Facebook and Twitter. The/. approach doesn't encourage longer-form commenting and intelligent discussion. And this is where/. is most needed.
Comment editing would I believe mostly be used by users to fix errors and refine their points or to add extra material. Obviously users could also abuse the system - get a highly modded comment, then modify the text to be offensive or completely change their argument, for example. That can be addressed by clearly indicating when a comment has been edited and offering a link to see the full edit history. Adding a "Report Abuse" button would help to out trolls and poor community players.
I'd like to see Slashdot evolve to better serve its existing users, but also to find new kinds of audiences and discussions. Embracing the editable social web is a step towards that.
It is wrong to assume refugees represent a pure cost. And you are talking about 0.1% of the GDP of Finland here. Do some research before spreading xenophobia.
https://www.washingtonpost.com...
The same code snippet gets recycled, munged, riffed on, ported to new languages, rewritten by multiple authors, commented on and then improved, reposted by new authors with bug fixes, and on... The whole value of sites like SO is this kind of sharing. But doesn't that mean attribution, especially for smaller snippets, will become a nightmare?
Masad is perhaps guilty of the very problem he identifies. He reads a science paper, latches onto the word "intuitive", misapplies it, and so misses a key point in the paper.
In the original study, the authors present the same cognitive test to two different groups, one time using Myriad 12pt, the other gray italicized Myriad 10pt. In another experiment they changed the masthead of a document to introduce nonsense characters like @$Ã. In a third experiment, they had one group furrow eyebrows while doing a test. In each case, they found that the group with the "disfluent" condition (small gray font, @$ characters in the masthead, furrowed eyebrows) performed better than the control condition. From this they conclude that their experiments support the cognitive theory that we have two distinct reasoning systems, a rapid "intuitive" reasoning system and a slow "analytical" reasoning system, and something about disfluency prompts us to switch from our rapid to slow reasoning, leading to improved scores.
Masad summarizes: "The theory behind this is that people will default to relying on the automatic, effortless, and primitive system for reasoning. But if things are counter-intuitive or harder to understand we switch to the deeper, deliberate and analytical mode of thinking." Note how "intuitive" has jumped ship. In the original paper, "intuitive" was a label for our fast reasoning system, contrasted with our slow analytical reasoning system. For Masad, "intuitive" refers not to one of our cognitive reasoning systems but rather to the -input-, he suggests that if the input (e.g. the software framework) is counter-intuitive or harder to understand then we use our more analytical reasoning. There is nothing to support that conclusion in this study... there is nothing counter-intuitive about using a gray 10 point font. The conditions with higher scores weren't harder to understand or more counter-intuitive, they were less legible and more difficult to read. If we translate this study to programming, as Masad proposes, it suggests that if you change your IDE to Myriad 10 pt gray italic, then all of a sudden your code will get better. Hey, go ahead, try it!
Ok, sure, what Masad is actually doing is using a science paper as a prompt, a poetic license for thinking about frameworks and coding. But the kinds of shortcuts he makes are informative - so I'm going to take some poetic license of my own...
First, I think Masad overlooks the importance of reading. The science paper suggests that something about how we read changes how we think. One thing I've noticed about beginner programmers is that they tend to be poor/lazy readers of code. They skim, treating a library or framework function as if it is are magic black box, never to be questioned or investigated. I've had many experiences where I've sat down with a programmer, cracked open a source browser, read the actual source of the library function they are relying on, and heard a gasp, as they realize their assumptions that the framework code is perfect/threadsafe/performant etc. fall away. "You mean every time I do this, it does a linear search through my entire dataset. OMG" "Well, yes, its just code. All you have to do is read it." Promoting code reading has nothing to do with whether or not the framework is intuitive or hard to understand or has "negative space". Its much more about business management priorities and deadlines and culture.
Second, its significant that Masad took a paper from one context and used it to think imaginatively about a very different problem space. Bouncing ideas around freely like that is precisely what the fast/intuitive (if potentially incorrect) style of reasoning is good for. His claim that we need to "overcome intuition" is wrong, in my opinion - its exactly how we stimulate new ideas and debate. His own thought-provoking post proves it.
Blogfather claims to be a champion of links, says they represent the open interconnected spirit of the internet, they are a way to abandon centralism and hierarchies, they are the eyes of the internet, the path to its soul, a way of transferring power out of a site, making us more outward looking, without them a page is blind.
If this is the case, why in the Guardian piece omit a link to the original publication of this story on a blogging platform. Certainly the fact that the story is seven months old and has already been circulated and commented upon is both relevant and interesting. And according to his argument, a link back to the Medium.com story would transfer power out mainstream media to a blogging platform, which is what he wants. And, he suggests, a link is a relation, not an object. Which suggests there is no reason not to include a link, no cost.
The problem is twofold. First, his notion that a link is a relation is far too simplistic. Links are much more thing-like than he implies, in that they encode a rich and living social dynamic. We can presume, for example, that one reason a link to the original article does not appear here is that newspapers trade on novelty, and reprinting a seven month old blog article is hardly that. Second, the very fact that an article is published on Medium.com, a blogging platform, only to be picked up and run by a newspaper - receiving wide commentary along the way - runs counter to his argument that the Internet is being killed by Instagram and Twitter. It demonstrates that these things can comfortably operate side-by-side.
I would have much more intrigued had he written his argument without attaching it to his personal biography and the "Blogfather" label. This is what made me question how his piece is better than Facebook. If his argument were more rigorous and deeply considered, the biographical element would be redundant. By linking his argument to his personal background, he shows that he is precisely aiming to ply reputation to boost polemic, and that's a tactic I associate with social media.
He published the same story in Matter back in June. But in the reprint in the Guardian he fails to link to the original article anywhere.
Pretty much disproves his thesis. The Internet is functioning just fine. Stuff circulates. The link has always been more than a relation between objects.
The blogfather just wants his crown back, and he is using alarmist rhetoric and his personal biography to try and achieve that. In what way is this better than Facebook?
They don't want to rewrite the Swift compiler in Swift.
No shit, they aren't retarded. Other than proving something, WHY WOULD YOU? NO ONE DOES THIS unless they are just trying to swing their dick around. You write your languages in C with ASM for the places it makes sense.
Actually there are loads of reasons to do this, and loads of languages do, including (from Wikipedia) compilers for BASIC, ALGOL, C, D, Pascal, PL/I, Factor, Haskell, Modula-2, Oberon, OCaml, Common Lisp, Scheme, Go, Java, Rust, Python, Scala, Nim, Eiffel, and more. One major reason for self-hosting the compiler is to support richer metaprogramming and tooling. Take a look at some of the posts on why Microsoft sunk years of effort into rewriting the C# compiler in C# (Roslyn). Ditto Perl 6 (Rakudo).
The Swift folks recognize this, even if you don't. That is why this is the only one of the feature requests they say would be nice to do - they just have other priorities first. My bet is, down the line, as the language matures, they will reach a point where they are forced to rewrite the compiler in Swift.
Hey Arca, take a tip from the WalkCar. Kill the narration, pick a good tune, and show your product doing something that is actually interesting. (water? obstacles? steps? a hill even?)
We need a mainstream front page news article "Government encryption backdoor is exploited by criminals." Instead the mainstream coverage fails to connect the Juniper story to the debate on backdoors at all. e.g. CNN runs with: "Newly discovered hack has US fearing foreign infiltration", an article stoking fears over hackers and cybersecurity without once mentioning the keys put under the mat by the government.
Lucas made a whole bunch of alterations to the original trilogy that change the feeling of the movie. If you want to time travel back to the 70's, you need to watch the despecialized edition.
I presume every time someone goes through the Automated Passport Control system they send the captured image, stamped with a passport ID, off to the FBI.
+1. Lets also not forget there is no good designer tooling story for CSS. With good-old-fashioned DTP apps, you could create a named style in your style catalog, click on an element in the document, and apply that style to it. You could even create based-on styles to manage large style catalogs. With the first wave of DTP apps, we gave designers WYSWIG, Drag-and-drop, and all that good stuff. But CSS didn't support this at all. Instead, designers had to learn to write CSS code in a code editor and then debug a non-trivial rule-based runtime. How many hours have we all spent sitting down with designers trying to debug some quirky CSS selector mess. What a headache. CSS slowed down good web design by years. Sure, CSS beats but we could easily have improved on by adding a few more layout tags to HTML, such as , , , etc, like you find in most other content presentation frameworks. That, plus a simple named-style catalog with variables and based-on would have been so much more appropriate and effective.
Yes, the whole detach content from style is an epic fail. Because the HTML DOM *is* a presentation layer, not a business-content layer. Its got loads of presentation-specific tags, its just missing the ones that we actually need for responsive layout. A more useful content-presentation separation would be more like MVVM (Angular notably heads in that direction).
+1. Lets also not forget there is no good designer tooling story for CSS. With good-old-fashioned DTP apps, you could create a named style in your style catalog, click on an element in the document, and apply that style to it. You could even create based-on styles to manage large style catalogs. With the first wave of DTP apps, we gave designers WYSWIG, Drag-and-drop, and all that good stuff. But CSS didn't support this at all. Instead, designers had to learn to write CSS code in a code editor and then debug a non-trivial rule-based runtime. How many hours have we all spent sitting down with designers trying to debug some quirky CSS selector mess. What a headache. CSS slowed down good web design by years. Sure, CSS beats but we could easily have improved on by adding a few more layout tags to HTML, such as , , etc, like you find in most other content presentation frameworks. That, plus a simple named-style catalog with variables and based-on would have been so much more appropriate and effective.
Yes, the whole detach content from style is an epic fail. Because the HTML DOM *is* a presentation layer, not a business-content layer. Its got loads of presentation-specific tags, its just missing the ones that we actually need for responsive layout. A more useful content-presentation separation would be more like MVVM (Angular notably heads in that direction).
when it comes to ethics, a capitalist upbringing appears to trump a socialist one.
All this study shows is is a difference in attitude towards a game with low stakes while queuing at a passport bureaucracy. Generalizing beyond that demonstrates the limits of the author's ethics, not the participants.
While I was at Microsoft, at one point my manager instructed me to stop having ideas that were outside my assigned area, because it was making another team member look bad, and this would impact the stack ranking of both the team member and my manager. So I saw up close how stack ranking sucks.
Still, if I was still at MSFT today, I would be very concerned that the new system drives even more of the compensation process into closed-door management sessions, along with the horse trading and cronyism that invites.
I worked as a research assistant for a professor for six years. It was a great job. The most rewarding part is that I worked on lots of different projects and most of them were cool and intellectually stimulating and fun. It was also fantastic going to conferences and presenting work. You can really push and challenge yourself. It feels a bit like working in a startup. Each professor has their own team and budget and grants and publications, so its like being part of a small company, except that there is a big institution providing backing and benefits. Will your work change the world to be a better place? That's often not so clear cut in academia, but it is certainly a tremendous opportunity for growth and development, and there is demand for computer programming in research.
Professors tend to be incredibly busy so they are looking for self-starters, people who can just get on and contribute without lots of supervision. If you want to get into this area of work, more than academic qualifications, what you need is to demonstrate your own ability to make things. Demo or die. For fields like bio research there's lots of use of small sensors and data capture devices, so one suggestion is to make your own Arduino or Rasberry project, to show that you can come up with a cool idea and have the passion to see it through from start to completion.
Academia is a two tier system, professors and then everyone else. Professors have full control over their research efforts. Researchers don't. After a while as a researcher you will start having your own ideas about where you think the research direction should go, and then you will encounter a glass ceiling about how far you can take this. There's no real career advancement path, so at that point you are stuck.
To address this, make it part of your plan from the outset to enroll in a part time degree program while you are working as a researcher. Most universities offer tuition remission for employees, so as you work you can also get a degree for a heavily discounted fee. Its an entitlement in many full time research assistant posts, but make sure to check this before you start. Any professor you would want to work for will immediately agree to help you figure this out, especially if the degree you want to do is in an area that is relevant to the research. That degree represents your exit strategy, either into full academia, or into a job beyond it, don't procrastinate.
Not as gullible as you, with due respect, since nowhere in my post did I say anything at all about what I believe petitions mean. I wonder, have you ever actually involved yourself in the political process? You might find it more fruitful than trolling forums posting ad-homina.
From petitions.whitehouse.gov: "In a few rare cases (such as specific procurement, law enforcement, or adjudicatory matters), the White House response might not address the facts of a particular matter to avoid exercising improper influence."
This allows Obama to simply say "We cannot comment on the Snowden petition, since he is subject to an ongoing legal enquiry, and we must avoid exercising improper influence."
Meanwhile, several members of government have already declared Snowden guilty of treason without trial - no improper exercise of influence there, right?
Anyone with thoughts about how the petition might have been worded to avoid this loophole?
Slashdot Mirror
Am I the only one who find's Musk's version of scientism worryingly naive?
Musk says other folks "engage in wishful thinking. They ignore counterarguments. They form conclusions based on what others are doing and aren't doing." But then in advocating for his version of the scientific method, he repeats these same errors. He talks about "truth", "probability", "axioms", "correctness", "objectivity", and what's "right," sliding casually between epistemology, naturalism, metaphysics, and ethics, but without pausing to define terms, examine what is given and what has presupposed, or consider the counterarguments those presuppositions have already silenced... surely a case of wishful thinking.
Musk identifies AI as the "biggest threat that humanity faces this century," AI is a product of "the scientific method" he advocates. So how to reconcile the poison and the cure? Shouldn't folks like Musk cogitate on that with a bit more critical depth, before spouting stuff like "It's really helpful for figuring out the tricky things," which sounds like a page from Zuckerberg's playbook, before Russia and Fake News turned up and proved that the world is a lot more complex than that.
Maybe my sense of ire is raised because I've been spending time reading Alfred Whitehead's books (Science and the Modern World, The Concept of Nature, Process and Reality). Whitehead was the co-author with Bertrand Russell of Principia Mathematica, so a major figure in logic. His discussion of the narrow-band thinking that takes place under the name of the scientific method is almost 100 years old, but still just as damning. In Whitehead's view, inductive and axiomatic methods are specialist modes of thought, useful in certain parts of science, but easily prone to fallacies and dogmatism in wider discussions. To pull up a random quote:
"In its use of [methods of induction] natural science has shown a curious mixture of rationalism and irrationalism. Its prevalent tone of thought has been ardently rationalistic within its own borders, and dogmatically irrational beyond those borders. In practice such an attitude tends to become a dogmatic denial that there are any factors in the world not fully expressible in terms of its own primary notions devoid of further generalization. Such a denial is the self-denial of thought."
Here's hoping that industry figures like Zuckerberg and Musk find a way to up their game - I don't expect them to be Whitehead readers, but can we at least move away from disappointing and disingenuous dogma?
With few self-drivers, won't insurance premiums for self-driving become so high that it will be unaffordable for the masses?
just wondering.
TLDR version: I spend a lot of time on Xenforo. On Slashdot I really miss the ability to edit comments, as well as a low-friction Like button. I think /. needs that.
The /. commenting system and Mod points (or God points as I call them) are antiquated and its hurting the community.
Here's why:
Slashdot's commenting system evolved in a time when a typical story had 1000-1500 comments. The comment moderation system was both necessary and innovative. Today it isn.t. There isn't a story on the front page of /. right now with more than 130 comments. A rare story spikes with several thousand comments, but that is atypical. We have lost commenters. The needs of the comment moderation system have changed. Web conventions have shifted but /. has not kept pace.
New Voices /., write a comment or two, don't receive any mod points, nobody responds, their comment disappears, they get disappointed and leave. (this is a guess - it would be interesting to back this with actual data).
I believe contributors come to
A low-friction Like button would be a way to acknowledge or reward a post without needing M[G]od privileges - it would be a way to encourage users to participate, and to recognize new voices.. A "Like" could be treated as e.g. 1/4 of a Mod point for filtering purposes. Fleshing out a Like feature could be part of a way of making /. more social, along with building out better Profile page feature (come on - when was the last time any of you read another users profile page here? They are very broken.) I'd also love Alerts, so you can see when a comment has been responded to. Showing a users karma / level next to their comments would be valuable. Heck, why not just port /. to Xenforo! Ok, that's going too far, but you asked for ideas.
The Long Read /. approach doesn't encourage longer-form commenting and intelligent discussion. And this is where /. is most needed.
The fact that you cannot edit a comment or delete it means users have to get a comment just right first time. You cannot fix typos, add new ideas, refine your argument, or withdraw a point. It promotes rapid fire one-liners and trolling --- but this is already well served by Facebook and Twitter. The
Comment editing would I believe mostly be used by users to fix errors and refine their points or to add extra material. Obviously users could also abuse the system - get a highly modded comment, then modify the text to be offensive or completely change their argument, for example. That can be addressed by clearly indicating when a comment has been edited and offering a link to see the full edit history. Adding a "Report Abuse" button would help to out trolls and poor community players.
I'd like to see Slashdot evolve to better serve its existing users, but also to find new kinds of audiences and discussions. Embracing the editable social web is a step towards that.
It is wrong to assume refugees represent a pure cost. And you are talking about 0.1% of the GDP of Finland here. Do some research before spreading xenophobia. https://www.washingtonpost.com...
The same code snippet gets recycled, munged, riffed on, ported to new languages, rewritten by multiple authors, commented on and then improved, reposted by new authors with bug fixes, and on... The whole value of sites like SO is this kind of sharing. But doesn't that mean attribution, especially for smaller snippets, will become a nightmare?
Masad is perhaps guilty of the very problem he identifies. He reads a science paper, latches onto the word "intuitive", misapplies it, and so misses a key point in the paper.
In the original study, the authors present the same cognitive test to two different groups, one time using Myriad 12pt, the other gray italicized Myriad 10pt. In another experiment they changed the masthead of a document to introduce nonsense characters like @$Ã. In a third experiment, they had one group furrow eyebrows while doing a test. In each case, they found that the group with the "disfluent" condition (small gray font, @$ characters in the masthead, furrowed eyebrows) performed better than the control condition. From this they conclude that their experiments support the cognitive theory that we have two distinct reasoning systems, a rapid "intuitive" reasoning system and a slow "analytical" reasoning system, and something about disfluency prompts us to switch from our rapid to slow reasoning, leading to improved scores.
Masad summarizes: "The theory behind this is that people will default to relying on the automatic, effortless, and primitive system for reasoning. But if things are counter-intuitive or harder to understand we switch to the deeper, deliberate and analytical mode of thinking." Note how "intuitive" has jumped ship. In the original paper, "intuitive" was a label for our fast reasoning system, contrasted with our slow analytical reasoning system. For Masad, "intuitive" refers not to one of our cognitive reasoning systems but rather to the -input-, he suggests that if the input (e.g. the software framework) is counter-intuitive or harder to understand then we use our more analytical reasoning. There is nothing to support that conclusion in this study ... there is nothing counter-intuitive about using a gray 10 point font. The conditions with higher scores weren't harder to understand or more counter-intuitive, they were less legible and more difficult to read. If we translate this study to programming, as Masad proposes, it suggests that if you change your IDE to Myriad 10 pt gray italic, then all of a sudden your code will get better. Hey, go ahead, try it!
Ok, sure, what Masad is actually doing is using a science paper as a prompt, a poetic license for thinking about frameworks and coding. But the kinds of shortcuts he makes are informative - so I'm going to take some poetic license of my own...
First, I think Masad overlooks the importance of reading. The science paper suggests that something about how we read changes how we think. One thing I've noticed about beginner programmers is that they tend to be poor/lazy readers of code. They skim, treating a library or framework function as if it is are magic black box, never to be questioned or investigated. I've had many experiences where I've sat down with a programmer, cracked open a source browser, read the actual source of the library function they are relying on, and heard a gasp, as they realize their assumptions that the framework code is perfect/threadsafe/performant etc. fall away. "You mean every time I do this, it does a linear search through my entire dataset. OMG" "Well, yes, its just code. All you have to do is read it." Promoting code reading has nothing to do with whether or not the framework is intuitive or hard to understand or has "negative space". Its much more about business management priorities and deadlines and culture.
Second, its significant that Masad took a paper from one context and used it to think imaginatively about a very different problem space. Bouncing ideas around freely like that is precisely what the fast/intuitive (if potentially incorrect) style of reasoning is good for. His claim that we need to "overcome intuition" is wrong, in my opinion - its exactly how we stimulate new ideas and debate. His own thought-provoking post proves it.
Blogfather claims to be a champion of links, says they represent the open interconnected spirit of the internet, they are a way to abandon centralism and hierarchies, they are the eyes of the internet, the path to its soul, a way of transferring power out of a site, making us more outward looking, without them a page is blind.
If this is the case, why in the Guardian piece omit a link to the original publication of this story on a blogging platform. Certainly the fact that the story is seven months old and has already been circulated and commented upon is both relevant and interesting. And according to his argument, a link back to the Medium.com story would transfer power out mainstream media to a blogging platform, which is what he wants. And, he suggests, a link is a relation, not an object. Which suggests there is no reason not to include a link, no cost.
The problem is twofold. First, his notion that a link is a relation is far too simplistic. Links are much more thing-like than he implies, in that they encode a rich and living social dynamic. We can presume, for example, that one reason a link to the original article does not appear here is that newspapers trade on novelty, and reprinting a seven month old blog article is hardly that. Second, the very fact that an article is published on Medium.com, a blogging platform, only to be picked up and run by a newspaper - receiving wide commentary along the way - runs counter to his argument that the Internet is being killed by Instagram and Twitter. It demonstrates that these things can comfortably operate side-by-side.
I would have much more intrigued had he written his argument without attaching it to his personal biography and the "Blogfather" label. This is what made me question how his piece is better than Facebook. If his argument were more rigorous and deeply considered, the biographical element would be redundant. By linking his argument to his personal background, he shows that he is precisely aiming to ply reputation to boost polemic, and that's a tactic I associate with social media.
He published the same story in Matter back in June. But in the reprint in the Guardian he fails to link to the original article anywhere.
Pretty much disproves his thesis. The Internet is functioning just fine. Stuff circulates. The link has always been more than a relation between objects.
The blogfather just wants his crown back, and he is using alarmist rhetoric and his personal biography to try and achieve that. In what way is this better than Facebook?
Actually there are loads of reasons to do this, and loads of languages do, including (from Wikipedia) compilers for BASIC, ALGOL, C, D, Pascal, PL/I, Factor, Haskell, Modula-2, Oberon, OCaml, Common Lisp, Scheme, Go, Java, Rust, Python, Scala, Nim, Eiffel, and more. One major reason for self-hosting the compiler is to support richer metaprogramming and tooling. Take a look at some of the posts on why Microsoft sunk years of effort into rewriting the C# compiler in C# (Roslyn). Ditto Perl 6 (Rakudo). The Swift folks recognize this, even if you don't. That is why this is the only one of the feature requests they say would be nice to do - they just have other priorities first. My bet is, down the line, as the language matures, they will reach a point where they are forced to rewrite the compiler in Swift.
Nice inflammatory comment though, thoroughly researched.
sounds a lot like taxes.
Hey Arca, take a tip from the WalkCar. Kill the narration, pick a good tune, and show your product doing something that is actually interesting. (water? obstacles? steps? a hill even?)
We need a mainstream front page news article "Government encryption backdoor is exploited by criminals." Instead the mainstream coverage fails to connect the Juniper story to the debate on backdoors at all. e.g. CNN runs with: "Newly discovered hack has US fearing foreign infiltration", an article stoking fears over hackers and cybersecurity without once mentioning the keys put under the mat by the government.
Lucas made a whole bunch of alterations to the original trilogy that change the feeling of the movie. If you want to time travel back to the 70's, you need to watch the despecialized edition.
Where is your proof?
I presume every time someone goes through the Automated Passport Control system they send the captured image, stamped with a passport ID, off to the FBI.
+1. Lets also not forget there is no good designer tooling story for CSS. With good-old-fashioned DTP apps, you could create a named style in your style catalog, click on an element in the document, and apply that style to it. You could even create based-on styles to manage large style catalogs. With the first wave of DTP apps, we gave designers WYSWIG, Drag-and-drop, and all that good stuff. But CSS didn't support this at all. Instead, designers had to learn to write CSS code in a code editor and then debug a non-trivial rule-based runtime. How many hours have we all spent sitting down with designers trying to debug some quirky CSS selector mess. What a headache. CSS slowed down good web design by years. Sure, CSS beats but we could easily have improved on by adding a few more layout tags to HTML, such as , , , etc, like you find in most other content presentation frameworks. That, plus a simple named-style catalog with variables and based-on would have been so much more appropriate and effective.
Yes, the whole detach content from style is an epic fail. Because the HTML DOM *is* a presentation layer, not a business-content layer. Its got loads of presentation-specific tags, its just missing the ones that we actually need for responsive layout. A more useful content-presentation separation would be more like MVVM (Angular notably heads in that direction).
+1. Lets also not forget there is no good designer tooling story for CSS. With good-old-fashioned DTP apps, you could create a named style in your style catalog, click on an element in the document, and apply that style to it. You could even create based-on styles to manage large style catalogs. With the first wave of DTP apps, we gave designers WYSWIG, Drag-and-drop, and all that good stuff. But CSS didn't support this at all. Instead, designers had to learn to write CSS code in a code editor and then debug a non-trivial rule-based runtime. How many hours have we all spent sitting down with designers trying to debug some quirky CSS selector mess. What a headache. CSS slowed down good web design by years. Sure, CSS beats but we could easily have improved on by adding a few more layout tags to HTML, such as , , etc, like you find in most other content presentation frameworks. That, plus a simple named-style catalog with variables and based-on would have been so much more appropriate and effective.
Yes, the whole detach content from style is an epic fail. Because the HTML DOM *is* a presentation layer, not a business-content layer. Its got loads of presentation-specific tags, its just missing the ones that we actually need for responsive layout. A more useful content-presentation separation would be more like MVVM (Angular notably heads in that direction).
All this study shows is is a difference in attitude towards a game with low stakes while queuing at a passport bureaucracy. Generalizing beyond that demonstrates the limits of the author's ethics, not the participants.
While I was at Microsoft, at one point my manager instructed me to stop having ideas that were outside my assigned area, because it was making another team member look bad, and this would impact the stack ranking of both the team member and my manager. So I saw up close how stack ranking sucks. Still, if I was still at MSFT today, I would be very concerned that the new system drives even more of the compensation process into closed-door management sessions, along with the horse trading and cronyism that invites.
in a region known for earthquakes. sounds fun!
I worked as a research assistant for a professor for six years. It was a great job. The most rewarding part is that I worked on lots of different projects and most of them were cool and intellectually stimulating and fun. It was also fantastic going to conferences and presenting work. You can really push and challenge yourself. It feels a bit like working in a startup. Each professor has their own team and budget and grants and publications, so its like being part of a small company, except that there is a big institution providing backing and benefits. Will your work change the world to be a better place? That's often not so clear cut in academia, but it is certainly a tremendous opportunity for growth and development, and there is demand for computer programming in research.
Professors tend to be incredibly busy so they are looking for self-starters, people who can just get on and contribute without lots of supervision. If you want to get into this area of work, more than academic qualifications, what you need is to demonstrate your own ability to make things. Demo or die. For fields like bio research there's lots of use of small sensors and data capture devices, so one suggestion is to make your own Arduino or Rasberry project, to show that you can come up with a cool idea and have the passion to see it through from start to completion.
Academia is a two tier system, professors and then everyone else. Professors have full control over their research efforts. Researchers don't. After a while as a researcher you will start having your own ideas about where you think the research direction should go, and then you will encounter a glass ceiling about how far you can take this. There's no real career advancement path, so at that point you are stuck.
To address this, make it part of your plan from the outset to enroll in a part time degree program while you are working as a researcher. Most universities offer tuition remission for employees, so as you work you can also get a degree for a heavily discounted fee. Its an entitlement in many full time research assistant posts, but make sure to check this before you start. Any professor you would want to work for will immediately agree to help you figure this out, especially if the degree you want to do is in an area that is relevant to the research. That degree represents your exit strategy, either into full academia, or into a job beyond it, don't procrastinate.
Wow, makes me wish I was starting all over again!
Not as gullible as you, with due respect, since nowhere in my post did I say anything at all about what I believe petitions mean. I wonder, have you ever actually involved yourself in the political process? You might find it more fruitful than trolling forums posting ad-homina.
From petitions.whitehouse.gov: "In a few rare cases (such as specific procurement, law enforcement, or adjudicatory matters), the White House response might not address the facts of a particular matter to avoid exercising improper influence."
This allows Obama to simply say "We cannot comment on the Snowden petition, since he is subject to an ongoing legal enquiry, and we must avoid exercising improper influence."
Meanwhile, several members of government have already declared Snowden guilty of treason without trial - no improper exercise of influence there, right?
Anyone with thoughts about how the petition might have been worded to avoid this loophole?
Doh - the US applicants were charged $38, so they have already bumped their funding level significantly.