The problem is that there is not a way that would allow for the encryption to actually protect the user's data at the same time as give law enforcement access. Take, for example, the physical master key. A landlord might have a single key that opens every lock for the complex in which he or she administers. The individuals living may feel protected since their keys only open each of their doors. A thief would only need wait until the land lord was complacent to steal the master key and then have access to entire complex. The same problem works in the virtual world with encryption. Even if there is not a malicious 3rd party involved, who watches the watchers? Let us say, in a near perfect world, that 99% of law enforcement is honest, there would still be that 1% that is dishonest. Even in the case of 100% being honest, many can name to where the road of good intentions will lead us; good actors having limited scope do no necessarily have good results.
In my experience, a person does not necessarily need to know or even understand Big O to write good code as long as they have been trained with good habits and this is more so if they can quote off that in most cases a quicksort averages better than a bubble sort (except when the list is mostly sorted and other similar bit of trivia).
Of course, the above is specifically for your average day-to-day code in which performance and memory requirements are relatively loose. Regarding the ones in which I have trained, only half had even heard of Big O, and maybe two actually had a real understanding. That said, someone who does have the concepts at least internalized will overall produce more efficient code. Note that I did not say better in this case since efficient code is not necessarily maintainable code.
I have found in a number of cases (training the incoming juniors; anecdotal) that many do not care about the "superfluous details" of what goes on "behind the scenes of algorithms" since there is the impression that the libraries are supposed to do the heavy lifting. In this case, I think there is a case of maturity; however, I found that plenty of repetition and reviews (not lectures, in spite of my verbose nature making me prone to giving them) will solidify (indoctrinate?) the concepts to the point they are accepted and appreciated.
My hypothesis is that there is a certain number of iterations you need to do before you understand most topics and being self taught somehow doesn't ensure those number of repetitions.
It may be to note, I was self-taught and understood those concepts prior to getting my original AS in computer science (which I got and later extended to a BS for career reasons). While I do not think this is untrue, I do not think it is always the case. My personal nature makes me a bit of a self-study and experimenter. The couple of trainees that I met that did already understand the concepts were pretty much the same.
How are a CS major and understanding big O efficiency related? A smart person will quickly grasp this concept. End of story. If you NEED a CS major to get such a simple concept, I really don't want you writing code.
I think this is a short-sighted point of view. Some people do need a bit of a shove to understand some concepts. Big O came naturally to me, but formal writing, the kind a project manager uses to communicate with the non-techies did not. I benefited greatly from being coached from my writing teachers in high school and college. In that area, I needed the extra push; some people are the other way around. In all honesty, I rather than writing efficient code, I rather have someone write maintainable code, i.e., code that is mostly easy to read, do not (excessively) rely on "tricks," and where "tricks" should be used, to have it well documented. I would also rather have someone that can work with the team. This does not, however, mean docile. One of my best subordinates challenged my instructions and design decisions daily, but he worked well with the team and his doing so helped to isolate edge cases which were otherwise invisible.
My old XT clone had a Reset button on the numeric keypad. It only actually did a reset with conjunction with the Ctrl key. I never did get to verify; however, I suspect that it sent the SysReq keycode and was merely intercepted by that particular version of the Phoenix BIOS.
Open source is about code. It's not a political platform.
Try looking at Eric S. Raymond's website (http://www.catb.org/~esr/). It's about open source, but he isn't shy about politics either.
It matters because bigotry, bias, racism, etc. can drive away contributors.
How do you think contributors feel about the idea that some "committee" is going to evaluate their morals and kick them out if they don't match the political manifesto du jour?
Neither point is mutually exclusive-- there is a point of balance. I would not want to work on an open source project that is rampant with bigotry, etc; however, I would not want to work on one where I feel as though the slightest hint of my very opinionated political standings would get me booted. That said, I have not read enough to determine what had happened, but usually in these cases, there is more than meets the eye. That is not to say that a fork is not a good thing. I have seen a few projects fork, focus on different features, and end up better pleasing different audiences. That is not to say that forks are permenant and cannot be reconciled later... Just don't ask me to do the merge of the branches.
It may help to specify what constitutes a proper backup.
In my case, I use an automated weekly full disk image to a larger external drive. In addition, I have configured automatic nightly zip and store on different machine on my network of a few key document directories, 60 day rotation. One folder contains automatic syncing (within a minute or so) to Google drive for stuff in which has a lower privacy threshold. I also have a reminder set on my phone to verify that the backups are actually working every six months or so. Besides that, I also keep a local SVN setup that has its own automatic zip and store of the repo itself weekly.
In regards to the original post, I think there is blame to share. A good UI should prompt for confirmation when a impossible to undo operation is pending. On the other hand, until something gets into version control, and even after, a mild amount of paranoia is good. I duplicate my working copy and the trunk prior to large merges, for example. Usually, it is a complete waste of time; however, it did on two occasions in the last year saved me from a lot of headache.
Allergies vary depending on the individual. I have a strange one: red onions. They will give me a mild contact rash that goes away after a day or so. It won't kill me; it does make me rather unpleasant for a day or so, less if I had taken an antihistamine about an hour or so prior to contact. On the other hand, I know someone that was put into hospital for over a week from eating a food to which he was allergic. I have to take quite a bit of care concerning food prep when he visits, but it is no reason to panic.
Concerning peanut allergies, I know several people with them. A few have minor reactions such as upset stomach from consuming or rashes from contact exposure. One swells up like a balloon from consuming them and must keep Epinephrine on person for such unfortunate occasions.
I think there is a place for notices in case of allergies. I also think that people should actually confirm they have an allergy before they announce it to the world and not use it as an excuse for not eating something he or she does not like. I have noticed that some individuals treat their (sometimes real) allergies as trophies. I think they like for people to make the effort to cater to them; however, that is just open speculation. For me, it's just easier to tell people that I do not like red onions and pick them off with a napkin if they disagree. As a side note, not so much an allergy per se, but, it is interesting to see how many people will have cheese removed from their dish because "lactose intolerance" but will order ice cream for dessert.
Purple people would tend to be a target for the Purple People Eater, making them quite the liability... just sayin'
Although the Purple People Eater does have the ability to fly, his monocular vision reduces his depth perception making him a somewhat less dangerous foe. Purple People should drop a point or two into agility to make evasion easier.
I would mod up if I have points, but alas I don't. That said, adding armor and/or shield, or shrinking... anything that raises Armor Class (AC) should help.
If I had points, I would upvote. There is no point in breaking stuff whether or not there is legitimate reason to be angry. That said, if the investigators didn't follow the proper rules set to protect people's rights, they should (proverbially speaking) be hung out to dry.
Beyond that, encryption is a cat and mouse game and the government does have more processing power that an individual citizen. I wouldn't assume anything less that 1024bit is annoying enough to leave the government complaining and a device secure. In a couple of years, maybe it'll need to be 4096bit
Cable networks, partially out of necessity, sells in packages. These packages come because networks sell their channels in sets in order to maximize profits for their shareholders (more channels mean more advertising slots to sell). I would imagine that cable companies have a hard to negotiate against larger networks so those channel groups in packages represent an (almost) fixed overhead. As cable companies get few customers, they raise prices to keep their own margins up. Unfortunately (for them), this only accelerates the number of subscribers lost. In the meantime, streaming services, in spite of decreasing the breadth of their selection, are still providing more individual programs which is better satisfies the busyness in everyday life without requiring an extra fee for a DVR. If networks were able to sell individual channels to people rather than packages, I would assume that more subscriptions would occur.
That said, cable companies might be better off ditching the idea of selling video services directly and spin off new companies from themselves that does video subscriptions separately leaving all of that bandwidth to compete with fiber.
... they want their logo back.
Joking aside, if changing to any, the Moz://a looks the best to me; however, I do not think that rebranding will solve any particular problem. On the other hand, I might be convinced to stick around with their brand a bit longer if they stop removing features I use and stop adding bloat that I do not need. It *is* difficult, I realize, to make a "one size fit all" piece of software.
Maybe if they were to go back to the roots of Firefox by making it lean and having many of the standard features converted back to plugins or extensions. More difficult to maintain, but it would make it easier for power-users to customize their experience while, if a good selection was made by default, still be easy for those that want things to just work.
Just my thoughts on the matter.
I currently live in a very rural area in a state east of Texas (not that far out; however, far enough that I must rely on satellite for internet since neither DSL nor cable extends to this point... so much government supplementary for rural internet, but enough of chasing that rabbit). Many, but not all, or even the majority, of roads here are also paved, yet unmarked roads with narrow lanes. Most people simply drive in the middle of the road, only moving over for oncoming traffic. The speed limit on a nearby road is 25mph (about 40 km/h); most motorists drive about 50mph (about 80.5 km/h). Rain, sleet, heavy winds, or wildlife (usually deer, but sometimes rabbits, possums, etc) usually does nothing to slow people down. Sometimes, when the weather is especially bad (white out from rain), they speed up with the probable intent to get out of the weather faster. I would assume that removing the lines in an existing area would temporarily slow down traffic in an area, but I suspect once acclimated, people will increasingly return to their previous driving habits.
Slashdot Mirror
The problem is that there is not a way that would allow for the encryption to actually protect the user's data at the same time as give law enforcement access. Take, for example, the physical master key. A landlord might have a single key that opens every lock for the complex in which he or she administers. The individuals living may feel protected since their keys only open each of their doors. A thief would only need wait until the land lord was complacent to steal the master key and then have access to entire complex. The same problem works in the virtual world with encryption. Even if there is not a malicious 3rd party involved, who watches the watchers? Let us say, in a near perfect world, that 99% of law enforcement is honest, there would still be that 1% that is dishonest. Even in the case of 100% being honest, many can name to where the road of good intentions will lead us; good actors having limited scope do no necessarily have good results.
I stand corrected. *tips hat*
Of course, the above is specifically for your average day-to-day code in which performance and memory requirements are relatively loose. Regarding the ones in which I have trained, only half had even heard of Big O, and maybe two actually had a real understanding. That said, someone who does have the concepts at least internalized will overall produce more efficient code. Note that I did not say better in this case since efficient code is not necessarily maintainable code.
I have found in a number of cases (training the incoming juniors; anecdotal) that many do not care about the "superfluous details" of what goes on "behind the scenes of algorithms" since there is the impression that the libraries are supposed to do the heavy lifting. In this case, I think there is a case of maturity; however, I found that plenty of repetition and reviews (not lectures, in spite of my verbose nature making me prone to giving them) will solidify (indoctrinate?) the concepts to the point they are accepted and appreciated.
My hypothesis is that there is a certain number of iterations you need to do before you understand most topics and being self taught somehow doesn't ensure those number of repetitions.
It may be to note, I was self-taught and understood those concepts prior to getting my original AS in computer science (which I got and later extended to a BS for career reasons). While I do not think this is untrue, I do not think it is always the case. My personal nature makes me a bit of a self-study and experimenter. The couple of trainees that I met that did already understand the concepts were pretty much the same.
How are a CS major and understanding big O efficiency related? A smart person will quickly grasp this concept. End of story. If you NEED a CS major to get such a simple concept, I really don't want you writing code.
I think this is a short-sighted point of view. Some people do need a bit of a shove to understand some concepts. Big O came naturally to me, but formal writing, the kind a project manager uses to communicate with the non-techies did not. I benefited greatly from being coached from my writing teachers in high school and college. In that area, I needed the extra push; some people are the other way around. In all honesty, I rather than writing efficient code, I rather have someone write maintainable code, i.e., code that is mostly easy to read, do not (excessively) rely on "tricks," and where "tricks" should be used, to have it well documented. I would also rather have someone that can work with the team. This does not, however, mean docile. One of my best subordinates challenged my instructions and design decisions daily, but he worked well with the team and his doing so helped to isolate edge cases which were otherwise invisible.
My old XT clone had a Reset button on the numeric keypad. It only actually did a reset with conjunction with the Ctrl key. I never did get to verify; however, I suspect that it sent the SysReq keycode and was merely intercepted by that particular version of the Phoenix BIOS.
I see you are a firm believer in continuous bugs
I think the politically correct term now-days is continuous integration.
Open source is about code. It's not a political platform.
Try looking at Eric S. Raymond's website (http://www.catb.org/~esr/). It's about open source, but he isn't shy about politics either.
It matters because bigotry, bias, racism, etc. can drive away contributors.
How do you think contributors feel about the idea that some "committee" is going to evaluate their morals and kick them out if they don't match the political manifesto du jour?
Neither point is mutually exclusive-- there is a point of balance. I would not want to work on an open source project that is rampant with bigotry, etc; however, I would not want to work on one where I feel as though the slightest hint of my very opinionated political standings would get me booted. That said, I have not read enough to determine what had happened, but usually in these cases, there is more than meets the eye. That is not to say that a fork is not a good thing. I have seen a few projects fork, focus on different features, and end up better pleasing different audiences. That is not to say that forks are permenant and cannot be reconciled later... Just don't ask me to do the merge of the branches.
It may help to specify what constitutes a proper backup.
In my case, I use an automated weekly full disk image to a larger external drive. In addition, I have configured automatic nightly zip and store on different machine on my network of a few key document directories, 60 day rotation. One folder contains automatic syncing (within a minute or so) to Google drive for stuff in which has a lower privacy threshold. I also have a reminder set on my phone to verify that the backups are actually working every six months or so. Besides that, I also keep a local SVN setup that has its own automatic zip and store of the repo itself weekly.
In regards to the original post, I think there is blame to share. A good UI should prompt for confirmation when a impossible to undo operation is pending. On the other hand, until something gets into version control, and even after, a mild amount of paranoia is good. I duplicate my working copy and the trunk prior to large merges, for example. Usually, it is a complete waste of time; however, it did on two occasions in the last year saved me from a lot of headache.
Allergies vary depending on the individual. I have a strange one: red onions. They will give me a mild contact rash that goes away after a day or so. It won't kill me; it does make me rather unpleasant for a day or so, less if I had taken an antihistamine about an hour or so prior to contact. On the other hand, I know someone that was put into hospital for over a week from eating a food to which he was allergic. I have to take quite a bit of care concerning food prep when he visits, but it is no reason to panic.
Concerning peanut allergies, I know several people with them. A few have minor reactions such as upset stomach from consuming or rashes from contact exposure. One swells up like a balloon from consuming them and must keep Epinephrine on person for such unfortunate occasions.
I think there is a place for notices in case of allergies. I also think that people should actually confirm they have an allergy before they announce it to the world and not use it as an excuse for not eating something he or she does not like. I have noticed that some individuals treat their (sometimes real) allergies as trophies. I think they like for people to make the effort to cater to them; however, that is just open speculation. For me, it's just easier to tell people that I do not like red onions and pick them off with a napkin if they disagree. As a side note, not so much an allergy per se, but, it is interesting to see how many people will have cheese removed from their dish because "lactose intolerance" but will order ice cream for dessert.
And, btw, bubble wrap is pretty fun to pop.
Purple people would tend to be a target for the Purple People Eater, making them quite the liability... just sayin'
Although the Purple People Eater does have the ability to fly, his monocular vision reduces his depth perception making him a somewhat less dangerous foe. Purple People should drop a point or two into agility to make evasion easier.
I would mod up if I have points, but alas I don't. That said, adding armor and/or shield, or shrinking... anything that raises Armor Class (AC) should help.
If I had points, I would upvote. There is no point in breaking stuff whether or not there is legitimate reason to be angry. That said, if the investigators didn't follow the proper rules set to protect people's rights, they should (proverbially speaking) be hung out to dry. Beyond that, encryption is a cat and mouse game and the government does have more processing power that an individual citizen. I wouldn't assume anything less that 1024bit is annoying enough to leave the government complaining and a device secure. In a couple of years, maybe it'll need to be 4096bit
Cable networks, partially out of necessity, sells in packages. These packages come because networks sell their channels in sets in order to maximize profits for their shareholders (more channels mean more advertising slots to sell). I would imagine that cable companies have a hard to negotiate against larger networks so those channel groups in packages represent an (almost) fixed overhead. As cable companies get few customers, they raise prices to keep their own margins up. Unfortunately (for them), this only accelerates the number of subscribers lost. In the meantime, streaming services, in spite of decreasing the breadth of their selection, are still providing more individual programs which is better satisfies the busyness in everyday life without requiring an extra fee for a DVR. If networks were able to sell individual channels to people rather than packages, I would assume that more subscriptions would occur. That said, cable companies might be better off ditching the idea of selling video services directly and spin off new companies from themselves that does video subscriptions separately leaving all of that bandwidth to compete with fiber.
Now make your father bankrupt and take your place on the darkside.
... they want their logo back. Joking aside, if changing to any, the Moz://a looks the best to me; however, I do not think that rebranding will solve any particular problem. On the other hand, I might be convinced to stick around with their brand a bit longer if they stop removing features I use and stop adding bloat that I do not need. It *is* difficult, I realize, to make a "one size fit all" piece of software. Maybe if they were to go back to the roots of Firefox by making it lean and having many of the standard features converted back to plugins or extensions. More difficult to maintain, but it would make it easier for power-users to customize their experience while, if a good selection was made by default, still be easy for those that want things to just work. Just my thoughts on the matter.
I currently live in a very rural area in a state east of Texas (not that far out; however, far enough that I must rely on satellite for internet since neither DSL nor cable extends to this point... so much government supplementary for rural internet, but enough of chasing that rabbit). Many, but not all, or even the majority, of roads here are also paved, yet unmarked roads with narrow lanes. Most people simply drive in the middle of the road, only moving over for oncoming traffic. The speed limit on a nearby road is 25mph (about 40 km/h); most motorists drive about 50mph (about 80.5 km/h). Rain, sleet, heavy winds, or wildlife (usually deer, but sometimes rabbits, possums, etc) usually does nothing to slow people down. Sometimes, when the weather is especially bad (white out from rain), they speed up with the probable intent to get out of the weather faster. I would assume that removing the lines in an existing area would temporarily slow down traffic in an area, but I suspect once acclimated, people will increasingly return to their previous driving habits.