Salary for Sr. Java Engineer

[Coronita]

[quote=meadandale][quote=flu]
Actually, technically, android is not linux anymore (it’s a technicality…Let’s just say it’s linux-ish).[/quote]

well, considering we are hacking the android linux kernel for a custom application I’d have to disagree with you…[/quote]

You’re not alone in hacking the kernel you know, particularly we’re trying to put it in devices other than phones…. But starting in 2.6.33, Android drivers/etc technically isn’t being maintained along with the main line due to numerous deviations from the main line. It was dropped in Feb 2010… It was a minor technicality I was trying to refer to….Froyo is 2.6.32 based…I believe the plan is to support Gingerbread on 2.6.33 or 34, with Google as maintainer. There’s some tweaking that needs to be done to get some things written on the android derivative work, as google has now branched off from the mainline. There really isn’t much cooperation going on between google and folks developing the main line.

So there’s some fragmentation going on here. Also, it’s going to get interesting with google’s strategy of targeting gingerbread for high end stuff while maintain a lower end froyo. Separate issue.

And technically, Android isn’t Java either. It uses the Java language to compile into a bytecode for a dalvik vm, but not a jdk and clearly the byte code isn’t compatible. (In hindsight that was the smartest thing to have done with Oracle now owning sun and butching the entire java space)…

And lastly, if you really think about it, Android really isn’t “open source”…Because if it were, you would have access to Gingerbread source right now, without a need to have a privilege to get early access.

Anyway, x86 ports are pretty interesting these days too.

[an]

[quote=flu]Also, it’s going to get interesting with google’s strategy of targeting gingerbread for high end stuff while maintain a lower end froyo.[/quote]
That’s the rumor I keep hearing. Is that confirmed? Do you have more information about Gingerbread than the general public? It seems like it can be a total deviation, or it could be just additional features that’s available only on Gingerbread (since there will be higher bar for hardware requirements, and high res screen support). Since I’m not a Google insider, my logical guess would be they both using the same framework, but Gingerbread would add a slew of apps/features that won’t be available to Froyo phones. This makes sense since Google are starting to make all of their apps download-able (at least their updates are download-able at the moment).

[an]

[quote=flu]Also, it’s going to get interesting with google’s strategy of targeting gingerbread for high end stuff while maintain a lower end froyo.[/quote]
That’s the rumor I keep hearing. Is that confirmed? Do you have more information about Gingerbread than the general public? It seems like it can be a total deviation, or it could be just additional features that’s available only on Gingerbread (since there will be higher bar for hardware requirements, and high res screen support). Since I’m not a Google insider, my logical guess would be they both using the same framework, but Gingerbread would add a slew of apps/features that won’t be available to Froyo phones. This makes sense since Google are starting to make all of their apps download-able (at least their updates are download-able at the moment).

[an]

[quote=flu]Also, it’s going to get interesting with google’s strategy of targeting gingerbread for high end stuff while maintain a lower end froyo.[/quote]
That’s the rumor I keep hearing. Is that confirmed? Do you have more information about Gingerbread than the general public? It seems like it can be a total deviation, or it could be just additional features that’s available only on Gingerbread (since there will be higher bar for hardware requirements, and high res screen support). Since I’m not a Google insider, my logical guess would be they both using the same framework, but Gingerbread would add a slew of apps/features that won’t be available to Froyo phones. This makes sense since Google are starting to make all of their apps download-able (at least their updates are download-able at the moment).

[an]

[quote=flu]Also, it’s going to get interesting with google’s strategy of targeting gingerbread for high end stuff while maintain a lower end froyo.[/quote]
That’s the rumor I keep hearing. Is that confirmed? Do you have more information about Gingerbread than the general public? It seems like it can be a total deviation, or it could be just additional features that’s available only on Gingerbread (since there will be higher bar for hardware requirements, and high res screen support). Since I’m not a Google insider, my logical guess would be they both using the same framework, but Gingerbread would add a slew of apps/features that won’t be available to Froyo phones. This makes sense since Google are starting to make all of their apps download-able (at least their updates are download-able at the moment).

[an]

[quote=flu]Also, it’s going to get interesting with google’s strategy of targeting gingerbread for high end stuff while maintain a lower end froyo.[/quote]
That’s the rumor I keep hearing. Is that confirmed? Do you have more information about Gingerbread than the general public? It seems like it can be a total deviation, or it could be just additional features that’s available only on Gingerbread (since there will be higher bar for hardware requirements, and high res screen support). Since I’m not a Google insider, my logical guess would be they both using the same framework, but Gingerbread would add a slew of apps/features that won’t be available to Froyo phones. This makes sense since Google are starting to make all of their apps download-able (at least their updates are download-able at the moment).

[meadandale]

[quote=flu]
And technically, Android isn’t Java either. It uses the Java language to compile into a bytecode for a dalvik vm, but not a jdk and clearly the byte code isn’t compatible. (In hindsight that was the smartest thing to have done with Oracle now owning sun and butching the entire java space)…

[/quote]

You need to differentiate between android applications (java) and the android OS (linux). For the most part, android apps are java. Yes, there are some minor differences between the android (dalvik) VM and a standard VM but they are mostly minor–with the exception of the entire android API. This is entirely different from J2ME which was not at all compatible with a standard java VM.

For the most part, we’ve been able to take libraries (jars) that we have built to run on the server (e.g. communication protocols, data models) and drop them directly on the android (including their external dependencies) and they run fine. We’d never have been able to do this on J2ME.

I’ve written applications for both–it’s a whole different animal.

[meadandale]

[quote=flu]
And technically, Android isn’t Java either. It uses the Java language to compile into a bytecode for a dalvik vm, but not a jdk and clearly the byte code isn’t compatible. (In hindsight that was the smartest thing to have done with Oracle now owning sun and butching the entire java space)…

[/quote]

You need to differentiate between android applications (java) and the android OS (linux). For the most part, android apps are java. Yes, there are some minor differences between the android (dalvik) VM and a standard VM but they are mostly minor–with the exception of the entire android API. This is entirely different from J2ME which was not at all compatible with a standard java VM.

For the most part, we’ve been able to take libraries (jars) that we have built to run on the server (e.g. communication protocols, data models) and drop them directly on the android (including their external dependencies) and they run fine. We’d never have been able to do this on J2ME.

I’ve written applications for both–it’s a whole different animal.

[meadandale]

[quote=flu]
And technically, Android isn’t Java either. It uses the Java language to compile into a bytecode for a dalvik vm, but not a jdk and clearly the byte code isn’t compatible. (In hindsight that was the smartest thing to have done with Oracle now owning sun and butching the entire java space)…

[/quote]

You need to differentiate between android applications (java) and the android OS (linux). For the most part, android apps are java. Yes, there are some minor differences between the android (dalvik) VM and a standard VM but they are mostly minor–with the exception of the entire android API. This is entirely different from J2ME which was not at all compatible with a standard java VM.

For the most part, we’ve been able to take libraries (jars) that we have built to run on the server (e.g. communication protocols, data models) and drop them directly on the android (including their external dependencies) and they run fine. We’d never have been able to do this on J2ME.

I’ve written applications for both–it’s a whole different animal.

[meadandale]

[quote=flu]
And technically, Android isn’t Java either. It uses the Java language to compile into a bytecode for a dalvik vm, but not a jdk and clearly the byte code isn’t compatible. (In hindsight that was the smartest thing to have done with Oracle now owning sun and butching the entire java space)…

[/quote]

You need to differentiate between android applications (java) and the android OS (linux). For the most part, android apps are java. Yes, there are some minor differences between the android (dalvik) VM and a standard VM but they are mostly minor–with the exception of the entire android API. This is entirely different from J2ME which was not at all compatible with a standard java VM.

For the most part, we’ve been able to take libraries (jars) that we have built to run on the server (e.g. communication protocols, data models) and drop them directly on the android (including their external dependencies) and they run fine. We’d never have been able to do this on J2ME.

I’ve written applications for both–it’s a whole different animal.

[meadandale]

[quote=flu]
And technically, Android isn’t Java either. It uses the Java language to compile into a bytecode for a dalvik vm, but not a jdk and clearly the byte code isn’t compatible. (In hindsight that was the smartest thing to have done with Oracle now owning sun and butching the entire java space)…

[/quote]

You need to differentiate between android applications (java) and the android OS (linux). For the most part, android apps are java. Yes, there are some minor differences between the android (dalvik) VM and a standard VM but they are mostly minor–with the exception of the entire android API. This is entirely different from J2ME which was not at all compatible with a standard java VM.

For the most part, we’ve been able to take libraries (jars) that we have built to run on the server (e.g. communication protocols, data models) and drop them directly on the android (including their external dependencies) and they run fine. We’d never have been able to do this on J2ME.

I’ve written applications for both–it’s a whole different animal.

[UCGal]

[quote=UCGal] (I work on vxwords stuff, though).[/quote]

And apparently I can’t spell. LOL.

[UCGal]

[quote=UCGal] (I work on vxwords stuff, though).[/quote]

And apparently I can’t spell. LOL.

[UCGal]

[quote=UCGal] (I work on vxwords stuff, though).[/quote]

And apparently I can’t spell. LOL.

[UCGal]

[quote=UCGal] (I work on vxwords stuff, though).[/quote]

And apparently I can’t spell. LOL.

[Author]

Posts