uluyol

20 ms·

181.
by uluyol 5y ago
> The Internet is designed on an end-to-end principle Yes, this is true, and the end-to-end principle is great. But it's not always straightforward to follow, and certainly is not a religion. In the end, no one cares about the end-t
182.
by uluyol 5y ago
Wow geez. There's been a lot of BS being thrown around about Cloudflare. I don't work for them, but I have been following the company for years. On Cloudflare being a gatekeeper: yes, if you care about load, cost, and attacks, you
183.
by uluyol 5y ago
jq is a fantastic tool for exploring data and doing simple transformations. I often wish it could consume/write data in other formats.
184.
by uluyol 5y ago
Any examples?
185.
by uluyol 5y ago
Of course. That makes sense. Thanks!
186.
by uluyol 5y ago
Is Java really memory safe in the face of races? The case I'm thinking about is this: Shared state: ArrayList A with intial buffer B and length L Thread 1: Grows A and replaces B with buffer C, length with M Thread 2: (Earlier loaded B
187.
by uluyol 5y ago
Ever seen a two-stroke lawnmower at work? Engine tech makes a big difference, as do catalytic converters.
188.
by uluyol 5y ago
Amazon, Microsoft, and Google have massive applications and systems that they run, some of which they sell as a service. They have plenty of workload data without having to poke around user VMs.
189.
by uluyol 5y ago
The signal based mechanism is only used for stragglers. Go still uses the function call check. The runtime devs found a way to combine it with a check to see if the goroutine's stack needs to be resized, so it doesn't actually cos
190.
by uluyol 5y ago
I think there's still some confusion. Why does the GPU need to handle more than one flavor of Y'CbCr? Why can't the jpeg/PNG/whatever decoder be relied on to convert whatever flavor it uses to the Direct X/Open
191.
by uluyol 5y ago
I don't think he's asking for video cards to natively handle JPEG images. ISTM what he is advocating for is keeping the JPEG decompressed in memory in a YUV format rather than RGB. The savings come from the fact that the UV part
192.
by uluyol 5y ago
Run lots of VMs and sell them to others... Various hardware costs get more expensive over time, so the fix is to make things bigger to amortize those costs. I think that even big players don't like running big instances (Google, Facebo
193.
by uluyol 5y ago
I don't think this is an issue with the latest models.
194.
by uluyol 5y ago
Various parts of Python's standard library are implemented in C for performance. E.g. see https://lwn.net/Articles/725114/ under "Optimizations"
195.
by uluyol 5y ago
True, but we have a kernel networking stack with a certain interface and a rich feature set. The kernel cannot break that API. In contrast, a new userspace stack doesn't need to worry about backwards compatibility or supporting every u
196.
by uluyol 5y ago
WRT large PRs, it doesn't sound like they expect all the improvements to be from small changes. I think the point is the code will be changed in increments so that even large changes (overall) will be easier to review and offer feedbac
197.
by uluyol 5y ago
This should be possible. I think it is important for scientists to do both novel and replication studies. One way to improve on the status quo would be to make students do both types of work (the point of a PhD is to demonstrate that you ca
198.
by uluyol 5y ago
> 1. Intel server CPU are usually generation behind customer ones, so they are little younger than one may think Yes but big customers get significantly earlier access than the general public. See how Intel shipped 110k+ units pre-launch
199.
by uluyol 6y ago
If it's FUD then it's been going on for over a decade. Back when Intel was ahead, people would say things like "Intel is first to 32 nm and has a better process than other fabs. So TSMC/GloFo/etc. won't catch u
200.
by uluyol 6y ago
Intel already said they would use chiplets [1] and TSMC has been talking about the various packaging technologies being developed [2]. [1] https://www.anandtech.com/show/16021/intel-moving-to-chiplet... [2] https
201.
by uluyol 6y ago
Isn't this probably because most developers have shifted focus on PipeWire? I thought both came from more-or-less the same community?
202.
by uluyol 6y ago
Size, heat, weight, and noise are more challenging for laptop design than desktops. Desktops tend to have things spread out much more and you just don't care about some of these issues.
203.
by uluyol 6y ago
https://opensource.google/projects/pdfium Seems to be derived from Foxit.
204.
by uluyol 6y ago
QUIC is TCP+TLS. HTTP is done as a separate layer on top. The benefits are: future protocol evolution (TCP is extremely difficult to change because of middleboxes, QUIC encrypts almost all of the header to stop middleboxes from messing thin
205.
by uluyol 6y ago
What about the precursor to Google talk? You know, chat integrated into Gmail before it was branded Google Talk. I thought it was Google Chat.
206.
Debian tech committee allows Kubernetes vendoring(lwn.net)
1 points by uluyol 6y ago|0 comments
207.
by uluyol 6y ago
The any is required to avoid a syntactic ambiguity. It was that or use the "type" keyword as in Print[type T] / Print[type T1, T2 Constraint]. The question of what the syntax should look like has been beaten to death.
208.
Building Red Hat Enterprise Linux 9 for the x86-64-v2 microarchitecture level(developers.redhat.com)
1 points by uluyol 6y ago|0 comments
209.
by uluyol 6y ago
Good point. Some Intel chips have had an on-package on-die?) 128MB "L4 cache" made of DRAM. That certainly sounds a lot like the M1's integrated memory.
210.
by uluyol 6y ago
And other things which you'd expect to be commands are both commands AND builtins! And they behave differently depending on which you call! Some examples are time and pwd.

More ›