Quotations tagged java
Filters: Type: quotation × java × Sorted by date
There is plenty of evidence in the ecosystem to support the hypothesis that, if given the tools to do so easily, object-oriented programmers are ready to embrace functional techniques (such as immutability) and work them into an object-oriented view of the world, and will write better, less error-prone code as a result. Simply put, we believe the best thing we can do for Java developers is to give them a gentle push towards a more functional style of programming.
— Brian Goetz # 19th August 2011, 12:20 pm
We all think of Java as a boring server-side language now, but the initial idea behind Java was that software developers could write applications in Java rather than writing them for Windows, and that those applications would work everywhere, thus defanging Microsoft’s desktop OS monopoly. Microsoft took various steps to prevent that from happening, but they lacked a tool like App Store that would enable them to just ban Java. Apple has that card to play, so they’re playing it.
— Rafe Colburn # 10th April 2010, 6:42 pm
Glitch is built in an entirely new and different way for a game. The back end (java at the lowest level, with game logic scripted in Javascript) is designed for maximum flexibility and ease of deployment. That means we’ll be able to push new content — new items, new places, new characters — on a daily basis. It also means that we’ll have lots of APIs with which the game can be expanded and extended.
— Glitch # 10th February 2010, 11:40 am
The compiler only pays attention to the semicolons and braces while ignoring the line breaks and indentation, but humans usually only pay attention to the line breaks and indentation while ignoring the semicolons and braces. This gives the code the opportunity to lie about what it’s really doing. Consequently we need to take extra care when writing in C, Java, C++, C# etc.
— Elliotte Rusty Harold # 2nd January 2009, 10:26 am
Once you reach a certain level of activity in the system where the garbage collector can no longer keep up (and it will happen), then every line of code in your system is now a potential failure point that can leave the whole program in a bad state. Lisp has this problem. Java has this problem. Erlang does not.
— Damien Katz # 14th April 2008, 3:17 pm
I can’t help feel that BDD is a case of a bad idea spreading; the motivations for BDD are fine (a change in developer testing workflow), but the technique they use to try to reach the desired workflow is totally bizarre.
— Ian Bicking # 27th November 2007, 7:16 pm
At one point I thought I hated programming because I was just so sick it... It turns out I don’t hate programming, I just hate programming in Java.
— Russell Beattie # 25th August 2007, 1:09 am
Erlang fits all the characteristics of an OO system, even though sequential Erlang is a functional language, not an OO language
— Ralph Johnson # 8th August 2007, 7:47 pm
I’d like to ask readers of this site which you’re more interested in, Sun’s JavaFX or signing up for TissueWorld 2008, the Premiere Exhibition and Conference for the International Tissue Industry.
— Stuart Langridge # 9th May 2007, 7:46 pm
Just because Java was once aimed at a set-top box OS that didn’t support multiple address spaces, and just because process creation in Windows used to be slow as a dog, doesn’t mean that multiple processes (with judicious use of IPC) aren’t a much better approach to writing apps for multi-CPU boxes than threads.
— Guido van Rossum # 8th May 2007, 9:21 pm
The promise [of J2EE] was that of infinite scalability based on tooling, which assumes that designing scalable systems is a general case problem. I now firmly believe that this is flawed reasoning. Frameworks don’t solve scalability problems, design solves scalability problems.
— Ryan Tomayko # 14th April 2007, 2:35 am
Two hosts are considered equivalent if both host names can be resolved into the same IP addresses [...] Note: The defined behavior for equals is known to be inconsistent with virtual hosting in HTTP.
— java.net.URL documentation # 31st January 2007, 9:13 pm