same. substitute VC with upper management and I (corporate dev through and through) became more queasy as I read. product and strategic mismanagement is the real deal regardless of the source of capital
my most mind blowing recent development here was testing the Gemma 4 models at release for vision and image recognition vs some benchmarks I had from using Gemma 3 for the same tasks. Gemma 4 is significantly faster and massively more accurate, to a level where I fundamentally can finally turn off my wifi and run a batch of my photos through the local model and trust the results for the extensive classification that Gemma seems well suited to handle. incredible times for local LLMs
two well-balanced takes making me think I should embrace the fun parts of this design and worry less about the risks! it’s a pretty cool idea and impressive it works
super interesting pseudo IPC channel and at least mildly concerning from a security perspective. saw it on your site first and am shocked there is not a single other comment yet here
was hoping to find at least one “cmon this is easy to avoid with X thing in the kernel/OS” info nugget dropped
really impressed with this. the author discusses on Reddit how they built it with Unity which I think is super cool and a really good use case for a game engine
You are correct, C# straddles that line better than any other language right now imo thanks to the APIs you linked. There was a good write up about this Rust vs C# Span comparison on HN a few weeks ago but the link escapes me
Well five is about the amount of sales people I remember joining an absolutely awful call with them a few years ago, so that’s my guess (edit: lol at getting downvoted for relaying an actual experience that happened. been using Vagrant since the original hobo logo circa 2012-2013 and have always been a HC fan, get off your high horse)
Cool post. Wonder if it would have helped to take a look at the MIT distributed systems course on the web and YouTube - one of the projects is exactly this (Go Raft implementation)
They have done this previously for dual socket Xeons. Historical precedence doesn’t necessarily hold here, but in fact, it’s been done on the “cheese graters” previously
You and I both, though they are a blessing and a curse. Profiles used to be my biggest issue with local and remote cred resolution, and then we layered AWS SSO on top of profile management, which doubled my problems. It’s all technically more secure and ultimately cleaner to work with when you know what to do, but trying to figure out how to transparently pass role based IAM creds into a running Fargate container to the AWS SDK was a lesson in pain (not to mention designing that to work locally). Lambda can fall through to an SSO/managed profile env fine if running w/o the container wrapper, and SAM plugins are pretty magic for making it work if you use their container, but otherwise I have been strongly avoiding custom OCI containers w/o SAM because the dev SDLC is going to require all kinds of env tweaking and cred directory mounts.
If you know and understand S3 pretty well, and you purely need to generate, store, and read materialized static views, I highly recommend S3 for this use case. I say this as someone who really likes working with DDB daily and understands the tradeoffs with Dynamo. You can always layer on Athena or (simpler) S3 Select later if a SQL query model is a better fit than KV object lookups. S3 is loosely the fire and forget KV DB you’re describing IMO depending on your use case
I’m not 100% sure as I didn’t create the image (though I’m evangelizing as someone who has found it truly helpful for daily dev.) . I believe the creators tarball’d the entire distro/execution environment from a running lambda so the file system layout and libs likely match Amazon Linux if that’s the default lambda execution distro image. If not I assume it matches the default
Logged in to say that this has actually been done (not by me) and my team has been finding it very helpful for local “serverless” SDLC: https://github.com/lambci/docker-lambda . It‘s billed as “ A sandboxed local environment that replicates the live AWS Lambda environment almost identically – including installed software and libraries, file structure and permissions, environment variables, context objects and behaviors – even the user and running process are the same.” We test our functions mocked and against local deployments of that lambci container . There also lambda “layers” (container images for building custom runtimes for AWS Lambda) but we have not used that feature at this point. Interesting space with lots of room for improvement in this tool chain though for sure