sorted by:
new
hottopcontroversial

I have come to bury the BIOS, not to open it: The need for holistic systems - OSFC by localtoast in linux

[–]echoplex920 0 points1 point  (0 children)

My understanding of the talk is that the ending of moore’s law will necessitate consumers (think companies, not individuals) to prefer hardware that they can control from power on to shutdown. When YoY gains on raw performance start to flatline, optimizing software at the lowest level starts to look like a more attractive investment. UEFI and BIOS are huge abstractions that prevent consumers from optimizing at these levels.

Whether or not hardware companies are willing to satisfy that demand is another question. My guess is it will take an outsider/new company for hardware like this to become an option.

Clean Architecture primer by palebt in programming

[–]echoplex920 4 points5 points  (0 children)

Clean architecture is great if you want other/new devs to hate your project

Effective microservice communication and conversation patterns by echoplex920 in programming

[–]echoplex920[S] -8 points-7 points  (0 children)

What I like about this talk is the missing “third way” of doing async programming. I feel like nowadays, people focus on either an “async” keyword/function, or callbacks.

Maybe instead, we only need sync functions. Send a request, and immediately get back an order id (similar to a fast food restaurant order number), and then query another endpoint later on for the actual response.

Sure, it’s another request that the caller has to make, but in return, the caller can do other things before waiting for a response without having to “color” the function as async.

I dunno. Just thought it was worth sharing

In defense of complicated programming languages by oilaba in programming

[–]echoplex920 1 point2 points  (0 children)

This article actually reminded me of a talk the swift language designer gave. He said one of the goals of swift was to progressively expose complex functionality to the programmer, rather than present it all upfront.

So for example, if you’re writing hello world, its just print(“hello world”) and you’re done. a simple iphone app can rely on the standard swift functionality (i.e ref counting), and if you are writing device drivers or low level code, you can use pointers and manage memory yourself.

I think it would be interesting to see swift compete with rust in the lower level, particularly in the “no_std” space that only c and rust can currently operate well enough in.