HN user
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 :).
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.
I'd like to move the cursor backwards and forwards in long commands easier, maybe even with the mouse (!).
You can. Just hold down the option key and click wherever you want in the command.
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.
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 :).
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.
Thanks for the pointer! And yes, there are, but I kind of enjoy going through the comment history while deleting. Memories :).
I've been working on deleting my reddit posts over the past year. The site now feels like it's almost 100% bots, which I find more than a little sad.
Agreed. And there's simply nothing that comes close to the power of the workspace when working on multiple projects that share dependencies.
How so? Use it daily, with hundreds of open projects and it just flies.
It was made by Connectix in 1994. The product line was acquired by Logitech in 1998.
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".
https://www.almannavarnir.is/english/general-information/eme...
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.
https://en.vedur.is/earthquakes-and-volcanism/earthquakes
Edit: And there we go. A stage of emergency was just declared for the town of Grindavík and it's being evacuated.
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?
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?
Intellij's refactoring crown
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?
Eclipse has seen vast development in the last few years and is fast and easy to use these days.
Objective-C was my first "real" language, started working with it with almost no knowledge of C to make some Mac Apps on Rhapsody and later Mac OS X. Nice documentation and an awesome first language, not least due to the lovely Foundation and AppKit frameworks and the nice UIs of ProjectBuilder and InterfaceBuilder at the time. It was pure fun writing software in that environment.
10 years is a long time and Eclipse then and now are two very, very different things. Eclipse is amazingly fast for what it does, I think.
Only started using IntelliJ about 3-4 years back (due to Android development) so I don't have any comparison from older days there.
Can't speak for the other platforms, but I work on an M1 Mac and using IntelliJ feels like trying to move while submerged in a barrel of syrup.
I switch between IntelliJ and Eclipse during my daily workflow and IntelliJ always feels like an absolute hog. And I do feel like it's been getting worse with the later releases.
I'm in my early forties but I still grew up with instructions and sets. Usually I'd assemble a set and probably learn a thing or two along the way, then I'd tear the sets down and build stuff myself.
As a father of three, that's exactly how I see my kids using the sets today. The sets get built once, then they get torn down and the bricks get reused.
Yes! I regret the time I spent without Rectangle. Effortlessly managing windows, just throwing them around or between monitors without ever touching the mouse is absolutely priceless.
I perceive him very differently (despite being a 100% Apple guy for the past 30 years - the stuff he criticizes Apple for is justified in my opinion). He's done a lot of good for the world with his activism and work on Right to Repair.
Random fact; this website is created and maintained by Sveinbjörn Þórðarson who also made Platypus (https://github.com/sveinbjornt/Platypus) and Sloth (https://github.com/sveinbjornt/Sloth) — software that Mac nerds might be familiar with.
Sveinbjörn is a ball of energy that just radiates positives for human society.
Even if this PR statement was correct, do we really need legislation to know leaking user data to third parties/CDNs is unethical and generally a bad idea?
It currently looks like Virtual Threads will be final in JDK 21, to be released in September this year.
I didn't understand the parent poster as advocating for "write it and you're done". To me "long term stability" and "things that will last over a year" simply mean it excels at creating maintainable software.
Sure, the mentality you mention has always existed, regardless of language or environment. But I believe that by it's verbose, static nature, Java's maintainability is a great tool to fight against it.
You can write unmaintained applications in any language or stack. An unmaintained system is not the language's fault, it's the maintainer's fault.
As a user that started my GUI life on an older Mac, hold-release menus always felt intuitive and "sticky menus" really felt weird when I first encountered them.
The logic behind that initial design was that menus were really just "buttons with options" and a mouseup should initiate an action. The menus had few items so there wasn't much dragging involved.
As software evolved, menus grew and spending an entire click on "present me with your selection of options" just became sensible.
Holy crap. Thank you for that pointer and my 92GBs of newly free space.