04-02-2018
Thoughts on Dystopian Future Likely?
Greetings Fellow NIX'ers,
For a while now I've been pondering the (to Me) Dystopian possibilities of "Cloud Computing", Web Apps
(Pay Per Each Use) of course, and... the Most Troubling of All:
The possible time when we will not be allowed to own a "Real" computer, only some silly little thing that can
barely run a web browser in order to "Consume" those Web Apps! I say "allowed", but also imply that Availability
of decent hardware may be threatened by the forces that are trying to make a "better future" for us all.
The same forces that are engineering this madness are of course behind Streaming Everything as well!
I am by no means against mobile devices, I have a smart phone myself that has been pretty cool.
What really does cause me concern as above is that the PTB might try to infringe upon our right to Own
Real Computers, Program them, and Distribute our own Free / Open Source software! Understandably many
typical non-NIX users may not Care about this stuff at all since they are used to being Told their future fate by
corporate entities and various interests.
In 1993 with some years as a developer, I discovered a reasonable facsimile of UNIX(tm) that I could use at home!
That is to say a distro I didn't have to completely create from scratch, Imagine that enormous stack of floppies!
Additionally, I've worked with SunOS, Digital UX, the BSD's and most Linux distros.
I have not looked back, ya gotta love the Freedom to breathe here!
Does any of this seem like a possibility to Anyone else, or... just my Imagination ?
That said, I'm primarily interested in the NIX' users, admins and devs thoughts here.
What sort of time line do you think we are looking at before the hardware vendors get the "Memo":
"Only Mobile devices without dev tools are Permissible!" I'd greatly appreciate hearing anyone's thoughts!
Before I forget I want to add what a Cool place this seems to be! There appear to be lots of "Adults" with
real stuff to say and share! That alone is something missing from "Most" other communities, IMHO!
Sincerely,
The Coding Coolie ;^)
Last edited by Coding Coolie; 04-03-2018 at 01:34 AM..
Reason: Cleaner formatting, etc.
This User Gave Thanks to Coding Coolie For This Post:
6 More Discussions You Might Find Interesting
1. AIX
I read that IBM came up with a new AIX version that would be fully integrated with Linux (I guess compared to older versions of AIX that could not) and I was hoping I bring this for discussion here so I learn more about IBM UNIX OS
Can anybody put few simple and practical comparisons between... (0 Replies)
Discussion started by: aliissa
0 Replies
2. Filesystems, Disks and Memory
I'm pretty new to UNIX and i'm planning to set up a server for my company.... i'm wondering if anyone could suggest a partitioning scheme for a standalone Solaris server with two 40GB disks and 1GB of memory... It would also be supporting 100 users...
thanks ! (1 Reply)
Discussion started by: martin11
1 Replies
3. SuSE
I wanted to get people's feedback on experiences with the KDE destop environment. I played with it for a while and was impressed.
I liked the non MS apps and non MS approach to mail. via K-mail
anyone else ? (8 Replies)
Discussion started by: simon2000
8 Replies
4. News, Links, Events and Announcements
For those of you you do not follow Slackware, one of the first Linux distros, going back to 1993, you may not know that Patrick Volkerding, the man behind it all, has been very ill:
http://www.slackware.com/~volkerdi/PAT-NEEDS-YOUR-HELP.txt
Please keep Pat in your thoughts and prayers.
Neo (1 Reply)
Discussion started by: Neo
1 Replies
5. Solaris
Good morning to one and all :-)
About to set up a M5000 server, then create a few zones to port over a few apps.
So, anyone had experience of zones ? and what things I need to consider / design / workout before hand ??
I need to work out whats going to be ported over, what the ip... (6 Replies)
Discussion started by: sbk1972
6 Replies
6. Web Development
Recently, have been learning Vue and, as always, learning-by-doing, which means writing code for real-world applications. In this process, I have learned something that is not really mentioned in the majority of online Vue tutorials.
Basically, when you create a Vue instance in your browser,... (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT DEBIAN
jifty::plugin::chart
Jifty::Plugin::Chart(3pm) User Contributed Perl Documentation Jifty::Plugin::Chart(3pm)
NAME
Jifty::Plugin::Chart - A charting API for Jifty
SYNOPSIS
In your config.yml:
Plugins:
- Chart: {}
In your Mason templates:
<% Jifty->web->chart(
type => 'Bar',
width => 400,
height => 300,
data => [
[ '2004', '2005', '2006', '2007' ], # labels
[ 14, 15, 17, 22 ], # first data set
[ 22, 25, 20, 21 ], # second data set
],
) %>
DESCRIPTION
CAUTION: This plugin is experimental. The API will change.
This plugin provides a charting API that can be used by Jifty applications to build data visualizations without regard to the underlying
rendering mechanism.
As of this writing, the API is a barely veiled interface over Chart. However, I intend to expand the interface to apply to something like
Maani's XML/SWF Charts or Imprise Javascript charts or even something like OpenLaszlo (or something Open Source and Perl if I can find or
build such a thing in time).
INTERFACE
By adding this method to the plugin configuration for your Jifty application, you will cause Jifty::Web to inherit a new method, "chart",
which is the cornerstone of this API.
This method is described in Jifty::Plugin::Chart::Web and an example is shown in the "SYNOPSIS" above.
CONFIGURATION
Here is an example configuration for config.yml:
Plugins:
- Chart:
DefaultRenderer: PlotKit
PreloadRenderers:
- XMLSWF
- SimpleBars
- App::Renderer::Custom
The available options are:
DefaultRenderer
This is the name of the class to use as the default renderer. Jifty::Plugin::Chart::Renderer::Chart is the current default, but that
could change in the future. It's recommended that you set this to your preference.
PreloadRenderers
This is a list of other render classes to load during initialization. If they are not loaded during initialization some renderers may
not work correctly the first time they are run because they are not able to inform Jifty of the CSS or JS files they need before that
part of the page is already rendered. If you use the "renderer" option of "chart" in Jifty::Plugin::Chart::Web, then you should make
sure any value you use is set here in the configuration to make sure it works properly.
METHODS
init
Adds the "chart" in Jifty::Plugin::Chart::Web method to Jifty::Web.
init_renderer
my $renderer = $chart_plugin->init_renderer($renderer_class)
This is a helper method that is used by the API to initialize the renderer class. This is handled automatically so you probably shouldn't
use this.
SEE ALSO
Jifty::Plugin, Jifty::Web, Jifty::Plugin::Chart::Renderer, Jifty::Plugin::Chart::Renderer::Chart, Jifty::Plugin::Chart::View
AUTHOR
Andrew Sterling Hanenkamp "<andrew.hanenkamp@boomer.com>"
COPYRIGHT AND LICENSE
Copyright 2007 Boomer Consulting, Inc.
This is free software and may be modified and redistributed under the same terms as Perl itself.
perl v5.12.4 2009-07-15 Jifty::Plugin::Chart(3pm)