TFW you are on a return trip to Earth after carefully sampling the solar wind and your drogue shoot doesn't open as you enter the atmosphere, and instead of being gracefully plucked out of the sky by helicopters you crash face first into the Utah desert.

en.wikipedia.org/wiki/Genesis_

Rainbow Airglow over the Azores

Image Credit & Copyright: Miguel Claro (TWAN); Rollover Annotation: Judy Schmidt

apod.nasa.gov/apod/ap210418.ht #APoD

shitpost 

@craigmaloney I could totally hear him say that just now. 😆

re: hardware 

@amiloradovsky I do want to try one of the languages you refer to. Probably Mingen to start. I've stayed away from it for work because it is much easier to find people who can work in Verilog and VHDL than other languages. In a pinch, a contractor can be brought in and they could probably easily get to work. I'll have to explore these options in my own time (like always).

re: hardware 

@amiloradovsky Thinking about it, whenever I am working, I tend to be targeting at least two implementations of Verilog: the toolchain used to generate a bitstream and the toolchain used to simulate. Often these disagree about what Verilog is. So I end up writing to the subset of the language they both can agree to, which is hopefully a useful subset. 😆

re: hardware 

@amiloradovsky I'm not sure. I've definitely used implementations of Verilog (not SystemVerilog) which would not let me create instances of modules or wires outside of generate blocks. I tend to think of generate blocks as a kind of weak templating system or slightly weird C macro system. Of course, what you say about types are true. Although plain Verilog has so few types anyway. ;)

hardware 

@amiloradovsky The "generate" statement is also available in plain Verilog. Generate will actually "instantiate" new constructs within it. So if you have a generate for loop with an instance of Module(), you will have the same number of Module() instances as you do loop iterations (of course same applies to wires etc). The names of module instances and wires defined in the loop are all scoped to the generate for loop. I've used that construct quite a bit over time in different scenarios.

Vaccine + 

Scheduled for my first dose.

@ND3JR "tried and true"... The computing industry's perspective on time is ridiculous sometimes... Or all the time really.

ugh 

@requiem Hopefully that's just 5G kickin' in.

(Seriously, though I hope your immune system builds up a good resistance to this stuff.)

@erkin If it's good enough for the grandmasters, it's good enough for me... er... Or something.

@djsundog I fall in to the awkward canyon all the time. I try stay out of the uncanny valley.

Today we're kicking off the #GNU Assembly!

gnu.tools

This is a new umbrella for GNU people seeking transparent decision-making and built around consensus. It's the result of a decade of struggle to make #GNU inclusive, transparent, and community-driven.

#GNU contributors: consider joining!

#FreeSoftware activists: help us spread the word!

re: controversial? 

@requiem @djsundog You know, when you construct a trap, you try to make it easy for your prey to fall int it. ;)

(Or to put it another way, if all we measure and optimize for is the number of people we can attract to a services/platforms, we will probably end up making traps.)

With you are emphasizing knowledge sharing, empowering people to participate as equals, and you aren't trying to capture " market", that will change the way things move forward.

Show older
social.coop

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!