It wouldn't help to port jQuery to Asm.js. The slowers part of the browser is the DOM and that is all jQuery does is talk to the DOM in a that appeals to a certain crowd.
The reason for it being slow is because you are bridging from one language (C++ of the browser engine) to the other (dynamically typed Javascript).
It has been suggested it might be useful to port something like DOM.js (a Javascript implementation of the DOM) to asm.js that way, that way the back and forth will remain within Javascript and thus will be faster.
(this also makes fun of hydrogen powered cars because with hydrogen powered cars 'fuel' also needs to be compressed very much, so a lot of energy is lost to transfer hydrogen into a car. So why not use that energy directly ?)
But let's have a look at something a bit more modern.
Did you know with LTE Advanced it's all IP-traffic ? Even speech is IP-traffic.
Did you know the encryption they use is IPSEC ? LTE is 2 types of packets: data and control.
Did you know IPSEC is optional ? The network operator decides what you get, when you roam and connect to an other operator you might actually get something else.
So they got proper encryption (at least I hope they pick the right algorithms, we know IPSEC supports some good but also bad ones), but it's optional. That doesn't sounds particularly smart.
I don't know what the operators really do, I read somewhere: control messages are encrypted, data not always.
Or use WebRTC, it's encrypted by default with the other encrypted RTP protocol: SRTP.
There is even a system where you can be sure who you are talking to and be sure there is no man-in-the-middle, with an RFC draft to tie it into oAuth or BrowserID protocols:
IBM Watson that defeated the humans at playing Jeopardy is basically just a cluster of machines running Apache Hadoop. So architecturally there isn't anything really special about the hardware or software.
If things keep progressing as they are: in 10 years, your smartphone will have the same processing power, storage and memory as IBM Watson does now at the price and size of a smartphone from now.
Every communication network is or is already moving to an IP-based solution.
For example 4G/LTE Advanced is also IP-based. Most TV is now digital. Although, at least in my country analog still exists.
That doesn't mean it's not on a separate network. Separate from the Internet. So it isn't like we all depends on the same network. The problem is more than 90% of a wireless network is actually wired. And they might end up in the same fiber trench.
We used to have only one bidirectional network, POTS (TV and radio are only one direction).
Now most people have 2 bidirectional networks: mobile and wired Internet.
The problem is POTS is powered by the network.
And lots of wired Internet connection don't have a battery back up. And smartphone battery life sucks.
Can we life with these disadvantages ? I guess we'll find out.
If something would happen at the IETF, mostly likely out come would be if the IETF would create a work group to create a protocol, maybe based on one of those existing protocols. Just like HTTP/2.0 is based on SPDY, but isn't SPDY.
OpenShift runs tenant programs in a SELinux 'jail', but OpenShift is going to adopt Docker. Just like OpenStack has already adopted Docker support. There is even an OpenStack project by many companies, including RedHat, which is gonna work on creating a well integrated OpenShift and OpenStack combination. The project name is: Solum.
You specify what distro and version your application can run on and you create a container with Docker which uses that image as a base to run your application.
Basically: Linux-application on top of Linux-distribution inside a container on top of an other Linux distribution.
Slashdot Mirror
Actually, lots of people use containers:
https://www.docker.io/
https://www.youtube.com/watch?v=p-x9wC94E38
Facebook, Google and many smaller players understood this years ago.
(not talking about the ridiculously oversubscribed VPS you can get for $3 a month)
It wouldn't help to port jQuery to Asm.js. The slowers part of the browser is the DOM and that is all jQuery does is talk to the DOM in a that appeals to a certain crowd.
The reason for it being slow is because you are bridging from one language (C++ of the browser engine) to the other (dynamically typed Javascript).
It has been suggested it might be useful to port something like DOM.js (a Javascript implementation of the DOM) to asm.js that way, that way the back and forth will remain within Javascript and thus will be faster.
That is what TypedArrays are for, look them up. They were introduced for WebGL, but also implemented by browsers that didn't even support WebGL.
I feel a Slashdot Poll might be in our future:
Number of Windows XP security updates Microsoft will release in the first and second year after they said they wouldn't:
- 0
- 1-5
- 5-10
- 11 or more
You build some pretty good cars with that (video from a couple of years ago):
https://www.youtube.com/watch?v=OJeMnZuOOJU
Looks to me like Peugeot might bring a hybrid in production:
http://www.dailymail.co.uk/news/article-2266632/Car-runs-air-coming-soon-Peugeot-Citroen-unveil-new-117mpg-hybrid.html
(this also makes fun of hydrogen powered cars because with hydrogen powered cars 'fuel' also needs to be compressed very much, so a lot of energy is lost to transfer hydrogen into a car. So why not use that energy directly ?)
That is exactly correct.
The summary is wrong.
Fedora has the same thing as the Ubuntu distributions, it's called a spin.
GSM has had problems for many years.
But let's have a look at something a bit more modern.
Did you know with LTE Advanced it's all IP-traffic ? Even speech is IP-traffic.
Did you know the encryption they use is IPSEC ? LTE is 2 types of packets: data and control.
Did you know IPSEC is optional ? The network operator decides what you get, when you roam and connect to an other operator you might actually get something else.
So they got proper encryption (at least I hope they pick the right algorithms, we know IPSEC supports some good but also bad ones), but it's optional. That doesn't sounds particularly smart.
I don't know what the operators really do, I read somewhere: control messages are encrypted, data not always.
Or use WebRTC, it's encrypted by default with the other encrypted RTP protocol: SRTP.
There is even a system where you can be sure who you are talking to and be sure there is no man-in-the-middle, with an RFC draft to tie it into oAuth or BrowserID protocols:
http://tools.ietf.org/html/draft-ietf-rtcweb-security-arch-07
https://air.mozilla.org/intern-presentation-seys/
With BrowserID/Persona your privacy will also be preserved.
Persona is the first implementation by Mozilla of the Mozilla developed protocol.
nVidia has already taken notice because they are one of the companies working with Valve: https://developer.nvidia.com/sites/default/files/akamai/gamedev/docs/Porting%20Source%20to%20Linux.pdf
IBM Watson that defeated the humans at playing Jeopardy is basically just a cluster of machines running Apache Hadoop. So architecturally there isn't anything really special about the hardware or software.
If things keep progressing as they are: in 10 years, your smartphone will have the same processing power, storage and memory as IBM Watson does now at the price and size of a smartphone from now.
Think about that.
In a way, yes. Browser were already using something called a the 'shadow DOM', they are starting to make it available to web developers:
http://blog.teamtreehouse.com/working-with-shadow-dom
So finally HTML5 is getting reusable components and templates, instead of more Javascript, finally some more declerative support:
http://html5-demos.appspot.com/static/webcomponents/index.html#1
Sure, but did you also see this ?:
"The Windows driver also had much larger spikes in the frame latency than the Intel Linux driver."
http://openbenchmarking.org/embed.php?i=1311280-SO-INTELWIN869&sha=869d65c&p=2
Do you remember the days when Linux didn't perform well in this area ?
You probably want LibreOffice instead of OpenOffice.
Depends on what more memory and higher resolution does with the battery life.
If the Jolla device has twice the battery life, I wouldn't mind paying for that.
Also at least 90% of a wireless networks is actually wired.
Yes, but the network powers the phone.
That is what potentially makes POTS more reliable.
And don't forget the phone is powered by the network.
So what is going on ?
Every communication network is or is already moving to an IP-based solution.
For example 4G/LTE Advanced is also IP-based. Most TV is now digital. Although, at least in my country analog still exists.
That doesn't mean it's not on a separate network. Separate from the Internet. So it isn't like we all depends on the same network. The problem is more than 90% of a wireless network is actually wired. And they might end up in the same fiber trench.
We used to have only one bidirectional network, POTS (TV and radio are only one direction).
Now most people have 2 bidirectional networks: mobile and wired Internet.
The problem is POTS is powered by the network.
And lots of wired Internet connection don't have a battery back up. And smartphone battery life sucks.
Can we life with these disadvantages ? I guess we'll find out.
If something would happen at the IETF, mostly likely out come would be if the IETF would create a work group to create a protocol, maybe based on one of those existing protocols. Just like HTTP/2.0 is based on SPDY, but isn't SPDY.
Well, it does brings cheap labor for US-based businesses.
Cheap labor, could mean easier to compete with other countries.
One part of being a white hat hacker would be to report the problem after you found the problem.
Instead of just abusing the hell out of it, hoping it won't get discovered.
Maybe people clicked through the warning ?
The people that cross the south border come into the US to work for very little money.
Maybe that has something to do with it.
OpenShift runs tenant programs in a SELinux 'jail', but OpenShift is going to adopt Docker. Just like OpenStack has already adopted Docker support. There is even an OpenStack project by many companies, including RedHat, which is gonna work on creating a well integrated OpenShift and OpenStack combination. The project name is: Solum.
In a way, yes.
You specify what distro and version your application can run on and you create a container with Docker which uses that image as a base to run your application.
Basically: Linux-application on top of Linux-distribution inside a container on top of an other Linux distribution.