By the way, if you are convinced of your argument then post under your real name as I do. Otherwise you only make you and your organization look worse.
I use my handle, but I provide my email address unobfuscated, which anyone can Google and get my real name (as it's in all the source code I have published, plus other things.) I simply hate my real name, and I always use the same handle. Is that fine?
And the retweet feature is how Twitter sublicenses the content in compliance with the TOS. This is all perfectly legal, NYT is just butthurt that someone is screwing them in a wholly legal manner.
I could write a program to calculate as many prime numbers as possible with given memory. The algorithm, possibly the entire executable file, would be (nearly) under 4k of code, yet if it stored it's results to a simple, linear array in memory, it would eventually consume all the RAM of almost any system*
*(Segmented memory, virtual addressing being narrower than physical - PAE or 32 bit code on 64 bit OS, etc aside, in such case, the program will consume as much memory as It can allocate from the OS.)
And not running Windows does not automagically invalidate the Alt+F4 thing. A number of X11 window managers have that keystroke bound to the usual command, or can be bound that way by user config.
If they are so desperate for the frist psot, why don't we let them have it and let their childless stand out on top as a warning of what not to do on Slashdot.
actually, they can put whatever they want in the EULA and it is contractually binding, that's why those pesky pirates always avoid accepting Sony's EULAs - the "you agree for us to kill you" clause can be a real killer for some
That application already exists, it's called the web browser. Also, the same lack of future also exists for file managers, anti-viral software, and the act of 'downloading', in the traditional sense. The future of client computing (both in the home and the office) is web browsing thin clients that are useless without a permanent Internet or intranet connection. "Traditional" software will only continue to exist if it's server software. Desktop software as we know it, is dying. The OS wars are pointless, Windows, Linux, and Mac OS X are soon to be footnotes except as the OSes running the websites that enable us to use our dumb web browsing kiosks. With the advent of entire x86 PCs being reduced to an SoC, including GPU and RAM, 3D accelerated graphics through webGL, web applications that can fully replace everything traditionally done on the client machine, there is no need whatsoever for an OS. All you need is a web browser.
And there will be tyranny as your data is no longer held by you.
Is everyone on Slashdot too stupid to realize that the S in SD means Secure and is an allusion to the fact that the card supports DRM at the hardware level?
Alright, let's say I want to write code against the IJG's JPEG implementation. Which version should I compile against? 6.x? 7.x? 8.x? And what do I do when a new major release of libjpeg comes around? Do I root all my user's machines so that I can replace their installed copies of my application to reflect the new libjpeg.so.9? Or do I just try to use libjpeg.so.8 linked executables against the new version and watch the dynamic linker errors fly?
Obviously you haven't heard of binary incompatibility. At least with Windows, you can load and run code compiled and linked against, say, NT 3.1's kernel32.dll 18 years ago on Windows 7 and have no afterthought of binary compatibility.
Let me support your case better: I have a Nokia 6620, that has a 150MHz TI OMAP-1510 ARM-based SoC and it can run Python. I once had a Nokia 6600 (which has a 104MHz ARM9T and discrete motherboard components, not SoC) and it, too, can run Python.
RIM's JavaME implementation is hackish, at best, and even then, you're best off writing "native" BlackBerry code... which is STILL Java. J2ME support only exists in BlackBerry so that they can get away with doing essentially what Google is doing, except the core differences are that:
BlackBerry's OS's, at least on ARM-based handsets, the entire native code portion consists solely of the JVM and hardware drivers - all other code and APIs in the OS is Java bytecode and
BlackBerry uses Sun's JVM and Java bytecode.
Java ME-specific APIs (those not shared with Java SE), IIRC, are all I/O (user (javax.microedition.lcdui), file, network, etc.), are probably just implemented as wrappers to RIM's own Java APIs (net.rim.*)
There's more native code in a $5 featurephone or an Android device than in a BlackBerry.
P.S. Yes, RIM's earlier x86 BlackBerry handsets ran native code and had native code interfaces for third party apps, arguably a whole different OS, but those handsets are so old that their relevance is nil.
Windows Explorer was designed to be essentially a clone of the Macintosh Finder. NewShell for NT3.51 was the first version of Windows Explorer, which was then included as the standard and default graphical shell and file manager in Windows NT 4.0 and Windows 95, and later versions, and aside from the IE integration in Windows 98 and Windows 2000, the shell has essentially remained the same up to Windows Server 2003. The classic Windows Explorer is meant to be a good emulation of the Mac OS Finder from 1984-2001 (original Mac 128k's System Software through Mac OS 9.2.2), and the Windows Explorer in Vista and later is meant to be a rough clone of Finder in Mac OS X, note the Finder-like navigation sidebar and back/forward controls, as well as the new high-resolution icon support.
KDE's Konqueror (at least in KDE 3.x, being replaced by Dolphin in 4.x) is (was) a good example of how Microsoft should have done their file manager. Konqueror's interface feels like almost a direct rip from Windows Explorer, yet it provides a tabbed interface, as well as a two-column layout (Norton/Midnight/Taco Commander, anyone?) for manipulating directories.
Except one big problem is that a site's favicon doesn't absolutely have to be.ico format. See the favicon Wikipedia article subsection on standardization and implementation and note that generally JPEGs, GIFs and PNGs can be used as well, which some browsers supporting GIF's and PNG's animated variant, and Opera even supporting SVG for favicon.
I don't know the full APIs provided on Mac OS X, as I don't know Objective-C, but AFAIK, process management and thread management require using POSIX API, as the OPENSTEP API doesn't concern itself with such things. Correct me if I'm wrong.
Developing for Linux is a lot like developing for OS X - pthreads, POSIX, OpenGL, and all. Besides, if they need their games ported to Linux, all they would have to do is contract Ryan Gordon.
Slashdot Mirror
By the way, if you are convinced of your argument then post under your real name as I do. Otherwise you only make you and your organization look worse.
I use my handle, but I provide my email address unobfuscated, which anyone can Google and get my real name (as it's in all the source code I have published, plus other things.) I simply hate my real name, and I always use the same handle. Is that fine?
Use proxies and clear your cookies often. Problem solved.
And the retweet feature is how Twitter sublicenses the content in compliance with the TOS. This is all perfectly legal, NYT is just butthurt that someone is screwing them in a wholly legal manner.
I could write a program to calculate as many prime numbers as possible with given memory. The algorithm, possibly the entire executable file, would be (nearly) under 4k of code, yet if it stored it's results to a simple, linear array in memory, it would eventually consume all the RAM of almost any system*
*(Segmented memory, virtual addressing being narrower than physical - PAE or 32 bit code on 64 bit OS, etc aside, in such case, the program will consume as much memory as It can allocate from the OS.)
And not running Windows does not automagically invalidate the Alt+F4 thing. A number of X11 window managers have that keystroke bound to the usual command, or can be bound that way by user config.
And this is exactly why 96% of the comments aren't worth reading.
If they are so desperate for the frist psot, why don't we let them have it and let their childless stand out on top as a warning of what not to do on Slashdot.
I believe it's a crack at the floating point division bug on the original Pentium processor. Don't take it seriously.
Except a company is just an conceptual and legal entity, and doesn't have human rights, so it should always get the short end of the stick.
actually, they can put whatever they want in the EULA and it is contractually binding, that's why those pesky pirates always avoid accepting Sony's EULAs - the "you agree for us to kill you" clause can be a real killer for some
That application already exists, it's called the web browser. Also, the same lack of future also exists for file managers, anti-viral software, and the act of 'downloading', in the traditional sense. The future of client computing (both in the home and the office) is web browsing thin clients that are useless without a permanent Internet or intranet connection. "Traditional" software will only continue to exist if it's server software. Desktop software as we know it, is dying. The OS wars are pointless, Windows, Linux, and Mac OS X are soon to be footnotes except as the OSes running the websites that enable us to use our dumb web browsing kiosks. With the advent of entire x86 PCs being reduced to an SoC, including GPU and RAM, 3D accelerated graphics through webGL, web applications that can fully replace everything traditionally done on the client machine, there is no need whatsoever for an OS. All you need is a web browser.
And there will be tyranny as your data is no longer held by you.
Pastebin example code or it didn't happen.
Content Protection for Recordable Media is the DRM scheme provided by the Secure Digital specification.
Is everyone on Slashdot too stupid to realize that the S in SD means Secure and is an allusion to the fact that the card supports DRM at the hardware level?
Secure Digital includes DRM. See this article for more information.
Alright, let's say I want to write code against the IJG's JPEG implementation. Which version should I compile against? 6.x? 7.x? 8.x? And what do I do when a new major release of libjpeg comes around? Do I root all my user's machines so that I can replace their installed copies of my application to reflect the new libjpeg.so.9? Or do I just try to use libjpeg.so.8 linked executables against the new version and watch the dynamic linker errors fly?
Obviously you haven't heard of binary incompatibility. At least with Windows, you can load and run code compiled and linked against, say, NT 3.1's kernel32.dll 18 years ago on Windows 7 and have no afterthought of binary compatibility.
I believe that you are mistaking licensing concerns with security concerns.
Obviously you're a fucking idiot that doesn't get that it's a joke.
I'm guessing that your phone is a Series 60 device. IYDK, Nokia ported Pythong to their Series 60 platform
Let me support your case better: I have a Nokia 6620, that has a 150MHz TI OMAP-1510 ARM-based SoC and it can run Python. I once had a Nokia 6600 (which has a 104MHz ARM9T and discrete motherboard components, not SoC) and it, too, can run Python.
RIM's JavaME implementation is hackish, at best, and even then, you're best off writing "native" BlackBerry code... which is STILL Java. J2ME support only exists in BlackBerry so that they can get away with doing essentially what Google is doing, except the core differences are that:
P.S. Yes, RIM's earlier x86 BlackBerry handsets ran native code and had native code interfaces for third party apps, arguably a whole different OS, but those handsets are so old that their relevance is nil.
So wouldn't Google's best option be for them to just implement the missing classes?
Windows Explorer was designed to be essentially a clone of the Macintosh Finder. NewShell for NT3.51 was the first version of Windows Explorer, which was then included as the standard and default graphical shell and file manager in Windows NT 4.0 and Windows 95, and later versions, and aside from the IE integration in Windows 98 and Windows 2000, the shell has essentially remained the same up to Windows Server 2003. The classic Windows Explorer is meant to be a good emulation of the Mac OS Finder from 1984-2001 (original Mac 128k's System Software through Mac OS 9.2.2), and the Windows Explorer in Vista and later is meant to be a rough clone of Finder in Mac OS X, note the Finder-like navigation sidebar and back/forward controls, as well as the new high-resolution icon support.
KDE's Konqueror (at least in KDE 3.x, being replaced by Dolphin in 4.x) is (was) a good example of how Microsoft should have done their file manager. Konqueror's interface feels like almost a direct rip from Windows Explorer, yet it provides a tabbed interface, as well as a two-column layout (Norton/Midnight/Taco Commander, anyone?) for manipulating directories.
Because being sued by Epic Games for breach of contract and improper use of intellectual property doesn't look that good on your resume.
Except one big problem is that a site's favicon doesn't absolutely have to be .ico format. See the favicon Wikipedia article subsection on standardization and implementation and note that generally JPEGs, GIFs and PNGs can be used as well, which some browsers supporting GIF's and PNG's animated variant, and Opera even supporting SVG for favicon.
I don't know the full APIs provided on Mac OS X, as I don't know Objective-C, but AFAIK, process management and thread management require using POSIX API, as the OPENSTEP API doesn't concern itself with such things. Correct me if I'm wrong.
Developing for Linux is a lot like developing for OS X - pthreads, POSIX, OpenGL, and all. Besides, if they need their games ported to Linux, all they would have to do is contract Ryan Gordon.