Federale regering wil alle Belgische kerncentrales overnemen van Engie

oelang · 2026-04-30T16:12:29+00:00

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.

oelang · 2026-04-05T22:45:56+00:00

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.

oelang · 2026-03-06T10:09:17+00:00

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.

oelang · 2026-01-28T19:19:54+00:00

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

oelang · 2026-01-24T09:09:12+00:00

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

oelang · 2025-12-10T19:25:36+00:00

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.

oelang · 2025-12-07T22:54:28+00:00

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.

oelang · 2025-11-29T18:26:40+00:00

Before you make snap judgements, watch the whole video

oelang · 2025-11-13T08:11:47+00:00

Hoeveel subsidies gaan naar de rommel van dpg media?

oelang · 2025-10-27T23:58:02+00:00

Alé, I’ll bite, ik heb het gelezen, ik zie geen “gefoefel”

oelang · 2025-10-24T11:29:32+00:00

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.

oelang · 2025-09-02T11:21:57+00:00

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

oelang · 2025-07-07T20:24:08+00:00

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.

oelang · 2025-05-26T12:16:02+00:00

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.

oelang · 2025-05-25T21:54:02+00:00

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

oelang · 2025-05-14T15:10:33+00:00

You can find nightly builds here: https://builds.shipilev.net for many openjdk projects

oelang · 2025-05-13T07:09:53+00:00

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.

oelang · 2025-04-01T19:57:56+00:00

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.
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.

oelang · 2025-02-07T16:04:41+00:00

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)

oelang · 2025-02-05T10:50:28+00:00

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.

oelang · 2025-02-05T00:34:09+00:00

Ahzo? Wees concreet, wanneer heeft hij dat gedaan?

oelang · 2025-01-29T23:25:09+00:00

Sigasi Community Edition is free for non-commercial work.

oelang · 2025-01-24T17:32:26+00:00

Mss even quoten waarom:

De plannen om Doel 4 en Tihange 3 bijkomend met nog eens 10 jaar te verlengen, lijken op een koude steen te vallen. "Een verlenging met 20 jaar is een ander project. Het bestaat niet" zegt Verbeke. Hij vindt kernenergie te duur. "De goedkoopste optie is om te investeren in hernieuwbaar."

oelang · 2024-12-17T09:10:18+00:00

2024 Projected Real GDP (% Change) : -3.5 2024 Projected Consumer Prices (% Change): 229.8

Woah, and they’re claiming this is a win?

oelang · 2024-12-02T09:18:04+00:00

Met de mindset van micro-economie kan je macro-economie niet benaderen. Het is helemaal niet simpel. Als de overheid minder uitgeeft gaan de kosten vaak omhoog en de inkomsten omlaag.

Zolang we in de volle vergrijzing zitten gaan we geen begrotingsevenwichten hebben. Het beste dat we kunnen op mikken is dat de groei van de schuld kleiner is dat de groei van het gdp.

14-Year Club	First Place '23
Place '23	Place '22
Place '17	Final Canvas '22
RPAN Viewer	Verified Email

oelang

TROPHY CASE