The biggest difference would be that instead of millions of run-off-the-mill configured-the-same-way insecure-by-default multipurpose Windows boxes we would have millions specialized Linux appliances - media players, media servers, write-a-doc laptops, etc.
Linux is all about diversity and being able to throw away what you do not need and build what you want.
The end result will be much more secure.
Re:Why are workflow notifications always ignored
on
Linux on the Desktop
·
· Score: 1
I am working on one. Thanks for yet another accidental validation of the idea;-)
Mine will be peer-to-peer/web services/messaging based, on top of Arliweb framework.
I predict new OS will emerge in next couple years
on
Linux on the Desktop
·
· Score: 2, Insightful
There seem to be an almost critical mass of ideas, tools, code, etc. surrounding "the Linux desktop thing" right now. It feels like something is about to happen.
What if someone comes up with new OS where encryption and strong auth are built-in, X is thrown out or reworked to some kind of networked XUL thing, file system is more like Reisers namespaces, DRM is builtin as well (to satisfy future Palladium sharks),
all configuration files are XML, etc?
Seems like with consolidation of Intel hardware and availability of huge number of Linux device drivers to look at, this is not a remote possibility.
Would not that be nice?
I got Lifebook E7110 last December and could not be happier. Very well put together, magnesium-whatever body, 1/3 skinnier than Inspiron, runs Mandrake like a charm including built-in WiFi and wireless mouse.
Liquid nitrogen would be cool (literally;-)
Especially if the laptop has fuel cell in it.
The whole thing would look like a rocket launch with fumes, pipes and hoses going to the docking station,...
the problem is that the escape pod for seven people would be huge and would not leave much to the rest of the shuttle.
A capsule like one from Apollo or Soyuz would work, but it is only for 2 or 3 people and they MUST be skinny (80kg / 170 cm or something like that was the limit for Russians I believe).
That is part of the problem - Americans insist on chairs with cupholders;-)
ok here we go:
1. Just read somewhere that there will not be as much "managed" code in Longhorn
4. agree 100%
5 and 6. Just finished major project where c# clients were calling Axis servers, no problem
7. niche heh? just within last couple years I personally worked on: major pharmacy management system, shipping system for biggest shipper in the world (all Linux,Java,Oracle), major (terabytes) internal system for big and unpopular three-letter goverment agency.
9. True
12. do not know about Sun. But Oracle eats their own food with both Java and Linux
13. no more than MS lifted from Java. Natural evolution of languages.
14. J2ME worked fine for me
16,17 J2EE when used properly gives you all that and more: roles, messaging, transactions, threads,...
Unlike other people I wont comment on the things I know nothing about
.. is the fact that people try to make it yet
another language. There are tags for (gasp) database and LDAP access, for email retrieval,etc.
What is the point of fighting MVC wars on subject of separation of the View and then load this View with logic again?
The whole idea of a JSP is to grab an Object from the request object and output its contents. The only code allowed in JSPs should be the %= obj.method() little things and simple loops to loop over the collections.
The tried-and-true architecture (what they call level 2) is to submit all the pages to the same URL (controller JSP or servlet), have it figure out what to do next, do it, load the request object with the data to be displayed and use RequestDispatcher to forward the request to JSP for display. Struts, etc does that but you do not have to use Struts, simple home-grown thing will do too.
yeah but in order to call Java from PHP in a nice platform-independent way you will have to pass XML over the wire, probably over HTTP, probably inside SOAP envelope == Web Service
I dont think this is going to fly.
The current trend is to move as much as possible into the same JVM (JSPs, middle tier, db access) instead of further separating the tiers (as PHP -> Web service -> Java middle tier would require).
believe it or not, in the env I am in right now people were using JSPs but _still_ use out.println() inside Java scriptlets!
The whole "view in MVC" discussion is way above the level of average developer.
Correct, but _massive_ annoyances are terror too.
What if all of (big metro area) have to drink bottled water? And we run out of it pretty quick and people raid other people homes to get some?
I am surprised how fragile the infrastructure thing is.
For 300 mln. people country, 9/11 was not a big deal. Look how much economy was derailed. And all the infrastructure remained intact in that case.
If this is classified, there will be no insentive for the comm companies to fix the problem and reduce vulnerability.
People (and big companies) do not move until it hurts. Make it hurt and they will move. If average Joe the Shareholder reads in the newspaper that company X has all their infrastructure in one place and the cables are wide open, you better believe it company X will do something.
Otherwise, it is classified, public do not know about the problem, nobody does anything, but the potential evildoers will get this info anyway.
Please, no!
They are going to embrace and extend J2EE just like they did with desktop Java!
I don't want Supreme Court to tell me how to deploy my EJBs!
I did not thnk about it in this way...
Swing was not even available so the only option for desktop gui was AWT and it was awful.
Servlets had not appeared until 99 (that is 4th year of Java), JSPs even later. EJBs had not kicked in until 2001 (that is 6th year).
In Java, I have seen people declare local,specific Exceptions like hypothetical "DataLayerException".
In this case, the Exceptions thrown inside the layer are always caught and sometimes re-thrown as DataLayerExceptions. So your business layer wont have to be recompiled because it already knows what to do with this general DataLayerException.
Yep you got that right.
However the argument goes that "throw SomeException" is in fact part of the interface. You in fact declare that you _expect_ a program to blow up in a certain way. That makes Interface definiton stronger which is good.
So if your new implementation introduces new problems it is better if you are FORCED to change the Interface definition so the callers of that interface can adjust their behaviour as well.
If, as in C#, exceptions are not "strongly typed", every caller should be prepared to handle every exception.
Respectfully:
1. C# JIT to latest Java JIT - about the same speed. Now, in some cases (encryption for example), c# is 100 times faster than Java (native libraries maybe?)
2. Java garbage-collects automatically as well. gc() simply forces the garbage-collection to happen.
3. "Doing anything" requires you to leave "managed" code and go native. Even for simple things - like opening the "Open folder" dialog.
4. Exception handling is there for reason. Makes larger projects much cleaner.
Having said that I do believe that c# is very good language and I use it personally for the reasons you stated.
I agree about the superset.
By "dumbed-down" I meant that the language was intentionally made "simplier" by omitting or hiding things that might confuse your average waiter->support_person>VB programmer.
Example - exception handling, the fact that in C# methods are not required to handle or declare the fact that they "throw" exceptions.
don't forget C# - it is a dumbed-down Java but sure is nice to program.
The way C# handles XML (for example, serializing Objects to XML and "resurrecting" them later) is very good. This is not easy in Java (Castor is only thing that comes close).
Same for Web Services.
I did not do any ASPX but I have heard it is much nicer than JSP (even with Struts).
With C# being an international standard and Mono well on the way, I think.Net is a good thing and will be moderately successfull.
Interesting point.
I think I respectfully disagree - In my experience, I went through a lot of "domains": equipment leasing, retail/distribution, defense and space, cosmetics, insentives management, pharmacy, logistics, government - and all the time the software problems were orthogonal to the "domain" problems.
Authentication, access control, persistence, queries, schema - the things that an application consists of seem to be not related to the application domain. If you are good at putting them together, you will succeed regardless of your domain experience.
Slashdot Mirror
What channel is it on?
The biggest difference would be that instead of millions of run-off-the-mill configured-the-same-way insecure-by-default multipurpose Windows boxes we would have millions specialized Linux appliances - media players, media servers, write-a-doc laptops, etc.
Linux is all about diversity and being able to throw away what you do not need and build what you want.
The end result will be much more secure.
I am working on one. Thanks for yet another accidental validation of the idea ;-)
Mine will be peer-to-peer/web services/messaging based, on top of Arliweb framework.
There seem to be an almost critical mass of ideas, tools, code, etc. surrounding "the Linux desktop thing" right now. It feels like something is about to happen.
What if someone comes up with new OS where encryption and strong auth are built-in, X is thrown out or reworked to some kind of networked XUL thing, file system is more like Reisers namespaces, DRM is builtin as well (to satisfy future Palladium sharks), all configuration files are XML, etc?
Seems like with consolidation of Intel hardware and availability of huge number of Linux device drivers to look at, this is not a remote possibility.
Would not that be nice?
Nice cherry finish! That is what I vote for! And call it Dell Wooderon
For limited time only
As response to and anticipation of MAJOR terrorist act - bombings in Tushino(sp)
People know about it
Does not sound like a big deal to me. Kind of like setting up road blocks in the area where suspect is on the run.
I wish US was this open while violating our privacy.
I got Lifebook E7110 last December and could not be happier. Very well put together, magnesium-whatever body, 1/3 skinnier than Inspiron, runs Mandrake like a charm including built-in WiFi and wireless mouse.
Liquid nitrogen would be cool (literally ;-)
...
Especially if the laptop has fuel cell in it.
The whole thing would look like a rocket launch with fumes, pipes and hoses going to the docking station,
the problem is that the escape pod for seven people would be huge and would not leave much to the rest of the shuttle. ;-)
A capsule like one from Apollo or Soyuz would work, but it is only for 2 or 3 people and they MUST be skinny (80kg / 170 cm or something like that was the limit for Russians I believe).
That is part of the problem - Americans insist on chairs with cupholders
1. Just read somewhere that there will not be as much "managed" code in Longhorn
4. agree 100%
5 and 6. Just finished major project where c# clients were calling Axis servers, no problem
7. niche heh? just within last couple years I personally worked on: major pharmacy management system, shipping system for biggest shipper in the world (all Linux,Java,Oracle), major (terabytes) internal system for big and unpopular three-letter goverment agency.
9. True
12. do not know about Sun. But Oracle eats their own food with both Java and Linux
13. no more than MS lifted from Java. Natural evolution of languages.
14. J2ME worked fine for me
16,17 J2EE when used properly gives you all that and more: roles, messaging, transactions, threads,
Unlike other people I wont comment on the things I know nothing about
.. is the fact that people try to make it yet another language. There are tags for (gasp) database and LDAP access, for email retrieval,etc.
What is the point of fighting MVC wars on subject of separation of the View and then load this View with logic again?
The whole idea of a JSP is to grab an Object from the request object and output its contents. The only code allowed in JSPs should be the %= obj.method() little things and simple loops to loop over the collections.
The tried-and-true architecture (what they call level 2) is to submit all the pages to the same URL (controller JSP or servlet), have it figure out what to do next, do it, load the request object with the data to be displayed and use RequestDispatcher to forward the request to JSP for display. Struts, etc does that but you do not have to use Struts, simple home-grown thing will do too.
yeah but in order to call Java from PHP in a nice platform-independent way you will have to pass XML over the wire, probably over HTTP, probably inside SOAP envelope == Web Service
I dont think this is going to fly.
The current trend is to move as much as possible into the same JVM (JSPs, middle tier, db access) instead of further separating the tiers (as PHP -> Web service -> Java middle tier would require).
believe it or not, in the env I am in right now people were using JSPs but _still_ use out.println() inside Java scriptlets!
The whole "view in MVC" discussion is way above the level of average developer.
Correct, but _massive_ annoyances are terror too. What if all of (big metro area) have to drink bottled water? And we run out of it pretty quick and people raid other people homes to get some?
I am surprised how fragile the infrastructure thing is. For 300 mln. people country, 9/11 was not a big deal. Look how much economy was derailed. And all the infrastructure remained intact in that case.
If this is classified, there will be no insentive for the comm companies to fix the problem and reduce vulnerability.
People (and big companies) do not move until it hurts. Make it hurt and they will move. If average Joe the Shareholder reads in the newspaper that company X has all their infrastructure in one place and the cables are wide open, you better believe it company X will do something.
Otherwise, it is classified, public do not know about the problem, nobody does anything, but the potential evildoers will get this info anyway.
Please, no!
They are going to embrace and extend J2EE just like they did with desktop Java!
I don't want Supreme Court to tell me how to deploy my EJBs!
I did not thnk about it in this way...
Swing was not even available so the only option for desktop gui was AWT and it was awful.
Servlets had not appeared until 99 (that is 4th year of Java), JSPs even later. EJBs had not kicked in until 2001 (that is 6th year).
In Java, I have seen people declare local,specific Exceptions like hypothetical "DataLayerException". In this case, the Exceptions thrown inside the layer are always caught and sometimes re-thrown as DataLayerExceptions. So your business layer wont have to be recompiled because it already knows what to do with this general DataLayerException.
Yep you got that right.
However the argument goes that "throw SomeException" is in fact part of the interface. You in fact declare that you _expect_ a program to blow up in a certain way. That makes Interface definiton stronger which is good.
So if your new implementation introduces new problems it is better if you are FORCED to change the Interface definition so the callers of that interface can adjust their behaviour as well.
If, as in C#, exceptions are not "strongly typed", every caller should be prepared to handle every exception.
1. C# JIT to latest Java JIT - about the same speed. Now, in some cases (encryption for example), c# is 100 times faster than Java (native libraries maybe?)
2. Java garbage-collects automatically as well. gc() simply forces the garbage-collection to happen.
3. "Doing anything" requires you to leave "managed" code and go native. Even for simple things - like opening the "Open folder" dialog.
4. Exception handling is there for reason. Makes larger projects much cleaner.
Having said that I do believe that c# is very good language and I use it personally for the reasons you stated.
I agree about the superset.
By "dumbed-down" I meant that the language was intentionally made "simplier" by omitting or hiding things that might confuse your average waiter->support_person>VB programmer.
Example - exception handling, the fact that in C# methods are not required to handle or declare the fact that they "throw" exceptions.
don't forget C# - it is a dumbed-down Java but sure is nice to program. .Net is a good thing and will be moderately successfull.
The way C# handles XML (for example, serializing Objects to XML and "resurrecting" them later) is very good. This is not easy in Java (Castor is only thing that comes close).
Same for Web Services.
I did not do any ASPX but I have heard it is much nicer than JSP (even with Struts).
With C# being an international standard and Mono well on the way, I think
Interesting point.
I think I respectfully disagree - In my experience, I went through a lot of "domains": equipment leasing, retail/distribution, defense and space, cosmetics, insentives management, pharmacy, logistics, government - and all the time the software problems were orthogonal to the "domain" problems.
Authentication, access control, persistence, queries, schema - the things that an application consists of seem to be not related to the application domain. If you are good at putting them together, you will succeed regardless of your domain experience.
What kind of IMAP was that?
I was not able to make OE to store Sent messages on the server with either Courier or Cyrus IMAP.