Silver Surfer
Veteran
That's going to change soon, Oracle is changing how Java works. No more Java 8 free updates in 2019 they going to that pay for play model.
yep heard that too recently.....Im waiting to see how that plays out
That's going to change soon, Oracle is changing how Java works. No more Java 8 free updates in 2019 they going to that pay for play model.
you think the market will abandon java in the future if they go this route?yep heard that too recently.....Im waiting to see how that plays out
I wouldn't say frameworks are trash. Not by a long shot. By all means, you must learn core Java as a foundation to even know what is going on behind the scenes of Spring. But once you do that, using frameworks cuts your development time dramatically. Why write boilerplate code/reinvent the wheel when you don't have to? Plus it's a necessity if you're doing any kind of enterprise development.
If I had to interview someone and he said something to the effect of "frameworks are trash" I would probably DQ him instantly.
you think the market will abandon java in the future if they go this route?
I meant as far as learning the core. For example I can show someone who never programmed how to create a restful application with a jpa connection in spring in under an a hour and they wont have to write anything but some getters and setters. If I were to teach code I wouldn't focus on a specific language but concepts cause languages come and go. Im porting code from python to c# now cause someome quit cause he didnt wanna use NET.
you need 30 mins to download dependencies in springbruh I can show rest call to a jdbc call in 10 minutes with core java
you need 30 mins to download dependencies in spring![]()
Might mention this to the lead developer during our meeting with stakeholdersIt also adds like 1gb of memory to a jvm
I was explaining to a director a few months ago why my team was not using spring...I said.."here is the proof...its not efficient for what we are doing...I dnt need all that overhead for something I can easily write with Java 8 libraries"
Might mention this to the lead developer during our meeting with stakeholders![]()
package com.training.example;
public class Vector2D
{
private float _x ;
private float _y ;
public Vector2D()
{
_x = 0.0f ;
_y = 0.0f ;
}
public Vector2D( Vector2D v )
{
this._x = v._x ;
this._y = v._y ;
}
public Vector2D( float x, float y )
{
_x = x ;
_y = y ;
}
public void setX( float x ) { _x = x ; }
public void setY( float y ) { _y = y ; }
public float getX() { return _x ; }
public float getY() { return _x ; }
}
package com.training.example ;
public class Example
{
public static void main( String[] args )
{
Vector2D v = new Vector2D( 9.0f, 10.4f ) ;
Vector2D c = v ;
c.setX( 110.0f ) ;
System.out.println( "X: " + v.getX() ) ;
}
}
I wouldn't say frameworks are trash. Not by a long shot. By all means, you must learn core Java as a foundation to even know what is going on behind the scenes of Spring. But once you do that, using frameworks cuts your development time dramatically. Why write boilerplate code/reinvent the wheel when you don't have to? Plus it's a necessity if you're doing any kind of enterprise development.
If I had to interview someone and he said something to the effect of "frameworks are trash" I would probably DQ him instantly.
yep heard that too recently.....Im waiting to see how that plays out
First off its NOT necessity...especially in backend development. My guys only code in core java for our back end micro-services....its helps the apprentices learn...and it makes debugging easier because you see exactly whats wrong.
With a framework...there are layers on top of layers that will do what the core language is doing.....thats a crutch....and there are benefits...but there are cons as well
If a guy told me spring is trash and he can do better with the core...that guy is an asset and means he has a better command of the language and if necessary he can learn the framework....if a guy only know a framework then I would at him sideways
The c.set method is changing the X value in the original object.Not particularly fond of the copy reference deal going on here...
Code:package com.training.example; public class Vector2D { private float _x ; private float _y ; public Vector2D() { _x = 0.0f ; _y = 0.0f ; } public Vector2D( Vector2D v ) { this._x = v._x ; this._y = v._y ; } public Vector2D( float x, float y ) { _x = x ; _y = y ; } public void setX( float x ) { _x = x ; } public void setY( float y ) { _y = y ; } public float getX() { return _x ; } public float getY() { return _x ; } }
Code:package com.training.example ; public class Example { public static void main( String[] args ) { Vector2D v = new Vector2D( 9.0f, 10.4f ) ; Vector2D c = v ; c.setX( 110.0f ) ; System.out.println( "X: " + v.getX() ) ; } }
How do I keep v's original value?
The c.set method is changing the X value in the original object.
Vector2D c = new Vector2D ( v)
// Instead of Vector2D c = v
Should create an entire new Object with its own instance variables