|
I started Mono for Andriod then tried Eclipse and Java, then tried Android Studio (also a kind of Eclipse), but a I'm not too good with Java so I looked for something else and found Intel XDK - it's just for me!
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: so I looked for something else and found Intel XDK
*Added to my ToDo list*
Thank you.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: Android Studio (also a kind of Eclipse)
I was under impression Android Studio was based on IntellJ, not Eclipse. Frankly, I can't stand Eclipse...
|
|
|
|
|
You right - my wrong. It based on InteliJ from JetBrains... (but it's all Java after all)...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
I'll add my 5 cents to that:
Eclipse for Android is pretty much FUBAR. The Android Studio is much better and even in it's beta stadium it beats Eclipse for lengths.
I will never again mention that Dalek Dave was the poster of the One Millionth Lounge Post, nor that it was complete drivel.
The console is a black place [taken from Q&A]
How to ask a question
|
|
|
|
|
Facebook users whose accounts that may be compromised will be offered antivirus scanning and removal from the site, using F-Secure and Trend Micro security. This could be the single best use of Facebook evAR
Have the site that sends you malware clean it up. Brilliant!
|
|
|
|
|
User: Do I have any virus?
Facebook: You do now.
|
|
|
|
|
Visual Basic Tools for Visual Studio is a language service extension for Visual Studio 2012 and 2013 allowing to work on classic Visual Basic projects within Visual Studio. Insert square peg into round hole
|
|
|
|
|
Dear God when will VB6 die?!
Jeremy Falcon
|
|
|
|
|
|
Jeremy Falcon wrote: when will VB6 die?!
Lots of code out there to maintain.
I guess it just means you can use VS’s IDE features instead of the VB 6 IDE. But there was kind of a demand for this anyway. Most accepted VB 6 was dead but still wanted to be able to use a modern IDE.
Kevin
|
|
|
|
|
Kevin McFarlane wrote: I guess it just means you can use VS’s IDE features instead of the VB 6 IDE. But there was kind of a demand for this anyway. Most accepted VB 6 was dead but still wanted to be able to use a modern IDE.
I get the reasoning, but if they are still maintaining they can stick with older IDEs and tools where they belong. Seriously, still maintaining at this point is just being lazy.
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: Seriously, still maintaining at this point is just being lazy.
You could say that about all legacy code but the fact is you have to do what businesses want. I just finished a contract that had legacy VB in it, even though the main application was ASP.NET MVC and C#. I wasn't entirely sure what the VB was for - it didn't concern my tasks but presumably, for whatever reason, they've seen fit to retain it.
Kevin
|
|
|
|
|
Kevin McFarlane wrote: You could say that about all legacy code but the fact is you have to do what businesses want.
You're absolutely right. I didn't mean always lazy on part of the developer. There are plenty of lazy business types out there too.
Jeremy Falcon
|
|
|
|
|
Kevin McFarlane wrote: Lots of code out there to maintain.
It should not be maintained, but (already have been) migrated. If it ain't worth migrating, it ain't worth keeping alive.
Kill it.
KILL IT WITH FIRE 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Eddy Vluggen wrote: it ain't worth keeping alive.
Exactly. I wouldn't want to use a product that hasn't been updated in 10 years. It just shows that the company really doesn't care about it.
Jeremy Falcon
|
|
|
|
|
Eddy Vluggen wrote: It should not be maintained, but (already have been) migrated.
It's not up to me. It's up to the businesses.
Eddy Vluggen wrote: If it ain't worth migrating, it ain't worth keeping alive.
Kill it.
If it works, why rewrite it just for the sake of it? I know as devs we always want to use the latest shiny toys (me included). But the world ain't like that.
Kevin
|
|
|
|
|
Whereas continuing to use an unsupported product way past its expiry date, on new platforms that may no longer guarantee support for all components, or security updates related to them, carries no risk whatsoever?
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Kevin McFarlane wrote: If it works, why rewrite it just for the sake of it?
It's not a rewrite for the sake of it. If the manufacturer of the screws you use tells you he's discontinuing production of a screw you often use, you can either adapt or become outdated.
VB6, XP, great - ten years ago, with hardware that was current ten years ago. Still being on that platform means you did not anticipate IT to move forward and implies one chose the wrong business. Just as Betamax and the Amiga - history. Yes, some people are still using them, but don't expect a business that builds on them to survive for very long.
.."it works" is an argumentation that cost our government money (with XP support), since they also assumed that nothing would ever change.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Eddy Vluggen wrote: It's not a rewrite for the sake of it. If the manufacturer of the screws you use tells you he's discontinuing production of a screw you often use, you can either adapt or become outdated.
Say I have some code written in VB. It's working. It's not going to wear out like a screw.
Eddy Vluggen wrote: VB6, XP, great - ten years ago, with hardware that was current ten years ago. Still being on that platform means you did not anticipate IT to move forward and implies one chose the wrong business.
XP has 40% market share. That's a lot of businesses out there who chose the "wrong business."
Eddy Vluggen wrote: ."it works" is an argumentation that cost our government money (with XP support)
Sure, but it would also have cost them money to upgrade to Windows 7 or 8.
Most businesses do move forward eventually but there's always a cost-benefit analysis and it doesn't always correspond to the point at which vendors like Microsoft want us to upgrade.
Kevin
|
|
|
|
|
Kevin McFarlane wrote: Say I have some code written in VB. It's working. It's not going to wear out like a screw.
The machine it ran on will not be produced anymore. There's no security-updates, no support, nothing at all, and you claim "it's working"? The screw will wear, and will need replacement sooner or later. Software may not rot, but the hardware that the platform was built for does.
And yes, even DOS is still in use.
Kevin McFarlane wrote: XP has 40% market share. That's a lot of businesses out there who chose the "wrong business."
Wrong, XP has a far higher market share - lot of them pirated copies. And yes, quite a lot of idiots out there, including some top-governments.
(and that's mostly the same fools that state that "security" is a priority)
Kevin McFarlane wrote: Sure, but it would also have cost them money to upgrade to Windows 7 or 8.
Yes, it is cheaper to be betamaxed. Becoming outdated can be done for free. I keep cringing when people try to sell sh*t that they themselves don't consider worth upgrading.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Ph'nglui mglw'nafh Codethulu VB6 wgah'nagl fhtagn.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
I have no idea what that means, but I'm just gonna agree with it.
Jeremy Falcon
|
|
|
|
|
You need to spend more time reading the classics[^] (fortunately, Lovecraft is public domain), it means: "In his house at VB6 dead Codethulhu waits dreaming."
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
After reading the preceding comments, I thought I'd put my 2 cents in.
If an application is used in a closed environment (no internet access, firewalls in place, virus/malware check software current) and it serves a purpose, why rewrite it?
Sometimes, the limitation on upgrading the application is brought on by forces beyond the control of the developer. I worked in an environment that, until last year, was running applications on a Windows NT node. The reason? The DCS the application communicated with would not work with anything past Windows NT.
The cost to upgrade the DCS? Over $200,000.
The cost to maintain the existing system: considerably less.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
