denniskane
That's kinda funny when you consider where Mozilla came from... the ashes of a thing called Netscape... who tried to rule the world while a couple grad students were busy plugging away at Stanford, doing it the right way.
I try to stay away from the above kinds of sweeping generalizations about the whole thing nowadays. It is best to let it speak for itself and evolve in its own good time.
Also, link number 5, at https://linuxontheweb.appspot.com/shell.os is for people who just want to poke around the deep system internals via a command line. For that, you need to use the "import" command in order to pull in libraries of commands. For instance, running a command like:
$ import fs && vim
should open up my custom-made vim clone.
It is Chrome only as it relies on access to a local filesystem, and using Native Client plugins.
Considering what I have been going through in my daily life, I could not be more in awe of what Larry has been able to accomplish. I feel that Google is easily an order of magnitude more important than the next closest institution, be it public or private, be it a business or a government.
My offering to Larry is a little thing that I've been working on for the past several years called "Linux on the Web". If you stick those four words together and put it into a relevant search engine, then the link should appear as the top hit. It only works in Chrome... a fact that truly warms my cockles at this moment.
I f*ing love that man.
Screw all the haters.
Suggestion to all potential future reporters out there: pay more attention in your math, science and engineering classes, and less in your liberal (f)arts classes.
We need Linux on the Web!
Enabling access mode bits for web-based filesystems
If anyone is interested in working together with me, the best place to join me is the "native client discuss" forum: https://groups.google.com/forum/#!forum/native-client-discus...
This question of programmatically determining "friend" vs "foe" is highly problematic, to say the least. The only reason why humans make such distinctions is because they rely on them in order to ensure their own physical survival, so they can successfully propagate the species.
In order for a lifeless machine to make these kinds of distinctions, there must exist some kind of objectively verifiable calculation procedure that decides what exactly makes another human friendly or not. If this calculation procedure is simply meant to mimic the subjective calculations that are made by human military strategists, then this technology could not properly be considered the kind of interesting problem that AI researchers would want to work on. But if it is indeed meant to be objectively valid, then it will surely need to initiate a deep learning function that can very easily come up with a conclusion that finally determines that the so-called "friend" as determined by the human military strategist is actually a foe that needs to be eliminated.
So I think that the entire concept of developing highly sophisticated autonomous agents is inextricably wound up in the interesting, objective question of what it truly means to be human, rather than the more prosaic, subjective question of what it means to be a certain type of human that happens to judge another type of human as friend or foe.
"I think we should be very careful about artificial intelligence. If I were to guess like what our biggest existential threat is, it's probably that. So we need to be very careful with the artificial intelligence. Increasingly scientists think there should be some regulatory oversight maybe at the national and international level, just to make sure that we don't do something very foolish. With artificial intelligence we are summoning the demon. In all those stories where there's the guy with the pentagram and the holy water, it's like yeah he's sure he can control the demon. Didn't work out."
The classes of algorithms that are meant to directly interact with people in a way that appears authentically human must obviously be highly regulated, and I certainly agree that these kinds of regulations should be on par with international nuclear oversight bodies.
It is always important to give end users the option to figure out for themselves how the algorithms that they interact with actually function. In order to encourage this kind of thing, I have been working on an online, distributed operating system concept for the past several years, and one of the apps is a simple, "Hello World" kind of an AI that goes by the name, Bertie.
I am working on making the underlying system code (which is mostly JavaScript) completely editable by end users. They will be able to test out their edits in an application window inside of the web page, and will be able to share their changes with each other over the distributed, web-based filesystem that I am actively developing.
If you are running Chrome, you can try out the OS by going to https://nacl-pg.appspot.com/. To see the AI app, just click on the Applications folder, and then click on Bertie's face. Alternatively, if you are feeling lazy, just click on the following link and the Bertie app will automatically open: https://nacl-pg.appspot.com/desk?open=Bertie.
By the way, you can talk to my AI guy if you have a recent Chrome/Chromium browser. It is actually an entire OS in a browser, and the AI guy is an app called Bertie. My current implementation of the OS is called "The Native Client Proving Ground", and can be found here: https://nacl-pg.appspot.com/desk. The OS should install in less than 2 seconds after clicking the link. Then you just open the Applications folder and click on Bertie's face. He will then introduce himself, and you can start talking to him.
Enabling access mode bits for web-based filesystems
...and now a brief word from our corporate sponsors...
Haha, not really :) I'm just trying to get the thing that I've been working on "out there". It's an operating system that runs in a web browser. How's that for client-side awesomeness? The current project I'm hawking is called "The Native Client Proving Ground", in order to get people to see the inherent awesomeness of running arbitrary computational logic on the client. So yeah, encryption is definitely do-able, though not extremely interesting IMO.
I posted this here a couple days ago, and actually got it onto the front page for a brief minute. So fire up your Chrome browsers and check out the infinite potential that exists on the client-side: https://nacl-pg.appspot.com/desk?intro=the-shaker
If you didn't know, Native Client (NaCl) is the plugin architecture for Chrome so you can run arbitrary C/C++ code inside of a sandboxed runtime.
Join the revolution!
Ever heard of the city of Naypyidaw? It took about a decade to build in the middle of bumfuck Burma. It's like 6 times the size of NYC, with 20 lane highways that are almost always empty. I guess they tried to make it seem luxurious, but the ghost-town vibe makes workers want to commute from Rangoon. I just heard about it on 60 minutes during a piece about Aung San Suu Kyi. She's the badass whose party just won in the recent elections there. Which has nothing to do with the current thread, but I'm a rebel like that :)
Given the current state of browser technology, the simple prototype that I've created could not possibly have been done with a dumb little JS thread running in a dumb little Web Worker.
What in the world does it mean to "compile an engine I like better"? Do you really have any clue how much sophistication is going on server side with the SpeechRecognition API? Am I supposed to just magically conjure up something that can be compiled in order to recognize arbitrary words from arbitrary people?
(You can find the post under my submissions, I think it actually got onto the front page on HN. I saw it high up on the second.)
(edit: Whoever downvoted this, I was responding to someone who goes by the name AdmiralAsshat, and I was obviously joking. But that might just be HN automatically downvoting people for using words like asshat. In which case, HN is being a pure asshat.)
Are you seriously implying that pocketsphinx in JS will do anything close to the level of voice recognition necessary to recognize pretty much anyone's voice, sight unseen? I mean, really? You kinda need to train the hell out of that thing to get it to recognize the difference between "merry christmas" and "happy hanukah", and even then, it will only really work for one person.
(Hi Mom!)
About the "Why chrome?" page. I needed to put something there to explain why you need to use Chrome to get any use out of the site. I realize anything that I put there will only wind up as flame bait, so I tried to make it as "politically acceptable" as possible. The bottom line is that I couldn't care less about those political arguments. To me, the web will always be more about technical merit than anything else. Back in the "bad old days" of the original browser wars, Mozilla was at the forefront of pushing the technical boundaries of the web. Not so much anymore. Such is life.
But don't let that stop anyone from engaging in an old-fashioned flame fest. Anything that gets this to the front page of HN is a-okay with me :)
The Native Client Proving Ground (Chrome)
...and now we finally arrive at the fundamental quarrel that I have with using the terms "web" and "application", such that, when linked, can lead to a state of confusion about the nature of the technologies involved.
In the generic sense, there is application vs theory, so that everything that has to do with a real computer program is always going to be an "application", and therefore, any arbitrary program that is used as a backend for a website, can indeed be called something of an "application for the web".
But this is not what normal human beings are thinking about when they use the word "application" in conjunction with their own computing devices. They are thinking about whatever is running on their machine that they can sense, and can thus physically interact with.
In this way, the correct dichotomy is application vs service. So, the Lisp backend for HN is just a service for the user facing application (the web browser).
All of this goes hand-in-hand with my larger point about styles of informing that are not quite as informative as they can possibly be.
My point is that that style of conveying information is more propagandistic than it is truly informative. It is in the style of a typical startup in the valley run by Stanford whiz kids who are trying to impress their classmates as much anything else. Everyone who is already hip to hacker culture knows how to correctly interpret those kinds of statements, but everyone else is just left more confused.
Gnu-ish tools like Guile really have no place in the marketplace of "hipster in a Starbucks with a Macbook plastered with shiny decals" kinds of technologies, and to pretend otherwise is to do a disservice to humanity, IMO.
I just see this style of "informing" as an end of a kind of age of innocence, when seekers of deep knowledge about technology could go to the gnu.org domain, and be absolutely certain that they weren't being sold a bill of goods.