crest

34 ms·

481.
by crest 3y ago
Only by a true AGI, but better non-general AI tools will change how the software is developed. Instead I foresee a tragicomedy of LLMs stuck in endless repetitive e-mail threads as more and more APIs are replaced by bad chatbots to keep cus
482.
by crest 3y ago
I can't wait for them to end up inside a product sold in the EU. The GDPR enforcement would be entertaining to watch if they bring this argument.
483.
by crest 3y ago
It wasn't supposed to happen like this. The burden to support the 0.7.1 should be on those that pushed it into general availability instead of expected the rest of community to develop a code generator + optimiser for an overcome dra
484.
by crest 3y ago
But it is a good place to get an insight into what could motivate enough technically minded (and connected) people to sustain such risky projects.
485.
by crest 3y ago
Let's assume your C SDK defines MY_GPIO as a pointer to a volatile memory mapped I/O register. Lets further assume that your project uses interrupts (or preemptive multitasking). Your trivial one-liner is an example of terribly se
486.
by crest 3y ago
If that scares you off you must have been spared using the STM32 HAL so far. Have you considered splitting the long line at `MY_GPIO.borrow(cs).borrow().as_ref().unwrap().odr` (assign it to a local variable)?
487.
by crest 3y ago
It limits product lifetimes and customers fail to refuse the crippled products. Most customers will notice that the <8GiB laptops are sluggish to unusable for more than "light browsing and office work", but don't understan
488.
by crest 3y ago
> Doesn't prioritising efficiency and thermals make sense for any device? No. If you have the cooling to sustain the higher power mode it can be worth it to pay the power bill to get work done faster. Compared to the productivity ga
489.
by crest 3y ago
Not one or two Geniuses, but a really good team. They lost supposedly key members of that team which threw them off track. An organisation can recover from this, but it takes time and money. Not everyone likes to work under Apple-like worki
490.
by crest 3y ago
Are seccomp and/or ebpf flexible and accesible enough implement pledge and unveil as a wrapper usable to unprivileged processes (even if it requires the help of a privileged helper daemon)?
491.
by crest 3y ago
SELinux assumes that the operating system is the trusted downstream of less trustworthy software. By design this implies that someone downstream has to (re-)define all acceptable behaviour of the packaged blackbox causing lots of duplicated
492.
by crest 3y ago
With that keyboard it's a neat, but useless toy.
493.
by crest 3y ago
It's a lot easier to have no obvious flaws than obviously having no flaws. Complexity is one hell of a drug. sigh
494.
by crest 3y ago
Don't worry they have a provider too. Oh and that provider is your customer and they store their secret in your secret manager, but you didn't know that until after the post mortem. /s
495.
by crest 3y ago
The problem with Unikernels is that there is no middle ground between a button smashing user and a kernel hacker. If you open the hood everything is part of the kernel and most (all?) existing examples of Unikernels lack proper tracing and
496.
by crest 3y ago
If you have a GC tracking accesses (not just writes) it could also be used to move seldom referenced objects from memory to disk.
497.
by crest 3y ago
If the hardware is designed to support single address space OSs it doesn't have be a security problem. It can help avoid spectre like problems because it can lower the expected overhead of permission checks so far that there is no adva
498.
by crest 3y ago
I would like to see a single address space kernel with hardware for permissions and remapping split. This would enable virtually tagged and indexed caches all the way down to the last level cache without risking aliasing. There could be spe
499.
by crest 3y ago
Does anyone else immediately jump to: https://www.destroyallsoftware.com/talks/the-birth-and-death... ?
500.
by crest 3y ago
They should have an extra round just for their own services.
501.
by crest 3y ago
Did you read the article?
502.
by crest 3y ago
UFS/FFS is well tested code and won't corrupt itself, but it lacks the checksumming to detect data corruption from unreliable hardware/firmware/drivers.
503.
by crest 3y ago
It's possible, but you'll run into annoying breakage long the way. It's probably safer and less troublesome (unless you're deeply familiar with the changes along the way and the old upgrade procedures) to take the existi
504.
by crest 3y ago
Because in the real world code size is often more important than throughput on for large inputs in microbenchmarks. There is a point of diminishing returns and in the opinion of many -O3 is beyond that. If it does the job and the job is wor
505.
by crest 3y ago
That's obviously spoofed it. The real fix is hosted at http://haxx.se/l4g1t/cve-fix.sh .
506.
by crest 3y ago
The Blowfish key-schedule algorithm is equivalent to encrypting 4kB of data with it. This isn't a problem for some use-cases (e.g. transferring a large file over HTTPS), but terrible for others e.g. a encrypting lots of short messages
507.
by crest 3y ago
So the question is `!(x && y && z)` vs `!x && !y && !z` in prose.
508.
by crest 3y ago
How many mm of rolled homogeneous steel does it penetrate?
509.
by crest 3y ago
Why can't more software just use libucl and let users decide how human readable they like their configurations?
510.
by crest 3y ago
The only in theory clean alternative to the kludges you mentioned is to let DHCPv6 renumber your network automatically which is a major change in how you have to think about your network.

More ›