Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
roca
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
71 ms
·
751.
▲
by
roca
6y ago
If you insist that the difference between "lockdown" and "no lockdown" is whether the authorities back their restrictions with legal authority, it makes the term "lockdown" meaningless and you should stop talki
752.
▲
by
roca
6y ago
More relevant practical experience: NZ's lockdown shows that we were able to eliminate COVID19 within the country. Six weeks of a pretty hard lockdown followed by six more weeks of gradual relaxing of restrictions.
753.
▲
by
roca
6y ago
Having zero cases all the time is remarkably hard but it's also not that important. A lockdown-to-elimination strategy is working well if you can keep driving the number down to zero with low restrictions in place. In NZ it is working
754.
▲
by
roca
6y ago
Test positivity in Sweden has been rising steadily and is now over 10%. So no, it's not "broader access to testing" --- in fact they aren't testing nearly enough and the rise in case numbers is probably even steeper than
755.
▲
by
roca
6y ago
Tegnell predicted that his approach would avoid a serious second wave in the autumn. He has admitted he was wrong about that: https://www.thesun.co.uk/news/13208429/sweden-lockdown-covid... That's a pretty bi
756.
▲
by
roca
6y ago
> "lockdowns may not be necessary to achieve reasonable results." Even so, Sweden doesn't prove this. They have had lockdowns, e.g. severe limits on social gatherings. You can only say they haven't had lockdowns if yo
757.
▲
by
roca
6y ago
People keep saying this but it's misleading. Swedish authorities have issued many directives that weren't legally enforceable but which they expected Swedes to follow, and most Swedes did follow them. Surely whether or not a direc
758.
▲
by
roca
6y ago
This is a good point. However it just means that once the industry decided to allow some DRM-free distribution of most/all content, a DRM boycott worked. Unfortunately it is still true that where the industry does not allow any DRM-fre
759.
▲
by
roca
6y ago
> We in fact tried, and mostly succeeded, in boycotting DRM when it was cumbersome, full of bugs, and annoyed users in the early 2000s. I wonder what the author could possibly be talking about. The only boycott that could be effective is
760.
▲
by
roca
6y ago
To help with this we've added a new "volume subscription plan" for individual users: 50 submissions per month for $50.
761.
▲
by
roca
6y ago
Usually they break rr by either blocking access to the hardware PMU entirely (e.g. on AWS, any instance that shares a CPU socket with other instances; on Azure/GCP, everywhere AFAIK), or by introducing subtle errors into the virtualize
762.
▲
by
roca
6y ago
The main thing is that rr recording needs access to the PMU. So generally AWS Nitro instances which occupy a whole CPU socket (or more than one) work. In particular AWS c5(d).9xlarge and larger are known to work. Other instance types (inclu
763.
▲
by
roca
6y ago
Yes, you can instrument simulators to get record-and-replay. Simics has a record-and-replay feature like that, so does QEMU lately. I don't know of anything specifically for microcontrollers but it certainly could be done.
764.
▲
by
roca
6y ago
The average session. Of course it's impossible to know the actual average number for any given developer but we often get developers estimating Pernosco saved hours, occasionally days, or occasionally the bug couldn't have been so
765.
▲
by
roca
6y ago
I suppose an option to run the same checks in rr at recording time would be a fine feature to have ... though you could implement it pretty easily as a wrapper script too.
766.
▲
by
roca
6y ago
Note that the pernosco-submit script supports detecting "sensitive" environment variables leaking into the recording: https://github.com/Pernosco/pernosco-submit/blob/a6119a1b291... And we accept PR
767.
▲
by
roca
6y ago
The service model is not just about monetization. It enables collaboration features that are really useful, e.g. https://pernos.co/about/browser Resource utilization is also an issue. To accelerate the debugging experi
768.
▲
by
roca
6y ago
We would love to talk about on-prem with those corporations --- contact us!
769.
▲
by
roca
6y ago
Yeah, Pernosco may not be a great fit when you have to do that. That's not just due to the pricing model --- which we can change! --- but the entire debugging approach, where we do a lot of analysis up front, speeding the debugging exp
770.
▲
by
roca
6y ago
> I assume it's still usable as a local rr-GUI (that hopefully adds something) without submitting? No. > I get that you are still looking for a model, but I would much more expect something like "my employer pays $X00 or $X0
771.
▲
by
roca
6y ago
We often get users estimating that a Pernosco session saves them half an hour or more. Let's say on average it saves 15 minutes. Let's say a reasonable developer's time is worth at least 50 USD an hour. Then Pernosco is givin
772.
▲
by
roca
6y ago
The comparison with other languages seems to miss the fact that the idiomatic approach in Rust and C++ is RAII, which does let you put the cleanup code next to the allocation code.
773.
▲
by
roca
6y ago
I'm sorry to hear that, but making false and intimidating claims about copyright doesn't help your situation.
774.
▲
by
roca
6y ago
The context and motivation are irrelevant. As a statement of fact the claim is simply false.
775.
▲
by
roca
6y ago
Their claim is simply incorrect. Copyright does not protect ideas. Claiming that they can infect ideas with the GPL is bizarre and deceptive bullying.
776.
▲
by
roca
6y ago
https://en.wikinews.org/wiki/New_Zealand_repeals_sedition_la... Of course, even if we did have a sedition law making it illegal to call for a putsch against the NZ government, that wouldn't make it illegal to call
777.
▲
by
roca
6y ago
We don't have an extradition treaty with China and we suspended our extradition treaty with Hong Kong because we don't trust the CCP, while we still have an extradition treaty with the USA, so that's one difference. Another d
778.
▲
by
roca
6y ago
Thanks! Sounds interesting, but it's not obvious to me that such a framework can't be captured in the Rust type/ownership system in a reasonably ergonomic way. Has anyone even tried doing that? For example you might be able t
779.
▲
by
roca
6y ago
The safety guarantees of Rust are much stronger than Zig's. For example Rust statically prevents use-after-free and data races, and Zig doesn't (and I don't think anyone expects it ever to). To me this matters more than which
780.
▲
by
roca
6y ago
The problem is that safety means, by definition, ruling out unsafe code at compile time or run time. If you don't prioritise safety early then you run a high risk of discovering when you try to retrofit safety later that you need to ru
More ›