Probably true, but I can confirm that this relationship does not go both ways :). Absolutely hated going from WO to Java EE back in the day. But I understand it's gotten better in recent years though.
Yeah, I've deployed a few WO apps in Java EE environments. How that works is WO will basically use a servlet (adaptor) for request handing, which will bridge calls and convert them from the Java EE APIs to the WO specific APIs. You don't actually interact with the Java EE APIs much (or at all).
I just meant that going from WO to Java EE didn't feel very nice :).
Absolutely. WO was a brilliantly designed framework (especially for the time) and being somewhat disillusioned with the state of web development in the last decade, I'm still using it as the UI layer for some of my own applications. It just can't be beat when it comes to throwing together a quick app, essentially being AppKit for the web. And as you say, it's influence was great, although I often wish it had a little more influence.
EOF was a great ORM framework as well and I never really understood ORM hate - until I had to use ORM frameworks other than EOF which generally feel … not that great. I ditched EOF a decade back though, due to it being, well, dead, and replaced it with Cayenne which is an excellent, actively developed ORM that feels very much inspired by EOF's design principles.
In the last few years, I've been working on a WO inspired framework (to the point of almost being a WO clone on the component/templating side) as a side project. It's still very raw when seen from the outside, no documentation and still operating under a bad codename - but hoping to make a release and port my remaining WO apps in the coming year. Hopefully it will add at least a bit to WO's influence on the web development world :).
Especially hilarious when you think of the rising popularity of HTMX.
WebObjects at the time revolutionary model of using the URL for state management would work really well with the new trend back towards server side rendered components.
Totally. I've been very happy to see the world embrace htmx in the last year and it's given me confidence knowing I'm doing the right thing with ng-objects.
The methodology htmx uses is in many ways identical to what we've been doing in the WO world for almost 20 years using Ajax.framework (which I don't know if you're familiar with), a WO plugin framework that most importantly adds "partial page updates". So you can wrap a part of a page/component in a container element, and target it so only that element gets rendered/replaced on the client side when an action is invoked (link clicked, form submitted etc.).
And yes, combined with WO's stateful server side rendering and URLs, it's ridicilously powerful. I usually design my WO apps so users never actually see a stateful URL, they always land on "static URLs" while stateful intra-page work happens through page replacements. I love it.
Seconded. I find it absolutely amazing that people try to paint the EU in a bad light for obliging web sites to let their users know they're being tracked. I'm grateful that I'm protected by institutions that work for the people, not for the corporations.
I wrote myself a little python script to do this a while back. I’m not sure that it will still work due to their API changes.
A longer while back I wrote a little JS bookmarklet to do it. It could just do a page at a time, which was annoying, but not too bad. However, when they would change the site, it would stop working and need to be fixed.
Remember to edit the comment before you delete it. From what I read, deleting a comment just sets a flag on the comment as delete, so it’s still in the DB for them to sell. Making it garbage text will kill the value of the comment in the DB as well, and probably really screw with the AI trying to train from it.
Pretty much it. We're at a "get people and services ready for a potential disaster" stage. And it's sort of mislabeled by the Guardian. We have three stages for events like this; "uncertainty", "alert" and "emergency". The state that's been declared is "alert" not "emergency".
Although sitting here and feeling my house rock back and forth, with the earthquake map looking like seen in the link below, I don't think it's too long until state of emergency.
Not sure IntelliJ has a crown here. I use Eclipse and it has some pretty amazing refactoring options. And I really prefer it to IntelliJ (for my use cases at least). Are there particular things IntelliJ can do that Eclipse can't?
I tried eclipse again last year and, while I cannot say it has bette for worse refactoring, I don’t understand how it could possibly be better given that its detection of available symbols seems to be little more than an RNG.
2008 was 15 years ago and many of the people I've spoken to formed their opinion of Eclipse (and IntelliJ) at that time. But what you saw back then and now isn't anywhere near being the same software.
Can you explain why Eclipse is worse than IntelliJ today?
I think I last used eclipse about 5 years ago, when I switched to VSCode. At the time, eclipse still felt like 2008 software, extremely sluggish and clunky. In particular, it really suffered taking advantage of multiple monitors.
What's changed since then? Has it gone through some kind of massive redesign?
Could you please explain? You say you don't know if it's better or worse for refactoring and then you say it's detection of symbols is like a random number generator? How so?
When I used eclipse, it is suggesting symbols from locations that are not even contextually available. Given how much refactoring often relies on accurate contextual symbol detection, there’s about a 0% chance that it does better than IntelliJ.
I didn’t even get to trying eclipse features because everything else in it is so remarkably stupid, useless, and actively battling me compared to IntelliJ.
I have been working on enterprise Java projects (basic consulting) which uses eclipse almost exclusively. We do not use Smurf naming convention (SmurfDto, SmurfDao, SmurfService, SmurfController) just for being able to find related classes. We do it because eclipse seems to randomly refactor classes based on non fully qualified names. No to naming something Constants as that will (randomly) refactor the codebase to break partially if you decide later to refactor something in that class.
I have tried everything from no vendor plugins for app servers to a vanilla eclipse and it still messes up.
I do like the product, but it can be very frustrating at times.
Kotlin. I switched to Intellij due to Kotlin, in is slow in Eclipse
But seriously, Eclipse was helping me more then Intellij does and has better defaults. It shows all errors and warnings at once etc. Even things Intellij actually has like call hierarchy tend to be sort of hidden by default.
"The next thing is also fairly straightforward: we expect Kotlin to drive the sales of IntelliJ IDEA. We’re working on a new language, but we do not plan to replace the entire ecosystem of libraries that have been built for the JVM. So you’re likely to keep using Spring and Hibernate, or other similar frameworks, in your projects built with Kotlin. And while the development tools for Kotlin itself are going to be free and open-source, the support for the enterprise development frameworks and tools will remain part of IntelliJ IDEA Ultimate, the commercial version of the IDE. And of course the framework support will be fully integrated with Kotlin."
