Knight Rider's theme is cool indeed... and it doesn't directly steal from kraftwerk, as Airwolf does ("trance europe express", anyone?).
Personally I also like Space 1999 theme, jumping from funky to orchestral.
Re:Rails, great for those fed up with J2EE.
on
Ajax On Rails
·
· Score: 3, Interesting
hmmmmm troll alert?
Ruby can't do complex things java can??? You meant rails, probably, and such confusion of terms is not a good sign.
Have you checked out the latest rails versions' API? I see transaction support and caching of db data and cgi actions too.
As for the 'inferior' object relational mapping: indeed Active record tries to keep things simple: I'm grateful for it. Rails developers got too far sometimes, as you see if you have a column named 'type' in your tables;) But, that's not being inferior, it's being different. If your app requires convolute mappings, either extend active record to suit your needs or do without it (possibly dropping rails altogether and wasting precious ram with a JVM;) ).
Yes, as the article points out. Ajax has also a problem in common with html frames, as it's difficult to associate content to an uri. The article covers this, too.
BTW I recommend giving rails a try, it's really a well thought out environment for your web apps. The site linked in my sig is a quick and dirty powerdns + lighttpd + rails experiment on a debian UML host (still on 2.4)
Full featured java is possible using IBM JDK (SDK and JRE) for power architecture. I dunno if they ship version 1.5 yet. Run it in xnest if it crashes your hardware accelerated X.
Wine is not possible as mac on linux is not possible on i386 linux, I'd say it's an architectural, not OS matter.
Let's wear our tinfoil hats: paper-based archives are being destroyed, so many little inventors' work may disappear, while special care will be taken to salvage big clients' patent portfolios.
More recent archives aren't a problem if big clients' older patents are generic enough.
And for those who actually take this seriously....
I do not. I mean, the best defence Microsoft has against the allegations is: "Oopsie, sorry, but we don't know how to properly design software in a modular way". You might consider it either comic or tragic (depending on what OS your IT infrastructure is based on, I guess), but it sure ain't serious...
Also, a sufficiently advanced alien civilization might have a tendency to explore the unknown AND not care one bit about our civilization.
Like us humans do not care much about a dog barking at the mailman, since explaining to a dog the purpose of a mailman's visit is beyond a dog's comprehension.
Getting to this specific case, the author of TFA asks the OSS/linux/whatever community to integrate itself into a M$ like monolith. This Is Never Going To Happen. First, it's an extremely complex task if there were the determination to integrate. Second, such determination does not exist. Third the resulting monolith would fall behind a centrally managed, Microsoft initiative.
So, while some points made in the article are insightful, the suggested course of action is suicidal. My 2 cents.
I'd use a NTFS partition for data exchange only, of course! The Linux system should reside on a filesystem that is better supported like the ones in topic. XFS is working well for me.
I'd love to be able to use a filesystem that can be seen in a dual-boot environment;
The "captive NTFS" driver that was easily installable in a kanotix environment seemed to work well enough, even for writing. I am not spending much time on intel linux so YMMV.
How often does the Debian community completely revamp a release because something could be done more intuitively, or easier, or perhaps possibly because it would just plain provide a better user experience. As I understand your comment, it's happening Now
QA is not a bug hunt, it is a complete picture of how the user and in this case, OS, will interact. I think they did a great job with the UI personally but failed in the security part of QA.
You are talking about SOFTWARE. QA is a broader subject than bug hunting, but bugs are the most important thing to get rid of, if you talk about quality, IMHO.
Cool, that would be the first rock stable thing seen on Windows.
Funny, I was sure that correct indentation was VITAL for punched cards...
Oh. You must be Guido. My congratulations on being the father of such a useful language as Python.
Considering what the car makers are doing, it wouldn't surprise me to see some wood panelling on computers soon.
Not just panels, all the shell. Not just a desktop box, a laptop.
It's the legnatile .
Indeed :D
Can you make an example where python would be more elegant than ruby?
The efficiency part I can understand, but having to declare self as first argument for every class method, for example, is far from elegant IMHO.
Knight Rider's theme is cool indeed... and it doesn't directly steal from kraftwerk, as Airwolf does ("trance europe express", anyone?). Personally I also like Space 1999 theme, jumping from funky to orchestral.
hmmmmm troll alert?
;) ;) ).
Ruby can't do complex things java can??? You meant rails, probably, and such confusion of terms is not a good sign.
Have you checked out the latest rails versions' API? I see transaction support and caching of db data and cgi actions too.
As for the 'inferior' object relational mapping: indeed Active record tries to keep things simple: I'm grateful for it. Rails developers got too far sometimes, as you see if you have a column named 'type' in your tables
But, that's not being inferior, it's being different. If your app requires convolute mappings, either extend active record to suit your needs or do without it (possibly dropping rails altogether and wasting precious ram with a JVM
Yes, as the article points out. Ajax has also a problem in common with html frames, as it's difficult to associate content to an uri. The article covers this, too.
BTW I recommend giving rails a try, it's really a well thought out environment for your web apps. The site linked in my sig is a quick and dirty powerdns + lighttpd + rails experiment on a debian UML host (still on 2.4)
You could have crunch-read TFA...
Sarge released, an Intel Macintosh, and now a low-ID Slashdot user with real life adventures.
Shall I place the order for Duke Nukem Forever?
I haven't had a digital camera die a natural death yet.
What's a natural death for a man-made artifact?
hehe, for camcorders I'd say natural death is "being accidentally dropped on a hard surface".
Full featured java is possible using IBM JDK (SDK and JRE) for power architecture. I dunno if they ship version 1.5 yet. Run it in xnest if it crashes your hardware accelerated X.
Wine is not possible as mac on linux is not possible on i386 linux, I'd say it's an architectural, not OS matter.
... but seeing an article about LFS in the index section feels like travelling back in time.
If only there were something like an article about Apple switching to Intel below, the effect would be complete...
To me that's just a sign they're willing to be pragmatic and use what works.
;)
They also have frequently spread FUD about "what works", so "pragmatic" isn't the first word that comes to my mind about them
One big question about the deployment of such mics: how will they interoperate with other WiFi networks?
If they will interfere or occupy the wrong frequency bands it's a big help to those who have all to fear from the technical achievements of WiFi.
Let's wear our tinfoil hats: paper-based archives are being destroyed, so many little inventors' work may disappear, while special care will be taken to salvage big clients' patent portfolios.
More recent archives aren't a problem if big clients' older patents are generic enough.
And for those who actually take this seriously....
I do not. I mean, the best defence Microsoft has against the allegations is: "Oopsie, sorry, but we don't know how to properly design software in a modular way".
You might consider it either comic or tragic (depending on what OS your IT infrastructure is based on, I guess), but it sure ain't serious...
Also, a sufficiently advanced alien civilization might have a tendency to explore the unknown AND not care one bit about our civilization.
Like us humans do not care much about a dog barking at the mailman, since explaining to a dog the purpose of a mailman's visit is beyond a dog's comprehension.
Any response from your public "servants?"
:D
Yep: 6 mail messages sent, one reply: a bounce, full mailbox in address belonging to istruzione.it.
If my requests were delivered on top of a 500 eur wad maybe they would get decent priority, surely no bounce
You're right.
Getting to this specific case, the author of TFA asks the OSS/linux/whatever community to integrate itself into a M$ like monolith. This Is Never Going To Happen. First, it's an extremely complex task if there were the determination to integrate. Second, such determination does not exist. Third the resulting monolith would fall behind a centrally managed, Microsoft initiative.
So, while some points made in the article are insightful, the suggested course of action is suicidal. My 2 cents.
I'd use a NTFS partition for data exchange only, of course! The Linux system should reside on a filesystem that is better supported like the ones in topic. XFS is working well for me.
I'd love to be able to use a filesystem that can be seen in a dual-boot environment;
The "captive NTFS" driver that was easily installable in a kanotix environment seemed to work well enough, even for writing. I am not spending much time on intel linux so YMMV.
Touche'.
Imagine a beowulf cluster of product activation procedures...
How often does the Debian community completely revamp a release because something could be done more intuitively, or easier, or perhaps possibly because it would just plain provide a better user experience.
As I understand your comment, it's happening Now
QA is not a bug hunt, it is a complete picture of how the user and in this case, OS, will interact. I think they did a great job with the UI personally but failed in the security part of QA.
You are talking about SOFTWARE. QA is a broader subject than bug hunting, but bugs are the most important thing to get rid of, if you talk about quality, IMHO.