synack

“I need my next laptop to have 64GB of RAM”

No, you need better software.

The debugger book is coming soon. https://nostarch.com/building-a-debugger

I’ve been working through this book implementing the compiler in Ada. So far, I’m really enjoying it. The book doesn’t make too many assumptions about implementation details, leaving you free to experiment and fill in the blanks yourself.

It feels like a more advanced version of Crafting Interpreters.

I haven’t looked at the OCaml implementation at all. The text and unit tests are all you need.

Discussion on the Ada Forum: https://forum.ada-lang.io/t/writing-a-c-compiler/1024

They won’t change their behavior unless it affects the bottom line. Time to lobby your corp travel departments to blacklist Hilton properties.

Use the semantics of the standard Incident Command System. Emergency responders have spent decades figuring out the best way to organize for these situations. Tech orgs should leverage that work.

https://en.wikipedia.org/wiki/Incident_Command_System

https://training.fema.gov/nims/

If this is for use during outages, I want to know exactly what network path is used, ideally with as few hops as possible. Starlink can’t guarantee that.

With launch costs dropping, I wonder if there’s a market for a low bandwidth “ssh via satellite” service. Could use AWS Ground Station to connect to your VPC.

~/src/projectname/ for things I've written, patched, or am contributing to.

~/build/projectname/ for things I've downloaded/cloned for reading or compiling.

I generally consider ~/build/ to be ephemeral and it gets deleted whenever I build a new PC or start running out of disk space.

~/src/* gets moved to ~/src.old/ roughly once every five years, just to keep things fresh. Both are still backed up.

I saw a nice exhibition of Emigre at the Stedelijk Museum in Amsterdam just last month. Worth a look if you're into typography.

I think there will eventually be a false advertising lawsuit or some regulatory action against Amazon about this. Until that happens, it’s hard to say for certain which items are used.

The toolchain is cached, so it only gets downloaded once.

SDLAda has been around for a while: https://github.com/Lucretia/sdlada

You can add it as a dependency to your Alire project: `alr with sdlada`

Rumors that they're discontinuing the snowmobile service: https://twitter.com/0xdabbad00/status/1776999225550938124

By lock-in, I’m referring to my EC2 committed use savings plan that would prevent me from considering migrating to GCP until it expires next year, even if Google’s instances are quantifiably better.

Google published PUE (https://en.wikipedia.org/wiki/Power_usage_effectiveness) numbers a while ago, I haven’t seen anything that specific from Amazon.

It’s difficult to quantify emissions because the power generation is mixed and changes based on demand. Water consumption should also be a factor, but there’s even less data available for that.

All I wanna know is how it compares to AWS Graviton2/3/4 instances. Axion needs to be cheaper, faster, or lower emissions to be worth even considering. Everything else is just talk and vendor lock in.

Looks like your data went missing. No rows in the table.

I'm far from an expert on compiler development, but I think it's just a matter of walking the AST to ensure that there aren't any calls to procedures with the Global or Nonblocking aspects inside a parallel block.

The bigger issue is that the `parallel do` and `parallel for` blocks added in Ada 2022 [1] haven't been implemented and as far as I know, nobody's working on it.

I suspect that if we ever do get parallel support, it'll come from the GNAT-LLVM project [2], rather than GNAT-GCC. In the meantime, there's a CUDA compiler [3].

[1] http://www.ada-auth.org/standards/22over/Ada2022-Overview.pd...

[2] https://github.com/AdaCore/gnat-llvm

[3] https://github.com/AdaCore/cuda

I don't think any compiler implements that yet.

I have an ansible playbook that does "git pull" in the right directory and restarts the daemon. I run it whenever I need code deployed, but it wouldn't be difficult to rig up to a CI system.

The EC2 instances are managed by terraform. Debian AMIs with a cloud-init script to get them bootstrapped with ssh keys and such to the point where ansible can run.

Yes, there are better options but with a team size of < 5, this works fine and there's really not much that can go wrong with it.

The people building it will be fed, housed, and their children educated with that amount of money. Jobs are what the world gets out of this sort of thing.

If you limit your dependencies to what’s available in your distro’s LTS or stable release breaking changes are much less common. Living on the bleeding edge has a cost.

Bradley Gawthrop: Wiring Boot Camp https://youtu.be/FMXdXCYvLQQ

Arduino or similar over USB.

Every release has an upgrade guide, like this: https://www.openbsd.org/faq/upgrade74.html

Make backups, make sure you can restore them, then just step through it one version at a time. Things got a lot easier around 6.6 when sysupgrade was introduced.

Cool, now make the same guarantee for the cloud services the phone connects to.

Agreed! Software modules and libraries can achieve the same independence of subsystems without implying a network topology.

Microservices are a solution to a social problem, not a technical one.

A team of N engineers requires N² coordination. Large teams get mired in endless meetings, email, design reviews. Small teams are more effective, but struggle to maintain large systems.

Splitting a system into subsystems allows each team to focus on their piece of the puzzle while minimizing the amount of peer-to-peer coordination.

Yes, microservices add complexity and overhead, but this approach enables a large organization to build and iterate on large systems quickly.

I had similar issues with EDID on an old monitor. I pulled the cover off the back and found the I2C EEPROM that stored the EDID data. I soldered a jumper to disable the write protect on the EEPROM and was able to reprogram it using the Linux i2c-dev device.

Seems a bit insensitive to sensationalize a headline with the word "firestorm" when entire towns are being leveled by actual firestorms. Open source licensing is not that serious.