News for hackers. Stuff that matters.

denormalfloat

Re:Google to Slow Hiring for Rest of 2020 on Wednesday April 15, 2020 @09:55PM (#22885308)
With the number of people who go through Google's interview process, this might actually change the industry to think more carefully about the interview process. If Google isn't making whiteboard interviews the norm, who will keep it going?
Re:The myth of the developer that can't code on Tuesday April 14, 2020 @04:13AM (#22863698)
>I'd love to hear what OP suggests to replace the coding tests with.

Making it easier to fire mishires would probably cover it.

Re:BPF Theremin, Tetris, and Typewriters on Sunday December 22, 2019 @11:13PM (#21861444)
But that's also why BPF doesn't seem to have a place in this world. Anything surfaced by a BPF program should probably be surfaced by a proper kernel module or syscall. As far as I can tell, the utility of BPF tracing is solely between the time a bug comes up, and a few weeks later when a kernel upgrade exposes this info anyways.
Re:User Agent Changes on Sunday December 22, 2019 @09:57PM (#21861192)
That's not how HTTP works. HTTP is a transfer protocol, and is not so opinionated on the semantic meaning of the Data it moves. HTTP, HTTP/2, and HTTP/3 were designed to be backwards compatible. It would break that compatibility if there were a semantic change in the absence of the UA string. Specifically, H/3 requests couldn't be downgraded to HTTP/1.1 requests by proxies. There are a lot of proxies.
Re:BPF Theremin, Tetris, and Typewriters on Sunday December 22, 2019 @09:54PM (#21861179)
I want to like BPF, but so few of my problems are in the kernel. Performance problems are usually at the application layer, either in my code or my dependencies. Even in the rare case that it something outside of my control (like the compiler, or the nature of the data), it's almost never the kernel. Lastly, when it is the kernel's fault, there's usually a sysctl or other knob to turn to fix it. Real kernel problems, such as some missing functionality, are usually better resolved by committing changes to the kernel itself, not so much on demand filters. BPF is a solution in search of problems.
Re:User Agent Changes on Friday December 13, 2019 @01:38AM (#21779596)
This would not work, too many websites (perhaps wrongly) depend on this string.
Re:User Agent Changes on Friday December 13, 2019 @01:36AM (#21779587)
There are wrong reasons to sniff the UA string, and less wrong reasons. If a Browser has a bug that gets fixed in later versions, sites have to sniff the UA string to do the right thing. For example, a browser bug may cause people to see an error, and the they are using an old version of the browser. The right thing to do is to upgrade, but how to tell? When you are subject to the bugs of some other code, and which are skewed across different versions of the software, the most reasonable way to work around it is by UA sniffing.
Java does something similar, decaying its HashMap into a binary tree after enough collisions.
That's not what big O notation is about. It represents the growth rate. In a the case of a hash table, the size of the thing you are hashing is not affected by the number of items present in the hash table. Putting a trillion bit integer into a hash table of other integers is still O(1); it's a constant.
Re:Goroutines and APIs on Tuesday November 19, 2019 @03:14AM (#21571391)
Yes, they still need unlimited kernel threads (for liveness reasons). When I asked a few years back about this, go-nuts@ suggested implemented my own rate limiting in application space.

In my case, it was for running Go on a resource constrained Raspberry-PI, where the kernel threads could easily live too long, and use up all memory. The threads were calling read(2) on a network mounted fuse fs, and would last for 30s+.

Re:Disney+ hit by technical glitches on launch day on Wednesday November 13, 2019 @03:16AM (#21522011)
Disney is in a tough spot since they also pay dividends. Companies typically don't ever reduce their dividends, which leaves Disney unable to spend that cash on their growth.
Re:Working with Errors in Go 1.13 on Saturday October 19, 2019 @05:11PM (#21300795)
It's poignant to watch Go slowly realize the why other languages have more powerful, more useful error types. The `error` interface is anemic to the point of uselessness. Making it unwrappable is step forward, but all that does is progress it the level of 1995 Java with their "cause" field. It still can't express suppressed errors (like those from `defer f.Close()`). There is no standard mechanism to include an optional stack trace. Worst of all, rolling your own error type and trying to use it everywhere is near impossible. Every method signature has to use `error` due to lack of covariant return types, and heaven help you if you return a nil struct pointer, which will be auto promoted to a non-nil interface. Perhaps in Go 3 they'll get it right.
Re:USB-C Has Finally Come into Its Own on Thursday October 10, 2019 @05:34PM (#21219410)
I didn't come to appreciate the power of USB-C until I started using it with my laptop. It is a single cable that connects to my monitor, powers the laptop, provides USB access to the keyboard and mouse, and to the hub on the monitor. This is a big enough improvement to the desktop-style workflow, since there is only a single wire, and no docking station. It's trivial to jump between desktop mode and laptop mode. That's usability changing experience with USB-C.
Re:An Antique Toaster That's Better Than Today’s [video] on Saturday October 05, 2019 @02:34PM (#21167132)
That is a lot of moving parts for a toaster. It seems like even a few crumbs falling into the wrong spot would jam the falling/raising mechanism.
There are more than 100k TVCs at Google. I don't think you can speak generally about them, because there is high diversity in their job roles.
Re:Linux Kernel 5.3 on Monday September 16, 2019 @09:30PM (#20990326)
They were previously allowed by the IP RFCs, but limitted by the kernel. They are in the 0/8 block.
Re:TCP Puzzlers (2016) on Sunday September 01, 2019 @01:24AM (#20850617)
It may not be the first but it is a reason to upgrade from HTTP/1.1. PING frames have other uses too, like being able to estimate connection latency in an application, rather than trying to read it from the kernel. This can be used to load balance across connections, or estimate the bandwidth delay product of a connection. PINGs have a lot of uses; the new thing is being able to control it from an app rather than it being OS specific.
Re:TCP Puzzlers (2016) on Sunday September 01, 2019 @01:13AM (#20850579)
A cool thing HTTP/2 provides is PING frames, which allow clients and servers to check if connections are still alive. In case your application can't turn on TCP keep-alives, you can enable it at the application layer. This allows both sides to know if the connection is still around and active, and avoids NAT boxes from removing long lived connections. Rather than wait around 5 minutes, or tune your system, you can control how quickly dead connections are discovered.
Re:Vickrey–Clarke–Groves Auction on Friday August 02, 2019 @02:43AM (#20591044)
It's needlessly complex because it doesn't solve any problems I have or any I have heard of. A simpler auction would still work pretty well, and be more easily understood by participants.

I ask because the only case I can think of this providing any value, it would be too complex. The example would be splitting up the assets after a divorce, where each spouse bids on the parts of the estate. A VCG auction may be more accurate, but what couple or lawyer would agree to use this system? It's too complex.

That's not right, you (we) get accurately priced securities. We also get tighter bid-ask spreads.
Without having read the regulation, why don't institutional investor just make a private market place where they can trade for sub-penny values?
Re:Vickrey–Clarke–Groves Auction on Friday August 02, 2019 @02:04AM (#20590924)
This seems needlessly complex. Aside from being an interesting thought experiment, what is the practicality of this style auction?
Exchange traded funds depend on special traders who buy the underlying stocks (like AMZN and MSFT), and sell them in exchange for the ETFs (like SPY and VOO). If the individual stocks are more valuable the special traders can buy the ETF shares, exchange them for the individuals, and then sell those for cash. If the ETF is more valuable, they can buy the individual stocks, exchange them for the ETF, and sell the ETF for cash. This is what keeps Index funds matching the underlying index.

Whenever the prices are out of whack, one of the assets can be exchanged for the other. However, there is the concept of tracking error, where by the value of the ETF doesn't track its index. High frequency traders are constantly trying to take advantage of this mismatch (i.e. arbitrage), and as a result the fund's tracking error is moved very close to 0 (i.e. it achieves the goal stated in the prospectus).

Retail investors (like you and me) benefit from this because the price of the index fund is kept in line, and HFT people get to make a little money being keeping it that way. Who would want to make a law that hurts everyone involved by preventing them from entering a mutually beneficial relationship?

Re:Lock-free multithreading with atomic operations on Tuesday July 30, 2019 @03:43AM (#20562851)
I found it surprising that atomic operations in Java are converted in to locking when compiling for some versions of android. The guarantees of Java (before 9) on ordering are slightly too strong and result in locks being used under the hood.
Re:Lock-free multithreading with atomic operations on Tuesday July 30, 2019 @03:39AM (#20562829)
The correct term to use here is blocking. The hardware bus locks finish in a bounded amount of time and allow the other processors to eventually make progress.
Re:Improved seam carving with forward energy on Monday July 29, 2019 @02:24PM (#20557677)
Do the seams need to be continuous? Intuitively it feels like the seam being carved out doesn't need to be made from pixels touching each other. What if the best seam has a slope of about 1/3 (i.e 1 vertical pixel for ever 3 horizontal pixels)?
If your DC had limited rack space it might start to make sense. Buying a cheaper processor means you would need more of them to accomplish the same amount of work, but also you need more space.
Re:Debian 10 “Buster” Released on Saturday July 06, 2019 @11:00PM (#20373337)
> I had broken sound drivers for a couple of months until someone else found that it wasn't actually the drivers but another broken package that as of a month or so ago still wasn't fixed (but the problem had been reported)

I had the _exact_ same problem (the issue ended up be a MIDI program called timidity). The main problem for me was that Debian doesn't give any advice on how to report such issues (the website is firmly planted in the early 90s), and the mailing lists I found all appear to be dead. I wish Debian had a slightly more modern website.

Perhaps we could combine the two? Make a slot machine that pays out in penny-stocks, rather than chips.

Older »