vips7L

17 ms·

1. 421.▲
   by vips7L 11mo ago

   Yes, calling people monkeys is a bad decision.
2. 422.▲
   by vips7L 11mo ago

   I genuinely believe its not a conscious design decision. Most people never properly learn how to turn things into objects. I've seen this happen in many projects across many companies. They simply just write procedural code without cen
3. 423.▲
   by vips7L 11mo ago

   I don't think anyone sets out to make an anemic domain model, it just happens. Lots of developers start with POJO's for JPA models and then never advance them into being full fledged objects when the requirements develop.
4. 424.▲
   by vips7L 11mo ago

   Honestly one of the best books I've read about programming. It's inspired me to try the language out just for fun things, think I'm going to use it for Advent of Code this year. I think it does benefit from being interoperab
5. 425.▲
   by vips7L 11mo ago

   Lots of modern OO uses immutable data.
6. 426.▲
   by vips7L 11mo ago

   There’s also automatic delegation like in Kotlin: https://kotlinlang.org/docs/delegation.html
7. 427.▲
   by vips7L 11mo ago

   Python was a mistake if you ask me ¯\_(ツ)_/¯
8. 428.▲
   by vips7L 11mo ago

   It is not a feature. Every programming language since has decided this was a mistake.
9. 429.▲
   by vips7L 11mo ago

   Service classes are the thing I hate most. They’re just namespaces for functions. They’re a product of Java not being able to have top level functions.
10. 430.▲
    by vips7L 11mo ago

    Object orientism is just encapsulation. It’s the only thing that is required. You can have objects without inheritance and virtual dispatch.
11. 431.▲
    by vips7L 11mo ago

    Compiler exhaustion is such a useful feature. I can’t believe TS doesn’t have it.
12. 432.▲
    by vips7L 11mo ago

    You don’t have to pay for Java AOT either. Graal is free.
13. 433.▲
    by vips7L 11mo ago

    > Basically they took a bunch of C# specifications and translate them to JSR format. I would really love for you to point out which ones, because I can't think of a single one. Most features being developed into Java are taken from
14. 434.▲
    by vips7L 11mo ago

    > - Enterprise Devs as the core user (Type safety, great stdlib) > - High level OO based interfaces > - Allows for low enough level programming that you can reasonably use in place of C/C++ This can reasonably said about any p
15. 435.▲
    by vips7L 11mo ago

    Not really. They're independent languages with different design goals. You're exact questions in this thread would have been just as relevant without bringing it up.
16. 436.▲
    by vips7L 11mo ago

    Everybody's gotta bring Java into it.
17. 437.▲
    by vips7L 11mo ago

    This is the same _type_ of elitism that I've seen from the Scala community and really makes TS seem unpalatable. Big "A monad is just a monoid in the category of endofunctors" vibes.
18. 438.▲
    by vips7L 11mo ago

    > I don't use the init decorator myself but I would hazard a guess it's similar. Genuinely curious, why not? Seems to be less verbose. I don’t write C#s so I’m not sure of the downsides of any particular feature.
19. 439.▲
    by vips7L 11mo ago

    I think you would want to use an init only property for your example class Test { public string Test { get; init; } } I'm not a C# expert though, and there seems to be many ways to do the same thing.
20. 440.▲
    by vips7L 11mo ago

    ScalaJs!
21. 441.▲
    by vips7L 11mo ago

    This is unpublished still but is worth checking out: https://www.manning.com/books/data-oriented-programming-in-j... Other than that, I think we’re all waiting for Josh Bloch to put out Effective Java 4th edition. The
22. 442.▲
    by vips7L 11mo ago

    I’m a huge Java fan, modern versions are amazing, but being stuck on 8 is the only time I’d recommend just using Kotlin or Scala and compiling to v8 byte code. 8 is just a miserable experience.
23. 443.▲
    by vips7L 11mo ago

    IIRC the native image GC is still the serial GC by default. Which would probably perform the worst out of all the available GCs. I know on HotSpot they’re planning to make G1 the default for every situation. Even where it would previously c
24. 444.▲
    by vips7L 11mo ago

    Java’s collectors vastly outperform Go’s. Look at the Debian binary tree benchmarks [0]. Go just uses less memory because it’s AOT compiled from the start and Java’s strategy up until recently is to never return memory to the OS. Java prog
25. 445.▲
    by vips7L 11mo ago

    I genuinely can’t think of anything the Java standard library is missing, apart from a json parser which is being added. It’s your preference to prefer one over the other, I prefer Java’s standard library because atleast it has a generic Se
26. 446.▲
    by vips7L 11mo ago

    Go is in the same performance profile as Java and C#. There are tons of benchmarks that support this.
27. 447.▲
    by vips7L 11mo ago

    Java has had CompletableFuture::allOf for a long time. The new structured concurrency api also has the same capabilities of waiting for futures.
28. 448.▲
    by vips7L 11mo ago

    > Java is quite busy also implementing features that are small in other languages like text blocks. Or named parameters or compile time null safety. Everyday I inch closer to moving over to C# from Java.
29. 449.▲
    by vips7L 11mo ago

    I hope once they introduce unions, they also introduce some sort of error union.
30. 450.▲
    by vips7L 11mo ago

    > So if you had 3 different disjoint exception types that you simply wanted to wrap and rethrow, you had to write 3 different catch blocks for them. Agreed. There's a proposal for exception catching in switch [0] which I'm hope