5 ms·

I call bullshit. The EE eco system while not perfect is basically a best in class for framework for everything we've learned about building business apps over

• bschwindHN 9y ago
  This doesn't refute the point you're replying to, you're essentially saying "Nuh uh it's the best" Too many knobs and dials can be a big problem, and verifying you have everything set up optimally for production is tough with all that configuration present.
  • abiox 9y ago
    > Too many knobs and dials can be a big problem, and verifying you have everything set up optimally for production is tough with all that configuration present. this seems like a tautology. too many knobs is too many.
    • thaumasiotes 9y ago
      "Too many" of something is bad by definition, but it's not a "big problem" by definition.
    • seandougall 9y ago
      I don't think it's a stretch to read the comment as "Java EE has too many knobs and dials", which is very much not a tautology. (Whether it's true or not is another matter, and not a point I'm qualified to argue)
  • w4tson 9y ago
    "general problem of Java EE style architecture." What style is that? The style of composing persistence technology, Authentication and Authorization, dependency injection, messaging, web communication etc to make a business application? If you know of a magical tech that doesn't aim to solve these problems in a standardized modular way so that the developer isn't socket programming from the ground up then please chip in. "There are many moving pieces and many permutations of how they interact together." Agreed. The problem space isn't todo apps or "Hotdog/No hotdog". "It's practically impossible to understand it in its entirety, and thus impossible to guarantee that it's secure." I don't understand the finer points of the myriad of TLS cypher suites etc, probably means I can't guarantee that they're secure. But what other option do I have? roll my own? Nope I'll take sensible defaults and twiddle the knobs where the client's requirements demand something different. "You're basically plugging holes as you find them, but you're never sure that there aren't more holes you don't know about." - this is FUD.
    • yogthos 9y ago
      The JEE stack is a monolith with many deeply intertwined components. The alternative is having a stack composed of small focused libraries that can be composed to fit the needs of the particular application. I'm not talking about understanding the finer points of the internals such as the implementation of the TLS cypher. I'm talking about the complexity of how different moving pieces fit together in the stack. This isn't FUD, it's the reality and it causes security breaches all the time in the real world.
• makomk 9y ago
  CVE-2017-9805 is yet another deserialization vulnerability from a language and set of frameworks that seem designed to produce an endless stream of deserialization vulnerabilities. This should very much reflect on Java EE.
  • Lightbody 9y ago
    Normalized by usage I would be surprised if it's actually as high as you suggest. The more popular a platform is, the more attention from bad actors there will be. Every platform has had similar vulnerabilities along the way. For example: https://www.google.com/search?q=rails+rce&ie=UTF-8&oe=UTF-8&hl=en-us&client=safari https://www.google.com/search?q=rails+rce&ie=UTF-8&oe=UTF-8&...
  • peoplewindow 9y ago
    Is Struts Java EE? There are quite a few web frameworks in the Java space and anyone who reviews Apache CVE history will see immediately that Struts has by far the most serious problem with exploits of any product they do, let alone any Java product.
• yogthos 9y ago
  That certainly hasn't been my experience working with JEE.