hah oh man.. you think congressmen don't already know that?
Sorry but this is pretty naive in the face of all that's happened in recent times. I agree that outright fighting isn't the answer but begging isn't going to work either. I'd suggest impeachments and instating true patriots. The government/TSA/police only have any kind of authority because the people let them. Don't like what they're doing? Then stop acknowledging their authority. Stop feeding into their power.
Considering Linux does have this capability in a few FS drivers now (ok.. some more stable than others, sure) I think the GP should be modded troll rather than the post pointing out it's likely a shill... too bad i'm out of mod points
And besides, the 'handle such loads' remark was referring to the context switching and script interpreting.... I'd love to see a gpu-accel'd javascript interpreter
We're not talking about rasterising 3d objects into a 2d plane here.. we're talking about SIMD-instructions moving 1's and 0's from one memory address into another (framebuffer). CPUs/are/ very good at this today.
Actually, blitting pixels to a surface/framebuffer/etc even with alpha compositing isn't *that* cpu intensive (but maybe it's bus io intensive in some circumstances). It's all the other stuff going on in the background that causes the chug - causes context switching and such - like events firing constantly, IPC, and so forth. And yes, abstracting these a few times through a C++ library then a javascript engine on top of it and then javascript itself does add up to overhead in a few places you seriously don't want it.
Having said that though, there's no reason it has to be so slow as to ruin the user experience either! Modern cpus handle such loads pretty well. Either the touchpads were using the wrong, underpowered cpus because some jerk wanted to shave $10 per unit, or, the programmers didn't spend a lot of time optimizing their code and testing it under load.
Not every country has the same laws and courts as the USA. At the very least though, even if invalid, it still means you might end up wasting some time in the courts disputing it.
I'm fairly sure the kind of app people are complaining about here are the entirely useless ones. If an app does something close to what it advertises, even if the production quality is low or it's unstable, they're usually content since they only paid $1 for it.. they don't have much expectation except that it be a solution to a particular problem. The bulk of apps though that people complain about are in fact entirely useless. Unusable due to forced closes every time you launch them, broken interfaces that don't let you progress through the app towards the intended goal, etc.
For every single complaint I've seen about an app simply being of poor quality, I've seen a hundred about an app not even coming close to doing what it claims either by being entirely broken or even being an outright sham. I think it's safe to say that in this context a bad apps as referred to here, and plaguing the various markets, are something worse than a poor quality app that achieves 90% of the solution or looks ugly.
Just to play devil's advocate with the initial analogy: A bad coffee is still coffee. At least you get your caffeine fix and/or sugar hit. A useless app is entirely useless. The perceived and actual losses experienced are still far greater with the apps. It would be more like buying a coffee and risking ending up with a cup of water or air instead (and far more frequently than one gets a bad coffee too..)
I do like this subscription idea, both as a user and a developer however. In the short term it gives users the ability to asses and filter their purchases with less risk. In the long term it makes more money for the dev, which is fair if the app is good enough to entice the user to keep subscribing. Since a large swath of these apps are more or less web widgets anyway it can't be too hard to implement.
Also make sure to read the nitty-gritty of your contract carefully. Many companies I've worked for try to sneak in clauses claiming they own the copyright for any and all code you write while employed by them on the clock or off, at the office or at home. I've had to ask for such clauses to be amended in the past. If you haven't been careful, they might just already legally own the software you wrote..
I'll admit vb.net isn't as bad as it's predecessors. But if you're going to teach a CLR lang, why not just start with C#? Is it really much of a leap from vb.net to c#?
And for the record, you would truly be AMAZED at how fast an inquisitive young mind would pick up something as esoteric as assembly language. The problem we have as adults isn't the learning new concepts, it's unlearning the old ones that keep interfering with our attempts to perceive and conceptualize the new ones. Young kids do not have that problem and will pick up Assembler in *days*.
I also started out on BASIC. But luckily a friend's uni professor father got me stuck into Pascal and Assembler in year 5 before too much damage was done. I do recall it being hard at the time to get my head around subroutines instead of gotos after BASIC pollution. Despite starting on BASIC, I have to agree that it's a bad choice for beginners, teaches the wrong things, and needs to be left as a footnote in history. There are much better designed modern languages that are just as easy to learn without encouraging bad habits.
Why? It'll be far more fun sitting back and watching them fall flat on their faces when they realize the internet doesn't work the way they think it does, despite them inventing it!
Maybe stop letting the tech-ignorant courts decide such things. Let the IEEE or some other tech-skilled body determine them, perhaps? But one that doesn't have vested interests in the outcome of the decisions, obviously
I don't have a dynamic IP (or use windows, heh). It still listed some crap I've never heard of (although 1 entry was correct, only 1). I know my wife didn't download them because she doesn't know even know what torrents are. I doubt any of my small handful of neighbours hacked my wpa2 just so they could download some self-motivation crap (it's not even tony robbins!). There seems to be more flaws with their data collection process than just the dynamic IP issue.
Slashdot Mirror
hah oh man.. you think congressmen don't already know that?
Sorry but this is pretty naive in the face of all that's happened in recent times. I agree that outright fighting isn't the answer but begging isn't going to work either. I'd suggest impeachments and instating true patriots. The government/TSA/police only have any kind of authority because the people let them. Don't like what they're doing? Then stop acknowledging their authority. Stop feeding into their power.
Considering Linux does have this capability in a few FS drivers now (ok.. some more stable than others, sure) I think the GP should be modded troll rather than the post pointing out it's likely a shill... too bad i'm out of mod points
And besides, the 'handle such loads' remark was referring to the context switching and script interpreting.... I'd love to see a gpu-accel'd javascript interpreter
We're not talking about rasterising 3d objects into a 2d plane here.. we're talking about SIMD-instructions moving 1's and 0's from one memory address into another (framebuffer). CPUs /are/ very good at this today.
Because the law says websites, not ftp or irc servers! Teehee..
Actually, blitting pixels to a surface/framebuffer/etc even with alpha compositing isn't *that* cpu intensive (but maybe it's bus io intensive in some circumstances). It's all the other stuff going on in the background that causes the chug - causes context switching and such - like events firing constantly, IPC, and so forth. And yes, abstracting these a few times through a C++ library then a javascript engine on top of it and then javascript itself does add up to overhead in a few places you seriously don't want it.
Having said that though, there's no reason it has to be so slow as to ruin the user experience either! Modern cpus handle such loads pretty well. Either the touchpads were using the wrong, underpowered cpus because some jerk wanted to shave $10 per unit, or, the programmers didn't spend a lot of time optimizing their code and testing it under load.
power LEDS?
Not every country has the same laws and courts as the USA. At the very least though, even if invalid, it still means you might end up wasting some time in the courts disputing it.
I'm fairly sure the kind of app people are complaining about here are the entirely useless ones. If an app does something close to what it advertises, even if the production quality is low or it's unstable, they're usually content since they only paid $1 for it.. they don't have much expectation except that it be a solution to a particular problem. The bulk of apps though that people complain about are in fact entirely useless. Unusable due to forced closes every time you launch them, broken interfaces that don't let you progress through the app towards the intended goal, etc.
For every single complaint I've seen about an app simply being of poor quality, I've seen a hundred about an app not even coming close to doing what it claims either by being entirely broken or even being an outright sham. I think it's safe to say that in this context a bad apps as referred to here, and plaguing the various markets, are something worse than a poor quality app that achieves 90% of the solution or looks ugly.
Just to play devil's advocate with the initial analogy: A bad coffee is still coffee. At least you get your caffeine fix and/or sugar hit. A useless app is entirely useless. The perceived and actual losses experienced are still far greater with the apps. It would be more like buying a coffee and risking ending up with a cup of water or air instead (and far more frequently than one gets a bad coffee too..)
I do like this subscription idea, both as a user and a developer however. In the short term it gives users the ability to asses and filter their purchases with less risk. In the long term it makes more money for the dev, which is fair if the app is good enough to entice the user to keep subscribing. Since a large swath of these apps are more or less web widgets anyway it can't be too hard to implement.
Also make sure to read the nitty-gritty of your contract carefully. Many companies I've worked for try to sneak in clauses claiming they own the copyright for any and all code you write while employed by them on the clock or off, at the office or at home. I've had to ask for such clauses to be amended in the past. If you haven't been careful, they might just already legally own the software you wrote..
I'll admit vb.net isn't as bad as it's predecessors. But if you're going to teach a CLR lang, why not just start with C#? Is it really much of a leap from vb.net to c#?
The unlearning of habits. Hence the basis for the entire argument..
And for the record, you would truly be AMAZED at how fast an inquisitive young mind would pick up something as esoteric as assembly language. The problem we have as adults isn't the learning new concepts, it's unlearning the old ones that keep interfering with our attempts to perceive and conceptualize the new ones. Young kids do not have that problem and will pick up Assembler in *days*.
I also started out on BASIC. But luckily a friend's uni professor father got me stuck into Pascal and Assembler in year 5 before too much damage was done. I do recall it being hard at the time to get my head around subroutines instead of gotos after BASIC pollution. Despite starting on BASIC, I have to agree that it's a bad choice for beginners, teaches the wrong things, and needs to be left as a footnote in history. There are much better designed modern languages that are just as easy to learn without encouraging bad habits.
Or better yet, when the internet 'self-heals' to exclude them entirely
Why? It'll be far more fun sitting back and watching them fall flat on their faces when they realize the internet doesn't work the way they think it does, despite them inventing it!
Maybe stop letting the tech-ignorant courts decide such things. Let the IEEE or some other tech-skilled body determine them, perhaps? But one that doesn't have vested interests in the outcome of the decisions, obviously
Just making sure
That was sarcastic, right?
I don't have a dynamic IP (or use windows, heh). It still listed some crap I've never heard of (although 1 entry was correct, only 1). I know my wife didn't download them because she doesn't know even know what torrents are. I doubt any of my small handful of neighbours hacked my wpa2 just so they could download some self-motivation crap (it's not even tony robbins!). There seems to be more flaws with their data collection process than just the dynamic IP issue.
Not free per-se.. Open source. There's a distinction ;)
Ofc, I am just guessing..
Unfortunately, I dare say the cellular stuff will remained closed. That's usually 3rd party IP.
Yeah I know it's a gambit. But stranger things have happened in the past.