wspeirs
The SaaSpocalypse Is a Credit Event
Bcachefs Removed from Linux Tree
Candystore: O(1) KV Store for Rust
A high-performance, zero-overhead, extensible Python compiler using LLVM
Artificial Bee Colony Algorithm
Next-generation data science IDE
Slack Built Distributed Cron
Dont have F-You money? Build an F-You Network
A new programming language that compiles to Go
I Charge a $100k Software Licensing Fee for 10 Lines of Code
TSPP: A Unified Benchmarking Tool for Time-Series Forecasting
Profit Sharing Startups
Does anyone regret being an entrepreneur
Discord Modernized MFA with WebAuthn
Mfio – Completion I/O for Rust
An IDE plugin for Rust that helps you focus on relevant code
Youki: A container runtime written in Rust
Piston Window v1 Released
How to Build a Better Social Network
Stop deploying web application firewalls
Fixing ClickHouse Lock Contention
Basic idea is to have a system call that allows library writers to get the bounds of a pointer. This way they can ensure they're not writing too much data to a location.
Another idea I've implemented in userspace is to create an allocator that allocates a page (via mmap) then set protections on the page before and after. The pointer returned aligns the end at the next page. If a write goes beyond the end of the pointer, it bumps into the protected page, and causes a fault. Then you can handle this fault, and detect an overflow.
A even more strict version of this is to add protection to the page the allocated pointer is assigned to. On _every_ write you get a fault, and can check that it's not out-of-bounds.
All of these methods are slow-as-hell, but detect any memory issues. While slow, they are faster than valgrind (not badmouthing it, it's an amazing tool!). So the recommendation is to use it in testing and CI/CD pipelines to detect issues, then switch to a real allocator for production.
The State of Async Rust
Show HN: HN-demo.log-store.com HN comments and stories in log-store
TL;DR: I loaded all 37M comments and stories into a demo version: hn-demo.log-store.comI created log-store to scratch 2 itches: 1) I was bored while working at Meta/Facebook 2) I wanted to see if I could make Splunk.I accomplished 1 and got laid-off, and I'll let folks here decide if I accomplished 2.If people here want to get a feel for log-store, you can play with the demo site[1] or the HN...
I don't think this is true... It's more nuanced than this. Developers are much more skeptical of a "benefits" pitch, and care more about a "features" (and limitations as mentioned above) pitch. However, if you're just pitching a developer, you're probably only pitching the user, not the buyer. The buyer VERY much cares about the benefits, otherwise they're not buying. The buyer won't using a single feature, so that type of marketing is lost on them.
This is the challenge: the right message (features or benefits) to the right person (user or buyer) AND at the right time!
You can with log-store[1], as it allows you to run custom Python commands to do _exactly_ this!