You can't make a BASIC interpreter App and get it listed on the Apple store, for folks to download.
Shhhh! Don't tell these guys because they don't know that-- they went ahead and wrote a BASIC interpreter for iPad in 2010 and it's now up to version 3.5.
There are also Ruby and Python interpreters available too and Pythonista is also a fully featured development environment.
Sounds like someone needs to take a look at Pythonista - a full featured development environment, including code editor with syntax highlighting and code completion, interactive prompt, support for graphics and a touch interface, with full featured libraries including math and text processing; runs on iOS (iPhone and iPad) you can even export the app you've developed and have running on your iPad to Xcode so that you can build it for submission to Apple's App Store.
It's a staple on my iPad and has been for a year or so.
Sounds like a bit more useful than a graphing calculator.
A chef having to give away his recipe because he used GPL spices...worst analogy ever. Reverse it and it would be correct because a developer is not going to take a small amount of gpl code and use that, they are gonna add their small amount of code to a largely GPL base. (well atleast 99% of the developers out there).
In every instance I've been involved with in the past 20 years or so of professional programming, this statement is 100% wrong-- at least from the commercial angle. We've gernerally got an application that is filling a particular need and we're looking to add functionality to the already 100's of thousands to millions of lines of code we've already written. The first thing we do is look and see if anyone has already solved the problem, and if so if we can use it; if we find something and it's GPLed, we can't use it. Adding an extra 10,000 lines of GPL code written last year to our legacy system in use for the past 10 years and now suddenly our legacy app is a derivitave work of the GPL code is out of the question. Which means that we end up either looking for (or buying) an alternative if we can't work out a deal with the original copyright holders (which so far has been nigh on impossible-- we've gotten exactly one license from a GPL project that we needed to use). If that fails, we end up writing our own code, which now is by default non-free.
While I'm not disputing the quantity of GPLed software out there, I know that many of these projects are giving up help just because of the license. As an example, in one case we had determined that we'd need to allocate at least 3 people to implement a particular feature that a specific GPL project already had (mostly) working. I contacted the project "leader" and tried to negotiate a different license for the use of their project that involved a cash payment and allocation of a full time employee for a year to help bring it up to spec. We were unable to come to terms not because of any desire on their part not to, but because they used code that was also GPLed. No one was ever able to locate every one of the copyright holders to get permission and so it never went anywhere.
Don't take the above as a gripe-- whatever license you want to use is fine by me-- if I can use it I will, if not I won't, no skin off my nose either way; I'm sure I'll be able to get my job done with your product, your competitor's project, or I'll become your competitor if I need to.
I'm not sure I can agree here-- I spent $299 + tax on my Nokia 770 as opposed to about $1200 for the Q1; while the Q1 is running Windows and has a more powerful processor, it's also much bigger. I can carry my linux based 770 with me wherever I go very easily (fits in a shirt pocket) and have had no problem using it anywhere. For me at least, the extra $800 isn't worth it.
While both.NET and Java are free, the application servers they run on are not. For ASP.NET, IIS is the application server. For Java/J2EE, it could be Web Sphere or a variety of others. In pretty much every case a Windows license will be a lot cheaper than the license for the J2EE app server... especially Web Sphere.
It is possible that WebSphere, WebLogic, and the like may cost more than the.NET equiv (not sure as I've not priced MS lately), but that does not consider:
That are completely free of charge to both develop and deploy for production use.
Support is also available if you'd like-- both free via the web and for-pay for each of these.
Many of your points may be correct, but a price comparison is not necessarily one of them.
when does it (?) make more sense to use JBoss than Tomcat and OpenEJB?
This is generally a matter of preference-- using JBoss (or Jonas, or Geronimo, or WebShere...) gets you the advantage of a single application server providing access to servlets, EJB, MDB, JNDI, blah, blah, blah, blah. There is nothing preventing you from breaking this up into discrete components and using just what you need, where you need it: Tomcat, OpenEJB, ActiveMQ, whatever. While every project should be evaluated on its own merits, my preference tends to be that I'll run a servlet container plus a dedicated MQ if needed, but if I *need* EJB, I'll generally bring in a full application server.
The issue predominantly comes down to simplicity and support; using one (certified) vendor such as JBoss for everything gives you one place to look for answers on how to put things together, at the possible expense of using less than optimal components (I've never been a fan of any of the JBoss MQ implementations for example). Using serveral tools means you can pick the "best" tool for each job, at the expense of fewer people that have exactly your setup.
Bear in mind that, due to the way JBoss is architected, components can be swapped out or removed. If you only need Servlets and MDB, you can have only those two things, and even replace JBossMQ with something else if you like.
I'm not down on JBoss-- I've used it in several projects and will probably use it again in the future. It does come down to using the best tools for the job however, and often a full blown J2EE application server is overkill. I've had to pick up the pieces from development groups who went full-on J2EE (including EJB, MDB, clusterable, etc), for a system that would never be deployed on more than one server, for more than one department, and taking months to deliver an application that should have taken weeks.
I've used both (as well as many other servlet containers, j2ee containers).
If you just need servlets/jsp, I'd recommend using Tomcat by itself; JBoss adds the rest of the J2EE stack on top of Tomcat, so if you're not using that you're kind of wasting effort.
On the other hand, if you *need* the full stack, JBoss is not a bad container. I would recommend having a look a Tomcat + Spring + Hibernate as an alternative however, as most apps (aside from a couple of banking apps) I've seen really don't need the added complexity, and Spring makes a very good alternative.
If you do use JBoss, keep in mind that they have had a tendency to do things their own way, which may have a tendency to bite you if you're assuming compliance to spec. (as an example, google: jboss unified classloader )
actually, I believe that for the mac you'd pay tax if you lived in any state that had an Apple Store (at least I know when I order from them online, I have to pay it, and I live in Florida).
Our definitions of "weekend" must differ-- to me Saturday, Sunday (and maybe Friday or Monday) is the weekend. Since July 26th is a Tuesday, you must have a different work week than I.
Regardless-- I was there last Wednesday, I'll be there next Tuesday as well. I'm driving over from Tampa-- have my KSC Car Placard, Launch Day Visitor Center Tickets, and Bus Tickets to the KSC Lauch Viewing Area. Whoo-Hoo!
actually, as of about a month or so ago, all WDW adult tickets require biometrics;
when they replaced the old park hopper style tickets with the new "magic your way", the new ones required it;
recently they've required anyone using an old park hopper to do the biometric thing too; so now any adult entering on any (at least multi-day) ticket has to have their hand scanned.
rob.
Re:Is it just me, or why not explain it better?
on
Eclipse 3.1 Released
·
· Score: 2, Informative
well, actually...
Since you said that you'd never heard of Eclipse, I thought you might be interested to know that your tool of choice was migrating there. I would expect someone who (presumably) programs professionally and uses a given tool to know about that tool and the industry as a whole. For example: at JavaOne this week the following sessions are about or include information on Eclipse:
Smarter Rich Client Through Middleware Services
Building Your Own Eclipse Plug-Ins
Introduction to Eclipse's Rich Client Platform
Write Once, Plug Everywhere: Extending the Major Java IDEs -- NetBeans(TM), Eclipse, and JBuilder
What's New in Eclipse? A Java(TM) Technology IDE and a Whole Lot More
Runtime Aspects With JVM(TM) Support
Java(TM) EE Ease of Development: Platform Specification and Tools Perspective
Introduction to the Web Tools Platform Project
And, just for a point of order, the press release where Borland announced they were migrating to eclipse was dated May of 2005-- the JavaOne release from June was talking about Together integration with Eclipse.
rob.
Re:Is it just me, or why not explain it better?
on
Eclipse 3.1 Released
·
· Score: 1
well, since you're using JBuilder from Borland, why not just ask Borland-- a member of the Eclipse Foundation and who has already announced that the next version of JBuilder will be based on Eclipse?
Nope, do this and you violate your support agreement which allows RedHat to audit you and charge you for the difference (and possibly 20% more in penalties).
4. REPORTING AND AUDIT. If Customer wishes to increase the number of Installed System, then Customer will purchase from Red Hat additional Services for each additional Installed System. During the term of this Agreement and for one (1) year thereafter, Customer expressly grants to Red Hat the right to audit Customer's facilities and records from time to time in order to verify Customer's compliance with the terms and conditions of this Agreement. Any such audit shall only take place during Customer's normal business hours and upon no less than ten (10) days prior written notice from Red Hat. Red Hat shall conduct no more than one such audit in any twelve-month period except for the express purpose of assuring compliance by Customer where non-compliance has been established in a prior audit. Red Hat shall give Customer written notice of any non-compliance, and if a payment deficiency exists, then Customer shall have fifteen (15) days from the date of such notice to make payment to Red Hat for any payment deficiency. The amount of the payment deficiency will be determined by multiplying the number of underreported Installed Systems or Services by the annual fee for such item. If Customer is found to have underreported the number of Installed Systems or amount of Services by more than five percent (5%), Customer shall, in addition to the annual fee for such item, pay a penalty equal to twenty percent (20%) of the underreported fees.
If you're looking for an interesting time at WDW, forget the rides and what-not (well, maybe except for the new Mission Space at Epcot, currently in soft-open), and take in the one or more of the "back stage" tours. These are multi-hour guided tours inside the parks. Different tours do differeet things, one includes exploring the corridors "under" the Magic Kingdom, another is a botanical tour of the many gardens, another is on animation, and the list goes on.
Anyone can do the parks, and once you're there it's hard not to, but for something that few people ever do at Walt Disney World, it's hard to beat the tours.
1) The idea behind JWS is that we're talking about end-user apps; i.e. things the user would run from their desktop; This would generally mean that the user is logged in and the security context is that of the user, and not nobody.
2) While you can run apt-get immediately before each run of the app, when you start a JWS app (which can appear as an icon on your desktop) will check all by its lonesome (if there is a network connection). If it finds an update, it performs an update without user intervention.
This is really, really choice to deploy apps across an enterprise.
We've got the new touch screen voting systems here in Tampa and I had no problems exercising my right to vote.
The software was very easy, and the only "issues" I had with it were:
The voting machine itself felt a little flimsy; it was very easy to make the whole thing move as you voted;
You had to remember to pull out the smart card and find the right person to return it to. (there was only one such person at my polling place and she was kept busy trying to explain how things worked to the old folks.
Overall, the experience was easy and fast; Even the checkin went very smoothly.
The software is literally so simple (at least from a UI perspective) that I can't see that it would make a difference as to how the software was developed.
As an aside-- they were upfront that this was coming and even setup "test days" when you could go down and try out the new voting system. The people that have had problems probably should have availed themselves of these sessions.
rob.
Re:It's proof positive...
on
Linuxworld Fun
·
· Score: 1
What you're saying doesn't make much sense. This is a penny stock-- what do investment analysts have to do with anything?
Look- the last time I checked the stock was at about $1.20, up $0.38. The previous close was at $0.82, so if I had put up $5000, I could sell and make an easy $2,250 on the +45% move.
But... BUT... just because you see a large gain today doesn't mean you won't see an equally large retreat tomorrow. When you're dealing with stocks that trade so cheaply, almost ANY move is a big move percentage wise. Crap, if they'd went up a DIME that would have been a 12% gain! This is NOT big money.
There is a big difference between the "irrational exuberance of the dot com era" when VA opened at $300/share and a stock trading at $1.12 on good news.
Think about it for a moment-- this is a publicly held company. They just announced a means by which they are going to "boost revenue". Since it's much easier to make licensing revenue off of "expensive" software as opposed to "free" software, the investors see this as a net positive. Also, selling a license for their product does not preclude additional service revenue from your licensees.
Keep in mind that share price has nothing to do with how good their product is or whether they will be successful. It only reflects investor confidence in the the company.
Whether you or I see this as a good move is immaterial (unless either of us are VA stockholders, of course).
Slashdot Mirror
Shhhh! Don't tell these guys because they don't know that-- they went ahead and wrote a BASIC interpreter for iPad in 2010 and it's now up to version 3.5.
There are also Ruby and Python interpreters available too and Pythonista is also a fully featured development environment.
rob.
Sounds like someone needs to take a look at Pythonista - a full featured development environment, including code editor with syntax highlighting and code completion, interactive prompt, support for graphics and a touch interface, with full featured libraries including math and text processing; runs on iOS (iPhone and iPad) you can even export the app you've developed and have running on your iPad to Xcode so that you can build it for submission to Apple's App Store.
It's a staple on my iPad and has been for a year or so.
Sounds like a bit more useful than a graphing calculator.
rob.
Kind of like the current AutoTrain from Amtrak?
http://www.amtrak.com/servlet/ContentServer?pagename=Amtrak/am2Route/Vertical_Route_Page&c=am2Route&cid=1081256321200&ssid=136
In every instance I've been involved with in the past 20 years or so of professional programming, this statement is 100% wrong-- at least from the commercial angle. We've gernerally got an application that is filling a particular need and we're looking to add functionality to the already 100's of thousands to millions of lines of code we've already written. The first thing we do is look and see if anyone has already solved the problem, and if so if we can use it; if we find something and it's GPLed, we can't use it. Adding an extra 10,000 lines of GPL code written last year to our legacy system in use for the past 10 years and now suddenly our legacy app is a derivitave work of the GPL code is out of the question. Which means that we end up either looking for (or buying) an alternative if we can't work out a deal with the original copyright holders (which so far has been nigh on impossible-- we've gotten exactly one license from a GPL project that we needed to use). If that fails, we end up writing our own code, which now is by default non-free.
While I'm not disputing the quantity of GPLed software out there, I know that many of these projects are giving up help just because of the license. As an example, in one case we had determined that we'd need to allocate at least 3 people to implement a particular feature that a specific GPL project already had (mostly) working. I contacted the project "leader" and tried to negotiate a different license for the use of their project that involved a cash payment and allocation of a full time employee for a year to help bring it up to spec. We were unable to come to terms not because of any desire on their part not to, but because they used code that was also GPLed. No one was ever able to locate every one of the copyright holders to get permission and so it never went anywhere.
Don't take the above as a gripe-- whatever license you want to use is fine by me-- if I can use it I will, if not I won't, no skin off my nose either way; I'm sure I'll be able to get my job done with your product, your competitor's project, or I'll become your competitor if I need to.
rob.
I'm not sure I can agree here-- I spent $299 + tax on my Nokia 770 as opposed to about $1200 for the Q1; while the Q1 is running Windows and has a more powerful processor, it's also much bigger. I can carry my linux based 770 with me wherever I go very easily (fits in a shirt pocket) and have had no problem using it anywhere. For me at least, the extra $800 isn't worth it.
rob.
- JBoss
- Jonas
- Geronimo
- Tomcat (web tier only)
- Jetty (web tier only)
That are completely free of charge to both develop and deploy for production use. Support is also available if you'd like-- both free via the web and for-pay for each of these.Many of your points may be correct, but a price comparison is not necessarily one of them.
rob.
This is generally a matter of preference-- using JBoss (or Jonas, or Geronimo, or WebShere...) gets you the advantage of a single application server providing access to servlets, EJB, MDB, JNDI, blah, blah, blah, blah. There is nothing preventing you from breaking this up into discrete components and using just what you need, where you need it: Tomcat, OpenEJB, ActiveMQ, whatever. While every project should be evaluated on its own merits, my preference tends to be that I'll run a servlet container plus a dedicated MQ if needed, but if I *need* EJB, I'll generally bring in a full application server.
The issue predominantly comes down to simplicity and support; using one (certified) vendor such as JBoss for everything gives you one place to look for answers on how to put things together, at the possible expense of using less than optimal components (I've never been a fan of any of the JBoss MQ implementations for example). Using serveral tools means you can pick the "best" tool for each job, at the expense of fewer people that have exactly your setup.
Bear in mind that, due to the way JBoss is architected, components can be swapped out or removed. If you only need Servlets and MDB, you can have only those two things, and even replace JBossMQ with something else if you like.
I'm not down on JBoss-- I've used it in several projects and will probably use it again in the future. It does come down to using the best tools for the job however, and often a full blown J2EE application server is overkill. I've had to pick up the pieces from development groups who went full-on J2EE (including EJB, MDB, clusterable, etc), for a system that would never be deployed on more than one server, for more than one department, and taking months to deliver an application that should have taken weeks.
rob.
I've used both (as well as many other servlet containers, j2ee containers).
If you just need servlets/jsp, I'd recommend using Tomcat by itself; JBoss adds the rest of the J2EE stack on top of Tomcat, so if you're not using that you're kind of wasting effort.
On the other hand, if you *need* the full stack, JBoss is not a bad container. I would recommend having a look a Tomcat + Spring + Hibernate as an alternative however, as most apps (aside from a couple of banking apps) I've seen really don't need the added complexity, and Spring makes a very good alternative.
If you do use JBoss, keep in mind that they have had a tendency to do things their own way, which may have a tendency to bite you if you're assuming compliance to spec. (as an example, google: jboss unified classloader )
rob.
except that their product is "Red Hat Enterprise Linux"
actually, I believe that for the mac you'd pay tax if you lived in any state that had an Apple Store (at least I know when I order from them online, I have to pay it, and I live in Florida).
rob.
Cool, Didn't know they were releasing this; I watched the UK versions, and much preferred the theme. must buy.
Our definitions of "weekend" must differ-- to me Saturday, Sunday (and maybe Friday or Monday) is the weekend. Since July 26th is a Tuesday, you must have a different work week than I.
Regardless-- I was there last Wednesday, I'll be there next Tuesday as well. I'm driving over from Tampa-- have my KSC Car Placard, Launch Day Visitor Center Tickets, and Bus Tickets to the KSC Lauch Viewing Area. Whoo-Hoo!
Go Discovery!
What Universal is saying: --rob.
actually, as of about a month or so ago, all WDW adult tickets require biometrics;
when they replaced the old park hopper style tickets with the new "magic your way", the new ones required it;
recently they've required anyone using an old park hopper to do the biometric thing too; so now any adult entering on any (at least multi-day) ticket has to have their hand scanned.
rob.
well, actually...
Since you said that you'd never heard of Eclipse, I thought you might be interested to know that your tool of choice was migrating there. I would expect someone who (presumably) programs professionally and uses a given tool to know about that tool and the industry as a whole. For example: at JavaOne this week the following sessions are about or include information on Eclipse:
Smarter Rich Client Through Middleware Services
Building Your Own Eclipse Plug-Ins
Introduction to Eclipse's Rich Client Platform
Write Once, Plug Everywhere: Extending the Major Java IDEs -- NetBeans(TM), Eclipse, and JBuilder
What's New in Eclipse? A Java(TM) Technology IDE and a Whole Lot More
Runtime Aspects With JVM(TM) Support
Java(TM) EE Ease of Development: Platform Specification and Tools Perspective
Introduction to the Web Tools Platform Project
And, just for a point of order, the press release where Borland announced they were migrating to eclipse was dated May of 2005-- the JavaOne release from June was talking about Together integration with Eclipse.
rob.
well, since you're using JBuilder from Borland, why not just ask Borland-- a member of the Eclipse Foundation and who has already announced that the next version of JBuilder will be based on Eclipse?
see: Borland Announces JBuilder® Product Roadmap, New Eclipse-Based Collaborative Developer Environment
and Borland to Ring In New Era of Java(TM) Innovation at JavaOne
rob
done.
enjoy.
rob.
1-407-WDW-TOUR for info and to book.
WDW doesn't really advertise the tours, except to the guests staying on property, but anyone can go.
Google returned:
this and
this
The Backstage Magic tour is the "best" in that you go underneath it all, but the Christmas, architecture, trains, and garden tours are very good.
If you've got the bucks, design your own tour via the special activities department.
If you're looking for an interesting time at WDW, forget the rides and what-not (well, maybe except for the new Mission Space at Epcot, currently in soft-open), and take in the one or more of the "back stage" tours. These are multi-hour guided tours inside the parks. Different tours do differeet things, one includes exploring the corridors "under" the Magic Kingdom, another is a botanical tour of the many gardens, another is on animation, and the list goes on.
Anyone can do the parks, and once you're there it's hard not to, but for something that few people ever do at Walt Disney World, it's hard to beat the tours.
two points:
1) The idea behind JWS is that we're talking about end-user apps; i.e. things the user would run from their desktop; This would generally mean that the user is logged in and the security context is that of the user, and not nobody.
2) While you can run apt-get immediately before each run of the app, when you start a JWS app (which can appear as an icon on your desktop) will check all by its lonesome (if there is a network connection). If it finds an update, it performs an update without user intervention.
This is really, really choice to deploy apps across an enterprise.
The software was very easy, and the only "issues" I had with it were:
The voting machine itself felt a little flimsy; it was very easy to make the whole thing move as you voted;
You had to remember to pull out the smart card and find the right person to return it to. (there was only one such person at my polling place and she was kept busy trying to explain how things worked to the old folks.
Overall, the experience was easy and fast; Even the checkin went very smoothly.
The software is literally so simple (at least from a UI perspective) that I can't see that it would make a difference as to how the software was developed.
As an aside-- they were upfront that this was coming and even setup "test days" when you could go down and try out the new voting system. The people that have had problems probably should have availed themselves of these sessions.
rob.
What you're saying doesn't make much sense. This is a penny stock-- what do investment analysts have to do with anything?
Look- the last time I checked the stock was at about $1.20, up $0.38. The previous close was at $0.82, so if I had put up $5000, I could sell and make an easy $2,250 on the +45% move.
But... BUT... just because you see a large gain today doesn't mean you won't see an equally large retreat tomorrow. When you're dealing with stocks that trade so cheaply, almost ANY move is a big move percentage wise. Crap, if they'd went up a DIME that would have been a 12% gain! This is NOT big money.
There is a big difference between the "irrational exuberance of the dot com era" when VA opened at $300/share and a stock trading at $1.12 on good news.
rob.
Think about it for a moment-- this is a publicly held company. They just announced a means by which they are going to "boost revenue". Since it's much easier to make licensing revenue off of "expensive" software as opposed to "free" software, the investors see this as a net positive. Also, selling a license for their product does not preclude additional service revenue from your licensees.
Keep in mind that share price has nothing to do with how good their product is or whether they will be successful. It only reflects investor confidence in the the company.
Whether you or I see this as a good move is immaterial (unless either of us are VA stockholders, of course).
rob.
not with that typo it won't.
rob.