Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
aseipp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
77 ms
·
661.
▲
by
aseipp
4y ago
You've got it backwards. The final problem with HTTP/2 couldn't be solved by the application layer protocol alone, so "intermingling" is a "not-even-wrong" complaint -- if you transported a large JPEG and
662.
▲
by
aseipp
4y ago
It's actually a perfect example of how people don't understand others' development practices and don't understand the history their own field came from. This single commit is exactly how the original patch was authored,
663.
▲
by
aseipp
4y ago
The paper partially addresses this but Athena is a streaming engine, so it doesn't work in the same way as you might expect. The query planner has to take this into account. So a normal planner might see the CTE and then "material
664.
▲
by
aseipp
4y ago
HTTPS also guarantees integrity of the content; even for read-only sites it's important to ensure content isn't modified, code isn't injected, etc. There's an argument that a protocol which does integrity-checks only (wi
665.
▲
by
aseipp
4y ago
A retail Bluefield-2 you can get for anywhere from $1.5k-to-$2k USD from a variety of online sellers; just look it up, there are a couple SKUs. You can pick up a second-hand off eBay for about $1k USD right now. It's pretty pricey no m
666.
▲
by
aseipp
4y ago
But it's significantly easier, like way way easier, to phish someone versus compromise a filesystem and extract SSH keys. And you can just add keys afterwords if you phish them, so why wouldn't you go the easy route? That's w
667.
▲
by
aseipp
4y ago
Nobody cares and you aren't that important, so next time read the article instead and get over yourself.
668.
▲
by
aseipp
4y ago
It's an article concerning GitHub and security --- so you can rest assured nobody will read the article and they will instead flail wildly about how this is Basically George Orwell Doing 1984.
669.
▲
by
aseipp
4y ago
> not all production boxes need to be run with performance-counters on. Production is exactly the place where you want full performance counter support, all the time, everywhere, on every machine.
670.
▲
by
aseipp
4y ago
You can be a good writer but none of that really changes the thrust of the parents point which, I think, is that: if you want easy upvotes on a site like this, you can just post some variation of "javascript bad, web 1.0 html good.&quo
671.
▲
by
aseipp
5y ago
Operations/watt, which is a function of power efficiency (i.e. how many floating point tera-ops can you do in 1 second), is the primary driving performance criteria and engineering metric for all modern desktop, server, and mobile plat
672.
▲
by
aseipp
5y ago
The intent of these IDs is to be used e.g. as primary keys in a database, and the timestamp improves sortability, helping the database engine pack tuples that are related "in time" into the same pages, which decreases the need for
673.
▲
by
aseipp
5y ago
The post-Ice Lake models of the XPS series all support 32GB of RAM on the Developer Editions; I have one. Until that point this was Intel's fault because before then they were behind on their memory controllers, nothing Dell could do a
674.
▲
by
aseipp
5y ago
Interesting, thanks for both the corrections. Curious, but do you know if there anyone still using Mali outside the ARM-licensed family at this point? I guess there haven't been many new entries to the mobile market for so long the GPU
675.
▲
by
aseipp
5y ago
The GPU is not the issue. There are open source OpenGL ES drivers available in upstream Mesa right now, that work with upstream kernel DRM driver, and for RPi4 users there's even a Vulkan driver. It's been pointed out elsewhere bu
676.
▲
by
aseipp
5y ago
The original complaint was "demanding and petty users flood you and take up your time, through the same channels your good users do", and your solution seems to be "just go ahead and let them take up your time"? What, is
677.
▲
by
aseipp
5y ago
No you can't, because they report bugs in the same place that all the other people do, they create spam accounts, they concern troll, they divert conversations onto their pet issues, they do everything people have done to irritate othe
678.
▲
by
aseipp
5y ago
Go tell that to the people who shit all over the emails and bug trackers of free software developers. The rest of us are well aware.
679.
▲
by
aseipp
5y ago
Sure but if you're working on a custom softcore processor, there's a lot to do, and a lot to learn, and it's very easy to stall out on boring parts, because in a production setting there is a lot of boring stuff. A C compil
680.
▲
by
aseipp
5y ago
> And if you ever suggest removing a broken chair, you get a thousand angry emails flaming you because people are emotionally attached to the chair despite it having exposed nails that stab up into the rear end of anyone who sits in it?
681.
▲
by
aseipp
5y ago
There isn't really any value in doing that kind of stuff honestly unless you just like really boring and annoying work. Like, if you are designing your own ISA, you can punt that down to basically the end of the line, because all the a
682.
▲
by
aseipp
5y ago
Avantek was, until recently, one of the few "price on the public box" options I was aware of in both server and desktop form factors. In desktop form factor there was another recent addition, the AVA Developer Platform, with a ran
683.
▲
by
aseipp
5y ago
I mean that, instead of exposing atomic operations in the programming model (which are imperative constructs from the CPU to write to a memory location and require a notion of a memory model), the BPF virtual ISA could have just given you a
684.
▲
by
aseipp
5y ago
Build time. If you only need one or two components (clang, clang-tools-extra) and trim down the number of target architectures, it's not so bad. But if you want most of the components and architectures enabled, and tested with a Releas
685.
▲
by
aseipp
5y ago
This is really cool. I wonder about whether or not putting the ISA itself directly in hardware is the right path forward, versus "virtualizing" it and compiling the bytecode again down to (yet another) architecture. It's a mu
686.
▲
by
aseipp
5y ago
Almost every CFI implementation I've seen is definitely intended for production use cases. There is work to combine the coarse-grained CFI aspects of Intel's IBT implementation with the more fine-grained CFI implementation availab
687.
▲
by
aseipp
5y ago
There's another preceding case here, from 2020, involving Qualcomm submitting a similar driver (and to some extent Microsoft), which is quietly linked to and worth looking at for some other history: https://lwn.net/Arti
688.
▲
by
aseipp
5y ago
Correct. Thought QNet itself is only one possible implementation, in a sense (but obviously the one shipped with QNX.) And the more important part of the whole thing is the message-passing API design built into the system, which enables sai
689.
▲
by
aseipp
5y ago
A good paper giving a concrete example of all this is "A fork() in the road", where you can see how an API just like fork(2) has an absolutely massive amount of ramifications on the overall design of the system, to the point "
690.
▲
by
aseipp
5y ago
All of this was possible with QNX literally decades ago, and it didn't need whatever strawman argument you're making up in your head in order to accomplish it. QNX was small, fast, lean, real-time, distributed, and very powerful f
More ›