The fact that people that have used Java do not realize that EJB3 is pretty good, when it's pretty old!
The fact that people that have used Java do not realize that EJB3 is pretty good, when it's pretty old! I switched to EJB3 in 2006, and I really couldn't see why people would choose Spring anything instead. The switch to Soap, and then to Rest, was changing a couple of annotations. Not bad for a 9 year old framework. Now, my biggest problem with the stack, and the reason I do not use it anymore, is Java itself. A switch to Scala makes a lot of the Java boilerplate go away, and even Java 8 doesn't get close. Now, I find all the major Scala web libraries to be lacking, in one form or another. Play's second compilation feels clumsy. Spray's freedom of routing leads to very ugly code: Just look at their own large examples. So what I am currently doing is using a homebrew routing on top of Spray, which also gives me some documentation for free: Pretty useful when you have hundreds of services in hundreds of servers. It's a pity that Java itself moves so slowly, and is so reluctant from adding key features, like pattern matching, because the rest of the tooling is pretty good.
Posted by hibikir on May 10, 2015, 1:09 PM
Tags
Related issues
- I think this release is really going to give them a hard time selling Fable: > On our benchmarks, Claude Opus 5.5 leads in agentic codin...
- My biggest problem with this is that this regulation is only aimed at AI.
- Because it works too reliably.
- OCaml's type system is quite janky and simplistic compared to Haskell's.
- This is a very annoying problem, it's infuriating, you pay 10 USD<->20 USD/mo, and the ads are not even removed.
- These are markets that are being developed actively by car companies.
Raise real-world problems, find people facing the same issue, and discuss solutions.6,500 issues0 comments
hackernews (Marketing)
I think this release is really going to give them a hard time selling Fable: > On our benchmarks, Claude Opus 5.5 leads in agentic codin...
My biggest problem with this is that this regulation is only aimed at AI.
Because it works too reliably.
OCaml's type system is quite janky and simplistic compared to Haskell's.
This is a very annoying problem, it's infuriating, you pay 10 USD<->20 USD/mo, and the ads are not even removed.
These are markets that are being developed actively by car companies.
> We can see that because people who put their money where their mouths are, like venture capitalists, encourage those behaviors.
So what is the unmet need behind an obsession with sexless/child-like figures?
The fact that people that have used Java do not realize that EJB3 is pretty good, when it's pretty old!
The fact that people that have used Java do not realize that EJB3 is pretty good, when it's pretty old! I switched to EJB3 in 2006, and I really couldn't see why people would choose Spring anything instead. The switch to Soap, and then to Rest, was changing a couple of annotations. Not bad for a 9 year old framework. Now, my biggest problem with the stack, and the reason I do not use it anymore, is Java itself. A switch to Scala makes a lot of the Java boilerplate go away, and even Java 8 doesn't get close. Now, I find all the major Scala web libraries to be lacking, in one form or another. Play's second compilation feels clumsy. Spray's freedom of routing leads to very ugly code: Just look at their own large examples. So what I am currently doing is using a homebrew routing on top of Spray, which also gives me some documentation for free: Pretty useful when you have hundreds of services in hundreds of servers. It's a pity that Java itself moves so slowly, and is so reluctant from adding key features, like pattern matching, because the rest of the tooling is pretty good.
Comments (0)
No comments yet. Start the discussion.