Spiffy. It would be nice if you included screenshots:) / example exported webpages. My other request is, make the swing converter convert to JSP, so you could create a usable interface for apps / webpages and the same java backend:)
Of course they did. The pentium 4 has a horrible performance / watt ratio, and teh Steve clearly showed a very different picture when comparing the G5 to "Intel".
I said the exact same thing when I learned Python instead of Ruby. Then in the interest of completeness I decided to see if Ruby was any better. BOY AM I GLAD I DID. Everything I hated about Python, Ruby did 100 times better. Don't let the project count scare you away. There are probably 10 times more VB apps than Python apps. Does that make VB a better language?
I think you'd be better off with rails. The base library for ruby is much nicer (and much better documented) than pythons', and the rails community is already rather huge and growing. Another important factor is there are now a million python projects all trying to take a stab at what rails can do, none which realize that rails is capable of doing what it can because of ruby. This also has the added side effect of splitting apart the entire python web community into splinters. You'll have one hell of a time getting SkunkWeb up to par with the features of rails even today. Imagine how far behind it will be in a few years when the (likely) chance is that skunkweb will be one of the projects to fall-out after the python web framework bust.
Give it a shot sometime in an Apple store if you can. You can create a web browser with 0 lines of code using IB. It's by far the best MVC based designer I've ever used. And with the new Cocoa Bindings you can even populate portions of your interface with data without writing more than a couple lines of code.
No, that's just a theme engine that uses GTK's theme layout, and compositing techniques, to "squeeze" a gtk theme into Qt's themeing system. It's not coded using the GTK API. How do you not understand the difference?
I suppose that's why Apple offers a service like.Mac, where you can have a "server in the sky" backup solution, for fairly little to no work to maintain. However it's definitely a problem. Us geeks have it good at least, with my digial photos being in (literally) 4 places due to RAID and my server.
Over the course of 4.5 billion years or so (length of the age of the earth) it could evolve into nearly everything you see before you given the right environments. It's all about natural selection (the most beneficial survival traits) permutating over the course of a long, long, time.
Obviously having traits like a very large brain, opposable thumbs, walking upright, having two eyes and two ears to not only see and hear but locate and judge distances, and being omnivorous are beneficial for survival.
my point being that even if LISP is the purest language ever created, it is not necessarily the most productive across a wide selection of developers because the syntax may not provide the best mapping of a mental model of computation to the processor for this set of developers
python can't really be a dialec of lisp. it can only do one statement lambdas (that's pretty damn useless). ruby's a lot closer really. not just because it supports lambdas, but because the language uses TONS of functional concepts all over the place. block structured programming is highly prevalent in ruby and it's a concept that lisp people will scoff at because they've been doing it since the beginning of time.
in the grand scheme of things, syntax is a factor of usability. however what the language can do, is a factor of how well it implements lisp-like semanetics. functional programming is absurdly powerful. and it's a sad turn of events that OOP so glaringly outshines it. it's not to say both can't be used in tandum. just look at ruby. i would say ruby is the modern evolution of lisp. it has the C derived imperative syntax, functional programming concepts ingrained in the base syntax, and extremely powerful and dynamic OOP tools as first class citizens (something lisp really should have done sooner).
not really. the grand parent poster is pretty much right. LISP solved programming about 45 years ago. once you reach a certain level of features (recursion, lambdas, continuations, redefining functions) you've pretty much written a dialect of lisp. rather than reinvent the same fucking thing over and over, why not use the solution created so long ago? i LOVE ruby. it's my favorite language right now, but NOT because ruby solves anything that lisp doesn't already, but because ruby's actually popular enough to get noticed now a days. LISP it seems is long since forgotten, which is utterly sad because people will fail to realize that lisp was the solution so long ago and until people do they will be doomed to repeat the past over and over reinventing new programming languages.
Slashdot Mirror
Spiffy. It would be nice if you included screenshots :) / example exported webpages. My other request is, make the swing converter convert to JSP, so you could create a usable interface for apps / webpages and the same java backend :)
Of course they did. The pentium 4 has a horrible performance / watt ratio, and teh Steve clearly showed a very different picture when comparing the G5 to "Intel".
And mac users are more willing to pay for software compared to BSD/Linux users.
There's no way in hell you have Ph. D in CS. If you did, you sure as hell wouldn't have such a retarded website hosted on geocities.
Not entirely. You get the privledge of using Mac OS X, a clearly better opearting system.
I said the exact same thing when I learned Python instead of Ruby. Then in the interest of completeness I decided to see if Ruby was any better. BOY AM I GLAD I DID. Everything I hated about Python, Ruby did 100 times better. Don't let the project count scare you away. There are probably 10 times more VB apps than Python apps. Does that make VB a better language?
Here's all my ruby bookmarks: http://otierney.net/ruby_bookmarks.html
I think you'd be better off with rails. The base library for ruby is much nicer (and much better documented) than pythons', and the rails community is already rather huge and growing. Another important factor is there are now a million python projects all trying to take a stab at what rails can do, none which realize that rails is capable of doing what it can because of ruby. This also has the added side effect of splitting apart the entire python web community into splinters. You'll have one hell of a time getting SkunkWeb up to par with the features of rails even today. Imagine how far behind it will be in a few years when the (likely) chance is that skunkweb will be one of the projects to fall-out after the python web framework bust.
And what does XUL draw from? Xlib? No. GTK.
Give it a shot sometime in an Apple store if you can. You can create a web browser with 0 lines of code using IB. It's by far the best MVC based designer I've ever used. And with the new Cocoa Bindings you can even populate portions of your interface with data without writing more than a couple lines of code.
No, that's just a theme engine that uses GTK's theme layout, and compositing techniques, to "squeeze" a gtk theme into Qt's themeing system. It's not coded using the GTK API. How do you not understand the difference?
I dont know out the other projects are licensed, but ruby is licensed under the Ruby, BSD, and GPL license.
It means they are rendered with the GTK Toolkit. That makes them GTK apps.
Spoken like someone who's never actually used IB / Xcode (and possibly not even glade?)
I suppose that's why Apple offers a service like .Mac, where you can have a "server in the sky" backup solution, for fairly little to no work to maintain. However it's definitely a problem. Us geeks have it good at least, with my digial photos being in (literally) 4 places due to RAID and my server.
Will the Fruit Fucker have +5 Bonus Hit point damage?
Over the course of 4.5 billion years or so (length of the age of the earth) it could evolve into nearly everything you see before you given the right environments. It's all about natural selection (the most beneficial survival traits) permutating over the course of a long, long, time.
Obviously having traits like a very large brain, opposable thumbs, walking upright, having two eyes and two ears to not only see and hear but locate and judge distances, and being omnivorous are beneficial for survival.
Call them. They're very good with phone support.
Now dat be a baaaad idea. Sheeeiit. Why duzn't ya' give it some try?
Lord knows you wouldn't get a damn thing done without it! :)
Sorry, I just though that combination of words together warranted repetition.
i really hope you're not talking about those shiny, glare prone, xbrite screens? those things are awful.
precisely! usability
python can't really be a dialec of lisp. it can only do one statement lambdas (that's pretty damn useless). ruby's a lot closer really. not just because it supports lambdas, but because the language uses TONS of functional concepts all over the place. block structured programming is highly prevalent in ruby and it's a concept that lisp people will scoff at because they've been doing it since the beginning of time.
in the grand scheme of things, syntax is a factor of usability. however what the language can do, is a factor of how well it implements lisp-like semanetics. functional programming is absurdly powerful. and it's a sad turn of events that OOP so glaringly outshines it. it's not to say both can't be used in tandum. just look at ruby. i would say ruby is the modern evolution of lisp. it has the C derived imperative syntax, functional programming concepts ingrained in the base syntax, and extremely powerful and dynamic OOP tools as first class citizens (something lisp really should have done sooner).
not really. the grand parent poster is pretty much right. LISP solved programming about 45 years ago. once you reach a certain level of features (recursion, lambdas, continuations, redefining functions) you've pretty much written a dialect of lisp. rather than reinvent the same fucking thing over and over, why not use the solution created so long ago? i LOVE ruby. it's my favorite language right now, but NOT because ruby solves anything that lisp doesn't already, but because ruby's actually popular enough to get noticed now a days. LISP it seems is long since forgotten, which is utterly sad because people will fail to realize that lisp was the solution so long ago and until people do they will be doomed to repeat the past over and over reinventing new programming languages.