Applets are dead - on the server side Java is running as other languages backend services. At the moment many companies are using Spring Boot in the backend (in Docker / Kubernetes) - as so many other also is running as.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Oracle Warns macOS 14.4 Can Cause Java to Terminate Unexpectedly
- Thread starter MacRumors
- Start date
- Sort by reaction score
Thanks, I'm well aware of that. I work on OSS Java/Groovy/Kotlin-based framework code. Also using Docker, GraaVM, TestContainers Cloud and so on. Spring Boot isn't the only game anymore. Micronaut and Quarkus are making inroads into the space dominated by Spring, especially for cloud.
I know someone who worked at Apple. Their back end systems are mostly written in poop and sticky tape apparently. He left, uses Linux and LineageOS and has does nothing to do with technology where possible.
And all of the developers using software running on Java - so IntelliJ and Android Studio.
That's basically every single developer who isn't working at a Windows only shop.
Right, because 1995 is pretty much the same as 1959.
All of this ragging on COBOL, have any of you ever done any COBOL programming?
I doubt it. COBOL does have many serious limitations; its instruction set is very limiting, it is wordy and it is highly inefficient. BUT it is a breeze to program with and the resulting code is easy to read and understand.
I doubt it. COBOL does have many serious limitations; its instruction set is very limiting, it is wordy and it is highly inefficient. BUT it is a breeze to program with and the resulting code is easy to read and understand.
Um, err, some of us actually use vim you know...
There's a whole load of VSCode users as well.
I use IntelliJ IDEA for Java/Kotlin/Groovy but I have colleagues using VIM and/or VSCode.
I'm partially retired and will be fully retired by this time next year, so I'm going to stick with what I know.
There’s no “probably” about it! Just search Apple’s job board: 338 positions open for Java developers right now, across many different teams.
This would be terribly slow! Memory access is controlled directly by the CPU (well, the MMU). If any error happens, it's handed over to the kernel that does what he needs to do.
Indeed. It seems unlikely that this issue can be fixed (quickly) in the JVM without any unacceptable performance hits. The situation is rather extreme, Java and all other languages running on the JVM cannot be used on macOS anymore. I am literary staring at a MacBook M3 Max with 14.4 now.. 😰 downgrading is the only option to make it usable again but this process seems somewhat painful. Would be nice if Apple commented on the situation, but I guess that’s not likely.
I alway keep a Time Machine backup on a SSD for my development M1 MacBook Pro, just in case. Fortunately a colleague warned me before I even knew about the minor release.
I know, but browsers stopped supporting them a long time ago and that was their execution environment.
I've been a Java developer since 1996/7 and haven't worked on any Applet code in the last 20 years or so. I used to teach/maintain Java training courses and removed all the Applet material from the courses about that long ago too.
JetBrains IDEs
We’ve introduced a workaround to reduce the probability of IDE crashes after updating to macOS Sonoma 14.4.
IntelliJ IDEA 2023.3.6 Is Out! | The IntelliJ IDEA Blog
We’ve just released a bug-fix update for v2023.3. You can download the latest build from our website, via the Toolbox App, or by using snaps for Ubuntu. This latest version brings an important fixblog.jetbrains.com
Confirmed fixed (by Apple) in the macOS 14.4.1 update:
On macOS 14.4:
After installing 14.4.1 update:
On macOS 14.4:
Code:
% cat sigbus_test.c
#include <stdio.h>
#include <sys/mman.h>
#include <pthread.h>
int main() {
pthread_jit_write_protect_np(0);
char* mem = (char*)mmap(0, 16 * 1024, 0, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0);
fprintf(stderr, "addr = %p\n", mem);
char value = *mem;
fprintf(stderr, "value = %c\n", value);
return 0;
}
% cc sigbus_test.c -o test
% ./test
addr = 0x100e48000
zsh: killed ./testAfter installing 14.4.1 update:
Code:
% ./test
addr = 0x104460000
zsh: bus error ./test