What's the alternative though? I think the threaded system actually helps somewhat against "first post" problems. But I agree with what you're saying. Perhaps the up modded posts could appear more abridged, and down modded could take even less space/smaller font?
Tweaking and submitting would be removing the plagiarism, which would still be caught on the instructor side. I fail to see the conflict here.
It isn't required to be word for word to be plagiarism. Replacing a few words here and there still isn't the same as doing the work and writing something yourself. A paper is supposed to show what you know and how well you can communicate it. A paper that you stole and then modified to pass plagiarism software only proves that you know how to be a criminal.
Well since niether have any actual evidence of their claims, I dont think you have to agree with either. Google may really have wanted the Nortel Patents, but to think they bought Motorola on some threat FROM Motorola, is a little hard to fathom. I do believe the bit about MS bidding for Moto though.
But Gruber is some mac fanatic spinning wild fabrications. It was clear in the original Slashdot article about his "interpretation" of some PR speak at a conference that he was imagining his own little reality with regards to Motorola's plans. They say something to the effect of "IP is important" and he translated that to "Moto is going all patent RABMO!" (exagerating here but it's not far off).
Driving the price up for Oracle, RIM, Apple and MS is good business. Google has been known to bid just to drive prices in the past.
As for MS acquiring Moto, I'd be a little surprised if they had a serious offer on the table. I'd wager they were also trying to drive price. These things make sense, Gruber's fantasy land doesn't.
As for HTC, Samsung, et al. I would guess that Google offered them some protection from Apple and MS to help reassure them that Android is worth sticking with. I'm sure hardware manufacturers are privately evaluating long term plans, and it would be silly to think Google would give no preference to Motorola at some point eventually. But for the next year or two at the very least, I'd wager most of the Android hardware companies are on board, but keeping a keen eye on things.
Thank you for calling Verizon. To go to the main menu, press 1. To exit this menu and go to the main menu, press 2. To return to the main menu, press 3. To hear these options again, press 4.
True, but they weren't sure how it would all turn out. I think while the summary is basied, they do a good job of admitting that it was partly their fault in the article, and something to watch out for. I think this also speaks to gaps between ad-supported apps and paid apps. Ad-supported will often out-perform paid apps leaving paid "tool" style apps and "use quickly once a day" apps at a severe diadvantage to games and other content style apps. This is despite the fact that the amount of work required to create both kinds of apps may very well be equal in many cases. Anyways, trolltastic summary for sure, but the article bias wasn't as bad.
Exactly my thoughts as well. It also appears to move them one step further away from potential spills and the bad publicity that follows. The exploration units wont be household names. BP tried to hide that it basically owned that platform in the Gulf by outsourcing it IIRC. So this looks to possibly be another layer to hide profits and more. This isn't free markets creating competition and innovation, this is shell games and accounting tricks. It's also ridiculous to think ExxonMobil is somehow powerless at the behest of Wall Street traders when it was the #1 most profitable company in 2010. They dont tremble when a barrel of crude hits $100+, they laugh all the way to the bank.
I thought the privacy robbing stuff was already there in HTML5 with local storage, and the like. It's the vector rendering animation engine, tools, text rendering, DRM, and ubiquitous video platform that are lagging. Isn't that the crux of some of the new "super" undeletable cookies? They make use of HTML5, JS, fIngerprinting, Flash, regular cookies, and more.
There is also a highly subjective argument to be made that ActionScript far outpaces JavaScript in feature and elegance -- being more akin to C#. (Also possibly performance. It certainly had a JIT first, though Adobe contributed some of the JIT to FF for JavaScript IIRC, but I dont think they use that JIT anymore) . But that's subjective so take it as you will. HTML does have some long held advantages with regards to reflowing content though.
There really are legit reasons to dislike Flash, dont get me wrong -- the privacy controls should be more easily discoverable and integrated with the browser. And it does hog CPU to give performance. But this kinda angry spite seems uninformed and unhelpful. IMHO, if people want Flash to go away, build alternatives, dont complain.
With things like FlashBlock and NoScript we've got it (relatively) easy these days when we want to block unwanted content. But if we removed Flash from the equation, you will just end up having privacy invanding HTML local storage with CPU hogging sites that are renderd completely in a canvas tag. Bad sites and ads aren't bad because of Flash, they are bad because of the motivations behind the people that built them. Those motivations wont change just because of HTML5.
Do people forget the GIFs that used to blink and fly accross the pages of bad sites in the pre-Flash days?
While certainly no one wants to be bombarded with 100,000 config options, I think you can agree there has been a movement to hide and simplfy UIs over the past few years especially, and that this particular UI looks more sparse than the last which looked more sparse than the previous and so on. I highly doubt we're just going to go to all text lists like in the past (and I wouldn't want that), but it was an example of a consistent UI element people have long learned to understand almost intuitively. There are others too, but it was just an example. The other point that's important to remember here is that everyone categorizes a bit differently. They may not think in the same terms as the UI designer.
And I use about:config. But I was talking about non-tech savvy users and how options are presented to them. Kind of an important part of the point.
And no, I wont be complaining about long lists, I'm saying that's one of the few things usability has taught most people over the years. It's (part of) why most webpages scroll down. People get that. Why would you think I would complain about the opposite? Anyways, I'm sorry but I dont get where you're coming from with that comment other than it seems like you're trying to be rude because you're frustrated at what you think I'm saying (which I am not).
I understand you are designing for the lowest common denominator. It makes sense, and I can see where you are going with this design direction.
However, please be sure to allow configurability at the very least, and even better resist the urge to remove UI elements and hide them behind menus.
I dont want more buttons hidden behind more menus that require more clicks. On my desktop I have a large amount of room and like all my important options in front of me. That's why it's a great computing device for work. On my mobile phone, a sparse UI is much appreciated. But I dont really need it, nor want it, on a desktop. It doesnt make any sense in keeping with the idea of easy "discoverability" in user experience design. It also could easily confuse users even more than you think.
Most users can learn to recognize that a little "house" icon is the home screen. However, many users will not understand that setting the home page is under [alt] > Tools > options > General tab. Non-tech savvy people dont understand all of this multi layered categorization. They may not think the same way the developers and designers do, and may not put the option under the same category if they were doing the organization. They also may understand what they need, but not what the categories mean. Simple UI controls work better for most people. As an example: almost everyone understand lists and scrolling, even if they are very long lists.
It would also be nice if the bugs regarding new versions of FF corrupting profiles be looked into. And I don't know of any users that really feel the new "rapid release" stuff is worth a dime. The people who know what it means think it's silly, and the people who don't wouldn't care anyways.
Don't get me wrong, you guys have done fantastic work over the years. And the world owes you *much* gratitude. But I feel the need to speak up at some of the recent changes in direction Mozilla has been making with FF and TB. A need I have never felt before regarding either product. As a fan I wish you all the best though and hope to keep using FF and TB as I have never been that interested in Chrome or Gmail.
I dont think where he wrote the code plays a big a role as people think it does. Rather what matters more is whether he was in an employer-employee relationship with them and if this was work that was part of that. Even though it appears he was freelance, if he worked onsite on company equipment for 6 years they may very well be enough to show an employer-employee relationship. Especially if this code was a part of one of their projects. It sucks, but now he knows what he needs to do legally next time.
Given the comment "It was done on my own time with the companyâ(TM)s full support.
Depends if he can prove that. "On company time" is not something that has held in court from what I remember. And to show they supported him owning the copyright, he would need a signed legal document (I think). I do agree he should consult a lawyer though if he really thinks he has a shot at this.
These factors are not exhaustive. The court left unclear which of these factors must be present to establish the employment relationship under the work for hire definition, but held that supervision or control over creation of the work alone is not controlling. All or most of these factors characterize a regular, salaried employment relationship, and it is clear that a work created within the scope of such employment is a work made for hire (unless the parties involved agree otherwise). Examples of works for hire created in an employment relationship include the following:
A software program created within the scope of his or her duties by a staff programmer for Creative Computer Corporation
Standard practice when hiring any employee is to write a legal agreement stating that any work you do there is "work for hire" and they own the copyright, not you. I *think* this can even be implied just by the fact that you were an employee, Unless you took specific action before writing this code, such as giving the company a specific license, or requireing them to let you contribute it, I think you are the one in *possible* legal danger here. (I am not a lawyer etc blah blah).
This is unfortunate but you need to get over the fact that work-for-hire does not belong to you and drop this quickly. The more you drum up publicity around this the more danger you could be in.
Chalk it up to a learning experience, and take solace in that you know what to do next time.
At the last company I worked with I asked my boss (a SVP level executive good enough for legal purposes) to sign a small contract with me that would allow me to bring in my own open source libraries I had built up over the years in exchange for letting me take code written on company time and contribute it back to the library or to an OSS project. I of course said this would not include anything proprietary to a client or any program as a whole, but rather utilities such as a date converter class or caching system. And that it was at my sole discretion to determine as best I could in good faith what code qualified to be contributed to open source.
The article mentioned power in the milli and microwatt neighborhood. So I dont think there will be anything like that in the *near* future. However, the article actually seemed a bit sparse when it came explaining the practicle uses. It mentioned a temperature sensor, but what would that sensor do? Would it transmit data? Would it record it? Just "sensing" is mostly useless, no? Admittedly my understanding of this tech is about nil -- but it mentioned charging capacitors with these things. So I gather that's where the power would come from to transmit and/or write to storage. So my question was how much of this power can be stored? How long would the charge take? That would give us the info needed to imagine practical applications I would think.
I also find the concept that this is "green" power a bit off considering just printing these things may take more power than they could give back. It surely may have some great logistical, industrial, consumer or other applications, but I'm not sure it's "green" energy in the way most people think about it.
Excellent! I think they should add another layer. Say like when I know what I want to watch 2-14 Buisiness days (M-F) from now, I could tell them and they'd send it to me on some type of disc and I could watch it whenever I got it and send it back when I was done.;)
I think part of why it works on Slashdot is that there is a community of continually interested people and a focused topic. It's hard to imagine people with that level of interest in "policing" the web at large. I think this is why crowd-sourcing is so easily gamed. While some people will sometimes be interested enough to help police things, the only ones who will be continuously motivated and dedicated are the spammers looking for financial gain.
A lot of NAS appliances offer this too. Some also have dedicated iPhone and Android apps -- though the quality probably varies a lot. Still, I personally find the Google Music app to be subpar on Android. It's gotten a lot better, but worse too in many ways. Some things require too many clicks/taps - and I dont really need a dynamic colored background or the little dropdown context menu. It seems somewhere alone the lines the UI designers forgot they were designing for touchscreens./endramble
I was going to mod you up but I think a reply is probably better. I absolutely love that Apple is pushing Bluetooth 4, and think it has so many advantages*, (many of which you state) over NFC for local communications. However, NFC is not without merit. While it's being sold on the merits of being contactless payment system, the really cool part of NFC is the auto-configuration and app launching abilities it will open up. The possibilities for how to use that are quite vast and cool. In fact, it could (in theory) be a great way to make Bluetooth pairing easier. Or, it could be a nice way to let a guest or relative visiting your house configure Wi-Fi on their device simply by waving their device next to an NFC sticker. There is much more too, but these are just ideas to get the mind thinking about the possibilities. (Also from what I understand cyrptography is certainly possible with NFC, but may not be built in).
So while you're right, Bluetooth is far superior as a connectivity technology, NFC fills a different need and it's not without advantages.
*(Admittedly I'm a bit biased because I have developed two apps that make heavy use of Bluetooth).
Slashdot Mirror
What's the alternative though? I think the threaded system actually helps somewhat against "first post" problems. But I agree with what you're saying. Perhaps the up modded posts could appear more abridged, and down modded could take even less space/smaller font?
Tweaking and submitting would be removing the plagiarism, which would still be caught on the instructor side. I fail to see the conflict here.
It isn't required to be word for word to be plagiarism. Replacing a few words here and there still isn't the same as doing the work and writing something yourself. A paper is supposed to show what you know and how well you can communicate it. A paper that you stole and then modified to pass plagiarism software only proves that you know how to be a criminal.
I thought they EOL'd it when the 90's called...
Well since niether have any actual evidence of their claims, I dont think you have to agree with either. Google may really have wanted the Nortel Patents, but to think they bought Motorola on some threat FROM Motorola, is a little hard to fathom. I do believe the bit about MS bidding for Moto though.
Why wouldn't the patents help against MS/Apple?
I could see the argument that they wouldnt help vs Oracle, but not against MS/Apple?
But Gruber is some mac fanatic spinning wild fabrications. It was clear in the original Slashdot article about his "interpretation" of some PR speak at a conference that he was imagining his own little reality with regards to Motorola's plans. They say something to the effect of "IP is important" and he translated that to "Moto is going all patent RABMO!" (exagerating here but it's not far off).
Driving the price up for Oracle, RIM, Apple and MS is good business. Google has been known to bid just to drive prices in the past.
As for MS acquiring Moto, I'd be a little surprised if they had a serious offer on the table. I'd wager they were also trying to drive price. These things make sense, Gruber's fantasy land doesn't.
As for HTC, Samsung, et al. I would guess that Google offered them some protection from Apple and MS to help reassure them that Android is worth sticking with. I'm sure hardware manufacturers are privately evaluating long term plans, and it would be silly to think Google would give no preference to Motorola at some point eventually. But for the next year or two at the very least, I'd wager most of the Android hardware companies are on board, but keeping a keen eye on things.
https://secure.wikimedia.org/wikipedia/en/wiki/Assembler_%28computer_programming%29#Related_terminology
Thank you for calling Verizon. To go to the main menu, press 1. To exit this menu and go to the main menu, press 2. To return to the main menu, press 3. To hear these options again, press 4.
4
Goodbye.
we had to code uphill in 10 feet of snow on an abacus using roman numerals.
Works fine for me. I just won 2 free $250 Walmart Pirce club cards and I get 20% off my next purchase of a HiPhone 5 Nano from Somy. Pretty exciting.
True, but they weren't sure how it would all turn out. I think while the summary is basied, they do a good job of admitting that it was partly their fault in the article, and something to watch out for. I think this also speaks to gaps between ad-supported apps and paid apps. Ad-supported will often out-perform paid apps leaving paid "tool" style apps and "use quickly once a day" apps at a severe diadvantage to games and other content style apps. This is despite the fact that the amount of work required to create both kinds of apps may very well be equal in many cases. Anyways, trolltastic summary for sure, but the article bias wasn't as bad.
Exactly my thoughts as well. It also appears to move them one step further away from potential spills and the bad publicity that follows. The exploration units wont be household names. BP tried to hide that it basically owned that platform in the Gulf by outsourcing it IIRC. So this looks to possibly be another layer to hide profits and more. This isn't free markets creating competition and innovation, this is shell games and accounting tricks. It's also ridiculous to think ExxonMobil is somehow powerless at the behest of Wall Street traders when it was the #1 most profitable company in 2010. They dont tremble when a barrel of crude hits $100+, they laugh all the way to the bank.
Thank you for the link, very informative.
I thought the privacy robbing stuff was already there in HTML5 with local storage, and the like. It's the vector rendering animation engine, tools, text rendering, DRM, and ubiquitous video platform that are lagging. Isn't that the crux of some of the new "super" undeletable cookies? They make use of HTML5, JS, fIngerprinting, Flash, regular cookies, and more.
There is also a highly subjective argument to be made that ActionScript far outpaces JavaScript in feature and elegance -- being more akin to C#. (Also possibly performance. It certainly had a JIT first, though Adobe contributed some of the JIT to FF for JavaScript IIRC, but I dont think they use that JIT anymore) . But that's subjective so take it as you will. HTML does have some long held advantages with regards to reflowing content though.
There really are legit reasons to dislike Flash, dont get me wrong -- the privacy controls should be more easily discoverable and integrated with the browser. And it does hog CPU to give performance. But this kinda angry spite seems uninformed and unhelpful. IMHO, if people want Flash to go away, build alternatives, dont complain.
With things like FlashBlock and NoScript we've got it (relatively) easy these days when we want to block unwanted content. But if we removed Flash from the equation, you will just end up having privacy invanding HTML local storage with CPU hogging sites that are renderd completely in a canvas tag. Bad sites and ads aren't bad because of Flash, they are bad because of the motivations behind the people that built them. Those motivations wont change just because of HTML5.
Do people forget the GIFs that used to blink and fly accross the pages of bad sites in the pre-Flash days?
Because there are thousands of new "developers" unwilling to learn correct FORTRAN.
While certainly no one wants to be bombarded with 100,000 config options, I think you can agree there has been a movement to hide and simplfy UIs over the past few years especially, and that this particular UI looks more sparse than the last which looked more sparse than the previous and so on. I highly doubt we're just going to go to all text lists like in the past (and I wouldn't want that), but it was an example of a consistent UI element people have long learned to understand almost intuitively. There are others too, but it was just an example. The other point that's important to remember here is that everyone categorizes a bit differently. They may not think in the same terms as the UI designer.
And I use about:config. But I was talking about non-tech savvy users and how options are presented to them. Kind of an important part of the point.
And no, I wont be complaining about long lists, I'm saying that's one of the few things usability has taught most people over the years. It's (part of) why most webpages scroll down. People get that. Why would you think I would complain about the opposite? Anyways, I'm sorry but I dont get where you're coming from with that comment other than it seems like you're trying to be rude because you're frustrated at what you think I'm saying (which I am not).
I understand you are designing for the lowest common denominator. It makes sense, and I can see where you are going with this design direction.
However, please be sure to allow configurability at the very least, and even better resist the urge to remove UI elements and hide them behind menus.
I dont want more buttons hidden behind more menus that require more clicks. On my desktop I have a large amount of room and like all my important options in front of me. That's why it's a great computing device for work. On my mobile phone, a sparse UI is much appreciated. But I dont really need it, nor want it, on a desktop. It doesnt make any sense in keeping with the idea of easy "discoverability" in user experience design. It also could easily confuse users even more than you think.
Most users can learn to recognize that a little "house" icon is the home screen. However, many users will not understand that setting the home page is under [alt] > Tools > options > General tab. Non-tech savvy people dont understand all of this multi layered categorization. They may not think the same way the developers and designers do, and may not put the option under the same category if they were doing the organization. They also may understand what they need, but not what the categories mean. Simple UI controls work better for most people. As an example: almost everyone understand lists and scrolling, even if they are very long lists.
It would also be nice if the bugs regarding new versions of FF corrupting profiles be looked into. And I don't know of any users that really feel the new "rapid release" stuff is worth a dime. The people who know what it means think it's silly, and the people who don't wouldn't care anyways.
Don't get me wrong, you guys have done fantastic work over the years. And the world owes you *much* gratitude. But I feel the need to speak up at some of the recent changes in direction Mozilla has been making with FF and TB. A need I have never felt before regarding either product. As a fan I wish you all the best though and hope to keep using FF and TB as I have never been that interested in Chrome or Gmail.
I dont think where he wrote the code plays a big a role as people think it does. Rather what matters more is whether he was in an employer-employee relationship with them and if this was work that was part of that. Even though it appears he was freelance, if he worked onsite on company equipment for 6 years they may very well be enough to show an employer-employee relationship. Especially if this code was a part of one of their projects. It sucks, but now he knows what he needs to do legally next time.
Given the comment "It was done on my own time with the companyâ(TM)s full support.
Depends if he can prove that. "On company time" is not something that has held in court from what I remember. And to show they supported him owning the copyright, he would need a signed legal document (I think). I do agree he should consult a lawyer though if he really thinks he has a shot at this.
However from: http://www.copyright.gov/circs/circ09.pdf (Emphasis mine)
These factors are not exhaustive. The court left unclear
which of these factors must be present to establish the
employment relationship under the work for hire definition,
but held that supervision or control over creation of the
work alone is not controlling.
All or most of these factors characterize a regular, salaried
employment relationship, and it is clear that a work created
within the scope of such employment is a work made for
hire (unless the parties involved agree otherwise).
Examples of works for hire created in an employment
relationship include the following:
A software program created within the scope of his or her
duties by a staff programmer for Creative Computer Corporation
Standard practice when hiring any employee is to write a legal agreement stating that any work you do there is "work for hire" and they own the copyright, not you. I *think* this can even be implied just by the fact that you were an employee, Unless you took specific action before writing this code, such as giving the company a specific license, or requireing them to let you contribute it, I think you are the one in *possible* legal danger here. (I am not a lawyer etc blah blah).
This is unfortunate but you need to get over the fact that work-for-hire does not belong to you and drop this quickly. The more you drum up publicity around this the more danger you could be in.
Chalk it up to a learning experience, and take solace in that you know what to do next time.
At the last company I worked with I asked my boss (a SVP level executive good enough for legal purposes) to sign a small contract with me that would allow me to bring in my own open source libraries I had built up over the years in exchange for letting me take code written on company time and contribute it back to the library or to an OSS project. I of course said this would not include anything proprietary to a client or any program as a whole, but rather utilities such as a date converter class or caching system. And that it was at my sole discretion to determine as best I could in good faith what code qualified to be contributed to open source.
The article mentioned power in the milli and microwatt neighborhood. So I dont think there will be anything like that in the *near* future. However, the article actually seemed a bit sparse when it came explaining the practicle uses. It mentioned a temperature sensor, but what would that sensor do? Would it transmit data? Would it record it? Just "sensing" is mostly useless, no? Admittedly my understanding of this tech is about nil -- but it mentioned charging capacitors with these things. So I gather that's where the power would come from to transmit and/or write to storage. So my question was how much of this power can be stored? How long would the charge take? That would give us the info needed to imagine practical applications I would think.
I also find the concept that this is "green" power a bit off considering just printing these things may take more power than they could give back. It surely may have some great logistical, industrial, consumer or other applications, but I'm not sure it's "green" energy in the way most people think about it.
Excellent! I think they should add another layer. Say like when I know what I want to watch 2-14 Buisiness days (M-F) from now, I could tell them and they'd send it to me on some type of disc and I could watch it whenever I got it and send it back when I was done. ;)
I think part of why it works on Slashdot is that there is a community of continually interested people and a focused topic. It's hard to imagine people with that level of interest in "policing" the web at large. I think this is why crowd-sourcing is so easily gamed. While some people will sometimes be interested enough to help police things, the only ones who will be continuously motivated and dedicated are the spammers looking for financial gain.
A lot of NAS appliances offer this too. Some also have dedicated iPhone and Android apps -- though the quality probably varies a lot. Still, I personally find the Google Music app to be subpar on Android. It's gotten a lot better, but worse too in many ways. Some things require too many clicks/taps - and I dont really need a dynamic colored background or the little dropdown context menu. It seems somewhere alone the lines the UI designers forgot they were designing for touchscreens. /endramble
I was going to mod you up but I think a reply is probably better. I absolutely love that Apple is pushing Bluetooth 4, and think it has so many advantages*, (many of which you state) over NFC for local communications. However, NFC is not without merit. While it's being sold on the merits of being contactless payment system, the really cool part of NFC is the auto-configuration and app launching abilities it will open up. The possibilities for how to use that are quite vast and cool. In fact, it could (in theory) be a great way to make Bluetooth pairing easier. Or, it could be a nice way to let a guest or relative visiting your house configure Wi-Fi on their device simply by waving their device next to an NFC sticker. There is much more too, but these are just ideas to get the mind thinking about the possibilities. (Also from what I understand cyrptography is certainly possible with NFC, but may not be built in).
So while you're right, Bluetooth is far superior as a connectivity technology, NFC fills a different need and it's not without advantages.
*(Admittedly I'm a bit biased because I have developed two apps that make heavy use of Bluetooth).