3 ms·
What a mountain of buzzwords! I miss Java Applets, which did many things better than the nonsense pushed today. Java integration with the DOM was actually very
by fgan 5y ago
What a mountain of buzzwords! I miss Java Applets, which did many things better than the nonsense pushed today.
Java integration with the DOM was actually very nice. Thread support in Java was (and is) light years ahead of Python.
When writing a Java Applet, you had the feeling that you understood the entire app. No one knows what is going on in these new frameworks, which may explain the increase in data leaks.
- zosima 5y agoExcept that Java Applets were an absolute security nightmares in and of themselves. They also looked very ugly and were extraordinarily slow, especially to startup. But the biggest difference between them and these frameworks are that writing Java Applets were aimed at real developers, while many of these frameworks are designed to be used by less technically experienced people, like data scientists or analysts learning to code. Therefore it's often easy to get started and create a simple dashboard, but the limits of the frameworks become evident after a while.
- dragonwriter 5y ago> But the biggest difference between them and these frameworks are that writing Java Applets were aimed at real developers I'd say the biggest difference is that applets are a client side piece of a solution, while these are server-side frameworks that generate the client (HTML/CSS/JS) and handle client-server interaction as well. It’s true that they tend to be data analysis focussed (because “dashboarding”), but that seems to manifest more in focus on integrating with data analysis libraries and tools (with which the target audience is already coding).
- oblvious-earth 5y agoOh yeah, I really loved debugging Java installations on clients PCs so our applets would work correctly.