raggi

29 ms·

391.
by raggi 3y ago
It'd be nice if the default was external symbols rather than none at all
392.
by raggi 3y ago
It seems actually FreeBSD has dropped a lot of old platforms in recent versions, so this may not be a problem anymore. I imagine it would be with some other BSD's.
393.
by raggi 3y ago
Yeah, the architecture point comes up in lost of rust in core type discussions, but I think when it comes to the BSD's it's actually a critical argument. I'm not particularly excited by limping along unusual architectures tha
394.
by raggi 3y ago
the doc site doesn't have this problem because it doesn't make a giant single archive of code that loads slowly on a single core. lighthouse doesn't even record the flash. most of the pages are getting 98/99 performance
395.
by raggi 3y ago
I see you citing usb armory a lot, but I haven’t yet seen any acknowledgement that it too is a go fork. Not everything runs on that fork, some things need patching. It’s interesting that you raise collaboration points here. When Russ was ge
396.
by raggi 3y ago
the x/ packages languish a lot, the problem is they follow a development model that slows the rate at which new contributors succeed to send patches The stdlib crypto package I would describe as another of Go's big successes. Open
397.
by raggi 3y ago
I worked on Fuchsia for many years, and maintained the Go fork for a good while. Fuchsia shipped with the gvisor based (go) netstack to google home devices. The Go fork was a pain for a number of reasons, some were history, but more deeply
398.
by raggi 3y ago
Windows Copilot answers (down the middle between github copilot and chatgpt): https://gist.github.com/raggi/eb42ebb04717e055678bffdec98c3e...
399.
by raggi 3y ago
Current Github Copilot chat answers (atrocious!!!): https://gist.github.com/raggi/2118c5caac63acd899dd782388bab1...
400.
by raggi 3y ago
Current Chat GPT 4 outputs: https://chat.openai.com/share/babb5d95-8220-48d3-b540-cc0314...
401.
Do Users Write More Insecure Code with AI Assistants?(arxiv.org)
5 points by raggi 3y ago|4 comments
402.
by raggi 3y ago
There are real integration challenges with the "simple file approach": - File locking and concurrency - Atomic writes / moves - Realtime change observations > clumsy use of regedit does have a chance of totally
403.
by raggi 3y ago
CC, CFLAGS and LDFLAGS conventions, and freshness checks (if you do it twice, it won't build again as it performs an mtime check on the source).
404.
by raggi 3y ago
If you want to write less makefile, you don't need to define foo. `foo` is an implicit target if foo.c is present. You can use make in this form without a makefile even: ~ % echo '#include <stdio.h>\nvoid main() { prin
405.
by raggi 3y ago
I campaigned for this for years when working on fuchsia, to folks in fuchsia and android folks. We lack a unixy API for “the radio is now on, do your reconnects or send your queues” The platforms always hoist this stuff higher level and it
406.
by raggi 3y ago
For zlib compatible workloads, there are cloudflare patches and chromium forks, intel forks, and zlib-ng which are compatible but >50% faster. (I think the cloudflare patches eventually made it into upstream zlib, but you may not see tha
407.
by raggi 3y ago
The answer is good, but is missing a key section: Salty form: They're all quite slow compared to modern competitors.
408.
by raggi 3y ago
I see so many organizations add weird slowdowns from debts associated with this. I reflect on some of the most successful tech businesses of the last decade and remember that all their APIs exposed this kind of data early on and many still
409.
by raggi 3y ago
Oh, and if you want to see some real experience writing an OS in Rust, there's someone regularly streaming their experience here: https://www.twitch.tv/sphaerophoria . I've stopped in a few times, they're doin
410.
by raggi 3y ago
> If there are any Rust experts around...what am I missing? Probably more good examples and possibly more ecosystem. A first big decision is if you're going no-std or not, and if you end up in the no-std world the ecosystem shrinks
411.
by raggi 3y ago
macOS LLVM is a bit of a special distribution. It's nice that there's a mostly well built LLVM distribution there, but the pain in the ass is that they ship a custom linker and _don't ship lld_, which means you can't rea
412.
by raggi 3y ago
It's "ok" along these axes, a bootstrap for gcc isn't all that straightforward either, the main difference being that if you've already done "apt install build-essential" or similar it just so happens that
413.
by raggi 3y ago
They need computers. I'd assume this came with a substantial budget promise.
414.
by raggi 3y ago
It's worth noting that the proxy and pinning behavior actually help with scope a fair bit. The threat is still there for new versions, but both visibility and external controls can still help.
415.
by raggi 3y ago
nope, just inconvenienced
416.
by raggi 3y ago
One I've noticed growing a gap in recent years is "attribute" which when I used to know as having different pronunciations for the verb and the noun. The links given for different English dialects demonstrate a conflicted ran
417.
by raggi 3y ago
Learning when to invest in type constraints and when not to is an important lesson. It’s not unique to rust, though it might express a little differently. I’ve dealt with excessively typed c++ and excessively abstracted and typed Java and t
418.
by raggi 3y ago
Is this an explicit feature of the wasm runtime in use here, or might this break with future optimizations in the runtime and the introduction of threads and other similar features?
419.
by raggi 3y ago
Correct, it's an alternative to the advertising model, which is what it was a response to.
420.
by raggi 3y ago
YouTube offers an alternative model: YouTube premium.

More ›