hctaw

22 ms·

181.
by hctaw 6y ago
Overwriting executables during a build rather than copying them at the end can be problematic if a build artifact is used to bootstrap itself (like a compiler). If the build fails you can't try again.
182.
by hctaw 6y ago
Yes, a tail recursive coroutine could reuse its previous frame context across yields. With a state machine transform the `resume()` method on a coroutine is a state transformation, it doesn't necessarily know what is "forward&quot
183.
by hctaw 6y ago
You don't need async-std for coroutines (generators) in rust (or async at all, they are two different, albeit related features). Async is implemented using generators.
184.
by hctaw 6y ago
Is that a given, though? Rust's generators are decent prior art - they generate a state machine that would only require heap allocation if the size of the state machine becomes unbounded (for example, a recursive generator). Otherwise
185.
by hctaw 6y ago
Modern stackful coroutines don't (or shouldn't) use context switching (at least not anything like ucontext_t, just use threads if you're going to spend the cycles to preserve the signal mask) or setjmp/longjmp. Those tri
186.
by hctaw 6y ago
> but can I await a function, which awaits another, and so on? Whether a coroutine is stackful or stackless is largely an implementation detail that has some tradeoffs either way, in either case coroutine semantics can allow you to write
187.
by hctaw 6y ago
Are C++20 coroutines allowed to be recursive? Or does recursing require boxing? For a stackless coroutine the compiler normally has to build a state machine to represent the possible execution contexts, but if the state machine includes its
188.
by hctaw 6y ago
They're obviously not, but they're the ones that package managers can help mitigate automatically. The rest is going to be up to the developers to patch.
189.
by hctaw 6y ago
I'd disagree that the problem of large organizations are different from the problems of the FOSS ecosystem. Organizations just have a financial incentive to fix them, the FOSS ecosystem does not. If mutually incompatible dependencies a
190.
by hctaw 6y ago
The day I stop static linking is the day I can compile on one distro and ship to many without worrying about users reporting loader errors. That day is not today. Until then, I'll keep doing it, because it saves me time and money. I do
191.
by hctaw 6y ago
> The distribution / maintainer / package manager approach has proven to be an extremely reliable way to get trustworthy software. Many of us love it and want to see it stick around. I disagree, it's proven to be inadequat
192.
by hctaw 6y ago
What about iterator invalidation or multiple mutable aliasing in concurrent code
193.
by hctaw 6y ago
I've never had a customer report performance issues relating to memory usage or a market analysis that suggested we should improve memory size or disk space used in the binaries we ship. What I have gotten are expensive bills for netwo
194.
by hctaw 6y ago
I was going to comment this elsewhere, but workstation class problems require workstation class solutions. If 16GB isn't sufficient for your work you should upgrade. Unfortunately Apple has stopped making competitive workstation laptop
195.
by hctaw 6y ago
you can't buy an M1 mac with more than 16GB of memory so it seems like you have bigger problems
196.
by hctaw 6y ago
I didn't say I was shipping GUI software ;)
197.
by hctaw 6y ago
As a developer shipping executables to MacOS, Windows, and Linux today this is the only assumption I can make. I cannot assume that dependencies exist or are the correct version, I can't assume the user knows that package managers exis
198.
by hctaw 6y ago
On the homes, offices, and industrial parks surrounding the vertical farms as well.
199.
by hctaw 6y ago
The greater problem to solve is maximizing nutrition for communities while minimizing the carbon costs of providing it. Vertical farms fit into that equation by moving production closer to the people that eat the produce, and making it more
200.
by hctaw 6y ago
They've been trending the last couple days.
201.
by hctaw 6y ago
I don't think fees are as large a problem as competing against first party apps in the same marketplace that don't pay the fees or have the same restrictions. iMessage for example doesn't require granular permissions for phot
202.
by hctaw 6y ago
> A mapping application having features which really don't save lives 99% of the time. And ruins thoroughfares not designed for heavy traffic, while degrading quality of life for people who don't use it!
203.
by hctaw 6y ago
> But let's hit the random button on wikipedia and pick a sentence, see if you can draw a picture to convey it, mm? To be needlessly pedantic, my computer drew the image that conveyed this to me. Less pedantically text is a medium o
204.
by hctaw 6y ago
That's not a nitpick, it's a legitimate issue with the chip. 8 cores is not consistent with the state of the art, it's consistent with low tier consumer CPUs. The other major issue is lack of memory (just by way of example, I
205.
by hctaw 6y ago
I think OP is taking issue with the claim that the M1 can compete with desktop class CPUs, which isn't true for multicore benchmarks. The M1 is about on par with current Intel/AMD offerings in single core benchmarks but can't
206.
by hctaw 6y ago
It's more about charging prices based on what customers are willing to pay rather than a fixed price. In B2B sales you can swing much higher prices from bigger clients for the same thing, but that's harder if they know what you ch
207.
by hctaw 6y ago
Make a landing page and create a real email. Set up a form to schedule demos.
208.
by hctaw 6y ago
Rust doesn't have a runtime so you're good
209.
by hctaw 6y ago
I don't know how best to articulate this, but it would be something like "Walter Cronkite never gave you a narrative." I don't think the fallacy lies in the power of institutions or print but the human desire to attribut
210.
by hctaw 6y ago
I thought flame baiting was against the rules here

More ›