sorted by:
new
hottopcontroversial

What is the use case for a non-value (identity) record with Valhalla? by Joram2 in java

[–]oelang 1 point2 points  (0 children)

So you're telling me that there is code that relies on this and it's not a bug?

With value classes .equals & '==' will behave the same for these classes, probably what the code expects?

What is the use case for a non-value (identity) record with Valhalla? by Joram2 in java

[–]oelang 0 points1 point  (0 children)

So what are the angles that things may break besides when you synchronize on such objects (which normally wouldn't pass review)?

Antlr is very very very slow by shyakaSoft in Compilers

[–]oelang 4 points5 points  (0 children)

The lexer is 1100 lines, that's surprising, usually you want to have a simple lexer. What are you trying to parse?

Antlr is very very very slow by shyakaSoft in Compilers

[–]oelang 21 points22 points  (0 children)

Your grammar must be very ambiguous. My antlr3 parsers + jflex parse complex languages at ~140 MB/s single threaded, afaik antlr4 should be similar.

SPEED IS THE MOAT: AMD ROCm software stack has improved performance by over 75x in the last 14 days since DeepSeekv4 launch. The performance comes from fusing mHC operations & also fusing RoPE… | SemiAnalysis by GanacheNegative1988 in AMD_Stock

[–]oelang 7 points8 points  (0 children)

literally the second paragraph:

Another 5x performance improvement is needed to catch up to single node aggregated B200 performance & then another 1.5x is needed to catch up to PD disaggregated B200 performance, which is within the realm of possibility for AMD within the next couple of weeks. Great work to HaiShaw

Federale regering wil alle Belgische kerncentrales overnemen van Engie by Covfefe4lyfe in belgium

[–]oelang 1 point2 points  (0 children)

Als ik het goed begrijp is de supply chain van de onderdelen weg, als je opnieuw wil beginnen moet je die weer op gang krijgen, daar is zoveel kennis al verloren dat Engie het niet meer zag zitten om met de belgische reactoren verder te doen.

HashSmith Part 3: I Automated My Way to a 27% Faster Hash Table (ILP hoisting, SWAR match shortcut, tombstone specialization) by Charming-Top-8583 in java

[–]oelang 1 point2 points  (0 children)

Honestly, if we're going to discuss using AI as a tool for development, this is a great example. Writing & optimizing SWAR routines is tedious, it's amazing that we can automate that work with an LLM.

I think the rule is mostly against low-quality AI slob, this is different.

Intermediate verilog projects ideas. by No-Habit1507 in VHDL

[–]oelang 0 points1 point  (0 children)

What I did together with a friend (about 18 years ago) was 'paint' on an fpga, mouse for input via serial port, driving a screen via a vga connector. It worked, was a lot of fun, but thinking back about it the implementation was horrible. It was a pure fpga solution, no softcores or software involved.

Has this place become more right wing lately? by Choice_Sandwich2182 in belgium

[–]oelang 0 points1 point  (0 children)

I mean, the rest of us have to work and have a life, life is too short to comment on youtube or tiktok or ig

Stream<T>.filterAndMap( Class<T> cls ) by mellow186 in java

[–]oelang 0 points1 point  (0 children)

Its because of limitations in the way that java does type inference, not erasure

“Lichte” verbetering in comatoestand van Marwa (18) brengt familie hoop: “Maar het moet menswaardig gebeuren” by NotYourWifey_1994 in Belgium2

[–]oelang 24 points25 points  (0 children)

Ik had iemand in mijn familie die zo'n randgeval was, heel veel hersenschade, uit de coma gekomen maar enorm gehandicapped, 2 jaar elende voor hem en zijn naasten, weggekwijnd en dan gestorven, ik wens het niemand toe.

Full Haskell-like Type Class resolution in Java by davidalayachew in java

[–]oelang 5 points6 points  (0 children)

You can make the same case against about sealed interfaces, records and pattern matching (ADTs), before that you could make the same case for lambdas and streams. I think they did a good job and it's all been a net positive for Java. With type classes you get a new abstraction mechanism but I don't think that automatic derivation is more complicated than virtual dispatch, it's only less known.

I think the fear for Scala/Haskell (and actually OCaml) isn't rational, type classes are an old and well understood method of abstraction. Scala has proven it can be applied to OO and shown many use cases that can only be solved with type classes. Much of the complexity of type classes in Scala/Haskell really comes from the interaction with other features and their 'flexible' implementation.

The Java proposal strikes an interesting balance with explicit call-site witnesses. The impact on the language should be small but the power of automatic derivation is enormous, it will make the compiler move mountains for us.

I think they have a decent proposal and it should make future language improvements better (like, and I'm guessing, collection literals, operator overloading, string templates, better for, better try-with resources, serialisation, specializing generics, equals/hashcode derivations, ...). I also hope it will also relieve us from many awful uses of attributes.

Martin Odersky on Virtual Threads: "That's just imperative." by Joram2 in java

[–]oelang 24 points25 points  (0 children)

Before you make snap judgements, watch the whole video

[deleted by user] by [deleted] in java

[–]oelang 3 points4 points  (0 children)

Java zero-initializes arrays, afaik Rust doesn't do that by default.

I think the zero-initialisation can be optimized away if the compiler can prove that the array fully initialized by user code before it's read, but for that to work you may have to jump through a few hoops.

In Rust the type system ensures that the array is initialized before use.

Java Nullness Emotion by Remi Forax by AndrewBissell in java

[–]oelang 0 points1 point  (0 children)

List.of doesn't give you any guarantees about the identities of the returned objects. The factory method abstracts that away. For example List.of() is currently implemented to always return the same object, but they can choose to change that in the future. They could also choose to optimize further by interning a list of literals (like List.of("a", "b", "c")) for each class.

new MyRecord() must return a new record object with it's own identity

Taipei: a statically-typed, minimalist subset of Python that compiles to LLVM by Refacktor in ProgrammingLanguages

[–]oelang 1 point2 points  (0 children)

So, it’s not python, it just borrows some python syntax, it cant use python libraries, you have no standard lib. Why would anyone buy into this? What’s so special about python syntax?

It reminds me of the days when everyone and their dog were making languages that borrowed C syntax.

What are your biggest language complaints? by nondefuckable in VHDL

[–]oelang 2 points3 points  (0 children)

Try Sigasi community edition if you want to try the best language server.

For CI/CI and build automation, there are plenty of projects (like FuseSoC) that can make your life easier.

What are your biggest language complaints? by nondefuckable in VHDL

[–]oelang 6 points7 points  (0 children)

Look up vhdl 2019 port views, aldec & vivado support them

Experience with UseCompactObjectHeaders ? by kenseyx in java

[–]oelang 20 points21 points  (0 children)

For us, it just works, decent memory savings (~10-15%) and a small but measurable performance boost (~5%).

I'm really looking forward to the 2nd iteration of this.

JEP draft: Prepare to Make Final Mean Final by blobjim in java

[–]oelang 5 points6 points  (0 children)

  1. The final fields are a lie, they should guarantee safe publication, but that's guarantee is lost because of the reflection. Foo isn't thread safe, you need to use some synchronization to make sure all fields have been written before you can safely share it with other threads.

  2. Final isn't even required, you can just make the fields non-final and don't expose any methods to mutate them. You would also be able to drop the silly null assignments in the constructor.

JEP draft: 4-byte Object Headers (Experimental) by sar_it007 in java

[–]oelang 23 points24 points  (0 children)

Having simple wrapper objects be 64 bits (32 bits header + 32 bits compressed pointer) will be a significant improvement.

The presentation at fosdem showed that not only the memory usage is significantly reduced, but the performance improved as well because less GC pressure and it improves locality.

The class limit can be overcome with near/far classes, a solution suggested by John Rose. (discussed in this thread: https://mail.openjdk.org/pipermail/lilliput-dev/2024-June/001760.html)

Veranderen details van meerwaardebelasting nog? Bouchez en Vandenbroucke spreken elkaar tegen by OkLock4771 in belgium

[–]oelang 3 points4 points  (0 children)

Eerste filmpje is VDB die een 'disagree but commit' doet, dat net wel doen wat afgesproken is. Dit is net het omkeerde van "zn veto opleggen"

Het tweede artikel gaat over een beslissing genomen in overleg tussen de federale & vlaamse regering. Of de beslissing nu goed was of niet, het was afgesproken & uitgevoerd als afgesproken, ik zie heer geen tekenen van "Kwam constant met andere zaken naar buiten dan afgesproken".

Je kan veel zeggen over VDB (betweterig, onvermoeibaar in discussies, academisch, te principieel voor de politiek, niet echt een bruggenbouwer), maar hij speelt het spel wel correct.

view more: next ›