1,278 karma · joined October 16, 2009
Second thought: so I'll be able to turn this off tomorrow right?
I do think, however, that this is a step in the right direction. In my opinion, GUI apps on Linux are for the most part extremely uninspired, and in spite of popular opinions to the contrary, I still prefer to use a native application in lieu of a web-based one. I think that webkit could be an awesome platform for desktop apps, both in ease of development and quality of finished product.
I don't think that this is quite a big enough step towards that though. For one, it makes the developer write html, css, and javascript. This means that ultimately the applications produced aren't going to really feel native on any platform. Rather, they'll feel like quick web app running in its own window. That's not necessarily a bad thing, but I think it could be better.
In my ideal world, this would be somewhat closer to a traditional widget toolkit, but built on top of webkit. It would still be html and js at its core, but from a developers perspective it would be closer to using something like SproutCore.
As I said though, I can't get it to run properly, so I may be way off base from just looking at the code for the sample applications. I think it may also be possible to get what I'm describing on top of Bowline. There's definitely some potential in this area though, and I'm going to mess with it some more and keep and eye on it.
The biggest reason that its' a good thing to learn a functional language is a lot like the reason that it's a good idea to learn more languages than just Java. In this case, all you have is one paradigm to think in (object-oriented (probably procedural as well, but...)). Functional programming is a completely different beast that requires different ways of thinking. Lots of the neater concepts of many popular languages now are lifted right out of functional ones. Python's list comprehensions and generators come to mind.
A more pragmatic reason to learn about functional programming is that it is becoming increasingly useful. Functional languages are, in general, much easier to parallelize. More importantly than that though, they make it easier to make _correct_ parallel and multi-threaded programs.
As for why these are often presented as the 'holy grail' of programming, many of features exist to make it simple to create concise, correct programs. The features are all the foreign-sounding buzzwords that people tend to rave about: composition, laziness, currying, lambda-functions, monads, strong type systems, type inference, higher-order functions, loop abstractions, and any number of other nifty things.
If you're interested in learning more, check out the Haskell or Ocaml languages (or Lisp, but Lisp isn't entirely functional).
Here's my revised method of picking:
* make a list of 5-10 languages that seem neat
* spend a few days on each one, learning the syntax and what it's useful for and what
libraries are available
* pick the one you like the bestOverall, it seems like the creator of it knew a little bit of math, and probably some physics, and extrapolated from there. More probable though is that their only knowledge of the subject came from philosophy, or epistemology.
while [ true ]; do
curl www.google.com
doneWhat I think is more interesting though is the idea of distributing it for free on channels that are usually limited to less legal endeavors, and later patching in a monetization scheme.
My dad is a contractor, and my mom is an interior designer. Family members, people from church, and random people alike assume that means that they can come fix whatever little problem they're having, or pick out drapes and furniture for their living room.
One issue I had with the article though, is the overuse of hyperbole. There is no indication of how much of it was fact, and how much was embellishments and exaggerations.
Overall, I agree with you though, there really are no safeguards to stop administrators from abusing their power. They only thing that I can think of to help curtail this sort of abuse is restricting the use of their remote control software to the networks explicitly provided by the school.
The school I go to now has a similar program (Macbooks for every student), and the Remote Desktop program is used on our laptops as well. It used to be a serious point of contention between the administration and the students. A large number of students actually covered up the webcams on their computer with tape or similar to stop people from watching them.
In theory, the requirements for monitoring were that every once in a while, everyone's computer would have its desktop monitored without their knowledge. If they were doing anything that they weren't supposed to (e.g. on Facebook (via proxies), or looking at porn) Photo Booth, the webcam application, would be opened and a screenshot would be taken, capturing both the offending behavior and the offender.
I know that on a computer provided by the school, any preconception of privacy should be abandoned, but it still seems like a bit much. It seems to me that simply logging activity and then punishing the student after it had been reviewed would be easier and more transparent.
No echoing audio effects unfortunately.
That and it took far too long to some up with a password passing the description...
To enumerate, the password had to:
- have exactly 8 characters
- contain characters from 3 of the following 4 groups
-- lowercase letters
-- uppercase letters
-- numbers
-- ? . , _ - + = $ ! –
There were also some things that the password could not do:
- be a dictionary word
- contain any series of characters in your username
All of this was enforced.