Um, duh. Plasma 5 is by far the best looking desktop out there. And if you don't like the default, well, it comes with four other Plasma themes, two icon themes, three window decoration themes, and five app widget themes (two by KDE and three by Qt itself).
Should have remained in the oven for two more releases at the very least.
The story is about openSUSE Tumbleweed, a rolling release distribution for advanced users. Regular openSUSE still comes with Plasma 4. openSUSE 13.3 has not even been dated yet and will come with a future Plasma 5 version.
Apparently you use (K)Ubuntu: Their QA track record regarding anything by KDE is absolutely horrible and their reputation for jumping onto new features way too early. Read the "Suitability and Updates" paragraph of https://www.kde.org/announceme... KDE has been absolutely forthcoming. Plasma 4 is maintained until at least August 2015 for a reason.
ackagers didn't learn that it's not wise to push software undercooked like what happened with KDE4
Only a single (!) major distribution shipped Plasma 4.0 exclusively. That was Fedora. All others either shipped it next to KDE 3.5 (like openSUSE and Kubuntu) or waited until 4.2 (Debian, Mandriva,)
Audacity does not have true surround support. The individual tracks can be mapped to a channel when saving. It's not a smooth way to support that feature but it's way ahead of the competition (i.e. GoldWave etc.)
If you actually read TFA, in the introduction he says that with a good video editor, video shops could be all-Linux shops. The intro doesn't say "free free free", it's about something that can do the job on Linux.
Quote from TFA: "I often ask myself what the current state of video editing is for free and open source software (FOSS)."
Does this wording really mean "proprietary software under Linux"? To me it does not but maybe that's because I'm not a native English speaker.
Audacity 2.0 introduced multi-track editing, but your comment still stands. It's not suited for any realistic workflow or editing audio synced with video.
Have you ever tried simple wave editing in a surround sound file? Among the non-professional / low-end tools Audacity is apparently the only wave editor to support that at least to some degree (although the channel mapping window when saving is awkward).
Sadly though, Reaper (for Windows only) is the DAW you want to use, not Ardour (Linux) or even Pro Tools (Windows, sort of industry standard for small / amateur projects). You can trust me on that one (because I've used different tools in real projects) or or have a look at a few forum threads to see what others say. No affiliation. It's just better and it makes things easier.
And others say Reaper, the product of former Winamp developers, sucks and you should use Ableton Live instead. Others say Logic Pro.
I'm not a musician myself but I know a few and each has their own preference.
In your opinion, which is obviously heavily skewed towards FOSS.
I had to do some simple editing (changing speed and so on) in a 2h audio file a few months ago. GoldWave 5 was completely unusable â" it just crashed. GoldWave 6 beta worked but at super slow speed on a 64 bit Win 8.1 Core i7 system. After 15 Minutes of waiting for the FLAC file to save, I just gave up. (GoldWave was my first wave editing love, so if anything my opinion was skewed towards that.)
Audacity was (and still is) not pretty but unlike GoldWave it worked. I prefer working software over non-working software and as simple wave editor Audacity does the job.
So the expectation that an application doesn't randomly crash-to-desktop makes one "spoiled"?
Your attitude to claim that all FOSS developers just accept crashes makes you spoiled. Not every bug is reproducible everywhere. If a bug does not occur or the developer's system, it's not his fault.
I'd still rather use Cool Edit from 1998 than Audacity. I'm glad we have a free tool like Audacity, but I currently use Adobe Audition 1.0 (they bought Cool Edit way back) running in Wine, which is a much better solution IMO.
If you want something like Adobe Audition, you should get something like Adobe Audition and not try to use a simple wave editor as DAW substitute. Get Bitwig Studio: https://www.bitwig.com/en/bitw... I heard it's by former Ableton people, so they know their stuff.
Things won't improve until two things are addressed. First FOSS devs drop the attitude that "It crashes sometimes" is an acceptable condition for software intended for productive work.
Really? That's the attitude of FOSS developers? I call that BS. I think chances are spoiled users of proprietary software mistake being able to communicate directly with the developers with entitlement that a developer has to jump directly when a user discovers a bug. No, bugs are handled with different priorities and just because a bug annoys you the most, it is not necessarily the most crucial bug to fix first.
If you want bug priorities to change, just announce to give 100 bucks to whoever fixes a bug you run into. Bug bounty programs are quite common in FOSS.
Audacity is a simple wave editor, not a Digital Audio Workstation (DAW). Audacity's direct competition are GoldWave, Nero Wave Editor, and so on and Audacity blows them all out of the water in areas that are objectively measurable, i.e. file compatibility, encoding performance, etc.
But comparing Audacity to a DAW is unfair. They are just different things with just some overlapping feature set – kinda like comparing a pure text editor with a word processor.
LightWorks is not FOSS. It works on Linux but so do Maya, Bitwig, RenderMan, and so on. Neither of those is FOSS. There is professional software available for Linux in this market but just like OSX and Windows you have to pay for them.
Yahoo has "Powered by Bing" at the bottom of all their searches. It's not that hard to check.
So? The claim was that before the Bing switch, Yahoo used Google. That's false. Yahoo had their own search technology which they then licensed to Microsoft.
The only reason Bing has 12.5% of the market is because it is the default search engine for any MS-based product, including (especially) its cell phones. Most people switch to Google as quickly as possible, but some just keep the defaults.
I doubt Windows Phone has a market share big enough to make a dent. More likely Siri from iOS.
What's been removed,dumbed down,made incompatible?
You know this is a release of the Frameworks, right? Nothing has been dumbed down, kde3support is gone but other than that KF5 is mostly source-compatible with kdelibs4.
Slashdot Mirror
It's because too few developers are too spread over all that irrelevant stuff like konqueror and pim.
No Plasma developer is involved with Kontact/KMail and Konquror is not developed at all.
Guake
Try Yakuake.
Um, duh. Plasma 5 is by far the best looking desktop out there. And if you don't like the default, well, it comes with four other Plasma themes, two icon themes, three window decoration themes, and five app widget themes (two by KDE and three by Qt itself).
Apparently there is enough choice already.
there is no support for screensavers
Congratulations, you are among a tiny minority of 2%: https://forum.kde.org/viewtopi...
Should have remained in the oven for two more releases at the very least.
The story is about openSUSE Tumbleweed, a rolling release distribution for advanced users.
Regular openSUSE still comes with Plasma 4.
openSUSE 13.3 has not even been dated yet and will come with a future Plasma 5 version.
Apparently you use (K)Ubuntu: Their QA track record regarding anything by KDE is absolutely horrible and their reputation for jumping onto new features way too early. Read the "Suitability and Updates" paragraph of https://www.kde.org/announceme...
KDE has been absolutely forthcoming. Plasma 4 is maintained until at least August 2015 for a reason.
ackagers didn't learn that it's not wise to push software undercooked like what happened with KDE4
Only a single (!) major distribution shipped Plasma 4.0 exclusively. That was Fedora. All others either shipped it next to KDE 3.5 (like openSUSE and Kubuntu) or waited until 4.2 (Debian, Mandriva,)
Audacity does not have true surround support. The individual tracks can be mapped to a channel when saving. It's not a smooth way to support that feature but it's way ahead of the competition (i.e. GoldWave etc.)
If you actually read TFA, in the introduction he says that with a good video editor, video shops could be all-Linux shops. The intro doesn't say "free free free", it's about something that can do the job on Linux.
Quote from TFA: "I often ask myself what the current state of video editing is for free and open source software (FOSS)."
Does this wording really mean "proprietary software under Linux"? To me it does not but maybe that's because I'm not a native English speaker.
Audacity 2.0 introduced multi-track editing, but your comment still stands. It's not suited for any realistic workflow or editing audio synced with video.
Have you ever tried simple wave editing in a surround sound file?
Among the non-professional / low-end tools Audacity is apparently the only wave editor to support that at least to some degree (although the channel mapping window when saving is awkward).
In the end I used ffmpeg and SoX
Sadly though, Reaper (for Windows only) is the DAW you want to use, not Ardour (Linux) or even Pro Tools (Windows, sort of industry standard for small / amateur projects). You can trust me on that one (because I've used different tools in real projects) or or have a look at a few forum threads to see what others say. No affiliation. It's just better and it makes things easier.
And others say Reaper, the product of former Winamp developers, sucks and you should use Ableton Live instead. Others say Logic Pro.
I'm not a musician myself but I know a few and each has their own preference.
In your opinion, which is obviously heavily skewed towards FOSS.
I had to do some simple editing (changing speed and so on) in a 2h audio file a few months ago. GoldWave 5 was completely unusable â" it just crashed. GoldWave 6 beta worked but at super slow speed on a 64 bit Win 8.1 Core i7 system. After 15 Minutes of waiting for the FLAC file to save, I just gave up. (GoldWave was my first wave editing love, so if anything my opinion was skewed towards that.)
Audacity was (and still is) not pretty but unlike GoldWave it worked. I prefer working software over non-working software and as simple wave editor Audacity does the job.
What kind of horse shit is this? I can think of at least 3 examples off the top of my head that make this false.
First, please provide proof that FOSS developers in general do not care about stability, as you claimed in your first post.
and none of those are nlve's either, whats your fucking point
RTFA!
The article claims to list "6 free and open source video editing tools" and includes LightWorks in that list.
That's my point. And now GTFO.
So the expectation that an application doesn't randomly crash-to-desktop makes one "spoiled"?
Your attitude to claim that all FOSS developers just accept crashes makes you spoiled.
Not every bug is reproducible everywhere. If a bug does not occur or the developer's system, it's not his fault.
I'd still rather use Cool Edit from 1998 than Audacity. I'm glad we have a free tool like Audacity, but I currently use Adobe Audition 1.0 (they bought Cool Edit way back) running in Wine, which is a much better solution IMO.
If you want something like Adobe Audition, you should get something like Adobe Audition and not try to use a simple wave editor as DAW substitute. Get Bitwig Studio: https://www.bitwig.com/en/bitw...
I heard it's by former Ableton people, so they know their stuff.
Things won't improve until two things are addressed. First FOSS devs drop the attitude that "It crashes sometimes" is an acceptable condition for software intended for productive work.
Really? That's the attitude of FOSS developers? I call that BS.
I think chances are spoiled users of proprietary software mistake being able to communicate directly with the developers with entitlement that a developer has to jump directly when a user discovers a bug.
No, bugs are handled with different priorities and just because a bug annoys you the most, it is not necessarily the most crucial bug to fix first.
If you want bug priorities to change, just announce to give 100 bucks to whoever fixes a bug you run into.
Bug bounty programs are quite common in FOSS.
Audacity is a simple wave editor, not a Digital Audio Workstation (DAW).
Audacity's direct competition are GoldWave, Nero Wave Editor, and so on and Audacity blows them all out of the water in areas that are objectively measurable, i.e. file compatibility, encoding performance, etc.
But comparing Audacity to a DAW is unfair. They are just different things with just some overlapping feature set – kinda like comparing a pure text editor with a word processor.
LightWorks is not FOSS. It works on Linux but so do Maya, Bitwig, RenderMan, and so on. Neither of those is FOSS.
There is professional software available for Linux in this market but just like OSX and Windows you have to pay for them.
Yahoo search was powered by Google circa 2000.
It then changed to Inktomi a few years after.
Yahoo used Google in 2000 but bought them and Overture/Altavista in 2002.
Yahoo did not switch from a Google back-end to Bing's.
Yahoo has "Powered by Bing" at the bottom of all their searches. It's not that hard to check.
So? The claim was that before the Bing switch, Yahoo used Google. That's false. Yahoo had their own search technology which they then licensed to Microsoft.
The only reason Bing has 12.5% of the market is because it is the default search engine for any MS-based product, including (especially) its cell phones. Most people switch to Google as quickly as possible, but some just keep the defaults.
I doubt Windows Phone has a market share big enough to make a dent. More likely Siri from iOS.
Good for them but I highly doubt the phrase "Yahoo it" will catch on.
Why shoukd it? Search is not Yahoo's primary product. The web portal is.
No. There's really no benefit. Your personal browser fingerprint can identify you, so what does it matter?
Browser fingerbrinting relies on stuff like installed fonts, screen resolution, etc. – i.e. things not tweakable on many mobile platforms.
Used to.
No.
What's been removed,dumbed down,made incompatible?
You know this is a release of the Frameworks, right?
Nothing has been dumbed down, kde3support is gone but other than that KF5 is mostly source-compatible with kdelibs4.