Naomi Ceder wrote:That's an interesting question. I'd also admit that my book doesn't really focus on web development.
What I would say is that with all of the resources out there it can be tough to know what's quality. The Quick Python Book has been well reviewed from the beginning and in much the same form since the 2nd edition. So there's that testimony that it's a good resource.
The other thing is that it while it covers pretty much all of Python, it focuses on what you need to know as a developer, and has always gotten good reviews for that focus.
So I know there is a lot of stuff out there, but I think the Quick Python Book has sort of stood the test of time as being a quality resource that covers a lot of ground, while still keeping focus on what a developer needs. :-)
Jeanne Boyarsky wrote:Alternatively, you can take the upgrade exam. Exam 813 takes you from any old version of Java (other than Java 7) straight to OCP 8.
That costs only $250 since it is one exam.
Bear Bibeault wrote:
kavin savvy wrote:If they can come up with kotlin to JS framework and make kotlin as one language for web development will be great. At the moment, Angular & react are dominating on frontend space.
This seems to indicate that Angular and React are alternative languages such as Kotlin that one can choose to use on the web (or anywhere else). In fact, React and Angular are both JavaScript frameworks, not languages -- anymore than Spring is an alternative "language" to Java.
While both React and Angular can be used with ES5 (the current version of JavaScript widely supported by currently employed browsers), they are more often written in ES6 (React) and TypeScript (Angular) and transpiled to ES5.
I'm sure someone could come with a Kotlin transpiler in order to be able to use it on the web, but there would need to be big incentive for people to use it -- like some killer new framework. Just the availability of the language wouldn't be enough enticement. TypeScript would be unheard of without Angular pulling it along.
Tim Moores wrote:I don't think the open source nature of it makes any difference at this point. Client-side Java is dead in general, irrespective of the framework it runs. Security concerns of the JVM have finished it off. Some companies may continue to use it internally on carefully controlled and updated machines, but not for anything that's meant for the general coderanch.