are you a platform/embedded developer?
do you need to interact with hardware in a semi-custom manner?
would you like to suffer a lot less doing it?
if so, #GlasgowInterfaceExplorer might be for you. the code below is all you need to build a custom testbench for a DUT you've never seen before. just as easily you can add JTAG/SWD debug, protocol analyzers, etc.…
so why on earth were CNCF/K8s kicked off Slack's enterprise plan, anyway?
cost? how much can it cost to store a bunch of chat messages for two moderately popular OSS groups, ten dollars a day? all of the capital cost has been paid at this point, it's just the marginal one at question, which cannot be high unless Slack's infrastructure is dramatically worse than any reason could allow
the amount of goodwill they know they'll lose can't possibly compensate the c…
her: (adorable cat drawing)
me: cute
her, 5 seconds later: i want someone to have my skull
my annoying engineering trait is that i don't like hardware abstraction layers
they're usually irritating to write code for, and equally irritating to reverse-engineer whenever i need to. i mostly end up reverse-engineering these days
always a good day when you can remove a complex piece of code and make a more powerful system that is easier to understand
https://github.com/GlasgowEmbedded/glasgow/pull/873