Windows Browser Plugins for Linux 88
An Anonymous Coward sent in: "NewsForge has a story about a company called Codeweavers releasing a program that allows nearly all Windows plug-ins such as Quicktime or Shockwave to run on Linux browsers including Netscape, Mozilla and Konqueror. The company's aiming the product at the embedded device market, but promises to release a version for the desktop, too."
Re:And what hardware? Performance? (Score:1)
I dunno. Do plugins have to run as 'root'? (Score:1)
Surely letting such programs will destabilize Linux as much as my company's "conversion to linux" involves massive use of threads and shared memory "because it's easier thas using separate processes and pipes". The new software crashes for undetectable/unexplainable reasons. Well, DUH, they recreated all the worst of windows behaviour (all threads(DLLs) being able to scribble over the memory of all other threads.) under linux.
Re:Quicktime for (embedded) Linux is inevitable. (Score:2)
When Quicktime is running on Windows, it is rumoured that it is actually emulating a Macintosh toolbox underneath. This would be a lot of work, since you have to move from the quick RISC math of a PowerPC to the slower math x86 units. You also have to let go of the many built in ROM functions available on the Macintosh. This can be seen when you load Quicktime on a Windows and MacOS machine at the same time. A slow PowerPC will load Quicktime faster and run it smoother than some of the fastest x86 machines. This is mostly because of the supposed emulation on the lesser processors.
Now imagine porting it to Linux. A whole new port of the toolbox will have to be undertaken. This would be a lot of work for a group of people Apple could probably care less about. It probably requires a lot of work to port and trim the toolbox, and a whole new API to have to port to would not be well received.
Unless Linux becomes very mainstream, Apple will most likely not port to it. Apple has never released an embedded Quicktime as far as I know, and probably never will.
Fud Watch (Score:1)
Your argument fails on one point, either out of misunderstanding or downright maliciousness. But the rest is okay.
The FSF does not care who looks at code. To say they do is only a political lie. They only care who cuts and pastes their code somewhere else which is what is meant by CopyRight the right to copy. Not the right to look at it. You are welcome to look, learn and write your own BSD liscenced equivelant as long as you don't copy the code.
But even then they don't care who uses their gzip compression algorithm or other advancements and innovations.
Mind you, I think BSD is a more free liscence the GPL is an enforced openness and that gives those who use it freedom. But as someone said before it isn't freedom, its guild socialism. And that is a good thing.
~^~~^~^^~~^
Re:Not necessarily a good thing. (Score:1)
2000 is a little better.
Win98 with its crash early crash often policy? NO thank you. I like a real pre-emptive, memory protected OS that when one program crashes it won't bring down the whole box. Besides, i like running the same OS on a LART as well as a ALPHA 36 processor supermachine.
Also, as is not brought up enough, WINE brings terminal service to windows programs. Yep, run multiple copies on the server and pipe the X display to your particular computer.
These things help the establishment of Linux as the desktop OS, along with customizability, speed, security and a very considerate and community minded group of developers. (Outside of the posers on slashdot that is.)
The lack of running existing software that people like (really just games and browser stuff now) is the only thing keeping people back. Its unlikely that OS can keep up on that bleeding edge of games and browser coolness anyway. So far it hasn't.
~^~~^~^^~~^
Re:Not necessarily a good thing. (Score:1)
Wow. i wish I could mod that up as most insightful.
True, Slashdot acts like a forum of managers and marketers more than a forum of hackers and coders. And bad ones at that. Collectively in my opinion their ideas would in general alienate more than anialate, oppress more than impress, and stifle more than rifle (another way of saying disable rather than enable.)
In general, it shows them as being the very beasts they proport to fight (in an Animal Farm kind of way.) Its a good thing those that really direct the course of Open Source aren't this dumb.
Oh that Slashdot could learn this one lesson, told by one of the smarter people on slashdot...
"[Customers] are used to being catered to, not lectured."
~^~~^~^^~~^
Re:mod parent up (Score:2)
Doing this requires strategy a little smarter than the kicking, screaming and sulking that most Open Source advocates mandate. For example:
"We don't want that software its not open source..."
compared that my five year old nephew...
"I don't want a burger, I want McDonalds!"
~^~~^~^^~~^
Re:Fud Watch (Score:2)
But like I said here or somewhere else, the most informative piece of information I ever learned on slashdot was from a small post about a year and a half ago. GPL != freedom, its guild socialism. BSD does mean more freedom to do what I want with code but I don't think it makes better software.
As Mr Katz, others on slashdot and many of my libertarian counterparts) fail to understand is that freedom does not mean you can do anything you want. Freedom means more and usualy comes as a direct byproduct of adherance to laws rather than the attempt to ignore them or make them go away.
Example is that you do have the freedom to drive on the wrong side of the road, but you don't have the freedom to say your chevy sprint won't be turned into a pancake by the oncoming semi. Only staying on the right side of the road (while everyone else does also) gives you the freedom to arrive safely at your destination. Restraint here means freedom.
Its not trading one freedom for another either. Freedom only has an accumulative effect. To continue the analogy, some would argue that my example is trading the freedom to drive on the wrong side of the road for the freedom to arrive safely. I say this is obviously false since even after you arrive you have the freedom to be stupid and die. However the person who already was stupid and die doesn't have the freedom to do it again.
~^~~^~^^~~^
"not open source" (Score:2)
hawk
Re:Wowee... (Score:2)
I suppose it depends on what your definition of "works fo fucking well" is. Usually when I see that sort of statement, I automatically assume it's sarcasm, because I've had such horrible luck with IE in the past and in recent history. If you weren't intending to be sarcastic, my apologies.
Re:Not necessarily a good thing. (Score:3)
Then again, you got the score of 5 for the "look, it's bad for Linux 'coz it lets you use non-Open-Source software on Linux." I suppose you refuse to play Quake 3 Arena on Linux, too. And you never used Netscape 4.x. And never used StarOffice to deal with Office documents. Never used aviplay to play DivX
One of the big complaints about Linux (and other free OSs) is the lack of commercial software. "Uh, we don't have the Sorenson codec for QuickTime, but Ogg Tarkin is gonna be l33t." Sure. So how is it I convert those Sorenson QuickTime files to Ogg Tarkin again? And how do I do it using 100% Open Source software? Oh, I don't because I'd have to use non-Free software and that's bad for Linux, eh? Sure. Whatever.
I see it as a good sign. People have an interest in seeing software "ported" to Linux. Means that there's an interest in marginalizing Windows. It's a first step. And frankly, I never understood why people had such a fit over WINE. Sure, there's a risk that developers won't port code over, and sure using binary drivers means you're stuck with x86 only. But WINE isn't just a binary abstraction layer; it's also winelib, a nice porting tool. Heck, if IE were ever to come over to Linux, what, you think Microsoft would pay people to remove all the Win32 API references and port it to, say, GTK+? LOL. How do you think IE was ported to Solaris?
you mean something sorta like this? (Score:1)
(See also commentary from LWN [lwn.net]).
Re:necessary? (Score:3)
The bigger question is whether or not this implementation will use XVideo. SHM is just too slow and CPU intensive. This questions means the difference between whether these plugins seem like bulky and awkward processes run on top of an emulator, or whether they perform as well as in Windows itself.
--
Re:Quicktime for (embedded) Linux is inevitable. (Score:5)
This topic has been discussed at length [slashdot.org] on Slashdot in the past. One notable thread [slashdot.org] reads,
I wouldn't hold my breath, embedded Linux or not. From the massive PR that Apple lavishes on QT to watching Steve Jobs soil himself yearly at Macworld and Comdex whilst marvelling the latest and greatest QT innovations, etc., you get the sense that Apple really thinks they're sitting on the greatest thing since sliced bread here (they're not).
--
Re:I am using Internet Explorer 5.5 under Wine (Score:2)
If you're going to use Windows system files to supplant the weaker parts of WINE, you're legally required to have a full license to Windows. Once you're paying for the full Windows license, isn't VMWare a better way to go? It provides a much better Windows-under-Linux environment than Windows-less WINE does even under ideal conditions. Point is, as a technology to roll out in environments where software piracy isn't an option, a tweaked WINE combined with MS's Windows DLLs isn't really a viable product.
Anyone here out of college yet? (Score:5)
WINE's commercial value is instead in the targeted use of it as a porting library or compatibility layer for specific applications, when Linux-compatibility is needed but a port to native *nix APIs is either too expensive or too far off to meet a desired street date.
They don't intend to make money selling this plugin compatibility adaptor to end-users running Linux on their desktop. While they might try to sell it--at a per-copy rolyalty--to commericial Linux distributors that target consumer desktops, that doesn't seem to be their goal here
Because this isn't going to help anyone install plugins on Linux, it's really something for companies that want to, say, sell web terminals that can play Quicktime and Shockwave, because those companies would also have to secure the rights to redistribute a repackaged version of their software (i.e. Quicktime and Showckwave players).
While an individual at home might manage to use this to run Windows Media Player, that home user doesn't have the right to run it on a system without a Windows license. Appliance vendors are unlikely to pay for Windows ME licenses solely for the right to put WMP on each Linux appliance they make, so in practice, this is really only a product for hardware vendors that want to license and distribute specific Windows browser plugins as part of their appliance.
This adaptor isn't the makings of a billion-dollar company, but there could be a nice business in this for the next few years.
Re:The same thing for drivers ? (Score:1)
No. Oh, no. Definitely not. MOST definitely not. Try owning a Mac, and you'll quickly find out that this is NOT the case. Usually, youre stuck buying SCSI cards and Ethernet adapters at a bloated price from a select few 'vendors' who actually bothered to support the Mac.
Hehe... (Score:1)
This is a good thing (Score:1)
Think of all those thin clients out there that run windows because it has the latest greatest web plugins. Now they will be able to run linux -- smaller footprint (good), more robust (good), and now able to access all the cool technologies of the web.
Re:saving grace (Score:2)
IMNERHO, any post that contains a link to Comet Cursors should be nuked by the same lameness filter that catches goatsecx and comp-u-geek links.
-
Re:Not necessarily a good thing. (Score:2)
Are you going to do any research at all on this thread [codeweavers.com], or just continue to make an ass of yourself?
-
Re:Not necessarily a good thing. (Score:3)
Perhaps you should have done more than glance, as should the moderators who modded you up to +5 for this uninformed opinion.
Their primary product is enhanced Wine, completely Open Source. Even this article makes it clear that they're discussing possible release of this new product under the Artistic License, which is what Perl uses. Folks may argue whether Perl's license is Free Software, but I haven't seen it argued that it ain't Open Source.
They say in their "About" page that they actively support open source.
They link to the FSF on their "links" page.
All their upcoming projects (all of them) are based on Wine, which is under the X11 license.
They're not GPL, but they're Free Software and Open Source as anybody. At this point, more so than Red Hat, for instance.
Oh, yeah; they pay people to work on Wine. They even have a web page devoted to it [codeweavers.com].
What the hell else do you want from them? Source code for the stuff they haven't written yet?
-
Re:Not necessarily a good thing. (Score:2)
You're just trading one form of freedom for another. Net gain: Zero.
---
Native Linux Implementations Suck (Score:1)
Re:Dupe the Windows Media Player (Score:1)
Doesn't sound like much of a solution. Linux users (like their M$ bretheren) should have audio and video deployed automatically by the browser without first doing serious black magic at the terminal.
come off crisp and play up to the cynic
clean and schooled right down to the minute
Dupe the Windows Media Player (Score:2)
I hope your listening CodeWeavers.
come off crisp and play up to the cynic
clean and schooled right down to the minute
Re:Douglas Adams has died (Score:1)
(And I haven't quite decided if the original fake troll was very clever or very distasteful.)
Re:Not necessarily a good thing. (Score:2)
Isn't this already the case? Macromedia's Flash plugin (there's a free alternative, but last time I played with it it didn't seem to support anywhere near as much) and Real's Realmedia plugin are both widely used and closed. The moment Netscape supported closed-source plugins, we'd pretty much lost in that respect already.
What's more of a problem is that if companies can get away with just recommending their Windows plugin for Linux use, non-x86 users are left out in the cold.
I am using Internet Explorer 5.5 under Wine (Score:1)
Yes, that's right. With the latest CVS updates the painting is better too! It now doesn't white out the toolbars when you load a new page. The toolbars still start out white sometimes, but nothing a quick rollup and rolldown can't fix (which used to not be true either).
My IE 5.5 is installed on a copy of Win95 OSR2 with updates (including Y2K) under Win4Lin. Unfortunately, since Win4Lin doesn't work with kernel 2.4 yet I am unable to use it, but it makes a nice installed Windows tree with native DLLs for Wine to use. Currently I am running with native commctrl,shell, and ole.
There are still some issues with the user code in Wine. It's old. Recently Alexandre Juliard has submitted some changes to better seperate the Wine graphics driver out of the user code. I believe Alexandre is looking to do some major improvement to user. Well, at least I hope so, the current user code is very old and crufty and is the cause of lots of painting issues. Even solitaire doesn't exactly paint right at the moment (move a window around over top of it and you'll see what I mean).
Wine has come a long way and if you haven't had the opportunity to use it lately, I suggest that you try it again. IE seems to be working just fine for posting this.
Re:I am using Internet Explorer 5.5 under Wine (Score:1)
First of all, IE is not my main browser. For this comment I am using Mozilla. However it just so happened that I was testing out IE on a newly compiled CVS build so I figured I'd write the comment.
I would have to say that I am not very thrilled with VMware from my personal experiences. IE running under Wine runs faster than Mozilla. IE running under VMware runs slow as shit. IE under Win4Lin is a bit slower too (but not very noticably so). Using Wine as a Win4Lin/VMware type thing is not such a bad idea. Sure it is not quite as compatible at the system level, but at the application level most things are working. Like I said, one of the major drawbacks to Wine is the USER/GDI code. With working core libraries in place WINE would provide a better solution than Win4Lin or VMware. Especially if a company (CodeWeavers would be the first Wine related company to come to mind) did some more work and packaged Wine as a Windows applications runner. However, I don't think you'll see them doing that, it doesn't seem to fit in to their business model from what I gather. However, Jeremy White and friends did do a very good job of packaging the Codeweavers releases of Wine.
About the license thing. Most (possibly all) of the DLLs I used native versions of actually came with IE because it updates the system. So theoretically if you can get the installer to work then you shouldn't need Windows at all.
RS-485? (Score:2)
What did IBM have to do with it? I wasn't aware that they designed it. One of the big applications was for fault-tolerant communication in automotive systems (I used to be in that industry). I have never, ever heard of a desktop, or other non-specialised computer with EIA485, including those from IBM.
Why not take a look at all of those embedded boards out there? EIA-485 is a must on those things. I can get transceiver chips from National Semiconductor, Maxim, TI, etc.
IBM did make something called GA-22-6974-0 for the 360/370, but it's not quite multidrop like 485 is. Multiple drivers can share a single line, though.
Interesting 485 tidbit, the electric part of the SCSI standard was based on 485.
Wowee... (Score:1)
Re:Fud Watch (Score:2)
Only if you do so to such an extent that your code constitutes a derivative work. I don't know how many lines of code you can hold literally in your head, but unless your memory is much better than mine, in any program of significant length the small bit I could recall would almost certainly be fair use.
The GPL does not prevent fair use. All it does is prevent you from creating a derivative work from a GPLed work without GPLing your derivative.
What constitutes a derivative work that falls outside of fair use? That is something of an open question, not just in software but all fields.
Tom Swiss | the infamous tms | http://www.infamous.net/
Re:Quicktime for (embedded) Linux is inevitable. (Score:2)
By holding tightly onto that Sorenson codec, Jobs is going to turn it into the Token Ring of the Video codec world. IBM has held just as tightly to many, many things; MCA, RS485, Token Ring, etc. By holding technology with a closed fist people eventually leave for a more open technology.
Re:The same thing for drivers ? (Score:1)
The same thing for drivers ? (Score:5)
A major step would be to allow Linux to run Windows hardware drivers. Many people are still keeping a Windows partition because there's no Linux driver for their printer (or not photo-quality), no driver for their (win)modem, and sometimes there's no hope and no way to help because hardware specifications are (and will remain) closed.
The same thing could apply to other architectures as well. Almost every piece of hardware comes with MacOS drivers. Maybe it would be possible to code a glue in order to use them on Linux/PPC.
Yes, natives drivers will always be better. But this trick would be better than no hardware support at all.
If it is possible to code something able to run every Windows browser plug-ins, I guess the same technology can also server device drivers. So why not focus on this instead ?
Re:The same thing for drivers ? (Score:1)
Thats a terrible idea!
What you're suggesting would basically force us to run wine at the kernel level, which is not going to happen.
Browser drivers seems like a nice idea, but I believe it when I see it and it doesn't crash all the time, act strangely, or require massive tweaking (e.g. as wine currently does for most windows apps)
saving grace (Score:2)
At least michael you could have posted the link for Comet Cursors [cometsystems.com] since you've mentioned it in the header. For those who don't know what it is, its what they've dubbed a "smart cursor" which allows you to select something in an article, highlight it, and get information on what you'd selected and with or without a hyperlink get information on it, or purchase something (if its a product)
Now for the Wine part of it, I think it's a great idea, and I also think the company would probably want to work around some of the bugs we often (or at least I do) get when visiting pages with Shockwave Flash, and other embedded technologies on a page. As for the above post claiming a degradation of Linux, I'd highly doubt it would degrade the views of Linux for simple reasons. By having more companies developing for the *Nix based market, it goes to show that contrary to anyone's beliefs (or secret wishes) Linux/BSD's aren't going anywhere anytime soon.
However I also hope this isn't just another one of those here-today-gone-tomorrow based ideas coming out of a company trying to ride the coattails of the open source market, gaining fame, then moving on (Caldera).
Re:just to clarify (Score:1)
Dive Gear [divingdeals.com]
Quicktime for (embedded) Linux is inevitable. (Score:3)
I''m trying to work out whether that sentence is badly constucted, or you actually mean what it says - that Apple at some point in the past has released Quicktime for Linux. Methinks the former.
The second part of that questions is much more of a concern. Linux is currently either the number one or two embedded OS, and it seem to me that Apple will release Quicktime for embedded Linux the same way there's 100% functional (ie, with chapter navigation and other features we're still waiting on from the other three)DVD players for embedded Linux. Just as there is a Windows Media Server used on an embedded Linux device (somebody please post the URL). Embedded Linux is simply too great a market to ignore.
But if you have some sort of authority for that statement (i.e, a message from Apple), please respond.
Re:Not necessarily a good thing. (Score:2)
Uhm, Free Software is not a Brain Washing Cult. It's founded on carefully argued reasoning and first principles. You can agree or disagree, but nobody is locking you in. Unless of course you are so weak-minded that you can't think for yourself, and your only idea of freedom is having 70 channels on the tv to choose from instead of 5. Well my friend, you are either pitiful or a troll.
Re:Oh the irony of it all (Score:2)
"I may not have morals, but I have standards."
Re:Not necessarily a good thing. (Score:1)
=\=\=\=\=\=\=\=\=\=\=\=\=\=\=\=\=\=
Re:Better software is the key to winning!not "nati (Score:1)
OK, I would like Photoshop too, but I'm sure I could learn Gimp. I reckon KWord gives MS Word a good run for its money, and if OpenOffice (aka. Star Office 6) gets rid of that stupid, stupid desktop-within-an-application thing and lets me run the apps individually (why should I load the whole stupid suite to edit a text document??????) then there's no contest. So.... let's bug Macromedia everybody. I would love to design pages on the same platform that I'm going to serve them on. (And I would love it if a browser crashing didn't take out the whole 'desktop'...)
Re:Not necessarily a good thing. (Score:1)
Having to boot Windows to get decent web access does a heck of a lot more to keep Linux in a niche than running Windows plugins on Linux will do.
Furthermore, native plugins, if hell froze over and someone actually wrote them, only address the past. What about the future? By running Windows plugins, Linux gets compatibility with any new format quickly.
Re:The same thing for drivers ? (Score:1)
What they have all overlooked is that (1) while the details differ, the high level design of the low level I/O system is actually pretty much the same on Windows, Linux, and most other operating systems more advanced than DOS, and (2) the interface to the driver for a given class of device is usually designed around what the device does, and since the device does the same thing on all OSes, the interfaces end up very similar.
The difficulty is in the details. You have to thouroghly understand all of the following:
1. Exactly what Linux wants from a driver for the given class of hardware,
2. Exactly what Windows wants from a driver for the given class of hardware,
3. The Windows file formats for drivers.
4. The in-memory format of a Windows driver. E.g., how data is accessed, how relocation is done when the driver loads, etc.
So, it is a lot of work, but the actual code you'd end up with between the Linux and Windows code once the Windows driver is loaded would be a bunch of thunking code, that would not be too big and would not hurt performance noticably. The big task would be writing the loader, beacuse you'd have to figure out a lot of Windows stuff that is either not documented or poorly documented.
Is this really sensible? (Score:2)
Progress is good, but I'd still rather see a Linux version of $PLUGIN, instead of a compatiblity layer to run the Windows version.
Plugins aren't exactly the be-all-and-end-all of OS use, but it's just a thought.
necessary? (Score:1)
Re:The same thing for drivers ? (Score:1)
Re:Not necessarily a good thing. (Score:2)
Re:And what hardware? Performance? (Score:2)
As for performance, a program under windows makes calls to the win32 library (.dll) files and the instructions are executed natively by an x86 processor. Under Linux, a program makes calls to the win32 library (Wine) and the instructions are executed natively on an x86 processor. Where does the wrapper come into play?
Re:The same thing for drivers ? (Score:2)
It is impossible to do this for drivers. There are countless reasons for that, but I'll just try to reiterate a few of them:
I am not a kernel hacker, so perhaps my reasoning is not complete (or exact). However, it seems to me that it is virtually impossible to use efficiently (i.e. the way consumers want) the drivers which were written for other operating systems. Considering the above topics, the overhead should be enormous, and who'd like to have his, say GeForce 3 perform like a Cirrus 5424?
Embedded Device Market? (Score:2)
Re:Now, with Eazel leaving... (Score:1)
Better software is the key to winning!not "native" (Score:5)
upset when they get Wine ports, or apps that run under emulation.
The key to beating windows is NEW ORIGINAL apps for Linux that are better than anything you can
get for windows.
That is the key to winning, apps that make your windows using friends want to switch because they
can't get those apps for windows!
I'm talking about kapital, Koffice, nautilus, everybuddy(an app my mom loves), Quanta+,
Evolution etc..
These are the apps that make your Windows using friends and relatives take sit up and take notice,
not ports of Windows apps, native or emulated, because they can already get that stuff for
Windows.
Wine is a usefull tool, and if it is used to port usefull windows apps to Linux so what, it makes no difference to the end user if a windows app has been ported to Linux native libraries, or winelib, the real stuff is are the apps you can get for Linux, that you can't get for Windows!
Re:Better software is the key to winning!not "nati (Score:1)
OTOH, WINE is sorta slow... most ppl won't be bugged by that so long as it costs less... the efforts here are great by Codeweavers! (Besides, wouldn't WINE make Linux unique that you can use two OS'es binaries on one OS; assuming they work to begin with?)
Re:The same thing for drivers ? (Score:2)
This could never work. Windows 9x VxD's, NT SYS modules and MacOS extensions are all kernel modules. They load similarily to the Linux modules at boot time, but they are designed for their specific kernel and its driver model.
NT drivers need the HAL, MacOS drivers need the CFM (code fragment manager) as well as other kernel specific things. To get them to work under Linux you would probably have to change the entire driver model that Linux is using.
It is unfortunate, but it just could never happen. Device drivers are too low in the system structure, whereas browser plugins reside on top.
just to clarify (Score:5)
so there pretty cool..
on another note, i wonder if the google toolbar works
Re:Not necessarily a good thing. (Score:2)
It's too early to tell if this is a good thing or not. It may even be better if itis closed source...
Remember how the KDE/Gnome wars started over the fact that one was using components not compatible with the GPL? We got desktop competition, better desktop support, and now both are on a solid open-source footing (some may disagree, but I believe this is a goal of both parties). What started to look like a loss for Linux turned into a big win.
What does this new plug-in tool mean for Linux? It's another step to kicking the Win partition off my drive, or at least uninstalling MSIE. If many people use a tool like this, plug-in makers may find a significant portion of the audience using Linux, at least through an emulator.
If the plugin is good, then others may decide using propriatary components is a bad thing, and start making GPL'd clones. It would take a while, but if it's a large enough itch, it will get scratched.
Soon, the plug-in makers are seeing that a Linux native plug-in is beating their own plug-in, see their downloads and purchases decrease, and may decide it would be a good thing to make a native plug-in...
I could be wrong, but this is just one possible path to the big vendors making Linux-specific drivers and plug-ins.
Re:Not necessarily a good thing. (Score:1)
The trick is to allow developers to use the same tricks, and a few extra. If there was a way to have half wined/half native linux code (is there?), developers seeking to port things to linux will be happier.
Re:Not necessarily a good thing. (Score:1)
Re:Not necessarily a good thing. (Score:2)
Maybe in the short term. The basic problem is that as it stands right now, many manufacturers don't think that developing for Linux would be profitable anyway which is exactly why Linux is a nich market OS (Servers and Geeks, and my parents too but that is another story). Until Linux gains much greater market share, this dynamic will hold true in the desktop arena.
Note that OSS developers will be able by the very nature of the sheer number of programmers to overcome proprietary software in most areas. Somewhere between 90 and 95 percent of developers in the US work only on inhouse applications and OSS gives great benefits there.
In the end, I think it is proprietary software which will end up in a niche role.
Now, with Eazel leaving... (Score:1)
Now, if only I could get it to display
Re:just to clarify (Score:1)
UNRELATED: These CodeWeavers are pretty mesed up (Score:1)
Re:UNRELATED: These CodeWeavers are pretty mesed u (Score:1)
this, from http://www.codeweavers.com/about/news/?view=20001
mod parent up (Score:2)
Re:And what hardware? Performance? (Score:1)
And that's why this doesn't solve anything. We still need native *nix plugins. I don't want to stick to x86 crap forever.
> Where does the wrapper come into play?
Windows: app -> windows api -> whatever draws things in windows.
Linux: app -> wine emulation -> Xlib -> Xserver
See, wine's an extra layer of sluggishness. And wine is not to be considered light.
And what hardware? Performance? (Score:2)
And what about performance with all the wrapper-crap? "Geez this Linux is slow. This c00lplugin(tm) runs much faster on my slower windows box." (Heh, java and flash in IE in vmware on a ppro200 are faster than Sun's JDK and flash natively under Linux. That doesn't say they would be fast, which they are not, just faster.)
Codecs in the plugin (Score:2)
Re:necessary? (Score:1)
Re:Not necessarily a good thing. (Score:1)
The FSF would have you believe that the GPL supports development by requiring that any modifications must be accompanied by source code. This completely violates any "freedom to keep changes proprietary" that a developer may have had. In fact, when this type of violation of the GPL occurs, the FSF and its advocates are quick upon the scene to denounce such actions. As a developer, am I not free to keep my changes to myself?
The GPL does not support Freedom because it is an attempt to keep a watchful eye on users.
Lame
Dancin Santa
Re:Fud Watch (Score:1)
Your point about the BSD license being more free than the GPL is well-taken. I believe that the BSD license is as close as you can come to public domain without losing the original author's rights.
Dancin Santa
Re:Business Model? (Score:2)
The Windows CE API is no more "fat" than any other embedded OS, though it has the possibility to become so as necessary.
If you want to talk NT embedded, that's a whole 'nother story, though.
Dancin Santa
Re:Not necessarily a good thing. (Score:5)
Free software does not live in a bubble, at least not in the eyes of the public. In fact, what you think of as free today may not be what will eventually be considered free 5 years from now. Perhaps it the definition is faltering now? When you say that Real and Macromedia no longer have to worry about developing for anything other than Windows, aren't you also, in essence, saying that Linux (or any OS that Codeweavers supports) is a viable choice for an OS? It seems that freedom from a single vendor is much more important than any ideology that attempts to lock me into a single "Open" vendor, namely the FSF.
Maybe it isn't Open Source, but the Codeweaver product allows greater leeway in choice of OSs. If that isn't progress towards freedom, maybe your definition needs tweaking.
Dancin Santa
Re:The same thing for drivers ? (Score:1)
Plugins are quite different. Usually a company comes up with a format and a plugin to read that application. Unless Open/Free source comes up with better formats and better plugins, this is going to be the domain of closed source companies. Even if they do, its an uphill battle. Look at Ogg Vorbis vs. MP3/Real/WMA.
*) Of course this doesn't apply to relative newcomers to linux since the probably have windows-only hardware. But even those that are just interested in Linux or other alternative OS's would do well to check out what kind of support they are likely to get.
What's Next? (Score:4)
Re:Quicktime for (embedded) Linux is inevitable. (Score:1)
However, QuickTime is just a way of storing digital audio and video, the same as AVI. There is Quicktime 4 Linux [heroinewarrior.com], and it supports several codecs, including DV and MotionJPEG. So, if you can find a QT clip not encoded with SorensonVision, you can watch it just fine on Linux. Also, I would imagine that it's only a matter of time before someone manages to hack the Windows SV codec into a Linux player, just like you can use Windows codecs with avifile.
Re:Dupe the Windows Media Player (Score:1)
Re:Embedded Device Market? (Score:1)
Re:Not necessarily a good thing. (Score:1)
Don't even? How do you suggest these people should pay their bills?
Re:Not necessarily a good thing. (Score:3)
Please stop talking this nonsense. This is a PREREQUESITE for Linux domination, just look at the market leaders today:
MS Office is the leader because it provided input AND export filters to various other Office suites in the early times.
IE is the leader because it implemented Netscape's HTML-extensions.
In fact you suggest to behave like a monopolist. But without a monopoly this is a stupid thing to do, barriers only hurt the smaller competitors and help the leader, and Linux is not yet the leader on the desktop.
In 2 years Linux will be the only OS that will be able to run DOS, Win16 and Win9x, WinNT and WinXP applications - and this will be a Windows-killer.
The Wine project is the second most important open-source project out there (after KDE).
Roland
Re:mod parent up (Score:2)
Ofcourse they wont, the only thing that will make them port the plugins to linux is when it becomes popular amongst the common user.. which is like, 2-4 years off?
This will have no affect at all on Macromedia and Apple.
Oh the irony of it all (Score:2)
It's about time they got a taste of their own medicine
Waste of time (Score:1)
Why anybody would want to waste time on trying to mimic something that Microsoft is doing is just BEYOND me. Embrace and Adopt my ass, RM AND FORMAT. Only a bigger idiot tries to mimic an idiot.
Re:Not necessarily a good thing. (Score:1)
Not necessarily a good thing. (Score:5)
While it's it may seem like a win for Linux, this is definitely a loss for free software. This will encourage people to use proprietary browser plugins for windows, rather than developing native ones for Linux. This sort of thing will end up restricting Linux to a secondary, niche market, which is just where MS wants it.
I glanced around their homepage, and codeweavers [codeweavers.com] don't even seem to be open source, as far as I can tell. Their mission statement [codeweavers.com] is a perfect piece of corporate doublethink, which might be more plainly interpreted as: "To free Macromedia and Real Networks from the hassle of ever having to support anything except windows ever again."
Business Model? (Score:3)
But still a proper business model is yet to emerge for the open software. Linux is gaining ground in embedded system market, but is the company aware of the difficulties in finding market for windows applications in linux platform? Definitely the linux platform might have been chosen by a client for its own advantages over windows like thin OS, customizable code etc. By bringing a fat windows API into embedded linux market, is the company towing a right strategy?