fl0ki

21 ms·

181.
by fl0ki 3y ago
An important clarification is that the leaks about NSA snooping on Google motivated end-to-end encryption between all pairs of Google internal services. It was a technical marvel, every Stubby connection had mutual TLS without any extra c
182.
by fl0ki 3y ago
> an incremental path towards a memory-safe subset I was always extremely skeptical of this claim. Let me take the best case here: in a few years, a language called Carbon exists which interfaces seamlessly with C++ code while also havin
183.
by fl0ki 3y ago
A very common failure mode I see even among experienced senior engineers is to talk about the availability only of their endpoint, not the user experience of the system to meaningfully address user requests. Well-intentioned SLOs around err
184.
by fl0ki 3y ago
Wherever we have enough redundancy that we have to tell a tool to write out more code for us within certain parameters, is somewhere we have yet to create the right high-level abstractions. This remains a problem even after LLMs do some of
185.
by fl0ki 3y ago
Would there be value in distinguishing -0 and +0? If a 0 was quantized from a small negative or a small positive, it seems like retaining the sign is better than forgetting it. The question remains whether the benefit and the simpler design
186.
by fl0ki 3y ago
Ah yes, the latest post about a marginal security concern leading neatly into an advertisement to give money to an LLM startup to address it only partially and at best probabilistically. If you're a potential customer for something lik
187.
by fl0ki 3y ago
On top of that, metrics can have exemplars, which give you more (and dynamic) dimensions for buckets without increasing the cardinality of the metric vectors themselves. It's pretty much a wide event, with the sampling rate on this ext
188.
by fl0ki 3y ago
This being HN, I thought this was going to be about SwissTable. I'm going to go touch grass now.
189.
by fl0ki 3y ago
I'm horrified to say that individual bugs we make can cost our large employer millions, yet leadership still overloads people with multiple projects on tight deadlines and loose engineering standards. I'm talking about global cont
190.
by fl0ki 3y ago
Your null implementation did help put it into context to some extent. Even then, in general, the API surface sufficient for a null implementation may not be enough for some real implementations. What if at least one real implementation ende
191.
by fl0ki 3y ago
I find Rust the language does make it possible to avoid allocation and copying for lots of types, but the library ecosystem hasn't agreed on types to do that in API boundaries. You often end up with e.g. `String`, especially in async l
192.
by fl0ki 3y ago
I've worked in environments where we had several people per large project and reviewers could genuinely point out important context from parts of the project they were more familiar with. It was an awesome environment for learning not
193.
by fl0ki 3y ago
> In theory, Rust allows even better optimizations than C thanks to stricter immutability and aliasing rules, but in practice this doesn't happen yet. Optimizations beyond what C does are a work-in-progress in LLVM, so Rust still ha
194.
by fl0ki 3y ago
I'm one of the most obsessive team members when it comes to commit / PR size and hygiene. I want each PR to change just one thing, for the commit title to uniquely identify it, and the rest of the commit description to explain eve
195.
by fl0ki 3y ago
I agree it's too long for an email, but it could be a reasonable length for a document that could avoid years of engineering costs. I'd still start with a TLDR section and maybe have a separate meeting to get everyone on the same
196.
by fl0ki 3y ago
They chose to put their name on gibberish, anything you politely call out as flawed is now on them. This time, pick just a couple of issues to focus on. Don't make it so long they're tempted to use GPT again to save on reading it.
197.
by fl0ki 3y ago
> Don't start with a complicated architecture because "well once we scale, we will need it". > You want the architecture to support growth that will more than likely happen The problem is even very experienced people ca
198.
by fl0ki 3y ago
Nice. If this can be reasonably retrofitted to existing libraries and projects so that the safety properties compose from local to global, then this could actually be a meaningful improvement to the safety of real-world C code. There would
199.
by fl0ki 3y ago
I'm not tuned in to the nuances here but I note that whoever felt they understood it well enough to update Wikipedia summarized this as "The C23 standard makes VLA types mandatory again. Only creation of VLA objects with automatic
200.
by fl0ki 3y ago
Variable Length Arrays were mandatory in C99, optional in C11, and are mandatory again in C23. I'm curious how these dynamics play out in less popular compilers. If a compiler implemented VLAs in C99, they almost certainly still have t
201.
by fl0ki 3y ago
And still not even mandatory if you use -fpermissive or -std=c89. I don't envy how much tech debt they have to deal with, while still trying to make it possible for new code to have a more modern experience. For all the excitement arou
202.
by fl0ki 3y ago
Maybe a more specific way to put it is: you only pay for the (combinations of) types you actually use, whether that's in argument position, return position, or even a local binding. So if it's always Vec<T> it's not cos
203.
by fl0ki 3y ago
There are definitely systems out there that can get away with being built primarily through kanban boards and fungible coders of average skill. The industry has decided that this is the default "best practices" for keeping a team
204.
by fl0ki 3y ago
Check if you have an old email or phone number tied to the account. Attackers can get Microsoft to send one-time codes to them, no matter what else you have set up on the account. Worse, it seems this feature was added some time ago and eve
205.
by fl0ki 3y ago
Please bear in mind that Linux has used non-standard GCC extensions to C for decades as well. The tradeoffs here are their call to make. Besides, at this stage, it makes perfect sense for Linux to use unstable Rust features. It was one thin
206.
by fl0ki 3y ago
That might be true for Hello World, but libgcc_s is where a lot of builtins for C itself go, so you'll find it ends up linked into a lot of non-trivial C programs as well. See https://gcc.gnu.org/onlinedocs/gccint&
207.
by fl0ki 3y ago
I agree, but I have yet to see a single real-world example of a Rust project meaningfully reducing its binary size by switching from monomorphization to dynamic dispatch in its own code. Many Rust developers boast that they virtually never
208.
by fl0ki 3y ago
The printing machinery alone is quite large when you consider that it includes the code & raw data for Unicode, whether or not similar facilities were already available on the host libc. Though you're not likely to avoid that in an
209.
by fl0ki 3y ago
When any new tech gets hyped enough, some people instinctively drag it, if not for technical reasons then for aesthetic and social ones. If the worst thing people can say about HTMX is that its creator posts memes, the tech itself must be d
210.
by fl0ki 3y ago
> The anti-Lisp is something like Go. Simple, not very flexible, everyone does it the same way mostly, you can plug & play developers like scrum demands we do. This has not been my experience with Go. The only areas where Go actually

More ›