Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
keldaris
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
33 ms
·
271.
▲
by
keldaris
8y ago
> You seem to imply that security will always result in less speed or less usability, and that is not always the case. Certainly not always, but often enough and more so than usual with Spectre and Meltdown. > As an example of simplic
272.
▲
by
keldaris
8y ago
> They don't set defaults for the average use case when security is involved. They certainly set the defaults for some usecase, it just happens to be more security-biased than most. They don't ship an OS for an airgapped toaste
273.
▲
by
keldaris
8y ago
There's no backpedaling, I still think their approach is crazy for any practical usecase I care about. Beyond that, I simply expressed curiosity to learn more about the extent of the tradeoffs they're willing to make.
274.
▲
by
keldaris
8y ago
As I already implied in the parent post, I've no doubt we'll see more Spectre-like issues and I don't find it hard to believe that there's yet another embargo going on, that something's leaked again and that the Ope
275.
▲
by
keldaris
8y ago
> if an OS is as security conscious as OpenBSD, there isn't really a different way to operate That's really what I was getting at with my question. There's no such thing as absolute security, it is a set of tradeoffs betwe
276.
▲
by
keldaris
8y ago
So... they "strongly suspect" (but don't know and haven't shown) there may be a Spectre-class bug enabled by current HT implementations and improving their scheduler is hard, so they'll pre-emptively disable HT outr
277.
▲
by
keldaris
8y ago
Unequivocally, C. Futhark is clearly meant for reasonably high performance computing and I don't know of a single person in that domain that isn't a competent C programmer even if they spend a lot of time writing code in other lan
278.
▲
by
keldaris
8y ago
Thank you for the detailed response. I'll try to allocate a weekend to port some of my usual scientific GPGPU test cases to Futhark and see how it goes. > Most low-level GPU languages (like OpenCL and CUDA) make it very hard to wri
279.
▲
by
keldaris
8y ago
I didn't assert that more people know OpenCL than functional programming, I said far more people know C than functional programming. Anyone who knows C can write (bad) OpenCL after a trivial tutorial, so the initial barrier to entry is
280.
▲
by
keldaris
8y ago
How close is Futhark to being considered production-ready? How close is the generated code to hand-optimized OpenCL for real problems (I did look at the benchmarks, but only the Rodinia suite had comparison numbers, and those are trivial to
281.
▲
by
keldaris
8y ago
No, the point of this new feature is to add safety where you want it. That's not the same as mandatory safety. You can use the safe semantics throughout your codebase while retaining the option of direct ("unsafe") dereferenc
282.
▲
by
keldaris
8y ago
As much as I dislike most of "modern C++", the one thing they have consistently kept intact is that all the safety guarantees, at least insofar as they have performance implications, are optional. That's how it should be, by
283.
▲
by
keldaris
8y ago
How is this dynamic loading implented? Is it effectively a cross-platform wrapper over LoadLibrary/GetProcAddress/etc. (and their POSIX equivalents) or is there more to it? Is it possible to make link time optimization work with d
284.
▲
by
keldaris
8y ago
This begs two questions, it seems to me: 1. Would it make sense to work on (for the community in general, not necessarily you personally) a header only standard library, a sane STL if you will, for betterC? 2. Is there any interest in langu
285.
▲
by
keldaris
8y ago
What's the plan for Phobos (and more generally the ecosystem) to be usable from the betterC subset of the language? In your opinion, how much of the development focus is aimed in that direction? Are there any parts of the language itse
286.
▲
by
keldaris
8y ago
I don't quite share the level of optimism the author seems to have, but I hope he's right. If so, good riddance, just a shame it took this long.
287.
▲
by
keldaris
8y ago
> I think you can answer this question yourself :). This happens all the time in real world contracts. Some unforeseen, unspecified circumstances crop up, and an arbiter or judge decides whether and to what extent they fall under the exi
288.
▲
by
keldaris
8y ago
Okay, so you agree that in the absolute majority of cases users have no legal obligation whatsoever to watch ads, but you're interested in a hypothetical website that has constructive notice for terms of service that specifically inclu
289.
▲
by
keldaris
8y ago
I disagree with you on quite a few different levels and, for clarity, I'll attempt to separate them out in this reply. First of all, you've completely conflated the distinction between legal and moral obligations. Your entire argu
290.
▲
by
keldaris
8y ago
> I believe fundamentally that any content creator has the right to specify the terms by which their content is consumed. If one of those terms is 'watch the ads', then you are morally obligated to watch the ads. In addition to
291.
▲
by
keldaris
8y ago
The HN title still doesn't include it, so I certainly didn't open it because of it. The GitHub repository, however, includes it in the project name, so I thought my question was not inappropriate. I'm certainly not out to dis
292.
▲
by
keldaris
8y ago
Interesting. Have you tried generalizing that for higher dimensions?
293.
▲
by
keldaris
8y ago
Since the project literally has "Rust" in the title, I'm curious - do the authors view Rust as being particularly suited to this kind of project? From a quick glance it looks like the heavy computational work is done in OpenC
294.
▲
by
keldaris
8y ago
If the originals were uncoated, shouldn't it be very easy to just make your own and make sure it dissolves at exactly the rate you need? Regardless, always nice to see people using creative low tech solutions to serious problems.
295.
▲
by
keldaris
9y ago
OpenCL isn't dead, if you write your code from scratch you can use it just fine and match CUDA performance. In my experience, OpenCL has two basic issues. The first is the ecosystem. Nvidia went to great lengths to provide well optimiz
296.
▲
by
keldaris
9y ago
> deliberately implemented in a manner which allows the operators to intercept the vast majority of the chats on the platform. Could you elaborate on this please? Are you just referring to the fact that the default settings don't en
297.
▲
by
keldaris
9y ago
It's certainly not a precise comparison, you're right. Nevertheless, compare for instance x264 and x265. Exactly how large the difference between the two is depends on the type of content, bitrate, resolution and other factors, bu
298.
▲
by
keldaris
9y ago
> Yes, VP9 is basically on par with H.265 at standard resolutions, so if AV1 is 34% better, then it is a lot better than H.265. Is that really true, though? The most comprehensive test I've seen [1] led Netflix to conclude that H.26
299.
▲
by
keldaris
9y ago
> It's much easier to write C++ than it is to read it. This is because you can always write using a simple clear subset of C++ that you understand. Try to pick a style that you think as many people as possible will understand. Progr
300.
▲
by
keldaris
9y ago
"Our testing shows AV1 surpasses its stated goal of 30% better compression than VP9, and achieves gains of 50.3%, 46.2% and 34.0%, compared to x264 main profile, x264 high profile and libvpx-vp9, respectively. This sounds like AV1 is a
More ›