This whole line of thought is broken by bad assumptions. You ask:
How is the median user (not an outlier technophile like much of the Slashdot population) expected to parse out a download URL from the result of wget http://getfirefox.com/ [getfirefox.com] or wget http://mozilla.org/ [mozilla.org] without using IE?
If you didn't include those URL's, you'd be closer to having a point. However, you did include them. Where'd they get those? They can get the download URL from the same place (maybe it was a friend, or an email, or an IM, or off a magazine ad... I have no idea).
You also added in the condition that it be for a median user, which the AC that TechyImmigrant was replying to did not include.
For a median user, they'll probably keep using whatever was installed when they bought their system, or maybe something someone else installed for them. Slight above that, it depends on their OS. If on Windows, they'll probably use IE, search bing for Firefox or Chrome, and click around (duh). That still doesn't apply to the question... how else are you supposed to download ?
That's a great question. You can't even use a naive "telnet getfirefox.com 80"... that'll just get you a 403 forbidden! If you include the "Host: getfirefox.com", then it'll give you a redirect to https://www.mozilla.org/firefo... NOTE: that's https... if you try to go to the non-ssl version, it just redirects to the HTTPS again. So you can't get that without something like "openssl s_client -connect www.mozilla.org:443", and I don't think you'll find that on windows.
ftp works with a little digging through ftp.mozilla.org (assuming you know that url). Finding the binary is pretty easy. One needs to know some basics, but it's one of the easiest protocols out there. Ok for a median user? probably not. But it IS an option.
You could also have someone email it to you (if you can get files that big), or send you a CD or thumb drive with it (ex. your kind sysadmin at work might do this for you if you ask nice just to get rid of another IE 6 user). This technique worked for newbs back in the day (aol cd's and floppies anyone?), so why not now?
It seems that IT workers think they are too smart to join a union or they are so super concerned that 1 person might freeload off their contract, so they are ready to spite their face to save their nose.
The current state of unions is, IMO, worse than the two party system in America. The basic idea of a union is excelent - but that basic implementation is now illegal. You can't simple band together workers and strike. You must have a propper union, and that's where it all goes downhill. Now part of your pay has to go to dues, and you're required to do so. Why? The people holding the purse have it in their best interests to keep their employment, union position, and keep dues coming in (which means keep your lot working). It's like a really broken HR department.
I don't think many people are worried about freeloaders. I think they are, and should be, worried about even more people sitting in management like positions doing nothing but gleening away money that should go to the pockets of the employees; about more red tape; about the restrictions that would limit their mobility in the workforce and between companies; etc.
Most in IT are also doing alright (desk job with decent pay), and many are young and happy to be making more than most of their peers. Where's the motivation to unionize? What will it bring that isn't easily found already?
Um... your linotype example tends to back up what I'm saying. I don't know ANYONE that prints out full books. It's cheaper to go buy one than print it at home. Fewer and fewer people are buying printers too... especially photo printers, where people just run down to their local kinko's/cvs/walmart/etc and get a better photo print than they could at home, for cheaper and in less time.
I get that 3d printing is for one-offs... but then who's making the design of the "one" to off, and who needs that at home? I do think it'll end up being used quite a bit, the way photo printing is now, but I doubt we'll get one in every house. The sad truth is that economies of scale mean that buying something that's been shipped from the other side of the world will still be cheaper, better, and faster than printing it out at home. It does make great fantasy though (Cory Doctorow's written about it a bunch and included it as part of some of his novels, which were excellent).
What I do hope happens is that the home versions of 3d printers continue to get better and cheaper so that people will have the option of doing it at home rather than paying a local service. That will keep things competitive, and still allow for edge cases where the home printer is actually very very useful (like prototyping).
My question is: where the HELL is the Labor Department and the Commerce Department on all this? The small company I work at went through a month of poking, prodding, audits, etc. by the Dept. of Labor looking for overtime violations or miscategorizing employees as salary vs. hourly, and all they found was $2000 over 3 years, and even that was questionable.
Questionable, but manageable. Can you imagine how long it'd take them to do a similar audit on a company the size of Google?!?! Some guy got to do your company over, get paid that whole time, and come way with something possitive (could have went the other way)... so it's a win/win for him/labor-commerce, and $2000 doesn't even hurt your company much. It's not right, but it makes sense.
Of course the over the air broadcasters are complaining. They actual PAY for the content. Then Aereo comes and leeches off the broadcasters, taking away a source of revenue...
That's not accurate. Maybe *some* of the local broadcasters are worried they'll have fewer viewers, but an equal or greater number are going to gain viewers.
In addition, there's a large group that can't get the broadcasts that would now be getting them over Aereo.... so that's more viewers and eyeballs on their commercials. That's a good thing. They could probably even get Aereo to provide some stats to them so they know how many people are watching what at what times... all stuff they can't get from their current user group (baring nelson families).
On the local front... I'd be more interested in my local news programs than some from another city, so if Aereo grew, there's good reason to suspect they'd add receivers in other locations.
I still think it's a pretty silly plan except for some edge cases, but I don't see any real problems with it.
3D printing is a prototyping tool, not a serious production tool.
THIS!!!
Sure, there are are nitch places for 3d printing (hard to find replacement parts, artistic stuff (even one off custom jewelery), etc). However, as soon as there is a 3d model good enough to print, if enough people want it, it'll be cheaper for mass production. And all the other little trinkets... your local 3d print shop (which will probably go the way of photo printers, so any CVS, Kinko's, Staples, etc).
There's a reason some parts are hard to find - there's little demand. So one shop that can do it per town will probably be more than enough for something like that can do sturdy parts (metal, resin, casting from printed wax, etc).
The only way I see it making it into many homes is if the big companies royally screw up. If they, for instance, make sure that Staples won't print anything that is copywritten or trademarked etc, then you won't be able to run down there and print out a new GIJoe head... a home printer starts to make a lot of sense then, but only really because of politics and red tape.
Of course the over the air broadcasters are complaining. They actual PAY for the content. Then Aereo comes and leeches off the broadcasters, taking away a source of revenue, without paying anything. When Aereo actually produces (or pays for) it's own content, then you may have a point.
How are they taking away a source of revenue? (bear with me... I haven't looked into Aereo much... maybe they're offering commercial skipping or something)
I get that the broadcaster has legit deals in place for the content the distribute. I get that Aereo is sending that broadcast content to users. But Aereo is using (supposedly) one antenna per user, and nothing is recorded (AFAIK), so the user is getting the exact same content they would get for free over the air. This doesn't take away anything from the broadcaster (AFAICT).
It has rotating levers on each side of the head that swing out when the blade enters the wood, pushing it apart in both directions (as opposed to the articles push in one direction). No twist of the handle and wrist pain needed.
I'm not a fan of Mir, nor a big fan of Unity, but I've been around long enough to see those sort of changes happen in every distro.
My personal favorite window manger was sawmill/sawfish, which was the default with gnome at one point in time. When it was replaced, the replacement didn't do half of the features I regularly used, so I kept using it. Then it became much more difficult to get working, so I dropped gnome and used some dumb little apps to get a desktop switcher and clock and such, and went pretty bare-bones. Then compiz got pretty stable, so I gave up and used that. wash/rinse/repeat for a ton of other things in life.
People turned against KDE for a long while too due to licensing issues. AFAICT, that has continued to hurt their image, even though all those issues have been resolved. IMO, that did push KDE/QT to change, and also pushed gnome to improve. Someone has to push the ball forward. Mir may never actually take off. If Wayland gets there first (and yes, there still is plenty to be done), Ubuntu could easily swap it into place. Similar with Unity... it does do a better job with touch than many of the other options. It, like almost everything else there is, won't last forever. It's not hurting things as long as there are other options (you can even just grab a xubuntu or kubuntu spin if you want).
Well, yeah. Within the same series, a larger device typically just has more of the same type of memory chip as is in the smaller device. More chips => greater possible parallelism in accessing them => faster device, assuming neither the controller nor the bus is the limiting factor.
...and that's the whole point of increased capacity = greater performance, especially over time. Sure, SLC has the potential to out perform TLC, but you can get a 1tb TSC SSD for about $450 today with 90k iOPS and 500mb/s throughput (or more). There is no sign that future releases of larger sizes will have reduced performance, as the summary/article implies.
I ended up going with an SSD for the OS and 2 mirrored HDDs for reliable storage.
I see a lot of people going with SSD for OS + core applications, and HDD's for everything else. I don't quite understand why? Is your usage pattern such that you are frequently rebooting and/or closing all apps and re-opening them (more so than working with documents)?
I completely understand HDD for media such as mp3's and videos - they handle throughput for those just fine and there's hardly any seeking when watching a video. And unless it's a video/music server that services a bunch of clients, a HDD will handle that just fine (a SSD would provide no noticable improvement to normal consumption/usage).
I don't understand the OS vs rest of the data. Anything I'm actively working on is the stuff I'd want on SSD. Editing video - put those on SSD while manipulating them. Editing code - checkout your repo's to SSD. Compiling, ditto. And for all that stuff, I can't imagine having the OS on SSD would provide any real improvement (libraries get loaded into memory once; frequently called apps will be in disk buffers/etc).
I've also heard recommendations to keep swap off of SSD. That also seems backwards to me (in a way). Reducing swapping, in general, is good. Setting swappiness to its lowest is sufficient for that. However, if you MUST go into swap, SSD seems like a great way to go - possibly worth dedicating a whole SSD just to swap (64gb DDR3 ram is at least $500 (8x8gb); 120gb SSD is ~$70; 1tb SSD is ~$450). Keeping things out of swap is still much faster, but for a home workstation that *can* handle giant memory loads, 16gb ram + 120gb SSD sounds like a great option.
They would have far less traffic transiting other networks, greatly reducing the thing they kept complaining about, which supposedly costs them money, so this would save money there. It would also provide a benefit to many of their customers experiences. This is all very similar to Akamai and other CDN's. As an ISP, it's a win-win, especially if the provider (netflix/akamai) foots the bill for their hardware.
Of course, they may be making more cash from this agreement with Netflix... but that's not really a good thing for anyone.
* This particular tagger isn't talented enough to be an artist
Pretty creative quoting there... you snipped our a whole two words so you could exclude the main point/categorization - they're taggers. That invalidates the latter two points, and the first point is much easier to approach - is tagging art?
Defining "art" is completely subjective. Was Duchamp's "Fountain" art? IMO, that piece is about as far as I'd push the definition, and I'm still not sure if it is. It did make a significant statement, but it did far more with the piece than tagging a building. (almost) anyone can sign their own name, and can do so anywhere, so there would have to be something else to justify a signature on some random piece of property as "art". In "Fountain", there was timing involved in what was happening at the time, the exhibit in which it was displayed, and a very minimal level of object manipulation to justify a change to the original (turned on its side, placed in a different environment than it's normally seen, and signed).
So, what does a tagger need to do for his tag to be considered art to you? (graffiti and other works do not apply here)
Your bad analogy led to your incorrect conclusion (though I wouldn't be surprised if you had already made up your mind in that regard).
Of course, you then have to ask yourself the question, "How did Person B come to be in possession of Person A's keys?" Presuming that Person A did not hand the keys over willingly, it can be assumed that Person B stole them in order to make a copy.
Ok, I'll go along with you that far...
Now to the digital part: Person A makes his living from taking pictures and posting them online;...
The rest of that doesn't matter, because that just broke the analogy. They posted them online, which made them readily available for legitimate copying. When you view an image online, you're not actually getting an image beamed directly to your monitor... you are downloading the image file and saving a copy on your hard drive (normally in your browser cache), then running it through libs to turn it into something you can see on your screen. IE. you and everyone else that looks at those images is making a copy of it.
So... your original analogy would have to have Person B placing a bucket filled with copies of their key on their side walk with signs around the neighborhood saying "please come examine my keys at 123 Happy Photographer St" etc.
At that point, well, I think we'd both say that Person B didn't steal the key. What he does with it afterwards is another matter (further theft, breaking an entering, mugging, kidnapping, whatever). In the digital world, that's just a copyright violation (since we're just talking about a photo, and not using someone else's username+password for nefarious purposes).
Add to that the fact that interpreters are generally written by expert programmers, and then they receive lots and lots of testing and debugging, and then (hopefully) become mature/stable shortly thereafter; whereas application code is often written by mediocre programmers and often receives only minimal testing and debugging.
I'd wager that most of those writing/maintaining OpenSSL are not only expert programmers, but, overall, are more security concious than the authors/maintainers of interpreters. You point would be completely valid if the topic was some builitin board / wiki / chat program / etc. Sadly, that's not the case at hand.
Is everyone else missing the point that 2/3 of buyers of wearable devices are still using them after six months?
That. And also the statement, "The idea of giving them up just wouldn't occur to them." (wrt early smartphone adopters) is rediculous. A large portion of early adopters of anything end up giving them up. That's part of the early adopter pattern... it's new and shiny, so they early adopt it, and then it's no longer new, so they move on. They may come back to those types of thing later, but it's normal for many people to give up up in the early days. For example, on my first phone with MMS, I set up an email forward to forward all my emails to my phone. Initially, it seemed useful. That was too much, so I changed it to only forward ones matching certain patterns. Initially, that was neat. Then I turned it off because I'd rather not be bothered by it. I rarely every check my email on my phone even today, and I was certainly an early adopter... that doesn't mean it won't or didn't catch on.
While there at it, can they make some that slip over popular andriod phones? By the look of the design, it seems like it'd be pretty easy to make versions that fit other popular phones, and keep using the same bluetooth keyboard (fyi, it extends the length of the phone a bit, so this isn't a question of how much non-screen real estate exists at the bottom of the phone).
Slightly off topic... anyone know of a good keyboard case for a galaxy S4? The only one's I've found add incredible bulk, have poor reviews, make camera use very awkward, and just don't seem usable. I miss my evo shift keyboard, and G1 before that:-(
rarely, but frequently enough that tire chunks are commonly seen on the highway (mostly from 18 wheelers)
WTF that has to do with this is beyond me, except that you didn't take two seconds to think about it (or google it) before posting and made a really bad guess:-)
If the flywheel spins parallel to the road I don't think it would affect turning left or right - except it would resist the car leaning to the side on a sharp turn, which might be a good thing.
Assuming it had significant gyroscopic effects, that would be just as bad as not being able to turn! Most bends in roads are banked, and many are banked a lot. Go into one of those with a strong horizontal gryo and your car would be on two wheels.
It's really not that hard. I've been through it on big projects with extensive history and multiple sync'd outside projects with internal patches and the whole 9 yards.
Start with what you own. If you don't own it, leave it be. Do all files in one big patchset. That'll be the point in time where stuff before and after won't diff very nicely, It sucks, but a year from now, it won't really matter.
Include a per-commit check. That way, no new problems get introduced. Include the header. One does HAVE to use vim or emacs, but the mode lines I supplied work with those two. If your group has another common editor, add its mode lines if it supports it. It's just a helpful extra, and is safely ignored by other editors. And if none of you use vim or emacs, disregard those lines.
If someone has a branch that was cut prior to the big reformatting patch, they'll have to deal with it at merge, or rebranch or rebase. Sucks, but it's a one time thing.
The alternative sucks more - having code with mixed standards. How do multiple groups deal with that? Your patches are going to be even worse! Someone uses their editor to indent a block or copy/paste it, and all those mixed tables and spaces go to whatever they're using, causing all lines to diff poorly, instead of just the little pieces they touched. It's awful, as you noted.
Your specific problem you referenced was users that were using an outdated 6 year old.vimrc that had been mailed around, and it caused problems with your code because of the difference in coding standards. ADDING THE MODE LINE FIXES THAT!
The rest of it sounds like you just don't want to be bothered to clean up the problem, and just want to complain and blame others. It's trivial to fix. It comes with a small cost (one time giant ugly patchset), but it's easy. And you don't need that one time giant patch.. you could let them be fixed as changes are made, but I wouldn't recommend that as every future patchset will be more complicated than it needs to be. Just get it all out of the way in one go and move on.
For integration with external code/repositories, work within the standard of the governing body. If they have a well defined standard, you can even add the pre-commit checks to your personal repository if you want. In general, this doesn't matter as much as the above, cause either your guys are behaving well and working with the external group, or they're not - manage accordingly.
That DOES solve the case in point. AT&T are just finger pointing and trying to latch on to a cash cow, while gaining an unfair advantage in customer pricing.
True net neutrality helps the little guys everywhere. Netflix noted that on the service side, as others have here, that if big companies have to pay for connectivity to the last mile to the users, small services will be hurt. It also makes absolutely no sense (services already pay for their internet access; customers already pay for theirs; there's lots of middle men, and those guys are trying to get around each other and get profit from customers on the other side).
The other side is that a competing ISP would also have trouble. If AT&T, for example, was charging all websites for their bandwidth to the end users, then at some point they really don't have to charge the end users anything. Where's the balance? How would a new ISP charge his customers?
The ISP tiered pricing is simply wrong if their network can't handle their customers requests. The cheapest possible plans often get you very good download speeds (ex. 15Mbps for the first 12months at $14.99/month for time warner). That's the problem right there. Their standard fee for that is $35/month, and $15 will only get you 2Mbps... which is still plenty for most people.
I'm all for cheaper and faster internet access, but if it's a problem for them, then they should put the squeeze on their customers, not the services their custom wants. Netflix is a selling point for the ISP; something they should, if anything, be paying MORE for to get improved quality for their customers.
The only reason they should want to squeeze netflix is, IMO, because it competes with their other services - TV. That's anti-competitive through and through.
You should/could also slap some mod lines at the start of your files. Ex: # ex: set tabstop=4 expandtab smarttab softtabstop=4 shiftwidth=4: # -*- Mode: tab-width: 4; indent-tabs-mode: nil; basic-offset: 4 -*- #
You could also just run it through a tidy program and a site-specific config if you really want to be a formatting nazi.
Say a server running service A uses service B on behalf of users of service B. In order to do this, service A needs to store a credential for each user of service B.
You're doing it wrong. One way is for Service A to establish a trust with Service B (ex. using SAML), and have the user at Service B authorize that usage. Service A and B agree on a unique key for that exchange (ex. private/public certs), and Service A issues those commands to Service B using its user + that authorized cert to perform on that users behalf. Of course, if Service B offers no such ability, then you'll need some sort of kludge like you suggested, but that doesn't make it right. Even so, they should protect those credentials in a much more sophisticated way than just another table in the same DB with an encrypted version of the Service B credentials (ex. a key server appliance).
Slashdot Mirror
Came out in 80.
Came out in 1977 named the Hungarian Magic Cube.
This whole line of thought is broken by bad assumptions. You ask:
How is the median user (not an outlier technophile like much of the Slashdot population) expected to parse out a download URL from the result of wget http://getfirefox.com/ [getfirefox.com] or wget http://mozilla.org/ [mozilla.org] without using IE?
If you didn't include those URL's, you'd be closer to having a point. However, you did include them. Where'd they get those? They can get the download URL from the same place (maybe it was a friend, or an email, or an IM, or off a magazine ad... I have no idea).
You also added in the condition that it be for a median user, which the AC that TechyImmigrant was replying to did not include.
For a median user, they'll probably keep using whatever was installed when they bought their system, or maybe something someone else installed for them.
Slight above that, it depends on their OS. If on Windows, they'll probably use IE, search bing for Firefox or Chrome, and click around (duh).
That still doesn't apply to the question... how else are you supposed to download ?
That's a great question. You can't even use a naive "telnet getfirefox.com 80"... that'll just get you a 403 forbidden! If you include the "Host: getfirefox.com", then it'll give you a redirect to https://www.mozilla.org/firefo...
NOTE: that's https... if you try to go to the non-ssl version, it just redirects to the HTTPS again. So you can't get that without something like "openssl s_client -connect www.mozilla.org:443", and I don't think you'll find that on windows.
ftp works with a little digging through ftp.mozilla.org (assuming you know that url). Finding the binary is pretty easy. One needs to know some basics, but it's one of the easiest protocols out there. Ok for a median user? probably not. But it IS an option.
You could also have someone email it to you (if you can get files that big), or send you a CD or thumb drive with it (ex. your kind sysadmin at work might do this for you if you ask nice just to get rid of another IE 6 user). This technique worked for newbs back in the day (aol cd's and floppies anyone?), so why not now?
It seems that IT workers think they are too smart to join a union or they are so super concerned that 1 person might freeload off their contract, so they are ready to spite their face to save their nose.
The current state of unions is, IMO, worse than the two party system in America.
The basic idea of a union is excelent - but that basic implementation is now illegal. You can't simple band together workers and strike. You must have a propper union, and that's where it all goes downhill. Now part of your pay has to go to dues, and you're required to do so. Why? The people holding the purse have it in their best interests to keep their employment, union position, and keep dues coming in (which means keep your lot working). It's like a really broken HR department.
I don't think many people are worried about freeloaders. I think they are, and should be, worried about even more people sitting in management like positions doing nothing but gleening away money that should go to the pockets of the employees; about more red tape; about the restrictions that would limit their mobility in the workforce and between companies; etc.
Most in IT are also doing alright (desk job with decent pay), and many are young and happy to be making more than most of their peers. Where's the motivation to unionize? What will it bring that isn't easily found already?
Um... your linotype example tends to back up what I'm saying. I don't know ANYONE that prints out full books. It's cheaper to go buy one than print it at home. Fewer and fewer people are buying printers too... especially photo printers, where people just run down to their local kinko's/cvs/walmart/etc and get a better photo print than they could at home, for cheaper and in less time.
I get that 3d printing is for one-offs... but then who's making the design of the "one" to off, and who needs that at home? I do think it'll end up being used quite a bit, the way photo printing is now, but I doubt we'll get one in every house. The sad truth is that economies of scale mean that buying something that's been shipped from the other side of the world will still be cheaper, better, and faster than printing it out at home. It does make great fantasy though (Cory Doctorow's written about it a bunch and included it as part of some of his novels, which were excellent).
What I do hope happens is that the home versions of 3d printers continue to get better and cheaper so that people will have the option of doing it at home rather than paying a local service. That will keep things competitive, and still allow for edge cases where the home printer is actually very very useful (like prototyping).
My question is: where the HELL is the Labor Department and the Commerce Department on all this? The small company I work at went through a month of poking, prodding, audits, etc. by the Dept. of Labor looking for overtime violations or miscategorizing employees as salary vs. hourly, and all they found was $2000 over 3 years, and even that was questionable.
Questionable, but manageable. Can you imagine how long it'd take them to do a similar audit on a company the size of Google?!?! Some guy got to do your company over, get paid that whole time, and come way with something possitive (could have went the other way)... so it's a win/win for him/labor-commerce, and $2000 doesn't even hurt your company much. It's not right, but it makes sense.
The GP said,
Of course the over the air broadcasters are complaining. They actual PAY for the content. Then Aereo comes and leeches off the broadcasters, taking away a source of revenue...
That's not accurate. Maybe *some* of the local broadcasters are worried they'll have fewer viewers, but an equal or greater number are going to gain viewers.
In addition, there's a large group that can't get the broadcasts that would now be getting them over Aereo.... so that's more viewers and eyeballs on their commercials. That's a good thing. They could probably even get Aereo to provide some stats to them so they know how many people are watching what at what times... all stuff they can't get from their current user group (baring nelson families).
On the local front... I'd be more interested in my local news programs than some from another city, so if Aereo grew, there's good reason to suspect they'd add receivers in other locations.
I still think it's a pretty silly plan except for some edge cases, but I don't see any real problems with it.
3D printing is a prototyping tool, not a serious production tool.
THIS!!!
Sure, there are are nitch places for 3d printing (hard to find replacement parts, artistic stuff (even one off custom jewelery), etc). However, as soon as there is a 3d model good enough to print, if enough people want it, it'll be cheaper for mass production. And all the other little trinkets... your local 3d print shop (which will probably go the way of photo printers, so any CVS, Kinko's, Staples, etc).
There's a reason some parts are hard to find - there's little demand. So one shop that can do it per town will probably be more than enough for something like that can do sturdy parts (metal, resin, casting from printed wax, etc).
The only way I see it making it into many homes is if the big companies royally screw up. If they, for instance, make sure that Staples won't print anything that is copywritten or trademarked etc, then you won't be able to run down there and print out a new GIJoe head... a home printer starts to make a lot of sense then, but only really because of politics and red tape.
Of course the over the air broadcasters are complaining. They actual PAY for the content. Then Aereo comes and leeches off the broadcasters, taking away a source of revenue, without paying anything. When Aereo actually produces (or pays for) it's own content, then you may have a point.
How are they taking away a source of revenue? (bear with me... I haven't looked into Aereo much... maybe they're offering commercial skipping or something)
I get that the broadcaster has legit deals in place for the content the distribute.
I get that Aereo is sending that broadcast content to users.
But Aereo is using (supposedly) one antenna per user, and nothing is recorded (AFAIK), so the user is getting the exact same content they would get for free over the air.
This doesn't take away anything from the broadcaster (AFAICT).
This also isn't the first inventive axe by a long shot... though it is unique and new to me.
This is what my dad often used (though possibly some other brand): https://www.chopper1axe.com/
It has rotating levers on each side of the head that swing out when the blade enters the wood, pushing it apart in both directions (as opposed to the articles push in one direction). No twist of the handle and wrist pain needed.
... giving some random 8 or 9 year old kid ... the capacity to tap into and take over these mobile platforms gives me shivers.
Not sure about 8 or 9, but I'm pretty sure I know what I'd be doing with them in my teens (as wrong as I know that is). In short, you're safe.
I'm not a fan of Mir, nor a big fan of Unity, but I've been around long enough to see those sort of changes happen in every distro.
My personal favorite window manger was sawmill/sawfish, which was the default with gnome at one point in time. When it was replaced, the replacement didn't do half of the features I regularly used, so I kept using it. Then it became much more difficult to get working, so I dropped gnome and used some dumb little apps to get a desktop switcher and clock and such, and went pretty bare-bones. Then compiz got pretty stable, so I gave up and used that. wash/rinse/repeat for a ton of other things in life.
People turned against KDE for a long while too due to licensing issues. AFAICT, that has continued to hurt their image, even though all those issues have been resolved. IMO, that did push KDE/QT to change, and also pushed gnome to improve. Someone has to push the ball forward. Mir may never actually take off. If Wayland gets there first (and yes, there still is plenty to be done), Ubuntu could easily swap it into place. Similar with Unity... it does do a better job with touch than many of the other options. It, like almost everything else there is, won't last forever. It's not hurting things as long as there are other options (you can even just grab a xubuntu or kubuntu spin if you want).
Well, yeah. Within the same series, a larger device typically just has more of the same type of memory chip as is in the smaller device. More chips => greater possible parallelism in accessing them => faster device, assuming neither the controller nor the bus is the limiting factor.
...and that's the whole point of increased capacity = greater performance, especially over time. Sure, SLC has the potential to out perform TLC, but you can get a 1tb TSC SSD for about $450 today with 90k iOPS and 500mb/s throughput (or more). There is no sign that future releases of larger sizes will have reduced performance, as the summary/article implies.
I ended up going with an SSD for the OS and 2 mirrored HDDs for reliable storage.
I see a lot of people going with SSD for OS + core applications, and HDD's for everything else. I don't quite understand why? Is your usage pattern such that you are frequently rebooting and/or closing all apps and re-opening them (more so than working with documents)?
I completely understand HDD for media such as mp3's and videos - they handle throughput for those just fine and there's hardly any seeking when watching a video. And unless it's a video/music server that services a bunch of clients, a HDD will handle that just fine (a SSD would provide no noticable improvement to normal consumption/usage).
I don't understand the OS vs rest of the data. Anything I'm actively working on is the stuff I'd want on SSD. Editing video - put those on SSD while manipulating them. Editing code - checkout your repo's to SSD. Compiling, ditto. And for all that stuff, I can't imagine having the OS on SSD would provide any real improvement (libraries get loaded into memory once; frequently called apps will be in disk buffers/etc).
I've also heard recommendations to keep swap off of SSD. That also seems backwards to me (in a way). Reducing swapping, in general, is good. Setting swappiness to its lowest is sufficient for that. However, if you MUST go into swap, SSD seems like a great way to go - possibly worth dedicating a whole SSD just to swap (64gb DDR3 ram is at least $500 (8x8gb); 120gb SSD is ~$70; 1tb SSD is ~$450). Keeping things out of swap is still much faster, but for a home workstation that *can* handle giant memory loads, 16gb ram + 120gb SSD sounds like a great option.
Anyway... why OS on SSD?
But how does that get them more money?
They would have far less traffic transiting other networks, greatly reducing the thing they kept complaining about, which supposedly costs them money, so this would save money there.
It would also provide a benefit to many of their customers experiences.
This is all very similar to Akamai and other CDN's. As an ISP, it's a win-win, especially if the provider (netflix/akamai) foots the bill for their hardware.
Of course, they may be making more cash from this agreement with Netflix... but that's not really a good thing for anyone.
Wait, are you saying it isn't art because:
* They're tagging and therefore it can't be art
* Grafitti isn't art no matter how it's executed
* This particular tagger isn't talented enough to be an artist
Pretty creative quoting there... you snipped our a whole two words so you could exclude the main point/categorization - they're taggers. That invalidates the latter two points, and the first point is much easier to approach - is tagging art?
Defining "art" is completely subjective. Was Duchamp's "Fountain" art? IMO, that piece is about as far as I'd push the definition, and I'm still not sure if it is. It did make a significant statement, but it did far more with the piece than tagging a building. (almost) anyone can sign their own name, and can do so anywhere, so there would have to be something else to justify a signature on some random piece of property as "art". In "Fountain", there was timing involved in what was happening at the time, the exhibit in which it was displayed, and a very minimal level of object manipulation to justify a change to the original (turned on its side, placed in a different environment than it's normally seen, and signed).
So, what does a tagger need to do for his tag to be considered art to you? (graffiti and other works do not apply here)
Your bad analogy led to your incorrect conclusion (though I wouldn't be surprised if you had already made up your mind in that regard).
Of course, you then have to ask yourself the question, "How did Person B come to be in possession of Person A's keys?" Presuming that Person A did not hand the keys over willingly, it can be assumed that Person B stole them in order to make a copy.
Ok, I'll go along with you that far...
Now to the digital part: Person A makes his living from taking pictures and posting them online; ...
The rest of that doesn't matter, because that just broke the analogy. They posted them online, which made them readily available for legitimate copying. When you view an image online, you're not actually getting an image beamed directly to your monitor... you are downloading the image file and saving a copy on your hard drive (normally in your browser cache), then running it through libs to turn it into something you can see on your screen. IE. you and everyone else that looks at those images is making a copy of it.
So... your original analogy would have to have Person B placing a bucket filled with copies of their key on their side walk with signs around the neighborhood saying "please come examine my keys at 123 Happy Photographer St" etc.
At that point, well, I think we'd both say that Person B didn't steal the key. What he does with it afterwards is another matter (further theft, breaking an entering, mugging, kidnapping, whatever). In the digital world, that's just a copyright violation (since we're just talking about a photo, and not using someone else's username+password for nefarious purposes).
Add to that the fact that interpreters are generally written by expert programmers, and then they receive lots and lots of testing and debugging, and then (hopefully) become mature/stable shortly thereafter; whereas application code is often written by mediocre programmers and often receives only minimal testing and debugging.
I'd wager that most of those writing/maintaining OpenSSL are not only expert programmers, but, overall, are more security concious than the authors/maintainers of interpreters. You point would be completely valid if the topic was some builitin board / wiki / chat program / etc. Sadly, that's not the case at hand.
Is everyone else missing the point that 2/3 of buyers of wearable devices are still using them after six months?
That. And also the statement, "The idea of giving them up just wouldn't occur to them." (wrt early smartphone adopters) is rediculous. A large portion of early adopters of anything end up giving them up. That's part of the early adopter pattern... it's new and shiny, so they early adopt it, and then it's no longer new, so they move on. They may come back to those types of thing later, but it's normal for many people to give up up in the early days. For example, on my first phone with MMS, I set up an email forward to forward all my emails to my phone. Initially, it seemed useful. That was too much, so I changed it to only forward ones matching certain patterns. Initially, that was neat. Then I turned it off because I'd rather not be bothered by it. I rarely every check my email on my phone even today, and I was certainly an early adopter... that doesn't mean it won't or didn't catch on.
While there at it, can they make some that slip over popular andriod phones? By the look of the design, it seems like it'd be pretty easy to make versions that fit other popular phones, and keep using the same bluetooth keyboard (fyi, it extends the length of the phone a bit, so this isn't a question of how much non-screen real estate exists at the bottom of the phone).
Slightly off topic... anyone know of a good keyboard case for a galaxy S4? The only one's I've found add incredible bulk, have poor reviews, make camera use very awkward, and just don't seem usable. I miss my evo shift keyboard, and G1 before that :-(
1) How fast do your wheels spin now?
about 800 rpm at 60mph.
2) How often do they shatter?
rarely, but frequently enough that tire chunks are commonly seen on the highway (mostly from 18 wheelers)
WTF that has to do with this is beyond me, except that you didn't take two seconds to think about it (or google it) before posting and made a really bad guess :-)
If the flywheel spins parallel to the road I don't think it would affect turning left or right - except it would resist the car leaning to the side on a sharp turn, which might be a good thing.
Assuming it had significant gyroscopic effects, that would be just as bad as not being able to turn! Most bends in roads are banked, and many are banked a lot. Go into one of those with a strong horizontal gryo and your car would be on two wheels.
It's really not that hard. I've been through it on big projects with extensive history and multiple sync'd outside projects with internal patches and the whole 9 yards.
Start with what you own. If you don't own it, leave it be. Do all files in one big patchset. That'll be the point in time where stuff before and after won't diff very nicely, It sucks, but a year from now, it won't really matter.
Include a per-commit check. That way, no new problems get introduced.
Include the header. One does HAVE to use vim or emacs, but the mode lines I supplied work with those two. If your group has another common editor, add its mode lines if it supports it. It's just a helpful extra, and is safely ignored by other editors. And if none of you use vim or emacs, disregard those lines.
If someone has a branch that was cut prior to the big reformatting patch, they'll have to deal with it at merge, or rebranch or rebase. Sucks, but it's a one time thing.
The alternative sucks more - having code with mixed standards. How do multiple groups deal with that? Your patches are going to be even worse! Someone uses their editor to indent a block or copy/paste it, and all those mixed tables and spaces go to whatever they're using, causing all lines to diff poorly, instead of just the little pieces they touched. It's awful, as you noted.
Your specific problem you referenced was users that were using an outdated 6 year old .vimrc that had been mailed around, and it caused problems with your code because of the difference in coding standards. ADDING THE MODE LINE FIXES THAT!
The rest of it sounds like you just don't want to be bothered to clean up the problem, and just want to complain and blame others. It's trivial to fix. It comes with a small cost (one time giant ugly patchset), but it's easy. And you don't need that one time giant patch.. you could let them be fixed as changes are made, but I wouldn't recommend that as every future patchset will be more complicated than it needs to be. Just get it all out of the way in one go and move on.
For integration with external code/repositories, work within the standard of the governing body. If they have a well defined standard, you can even add the pre-commit checks to your personal repository if you want. In general, this doesn't matter as much as the above, cause either your guys are behaving well and working with the external group, or they're not - manage accordingly.
... Netflix are aware of that and have the Open Connect Content Delivery Network, but that won't solve all the probelms.
That DOES solve the case in point. AT&T are just finger pointing and trying to latch on to a cash cow, while gaining an unfair advantage in customer pricing.
True net neutrality helps the little guys everywhere. Netflix noted that on the service side, as others have here, that if big companies have to pay for connectivity to the last mile to the users, small services will be hurt. It also makes absolutely no sense (services already pay for their internet access; customers already pay for theirs; there's lots of middle men, and those guys are trying to get around each other and get profit from customers on the other side).
The other side is that a competing ISP would also have trouble. If AT&T, for example, was charging all websites for their bandwidth to the end users, then at some point they really don't have to charge the end users anything. Where's the balance? How would a new ISP charge his customers?
The ISP tiered pricing is simply wrong if their network can't handle their customers requests. The cheapest possible plans often get you very good download speeds (ex. 15Mbps for the first 12months at $14.99/month for time warner). That's the problem right there. Their standard fee for that is $35/month, and $15 will only get you 2Mbps... which is still plenty for most people.
I'm all for cheaper and faster internet access, but if it's a problem for them, then they should put the squeeze on their customers, not the services their custom wants. Netflix is a selling point for the ISP; something they should, if anything, be paying MORE for to get improved quality for their customers.
The only reason they should want to squeeze netflix is, IMO, because it competes with their other services - TV. That's anti-competitive through and through.
You should/could also slap some mod lines at the start of your files. Ex:
# ex: set tabstop=4 expandtab smarttab softtabstop=4 shiftwidth=4:
# -*- Mode: tab-width: 4; indent-tabs-mode: nil; basic-offset: 4 -*- #
You could also just run it through a tidy program and a site-specific config if you really want to be a formatting nazi.
Say a server running service A uses service B on behalf of users of service B. In order to do this, service A needs to store a credential for each user of service B.
You're doing it wrong.
One way is for Service A to establish a trust with Service B (ex. using SAML), and have the user at Service B authorize that usage. Service A and B agree on a unique key for that exchange (ex. private/public certs), and Service A issues those commands to Service B using its user + that authorized cert to perform on that users behalf.
Of course, if Service B offers no such ability, then you'll need some sort of kludge like you suggested, but that doesn't make it right. Even so, they should protect those credentials in a much more sophisticated way than just another table in the same DB with an encrypted version of the Service B credentials (ex. a key server appliance).