Yes, but I can't find any information that clarifies if the technology under the legal telegram is still the old telegraph or if it was replaced with something new.
He uses regular Bic ballpoint pens (he said so in his DeviantArt page) which is simply amazing. I'm actually a fan of the basic Bic pen. Considering how cheap they are, they're very reliable.
In January 2010 I spent two weeks at the Mars Desert Research Station, a simulated Mars base in the Utah desert. Although the Martian conditions were simulated, the science was real, as were the isolation, hostile environment, and problems faced by the six-person crew. Although my official title was Crew Journalist, I soon found myself repairing space suits, helping to keep the habitat running, and having interplanetary adventures I'd never before imagined. My talk on the experience is profusely illustrated with photographs and has gotten rave reviews. Please see http://bentopress.com/mars/ for more information."
That is true. Software developers don't know anything about maintaining a network and are probably a pain in the ass to support. But they do have special needs in that they need to be able to use the web freely, to try out software and keep their own up to date. They need to be able to have a nightly version of a browser updated and install the latest version of Node.js. When firewalls and policies get in the way the company is shooting itself in the foot.
And where would the unobservable universe be? Unless you're thinking about antimatter being coiled up in extra spatial dimensions, everything points to there being a process by which the symmetry is broken.
I'm not sure there can be anything done to improve the "support" of PDF files by the Kindle. I think we need better tools for mungling the PDF file and returning a good combination of plain text and images.
It is part of the core system. There are 3 ways you can use Mobile Safari: opening it, using an installed web app and through WebViews inside other apps. All of them are WebKit and to a certain level Mobile Safari. And Apple explicitly forbids the publication of browsers that don't use WebKit or that use another JavaScript runtime. That's why there's even talk about Firefox for jailbroken iOS devices.
I think the ones that missed the point were the developers and reporters. The whole point of an AI helper is that it behaves as if it were alive, and there is absolutely no way you can accomplish that in 8 hours of work. It's the details that matter for the life-like experience, not the general idea.
It will probably be patentable, and even the algorithm could be patented, but that would hardly be a useful patent. See what the creators of Graphene said about it
We considered patenting; we prepared a patent and it was nearly filed. Then I had an interaction with a big, multinational electronics company. I approached a guy at a conference and said, "We've got this patent coming up, would you be interested in sponsoring it over the years?" It's quite expensive to keep a patent alive for 20 years. The guy told me, "We are looking at graphene, and it might have a future in the long term. If after ten years we find it's really as good as it promises, we will put a hundred patent lawyers on it to write a hundred patents a day, and you will spend the rest of your life, and the gross domestic product of your little island, suing us." That's a direct quote.
Some performance tips make sense. CSS transforms basically paint an image into GPU memory, so this makes a lot of sense:
Keep layers small – Don’t inadvertently create gigantic layers – Memory consumption = width x height x 4 (bit depth)
However, other tips don't make as much sense:
Use closures sparingly & only where necessary
Closures are in the heart of JavaScript. You can't avoid them even if you want to. Instead, learn to write destruction lifecycles for your objects in which you expressively remove references that may cause leaks.
Maybe they need to come up with some kind of "use sanity" mode to build on the existing "use strict",
That's the idea. You'll be able to set "application/ecmascript-6" or something similar to the type attribute of the script tag.
I think in the context of a discussion related to a (not even published) new language that aims to fix front-end development, the future of JavaScript is more relevant than its present.
If I declare a "var" inside a pair of curly braces, it should only be visible in those curly braces
The "let" keyword will fix that. It has block scope. Eventually all variables should be declared with "let".
Syntax for lambdas is overly verbose
There is still no agreement in the ECMAScript comitee about which option to take, but there are two very good proposals: - Arrow function syntax taken from CoffeeScript: (x) -> x * x; - Block lambdas, which allow you to treat chunks of code as data Personally, I love arrow functions.
"new Boolean(false)" is considered true in a conditional expression..
I never heard of that particular example and trying "true == new Boolean(false)" always evaluates to false in a console. But yes, the == type coercing operand is the worst part of JavaScript. The === operator solves 99% of cases. For the 1% that it doesn't help with, ECMAScript 6 will have an "is" operator, and before that probably an Object.is() function.
While we're at it, what's up with the whole separation into primitives and objects?
I agree with you, everything should've been an object from the start. That's probably because of the Java legacy.
Slashdot Mirror
Yes, but I can't find any information that clarifies if the technology under the legal telegram is still the old telegraph or if it was replaced with something new.
You're assuming the tempo doesn't change throughout the piece. This isn't true for a lot of musical pieces. This really needs a technical solution.
Wasn't there a movie in which space suits were exactly like this? I can't remember which.
Introductory wikipedia article: http://en.wikipedia.org/wiki/Graph_theory
He uses regular Bic ballpoint pens (he said so in his DeviantArt page) which is simply amazing. I'm actually a fan of the basic Bic pen. Considering how cheap they are, they're very reliable.
How is that not obvious even under the understanding of obviousness by the USPTO?
No idea. Mechanical energy -motion and/or sound waves- seems a more likely source of power for a phone.
...about a trip to "mars". http://www.youtube.com/watch?v=aZo36huahoI Summary:
"Presented by David D. Levine.
In January 2010 I spent two weeks at the Mars Desert Research Station, a simulated Mars base in the Utah desert. Although the Martian conditions were simulated, the science was real, as were the isolation, hostile environment, and problems faced by the six-person crew. Although my official title was Crew Journalist, I soon found myself repairing space suits, helping to keep the habitat running, and having interplanetary adventures I'd never before imagined. My talk on the experience is profusely illustrated with photographs and has gotten rave reviews. Please see http://bentopress.com/mars/ for more information."
For that reason it is much better to use a server sent header than the meta tag.
Shouldn't he contact the Electronic Frontier Foundation? Isn't its purpose to provide advice in this cases?
That is true. Software developers don't know anything about maintaining a network and are probably a pain in the ass to support. But they do have special needs in that they need to be able to use the web freely, to try out software and keep their own up to date. They need to be able to have a nightly version of a browser updated and install the latest version of Node.js. When firewalls and policies get in the way the company is shooting itself in the foot.
Silicon can (and should) be recycled.
And where would the unobservable universe be? Unless you're thinking about antimatter being coiled up in extra spatial dimensions, everything points to there being a process by which the symmetry is broken.
I'm not sure there can be anything done to improve the "support" of PDF files by the Kindle. I think we need better tools for mungling the PDF file and returning a good combination of plain text and images.
It is part of the core system. There are 3 ways you can use Mobile Safari: opening it, using an installed web app and through WebViews inside other apps. All of them are WebKit and to a certain level Mobile Safari. And Apple explicitly forbids the publication of browsers that don't use WebKit or that use another JavaScript runtime. That's why there's even talk about Firefox for jailbroken iOS devices.
I think the ones that missed the point were the developers and reporters. The whole point of an AI helper is that it behaves as if it were alive, and there is absolutely no way you can accomplish that in 8 hours of work. It's the details that matter for the life-like experience, not the general idea.
States already make vaccination mandatory, including some during pregnancy. It's not that crazy to imagine a "vaccine" for Alzheimer's.
News flash: it won't and it will only get better.
Remember that most users are not technologically literate.
That used to be true. People are getting more and more tech savvy and everyone in the tech industry is aware of it.
It will probably be patentable, and even the algorithm could be patented, but that would hardly be a useful patent. See what the creators of Graphene said about it
We considered patenting; we prepared a patent and it was nearly filed. Then I had an interaction with a big, multinational electronics company. I approached a guy at a conference and said, "We've got this patent coming up, would you be interested in sponsoring it over the years?" It's quite expensive to keep a patent alive for 20 years. The guy told me, "We are looking at graphene, and it might have a future in the long term. If after ten years we find it's really as good as it promises, we will put a hundred patent lawyers on it to write a hundred patents a day, and you will spend the rest of your life, and the gross domestic product of your little island, suing us." That's a direct quote.
http://www.techdirt.com/articles/20101008/09595411336/why-this-year-s-physics-nobel-winner-never-patented-graphene.shtml
Some performance tips make sense. CSS transforms basically paint an image into GPU memory, so this makes a lot of sense:
Keep layers small
– Don’t inadvertently create gigantic layers
– Memory consumption = width x height x 4 (bit depth)
However, other tips don't make as much sense:
Use closures sparingly & only where necessary
Closures are in the heart of JavaScript. You can't avoid them even if you want to. Instead, learn to write destruction lifecycles for your objects in which you expressively remove references that may cause leaks.
Direct link to the slides: https://docs.google.com/viewer?url=http%3A%2F%2Fassets.en.oreilly.com%2F1%2Fevent%2F61%2FNetflix%2520Webkit-Based%2520UI%2520for%2520TV%2520Devices%2520Presentation.pptx
Maybe they need to come up with some kind of "use sanity" mode to build on the existing "use strict",
That's the idea. You'll be able to set "application/ecmascript-6" or something similar to the type attribute of the script tag.
I think in the context of a discussion related to a (not even published) new language that aims to fix front-end development, the future of JavaScript is more relevant than its present.
Global-by-default-unless-declared for variables is a recipe of disaster.
ES5 strict mode already disallows that.
If I declare a "var" inside a pair of curly braces, it should only be visible in those curly braces
The "let" keyword will fix that. It has block scope. Eventually all variables should be declared with "let".
Syntax for lambdas is overly verbose
There is still no agreement in the ECMAScript comitee about which option to take, but there are two very good proposals:
- Arrow function syntax taken from CoffeeScript: (x) -> x * x;
- Block lambdas, which allow you to treat chunks of code as data
Personally, I love arrow functions.
"new Boolean(false)" is considered true in a conditional expression..
I never heard of that particular example and trying "true == new Boolean(false)" always evaluates to false in a console. But yes, the == type coercing operand is the worst part of JavaScript. The === operator solves 99% of cases. For the 1% that it doesn't help with, ECMAScript 6 will have an "is" operator, and before that probably an Object.is() function.
While we're at it, what's up with the whole separation into primitives and objects?
I agree with you, everything should've been an object from the start. That's probably because of the Java legacy.
Maybe the question should be how to promote policies that prevent software engineers from going to the evil dictator side.