Thin is relative.
65K is not a small application... to a C64. I've got over 2 gigabytes of flash memory and at least 128MBs of RAM just on the handheld devices -in my backpack-, all of which more than adequate to run an AJAX client.
Aren't they completely in the right to try to stop piracy of their intellectual property?
If you don't like windows, use something else... but stealing software is still stealing.
A significant portion of the chinese, korean, japanese, and indian arts came from the buddhist monasteries, of which the Shaolin sects are the most widely known.
http://en.wikipedia.org/wiki/Shaolin
I can't imagine the actual wafers in RAM 'chips' are that terribly big... a lot of space is wasted on wiring to the legs without creating capacitance problems at the 400mhz+ mark we're clocking memory at...
Likely this would be on firmware; wiping the drive would be pointless (and probably past the abilities of most crackheads anyways - wiping the drives means a reinstall before resell).
Blocking outgoing traffic on a possibly random port with a firewall isn't as easy to do as you'd think.
And here, folks, you have a PHP developer demonstrating a fundamental misunderstanding of multithreaded applications.
You replicate with mySQL? Why? Because the data integrity wasn't bad enough for you, so you figured you'd try to spice it up a bit?
You can do basically anything in PHP that you can do in Perl, Java,.NET, Ruby, etc.
-->Um, wrong. So very, very wrong.
Re:Stopped reading it when it got so political...
on
The Onion in 2056
·
· Score: 1
If you watch COPS and think they're oppressing people you actually -want- in your backyard, I'm moving to a different neighborhood...
I can't recall an episode where I was like "Damn, sure he beat his wife with the butt end of his AK-47, but they didn't have to confiscate his meth lab! Bastards!"
I don't have to synclock DA objects running SELECTs... do you? No wonder you think this is hard.
There isn't synch issues in the above if you partition your code properly. The only time locking should come into play is if you have a cache you're dumping the returned data into... which was clearly outside the scope of my simple example provided to prove a point.
It's very simple, actually, I do it quite frequently. Let's say you need to populate a drop-down based on user input in another drop-down.
At the start of the page you collect user input and fire off the data access code for the original drop and the parameterized drop, each in a seperate thread.
This executes while you're performing other formatting actions, like include headers, menu formatting, and outputting strings to your response (like client scripts, etc).
All the while, the other threads are formatting the first & second dropdown with the returned data, while your main thread is doing more menial UI tasks like formatting the tables and such that hold your page.
This is simply a basic example, but anyone who uses data access code even for a single databound table or drop should always be running it in a seperate thread and letting the main thread handle the non-data related rendering. There is a TON of work on web pages that you can be doing that is not data related, nor is it required to be peformed before or after the data is available.
Sooo... basically they're using an operating system to do what they should have an FPGA perform?
I mean, rah-rah-go-linux... but sounds like a dramatic over-use of power. Why one would use a modern OS to perform tasks that should be handled by dedicated hardware... is beyond me.
Uhm... no.
1. MS never disbanded the IE Dev team... otherwise where is IE7 coming from??
2. If you've ever done any serious app development you'd know that the work going into the product in the first few versions FAR outweighs the last few. Later versions of applications are often refactoring or building on your existing base. Early versions of code is where 90% of the functionality is solidified. Hence, later versions of applications usually need far less developers.
2. If you've ever taken a look at microsoft's roadmap throughout the mid-late 90's & early 2K you'd know why they needed many more developers; During that time they launched Win95 (new OS codebase), NT4, WinXP, and Win2K. Dramatically different and new OS's and APIs requiring a lot more developers at the time. With all the W3C spec changes plus all the OS changes... your team would be 2x the size it would be today.
Slashdot Mirror
Thin is relative. 65K is not a small application... to a C64. I've got over 2 gigabytes of flash memory and at least 128MBs of RAM just on the handheld devices -in my backpack-, all of which more than adequate to run an AJAX client.
Aren't they completely in the right to try to stop piracy of their intellectual property? If you don't like windows, use something else... but stealing software is still stealing.
Nope. Piracy -will- be rampant for non-UMD'd software... copy protection will be difficult.
Why send it to sony? A forward-thinking company should gather the money for the licensed SDK, and do this themselves.
A significant portion of the chinese, korean, japanese, and indian arts came from the buddhist monasteries, of which the Shaolin sects are the most widely known. http://en.wikipedia.org/wiki/Shaolin
Interestingly enough, it was the buddhists who developed many forms of martial arts... violence is often necessary.
I can't imagine the actual wafers in RAM 'chips' are that terribly big... a lot of space is wasted on wiring to the legs without creating capacitance problems at the 400mhz+ mark we're clocking memory at...
What's the likelihood it will become firmware once wireless manufacturers hear about it? Think about it...
Likely this would be on firmware; wiping the drive would be pointless (and probably past the abilities of most crackheads anyways - wiping the drives means a reinstall before resell). Blocking outgoing traffic on a possibly random port with a firewall isn't as easy to do as you'd think.
And here, folks, you have a PHP developer demonstrating a fundamental misunderstanding of multithreaded applications. You replicate with mySQL? Why? Because the data integrity wasn't bad enough for you, so you figured you'd try to spice it up a bit?
Multithreading? Distributable compiled controls? OOP?
You can do basically anything in PHP that you can do in Perl, Java, .NET, Ruby, etc.
-->Um, wrong. So very, very wrong.
If you watch COPS and think they're oppressing people you actually -want- in your backyard, I'm moving to a different neighborhood... I can't recall an episode where I was like "Damn, sure he beat his wife with the butt end of his AK-47, but they didn't have to confiscate his meth lab! Bastards!"
I don't have to synclock DA objects running SELECTs... do you? No wonder you think this is hard. There isn't synch issues in the above if you partition your code properly. The only time locking should come into play is if you have a cache you're dumping the returned data into... which was clearly outside the scope of my simple example provided to prove a point.
It's very simple, actually, I do it quite frequently. Let's say you need to populate a drop-down based on user input in another drop-down.
At the start of the page you collect user input and fire off the data access code for the original drop and the parameterized drop, each in a seperate thread.
This executes while you're performing other formatting actions, like include headers, menu formatting, and outputting strings to your response (like client scripts, etc).
All the while, the other threads are formatting the first & second dropdown with the returned data, while your main thread is doing more menial UI tasks like formatting the tables and such that hold your page.
This is simply a basic example, but anyone who uses data access code even for a single databound table or drop should always be running it in a seperate thread and letting the main thread handle the non-data related rendering. There is a TON of work on web pages that you can be doing that is not data related, nor is it required to be peformed before or after the data is available.
Single-threaded webpages are -terrible-.
I mean, unless you like your data access code holding up the page rendering.
You mean like they outsourced electronic voting? Don't be fooled. All the IT in government is outsourced to companies run by republicans.
Sooo... basically they're using an operating system to do what they should have an FPGA perform?
... is beyond me.
I mean, rah-rah-go-linux... but sounds like a dramatic over-use of power. Why one would use a modern OS to perform tasks that should be handled by dedicated hardware
"I'm sad that the reality was that this argument was not well founded." Dare I say it? TOLD YOU SO.
Back then, we just had a Slash - AND WE LOVED IT.
Seriously. Likely we're going to /. his homebrew 48.8KBPS ISP LONG before we hit his CPU. :0
1MHZ is a million cycles a second. Kilohertz is thousands.
Doesn't that require nookie to replicate? The nookie level around /., I dunno if that'd be a very good example...
Uhm... no. 1. MS never disbanded the IE Dev team... otherwise where is IE7 coming from?? 2. If you've ever done any serious app development you'd know that the work going into the product in the first few versions FAR outweighs the last few. Later versions of applications are often refactoring or building on your existing base. Early versions of code is where 90% of the functionality is solidified. Hence, later versions of applications usually need far less developers. 2. If you've ever taken a look at microsoft's roadmap throughout the mid-late 90's & early 2K you'd know why they needed many more developers; During that time they launched Win95 (new OS codebase), NT4, WinXP, and Win2K. Dramatically different and new OS's and APIs requiring a lot more developers at the time. With all the W3C spec changes plus all the OS changes... your team would be 2x the size it would be today.
Well, then perhaps you better get realistic here, because anyone can cause memory leaks in any JS-compliant browser in their own JS code.