OK, so that makes sense. They have one massive monolithic product, and have to replay history of patches on top of themselves. Most annoying is when you apply many patches, just to have the Windows tell you that those patches have prepared you for the next set of patches.
I've never understood the need to apply patches on patches on patches on... Maybe it's just a Linux thing I'm used to, or maybe I'm not even aware it's happening, but why isn't there just a single "updated" version that is pushed out?
I've only been using Linux for ~2 years. and funny enough I've already experienced the same thing. The first 6 months using Linux was just trying every different distros/windowing system combination possible. When I finally found my most optimal setup, they changed it into some horrible thing called Unity. So for a short time I went back to Windows, until I lost my mind over loss of functionality, and came back to Linux-land.
The second most frustrating thing is lack of decent graphics drivers. It took me weeks to figure out the optimal setup for the stupid nvidia optimus card.
I'd love to recommend Linux to my friends and family but I can't until they can do things like run Photoshop, play video games, and not have to use the command line when things go horribly wrong.
I hear and read glimpses that the government can enable a tracker inside your phone, even when you have it off. How likely is it that the government can track you even if you phone is in airplane mode?
I emailed someone from project honeypot about this same thing. They said they would setup a service where people could submit unauthorized login attempts automatically. (right now my honeypot just emails the result of logwatch --service sshd to an account)
It it useful information. I've used it to contact some providers (e.g. aws, linode, etc.) about the machines making unauthorized attempts. Usually it's from a server hosting a website that hasn't been updated in years.
Can we all email this a million times to the "Cambridge academic" that believes suing developers is a good? Seriously, how long did it take to figure out this was such a bad idea.
Thank you for posting this. I've been programming JavaScript since 2007, and it's the only language I've ever really took the time to understand. So I can't comment from your vantage point. But what I can say is that once I had a full appreciation for JavaScript inheritance, first-class function, and the other things that make JavaScript great, it has been extremely easy to work with. Of course there are parts that will kill you if abused, but doesn't every language?
Since they are more difficult to build, I would think they should get started sooner. If there's a bandwidth problem now, just imagine how bad it will be in 3 years.
I won't disagree that the majority of web developers do things like load jQuery, before they even know why they need it. Usually because they're a novice trying to create a blog for their cousin and never had any actual web development experience. But please remember that not all web developers are like that.
When used properly JavaScript can enhance the overall security and experience of the site. For example, I like to SHA1 my user's passwords before submitting them to the server. Then I'll SHA1 that with a random seed and store it in the database. Or I'll add simple encryption algorithms to encrypt sensitive data. Of course it all runs under HTTPS, but never hurts to have a little more security.
Unfortunately the masses of web developers who "have gone suck fucking heavy" with JavaScript drown out the few of us who know when and how to use it.
What you're not taking into account is the complexity of State laws. States have a wide range of gun regulations that vary greatly. Let's look at Gun Homicides specifically. In California, which is the most restrictive State, is the 4th highest at 4.82 per 100,000. While Utah, which has some of the most lenient laws, has 0.93 per 100,000. If you take the time to graph out all the data you'll find that there are States with very restrictive gun laws, which have both high and low death rates per capita. Same with lenient States. What you'll find is low statistical correlation between gun restrictions and gun deaths.
In the end the statistics plainly show that it is impossible to say either way whether gun restrictions prevent deaths.
This is hardly going to affect Google. DNT basically says you can't be tracked by third-party cookies. Meaning, a third party can't set a cookie on your browser from some other website. Since Google can set a cookie on your machine when you use their search engine to find something, it's not in violation of DNT. And if you're logged in to your Google account, they can still cross-reference all your search history, +1's, etc. to get you personalized results. It's mostly going to affect companies like AdClickMedia.
No straw-man here. You're original comment was just all inclusive. All you said was "supporting code [...] necessary to run". So you would have to include all supporting code. If you had excluded OS level instructions, then I wouldn't have had a problem. Because if Tron had been written in Java, you would also have to include all the source for the JVM. Now, a C level program that compiled down to machine code, then cool. But you didn't specify the scope of "supporting code".
- Appreciating data-types, their limitations and the perils of using casting them incorrectly helped me a lot in understanding about things I need to be careful about
Understanding data types is important in JavaScript. How to convert from one type to another (e.g. String to Number). Just need to remember that you can reuse a variable name. Also it's important they understand that there are no integers (only IEEE-754 double precision floats), and why 0.1 + 0.2 !== 0.3.
Are they going skip the concept of Pointers ? It's not wise to use them unless necessary but to be aware of the concept was very rewarding for me
Understanding pointers in JavaScript is very necessary. All Arrays and Objects in JavaScript are passed by reference. If you don't understand the concept of a pointer in JavaScript then you will spend a lot of time beating your head into the screen wondering why the Array you passed as a function argument keeps getting altered.
If they switch to another language to teach stuff which JS doesn't support, they might lose their audience and so blind side a large set of them.
I'm not being facetious here, but I could say the same about developers everywhere who hate JavaScript but have little exposure to the language. That problem goes both ways.
I'm calling B.S. I was raised in a single parent low income home where my mother was able to hold a full-time job and was still able to make us healthy meals. Morning was easy, just a bowl of oatmeal or such. Takes a whole 3 minutes for a PB&J, or even easier was to have yesterdays leftovers for lunch. Dinners would be pre-prepared or left in a crockpot or any number of different methods that were quick and easy.
I mean really, look at the number of hours spent on the TV each week and tell me they couldn't take 30 mins out every day for at least one decent meal. It all comes down to priorities. Nothing more.
There are plenty of awesome books that clearly and concisely explain how to use JavaScript most efficiently. Off the top of my head, John Resig's two books "Pro JavaScript Techniques" and "Secrets of the JavaScript Ninja" would also have to be at the top of your "most widely-respected" list. "The Good Parts" has a small section explaining things that will cause programmers problems down the road. And it does this because the language is so flexible people who don't want to learn the language properly will hack together anything just to get past the "pain" of it all.
I've been coding javascript since 2002 and love the language. To quote Robin Williams, "People call these things imperfections, but there not. Ah, that's the good stuff." And that's the way it is. JavaScript has way more things right about it then there are wrong. Every language has its imperfections, and for some reason people are convinced that javascript is only that. Unless you code in a language full time for years, don't think you can speak authoritatively on it.
Slashdot Mirror
OK, so that makes sense. They have one massive monolithic product, and have to replay history of patches on top of themselves. Most annoying is when you apply many patches, just to have the Windows tell you that those patches have prepared you for the next set of patches.
I've never understood the need to apply patches on patches on patches on ... Maybe it's just a Linux thing I'm used to, or maybe I'm not even aware it's happening, but why isn't there just a single "updated" version that is pushed out?
ggdG
I'm interested to see how this would work with the WebRTC API, to allow for browser-based encrypted P2P communications.
ok, so there went 30 mins of my life.
Am I the only one that read "Domscheit-Berg" as "DumbShit-Berg"?
I've only been using Linux for ~2 years. and funny enough I've already experienced the same thing. The first 6 months using Linux was just trying every different distros/windowing system combination possible. When I finally found my most optimal setup, they changed it into some horrible thing called Unity. So for a short time I went back to Windows, until I lost my mind over loss of functionality, and came back to Linux-land.
The second most frustrating thing is lack of decent graphics drivers. It took me weeks to figure out the optimal setup for the stupid nvidia optimus card.
I'd love to recommend Linux to my friends and family but I can't until they can do things like run Photoshop, play video games, and not have to use the command line when things go horribly wrong.
Awesome. That gives me a little stronger sense of security when I put my phone in airplane mode.
I hear and read glimpses that the government can enable a tracker inside your phone, even when you have it off. How likely is it that the government can track you even if you phone is in airplane mode?
I emailed someone from project honeypot about this same thing. They said they would setup a service where people could submit unauthorized login attempts automatically. (right now my honeypot just emails the result of logwatch --service sshd to an account)
It it useful information. I've used it to contact some providers (e.g. aws, linode, etc.) about the machines making unauthorized attempts. Usually it's from a server hosting a website that hasn't been updated in years.
Can we all email this a million times to the "Cambridge academic" that believes suing developers is a good? Seriously, how long did it take to figure out this was such a bad idea.
Thank you for posting this. I've been programming JavaScript since 2007, and it's the only language I've ever really took the time to understand. So I can't comment from your vantage point. But what I can say is that once I had a full appreciation for JavaScript inheritance, first-class function, and the other things that make JavaScript great, it has been extremely easy to work with. Of course there are parts that will kill you if abused, but doesn't every language?
Since they are more difficult to build, I would think they should get started sooner. If there's a bandwidth problem now, just imagine how bad it will be in 3 years.
I won't disagree that the majority of web developers do things like load jQuery, before they even know why they need it. Usually because they're a novice trying to create a blog for their cousin and never had any actual web development experience. But please remember that not all web developers are like that.
When used properly JavaScript can enhance the overall security and experience of the site. For example, I like to SHA1 my user's passwords before submitting them to the server. Then I'll SHA1 that with a random seed and store it in the database. Or I'll add simple encryption algorithms to encrypt sensitive data. Of course it all runs under HTTPS, but never hurts to have a little more security.
Unfortunately the masses of web developers who "have gone suck fucking heavy" with JavaScript drown out the few of us who know when and how to use it.
What you're not taking into account is the complexity of State laws. States have a wide range of gun regulations that vary greatly. Let's look at Gun Homicides specifically. In California, which is the most restrictive State, is the 4th highest at 4.82 per 100,000. While Utah, which has some of the most lenient laws, has 0.93 per 100,000. If you take the time to graph out all the data you'll find that there are States with very restrictive gun laws, which have both high and low death rates per capita. Same with lenient States. What you'll find is low statistical correlation between gun restrictions and gun deaths.
In the end the statistics plainly show that it is impossible to say either way whether gun restrictions prevent deaths.
Just wonder how useful iris scans are going to be: http://www.i-programmer.info/news/149-security/4278-irises-change-over-time-problem-for-biometric-testing.html
I can confirm that this is not a complete list. None of the passwords I've ever used are in the list.
This is hardly going to affect Google. DNT basically says you can't be tracked by third-party cookies. Meaning, a third party can't set a cookie on your browser from some other website. Since Google can set a cookie on your machine when you use their search engine to find something, it's not in violation of DNT. And if you're logged in to your Google account, they can still cross-reference all your search history, +1's, etc. to get you personalized results. It's mostly going to affect companies like AdClickMedia.
More practically, they have good code tracking so they know exactly who committed each bug. Wonder if they have a three strikes rule?
No straw-man here. You're original comment was just all inclusive. All you said was "supporting code [...] necessary to run". So you would have to include all supporting code. If you had excluded OS level instructions, then I wouldn't have had a problem. Because if Tron had been written in Java, you would also have to include all the source for the JVM. Now, a C level program that compiled down to machine code, then cool. But you didn't specify the scope of "supporting code".
If you're going that far, then how many more lines of code were required to write the kernel of your operating system?
You've just stuck your head down a rabbit hole, and the rabbit ripped your head off.
Seriously. Disable scrollback and use screen. You're life will improve.
- Appreciating data-types, their limitations and the perils of using casting them incorrectly helped me a lot in understanding about things I need to be careful about
Understanding data types is important in JavaScript. How to convert from one type to another (e.g. String to Number). Just need to remember that you can reuse a variable name. Also it's important they understand that there are no integers (only IEEE-754 double precision floats), and why 0.1 + 0.2 !== 0.3.
Are they going skip the concept of Pointers ? It's not wise to use them unless necessary but to be aware of the concept was very rewarding for me
Understanding pointers in JavaScript is very necessary. All Arrays and Objects in JavaScript are passed by reference. If you don't understand the concept of a pointer in JavaScript then you will spend a lot of time beating your head into the screen wondering why the Array you passed as a function argument keeps getting altered.
If they switch to another language to teach stuff which JS doesn't support, they might lose their audience and so blind side a large set of them.
I'm not being facetious here, but I could say the same about developers everywhere who hate JavaScript but have little exposure to the language. That problem goes both ways.
I'm calling B.S. I was raised in a single parent low income home where my mother was able to hold a full-time job and was still able to make us healthy meals. Morning was easy, just a bowl of oatmeal or such. Takes a whole 3 minutes for a PB&J, or even easier was to have yesterdays leftovers for lunch. Dinners would be pre-prepared or left in a crockpot or any number of different methods that were quick and easy.
I mean really, look at the number of hours spent on the TV each week and tell me they couldn't take 30 mins out every day for at least one decent meal. It all comes down to priorities. Nothing more.
There are plenty of awesome books that clearly and concisely explain how to use JavaScript most efficiently. Off the top of my head, John Resig's two books "Pro JavaScript Techniques" and "Secrets of the JavaScript Ninja" would also have to be at the top of your "most widely-respected" list. "The Good Parts" has a small section explaining things that will cause programmers problems down the road. And it does this because the language is so flexible people who don't want to learn the language properly will hack together anything just to get past the "pain" of it all.
I've been coding javascript since 2002 and love the language. To quote Robin Williams, "People call these things imperfections, but there not. Ah, that's the good stuff." And that's the way it is. JavaScript has way more things right about it then there are wrong. Every language has its imperfections, and for some reason people are convinced that javascript is only that. Unless you code in a language full time for years, don't think you can speak authoritatively on it.