I’ve had some not so good pig intestine and some phenomenal, and the worse ones were similar to how you described it. If you ever decide you’d try it again, I think it’s so much better when crispy. The texture reminds me of bacon with a gelatinous, melt in your mouth center almost like burnt ends.
I wouldn’t buy a whole thing from the store unless you know you like it, but if you like cilantro and jalapeno, a banh mi with head cheese and pate is a good way to try it. It’s a delicious mix of fresh, savory, fluffy, crunchy, and chewy.
Canonical’s hiring process is wild. The number of stages is a deal breaker in itself, but the bizarre questions and the tests you mentioned don’t do them any favors either.
I lost interest in the first stage with them asking for an essay about things like what kind of student I was in high school. The full email was massive.
Slop, I think. Their replies smell like they came out of an LLM, and they have a Claude attribution in their commits. Comes off as grifting or cosplaying to me.
deleted by creator
- How can iodéOS (Lineage fork) be installed on phones with bootloaders locked?
I just don’t understand how they can create an installer that works with bootloader locked phones, and then the OS remain completely secure.
Barring exploits, phones with a locked bootloader can’t be flashed with a different OS by design.
If you’re comfortable with vim, vimdiff is lightweight, works well for simple stuff, and you probably have it installed already (can use vim -d if not)
Thanks for calling out the bullshit, friend. Mainstream science literacy is in a sad state.
Not moving the goalposts at all, you’re just missing the forest for the trees. The main point is that there are plenty of use cases that can use pure C with no assembly. I went with a simple example because I thought you’d have an issue with more complex examples like sending a notification over SMS via modem or providing a serial interface for sensor data.
I don’t feel like arguing for the sake of arguing, though, and I feel like we’re in a pedantry spiral, so I’ll leave the conversation at that. Hope you enjoy your day.
Again, those aren’t universally required. You can make an embedded device that reads the ambient light levels and turns on an LED when it’s dark without thread stacks, privileges, or interrupts. Don’t make your system more complicated than it needs to be.
Not necessarily. Let’s say that…
_entry(), with a linker script to take care of its memory placement.You can compile only your C source file that defines _entry() and interrupt vectors, then flash the resulting firmware. No assembly involved, no external linkage, and no stdlib required.
My point is that assembly isn’t strictly required. You can do memory-mapped reads and writes from C all you want, which is enough for plenty of I/O: storage, serial, sensors, GPIOs… You can build quite a few things with these without touching system registers.
I’m not saying we should abolish assembly. Just that it isn’t a universal requirement.
Yeah, if your bootloader is expected to handle that you’re going to need assembly. That can also be delegated to the kernel, RTOS, or bare metal reset vector later on in the boot sequence, though. I had to write a bootloader for an embedded system like this once and it basically just applied firmware updates, validated the firmware, and handed control over to the firmware.
Reminds me of not long after I started using Linux. I thought the kernel was “just a program” like cat and tried to run the kernel from the terminal, only to be disappointed when a new kernel in fact did not start running inside the terminal window.
A little hair-splicy, but an assembly-free bootloader is definitely doable on some platforms – Cortex-M processors load the stack pointer from the vector table, and the initialized memory setup can be taken care of with memcpy.
I took it more as a plea to people who think it’s optional year round