I think Microsoft is at an advantage here, because they play both sides and developers probably have an easier time porting between the two Microsoft platforms.
Re:I used to laugh at "web programmers"
on
In-Depth Look At HTML5
·
· Score: 4, Interesting
I don't know how it is in the US, a lot of the time this is all self-taught. Because pretty much no-one seems to teach HTML/CSS/JS/etc. properly in school/university and so on.
Javascript is one of the most used programming languages and because it looks simple or familair most people assume it is, but in reallity it is the probably the least understood language by frequent developers. Most have no clue what prototypal inheritance is for example.
Also the Javascript name is just a marketing ploy because it has nothing to do with Java.
The core of the language is very small and was created and working in just 10 days.
It is a functional programming language with a C-syntax.
With the recent creating of node.js (a fully event-driven framework for writing network programs) Javascript has also become much more populair on the server.
Node.js was created in 2009 and is already almost the most watched project on github.com for example.
There introduction video where the creator/author explains what it is about:
Firefox and Chromium (non-Google-branded open source base of Chrome) are open source browsers, the H.264 license model does not fit well with the open source development model.
For example when a Linux distribution compiles Firefox or Chromium, they would need to get their own license for all the users of that distribution.
The license cost up to 5000000 annually.
In the past only Chrome included H.264 and not Chromium, Google didn't want to seperately maintain that part of the code, thus they dropped support for H.264 from Chrome.
Just get with the program, H.264 for all browsers is not going to happen.
There is already a kitchensink in the specification. Although at this point it is only an image:
http://images.whatwg.org/abstract.pnghttp://www.whatwg.org/specs/web-apps/current-work/complete/
Anyway support for the device-tag is planned for the next big update. The device-tag allows access to the webcam (like Flash currently does), serial ports (so you can use your barcode reader with your webapplication), but also supposedly USB-stick-fileaccess (maybe useful for something like ChromeOS ?) and so on.
Yes, yes, all with a banner at the top of the browser "would you like to give this website access to the filesystem of your recently plugged in USB-stick.", bla, bla.
How do you think H.264 started out ? With zero hardware support, this is where VP8 was a few months ago. Now they have a few hardware manufacturers that ship VP8 built in. Any many said they would do the same.
The whole H.264 / VP8 debate is also about looking at the future not just now.
Some say the SSD technology will reach a limit in a few years this is because of similair limits as processors have with 25nm manufacturing process and so on.
Atleast that is what some say, I don't know if it is true.:-)
You forgot one thing, many many people are starting to use mobile devices more and more to surf the web. Mozilla latest beta of Mobile Firefox is supposedly the fastest browser for mobile devices.
Having more competition in the mobile space is also a good thing because it allows webdevelopers to create websites which can take advantage of the new HTML5-API's for offline use. HTML5 is not only a new version of HTML but was specifically created to allow developers to easily create applications for the web (so for example you won't need an appstore/native apps in many different programming languages but just use 'one' open standard for all devices).
This allows a for example a webmail 'application' to pre-download messages to your phone for when you don't have an internet connection but still like to view your e-mails and reply. The reply message can than be saved and automatically sent when the internet connection works again.
IE might have improved a lot performance wise, it is still way behind implementing many parts of many of the specs the other browsers already supported in their previous versions like Firefox 3.6.
Actually the oil industry in the US gets money from the government. This is because getting oil out of the ground in the US isn't very economically viable anymore.
Maybe the last few months it wasn't necessary anymore because the oil price was high. But people really do (maybe did) get paid to do so.
To put it bluntly artificial Intelligence software is software of which the behaviour can be different in similair situation based on past experiences.
I would rather have something of which the behaviour is predictable thank you very much.
If you want to parse HTML as XML, just use HTMLTidy. I know it can create proper XHTML-document (thus XML) of pretty much any HTML4-document. I guess it can handle HTML5 too, but haven't tested it.
Yes, I'm sure that is interresting. But why not use DNSSEC, SSL/TLS-certificates, SSL/TLS Certificate Authorities and DKIM which already solve all these problems. 1. SSL/TLS-certificates are created by the Certificate Authorities 2. SSL/TLS encryption for communication between mailservers 3. SSL/TLS encryption with authentication for delivery from the user to the mailserver 4. DKIM signing of the e-mail on the mailserver to verify that the mail came from the user 5. DNSSEC to publish the DKIM key 6. DNSSEC to verify the domain 7. All we need is an interface in the e-mail client (or maybe partly on the mailbox server where the e-mail is delivered to) which checks that the the above is valid and the domain has an HTTPS EV-like certificate (green bar in the browser) to prevent phishing with similair looking domains.
I think simpler is possible too, it is more a list of technology which can already be applied.:-)
Let's see, they create new drivers which are used in the other BSD and the Linux kernel, they are used as a base for Junos for the Juniper routers. I guess FreeBSD like the Linux kernel is used for TCP/IP-research.
But OpenBSD maintains OpenSSH which is used in pretty much all Unix-like environment and embedded system like routers and managed switches.
I still think it makes Debian interresting because they adopted FreeBSD as their second kernel, having the same environment on all systems is very useful.
Slashdot Mirror
I run my apps on a 'private-cloud', a small Soekris box in the corner with an encrypted backup in the 'real cloud'.
And life is good again.
I'm just waiting for the 'freedombox' to be ready and easy to install to replace it.
I think Microsoft is at an advantage here, because they play both sides and developers probably have an easier time porting between the two Microsoft platforms.
I don't know how it is in the US, a lot of the time this is all self-taught. Because pretty much no-one seems to teach HTML/CSS/JS/etc. properly in school/university and so on.
Javascript is one of the most used programming languages and because it looks simple or familair most people assume it is, but in reallity it is the probably the least understood language by frequent developers. Most have no clue what prototypal inheritance is for example.
Also the Javascript name is just a marketing ploy because it has nothing to do with Java.
The core of the language is very small and was created and working in just 10 days.
It is a functional programming language with a C-syntax.
With the recent creating of node.js (a fully event-driven framework for writing network programs) Javascript has also become much more populair on the server.
Node.js was created in 2009 and is already almost the most watched project on github.com for example.
There introduction video where the creator/author explains what it is about:
http://developer.yahoo.com/yui/theater/video.php?v=dahl-node
So it is just an event-loop just like a webserver like nginx.
One of the design goals is actually:
The API should be both familiar to client-side JS programmers and old school UNIX hackers.
I guess that applies to me twice. :-)
Firefox and Chromium (non-Google-branded open source base of Chrome) are open source browsers, the H.264 license model does not fit well with the open source development model. For example when a Linux distribution compiles Firefox or Chromium, they would need to get their own license for all the users of that distribution. The license cost up to 5000000 annually. In the past only Chrome included H.264 and not Chromium, Google didn't want to seperately maintain that part of the code, thus they dropped support for H.264 from Chrome. Just get with the program, H.264 for all browsers is not going to happen.
There is already a kitchensink in the specification. Although at this point it is only an image: http://images.whatwg.org/abstract.png http://www.whatwg.org/specs/web-apps/current-work/complete/ Anyway support for the device-tag is planned for the next big update. The device-tag allows access to the webcam (like Flash currently does), serial ports (so you can use your barcode reader with your webapplication), but also supposedly USB-stick-fileaccess (maybe useful for something like ChromeOS ?) and so on. Yes, yes, all with a banner at the top of the browser "would you like to give this website access to the filesystem of your recently plugged in USB-stick.", bla, bla.
How do you think H.264 started out ? With zero hardware support, this is where VP8 was a few months ago. Now they have a few hardware manufacturers that ship VP8 built in. Any many said they would do the same. The whole H.264 / VP8 debate is also about looking at the future not just now.
Some say the SSD technology will reach a limit in a few years this is because of similair limits as processors have with 25nm manufacturing process and so on. Atleast that is what some say, I don't know if it is true. :-)
Let's try that again because that was horrible. Here are the proper links, I hope: http://caniuse.com/#compare=y&b1=ie|9&b2=firefox|4 http://caniuse.com/#compare=y&b1=ie|9&b2=firefox|3.6 Although I think the site doesn't want to help either. whatever.
You forgot one thing, many many people are starting to use mobile devices more and more to surf the web. Mozilla latest beta of Mobile Firefox is supposedly the fastest browser for mobile devices.
Having more competition in the mobile space is also a good thing because it allows webdevelopers to create websites which can take advantage of the new HTML5-API's for offline use. HTML5 is not only a new version of HTML but was specifically created to allow developers to easily create applications for the web (so for example you won't need an appstore/native apps in many different programming languages but just use 'one' open standard for all devices).
This allows a for example a webmail 'application' to pre-download messages to your phone for when you don't have an internet connection but still like to view your e-mails and reply. The reply message can than be saved and automatically sent when the internet connection works again.
IE might have improved a lot performance wise, it is still way behind implementing many parts of many of the specs the other browsers already supported in their previous versions like Firefox 3.6.
Here an example list:
http://caniuse.com/#compare=y&b1=ie|9&b2=firefox|4
http://caniuse.com/#compare=y&b1=ie|9&b2=firefox|3.6
Switch browser vendor I would say ! :-)
Actually Microsoft just recommends people to upgrade to IE8:
http://www.ie6countdown.com/
Yeah, this is true.
I was wondering if people knew more than I did because I don't really use Facebook.
But I guess it is mostly convience, no double administration and less setup time.
Yes, yes, that is all fine. But why do you need Facebook for that ?
That is why people keep saying we'll be using a mix of all these forms because some are going to be more expensive and others are not reliable enough.
Actually the oil industry in the US gets money from the government. This is because getting oil out of the ground in the US isn't very economically viable anymore.
Maybe the last few months it wasn't necessary anymore because the oil price was high. But people really do (maybe did) get paid to do so.
If I should believe this comment:
http://science.slashdot.org/comments.pl?sid=2024518&cid=35395010
It might not be the same kind of aerogel.
Sorry wrong thread. :-(
I guess we'll know when defcon changes to something other then the current 5
I guess we'll know when defcon changes to something other then the current 5.
Doubt it.
To put it bluntly artificial Intelligence software is software of which the behaviour can be different in similair situation based on past experiences.
I would rather have something of which the behaviour is predictable thank you very much.
If you want to parse HTML as XML, just use HTMLTidy. I know it can create proper XHTML-document (thus XML) of pretty much any HTML4-document. I guess it can handle HTML5 too, but haven't tested it.
Yes, I'm sure that is interresting. But why not use DNSSEC, SSL/TLS-certificates, SSL/TLS Certificate Authorities and DKIM which already solve all these problems.
1. SSL/TLS-certificates are created by the Certificate Authorities
2. SSL/TLS encryption for communication between mailservers
3. SSL/TLS encryption with authentication for delivery from the user to the mailserver
4. DKIM signing of the e-mail on the mailserver to verify that the mail came from the user
5. DNSSEC to publish the DKIM key
6. DNSSEC to verify the domain
7. All we need is an interface in the e-mail client (or maybe partly on the mailbox server where the e-mail is delivered to) which checks that the the above is valid and the domain has an HTTPS EV-like certificate (green bar in the browser) to prevent phishing with similair looking domains.
I think simpler is possible too, it is more a list of technology which can already be applied. :-)
Combine it with DKIM and DNSSEC and your are done.
It is not even encrypted. Just a the mailservers use encryption for the transport and the system is seperate from the normal internet mailservers.
My guess is, it is SMTP-authentication over SSL/TLS for sending mail so they know exactly who send it (atleast which e-mail client).
Let's see, they create new drivers which are used in the other BSD and the Linux kernel, they are used as a base for Junos for the Juniper routers. I guess FreeBSD like the Linux kernel is used for TCP/IP-research.
But OpenBSD maintains OpenSSH which is used in pretty much all Unix-like environment and embedded system like routers and managed switches.
I still think it makes Debian interresting because they adopted FreeBSD as their second kernel, having the same environment on all systems is very useful.