KDE Releases Plasmate 1.0, A Plasma Workspaces SDK
jrepin writes "The KDE Plasma Workspaces team is excited to announce the first stable release of Plasmate: an add-ons SDK that focuses on ease of use. Plasmate follows the UNIX philosophy of "do one thing, and do it well". As such, it is not a general purpose IDE but rather a tool specifically tailored to creating Plasma Workspace add-ons using non-compiled languages such as QML and Javascript. It guides each step in the process, simplifying and speeding up project creation, development, adding new assets, testing and publishing. The goal of Plasmate is to enable creating something new in seconds and publishing it immediately."
This specific bit of the "UNIX philosophy" is referring to the transformation of STDIO to facilitate piping. That is clearly not what this tool is designed to do: Plasmate clearly encompasses every part of a specific task, instead of being a general tool designed for reuse in any context to achieve any task.
I call it utter crap to describe a useful GUI as bloat.
A useful GUI will be a graphical front end (really!) to the actual tools a nerd or specialist would employ via command prompts. The non-specialist does have little knowledge of the proper names or spelling of tools he otherwise knows to exist, the GUI is the reminder, the pick list if you like, and a good GUI will lead him to a workable solution.
The useful GUI will also supply sufficient information for the non-specialist to make up his mind and lead to a correct order of operations.
"The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
I agree that a gui doesn't fit the description but a gui can be made up of components that do.
My point is that GUI stuff is different than command line stuff, if only because you don't paste multiple GUI apps together to accomplish more complex stuff.
Clearly he's never seen a tangible functional interface with direct manipulation before.
Ezekiel 23:20
Is "do one thing, and do it well" really still the Unix philosophy - for GUI stuff as well?
Well, it can be.
This works great for command-line stuff, where you incorporate commands into pipes and scripts.
There are many programs which consist of one or more command-line tools which perform the heavy lifting, and a GUI which calls them. That is an example of GUI programs which follow the Unix way. If this program works that way, then it follows the Unix way. If not, then not, because it could.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"