Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror

Comment: Re:Linux has become like Windows (Score 1) 223

by vilanye (#49754681) Attached to: Linux 4.0 Has a File-System Corruption Problem, RAID Users Warned

Not even a decent troll.

Running opensuse 13.2 on desktop and server, no crashes and with KDE with all the bells and whistles it still comes in under 400 MB of RAM when the boot process is completed.

Sure the kernel sources are getting large, but it supports a ton of hardware on several processor architectures.

Talking about "the file system" and "the desktop" not only shows you are in fact a troll, but displays your total ignorance of Linux.

Comment: Re:New version ... (Score 1) 223

by vilanye (#49754601) Attached to: Linux 4.0 Has a File-System Corruption Problem, RAID Users Warned

"Stable" distros like Debian and redhat patch in a lot of bug fixes and other things into their kernel, so there is no real sense of where they are feature and bugfix-wise.

3.2 on Debian is not the same kernel as a distro that ran 3.2 when 3.2 was the current kernel.

Those "stable" distros crack me up, the kernel and almost all of its packages are significantly behind and they are no more stable than my opensuse 13.2 servers that have been upgraded in place since 11.3, but this is a rant for another topic.

Comment: Re:"Easy to read" is non-sense (Score 1) 408

by vilanye (#49747867) Attached to: The Reason For Java's Staying Power: It's Easy To Read

foo(bar); where bar is an int vs foo(bar); where bar is an object - pass by reference, and again no way to tell by the syntax.

Java is always pass-by-value. ALWAYS

What gets mistaken for pass-by-reference behaviour is really just a mutable object getting changed in a method call.

Primitive or object, Java is always pass by value.


swap(Type arg1, Type arg2) {
        Type temp = arg1;
        arg1 = arg2;
        arg2 = temp;
}

Type var1 = ...;
Type var2 = ...;
swap(var1,var2);

Those semantics fail in Java, because Java is always pass by value

In the same way, if i'm calling a Foo( Bar bar ), I do not expect for the function to change the state of my bar.
In Java, there is no way to be sure of this.

Sure there is, if an object passed is mutable, the state of the object might be changed. That's it. Check the method docs to see if it does change it. If the object is immutable, it obviously won't change.

It is not that complicated.

Some day, Java might even be acceptable. It finally got a real lambda, too bad Swing is dead or it would really benefit from not having all those inner-classes making a mockery of proper programming.

Comment: Re:There can be only one. (Score 1) 441

by vilanye (#49740313) Attached to: Choosing the Right IDE

To clarify, if your accessor and mutator methods do any sort of validation or transformations an IDE provides very little help and if not you are better off making them public or in a language where object variables are always private, use built in metaprogramming constructs like attr_accessor in Ruby and ditch the needless boilerplate.

But you are talking about Java, so there isn't much help for you and boilerplate is the order of the day, every day.

I have see so much nonsense in java like:

public void setMyVar(int myVar) {
this.myVar=myVar;
}

That is common, accepted and epically stupid.

Comment: Re:$30 per month (Score 1) 216

by vilanye (#49617397) Attached to: Netflix Is Betting On Exclusive Programming

I year or two ago I looked at one of their public reports

DVD's by mail brings in more revenue and has a higher profit margin than streaming. Like 800% more.

If you notice how little they charge for streaming and the size of all their content-rights contracts it isn't surprising.

That is why I was shocked that they tried to spin off their DVD service.

"I think trash is the most important manifestation of culture we have in my lifetime." - Johnny Legend

Working...