11 ms·
Javapocalypse
- jstsch 13y agoWith the domain java.no, this headline sounded like a plea to stop all Java development ;)
- afandian 13y agoMy first thought was "I bet this is another abuse of TLDs, what are the chances this is actually Norwegian". Pleasantly surprised.
- deadairspace 13y agoFrom wikipedia: [.no] domain registrations are limited to organizations with a presence in Norway and registration at the Brønnøysund Register Centre.
- dergachev 13y agoHey that was a lot less lame than expected!
- tommorris 13y agoThe JavaZone people do great trailers. Lady Java - https://www.youtube.com/watch?v=Mk3qkQROb_k https://www.youtube.com/watch?v=Mk3qkQROb_k The Streaming - http://jz11.java.no/trailer_video.html http://jz11.java.no/trailer_video.html Java 4-Ever - http://jz10.java.no/java-4-ever-trailer.html http://jz10.java.no/java-4-ever-trailer.html
- Espenhh 13y agoWe have collected all the previous videos at the "videos-tab" on the web page as well: http://jz13.java.no/videos.html http://jz13.java.no/videos.html There are some great talks from last year's conference there as well, many of them in English. The one by Tim Berglund about Git is great!
- casca 13y agoAlso, the headline piece: https://www.youtube.com/watch?v=E3418SeWZfQ# https://www.youtube.com/watch?v=E3418SeWZfQ#!
- BonoboBoner 13y agoAnd here I was thinking these airport towers run COBOL.
- makmanalp 13y agoYou could say Java is the new COBOL :) </tongue-in-cheek>
- victorf 13y agoADD ONE TO COBOL GIVING Java
- Roboprog 13y agoMore like, "ha ha, only serious" Object fields = Data Division; Bean = Copy Book Practices that actively discourage functional style programming in favor of procedural style programming with widely scoped variables. I'm glad Java is more widely used than C++, but it's a hard language to really love, despite being (mostly) how I earn my living.
- chii 13y agoHe is the Javatar! ROFL
- sleepyhead 13y ago"Patrol 403 investigating reports of open source activity"
- talloaktrees 13y agoThat was the best part.
- StavrosK 13y agoThis is irrelevant, but I just had my first Java experience yesterday. I decided to make an Android app, it's a simple remote control for hobby projects (Raspberry Pi/etc) that gives you a customizable UI with buttons that perform API calls. It'd be pretty simple to do in Python, which is the language I am proficient in, but Android development sounds fun so I wanted to get started in that. Creating the UI was easy enough, but making an HTTP response was hell. The simplest HTTP GET took around 30 lines of code, and the compiler kept complaining about unhandled exceptions (I know the URL is fine, it's a fixed string I can see, it's not going to throw MalformedURLException, I don't want to catch it, thank you. What? I can't compile without it?). Wrapping the calls up in try/catch blocks was easy enough (if a bit verbose), but now the variable only existed in that scope. I know I'm new enough that I can't form an opinion about the language, but I know that something that has as simple an interface as an HTTP GET call shouldn't take 30 lines of boilerplate to do. I'm wondering how people deal with this issue (I'm guessing it's a lack of a good standard library?). What attracts people to the Java world? Is it the tooling (Eclipse was, admittedly, very good about auto-fixing my mistakes). Is the verbosity just "the way it is", or am I doing something wrong?
- peroo 13y agoVerbosity is Java's middlename. That said, 3rd party libraries can get you a long way.
- StavrosK 13y agoIt looks like it, I just wish that the most frequently used libraries were standard in the language. That said, it's really magical for me to write something that runs natively on my phone, so it's still lots of fun.
- bru 13y ago>What attracts people to the Java world? Portability, security (automatic memory, static typing, etc.): you cannot bore a hole in your feet when shoving a nail. And backed by a huge company. Relatively fast. More reasons there: http://c2.com/cgi/wiki?WhyJavaIsGreat http://c2.com/cgi/wiki?WhyJavaIsGreat >exception-related problems A common hack it to wrap your code in a dumb try/catch block at the uppermost level. That way there is no scope-related problem and the compiler won't complain. Ofc that should only been done in a situation such as yours, not in "real life" (i.e. "entreprise world" for java).
- mordae 13y agoHmm, the video makes me wonder. What if the button software was written in Java and did, in fact, nothing. Perhaps with a nice 40-something line stack trace in the log file. Meanwhile, a completely new worm targeting the Java platform crashed most of the infrastructure.
- jph98 13y agoNearly £700 really? I spent £100 on Geecon last year.
- tommorris 13y ago"But, Mr President, if we destroy Java, what will parse the 5,000 line XML files we use...?"
- tzury 13y agoI haven't seen geek-related commercial made so well and funny for quite a long time.
- transfire 13y agoThe sad irony is that it is the termination of COBOL that could actually bring society to its knees. If Java died, it wouldn't take long for all that code to be rewritten in Go. But how many COBOL programmers do you know?
- DanHulton 13y agoOh, it's worse than that. I took three years of it in community college and could probably pick it up again in a hurry. If I did pick it up again, I could probably easily double my current (very reasonable) salary. But I'll be damned if I go back to writing COBOL, and I know a great many programmers like myself who feel the same way. And (modesty aside for a second here) they tend to be the better programmers. So you're left with the "for-the-paycheque" programmers writing COBOL, and the programmers who couldn't find a job they cared about more. That's who's going to be rewriting all those mission-critical COBOL apps once people want to start expanding into more modern languages.
- bilbo0s 13y ago"...If Java died, it wouldn't take long for all that code to be rewritten in Go..." Guy... You don't just rewrite code that's been through the FDA approval process. It doesn't work like that. If you want to replace a java or c based medical imaging viewer... you can... but you have to prove it won't kill anybody. Or make any doctors cut off the left leg instead of the right one because a transform is flipped due to a DICOM attribute being interpreted incorrectly. Or that RTP calculations are still correct, and the PET/CT fusion is registering correctly. You can't get Radiation dosage calculations wrong by even a tiny amount. And you have to prove all of that to the FDA and sign thousands of sheets of documentation swearing to it. And the standard fine print in that documentation makes you criminally liable if a bug is found. And that's just 1 tiny industry that java is used in. Multiply that difficulty by every life and death or money based industry and you begin to get an idea of what a monumental task getting rid of java would be. Think oil extraction and exploration systems... uh... no excuses there... they MUST work. Think industrial control systems... software for nuclear facilities, or even software for a simple coal based energy plant, can't just be thrown together. People in a city or area depend on these facilities to meet their energy needs. Maybe I'm misunderstanding you... what is your definition of "wouldn't take long"?
- Roboprog 13y agoYay Oracle! Save us from the 42 year lag to create an open source alternative. I know the video is a joke, but that was harsh. I think there are quite a few good open source languages that only took about 5 years or so to get going with a decent runtime library. What takes years is to get adoption of new tools from the grass roots up, more so than implementation.
- tharshan09 13y agoI may not like java that much - mostly due to bad experiences from uni. But WOW! that video was really great, very funny.
- sivanmz 13y agoJava is just not made for quick prototyping. In production, the URL will come from somewhere, not written by hand, so it would need to be checked anyway. Sadly there's no quick-prototyping mode in Java where you can say, just call this URL string an don't bother checking. Another example is the inability to just read a local file into a string with a simple API call. It's this way, again, because in production the program has to reason about paths and file systems and can't make assumptions about the validity (or size) of the file you just want to load and play with. In production code, no matter the language, you have to guard against these issues. The nice thing about objects (immutable, anyway), is that once constructed and validated, they do not require tedious validation at every method and client they are passed into. That actually results in less boilerplate, and less test writing. So just remember, Java always assumes your code is production-bound and requires upfront planning and checking. That's why it's unpleasant to prototype with.
- dromidas 13y agoWas I the only one that read this as "JAV Apocalypse"? I don't want the Japanese Adult Videos to go away :(