Hacker News new | past | comments | ask | show | jobs | submit | benjaminjackman's comments login

Genuinely curious what the use case(s) of reading from uninitialized are. Performance?

It was used as a source of randomness. Someone blindly fixing a "bug" as reported by a linter famously resulted in a major vulnerability in Debian: https://www.debian.org/security/2008/dsa-1571

This is incorrect.

If they had simply removed the offending line (or, indeed, set a preprocessor flag that was provided explicitly for that purpose) it would have been fine. The problem was that they also removed a similar looking line that was the path providing actual randomness.

It could be possible that [some, (0,100]%, portion of the benefit provided by] the vaccines wear off after a certain amount of time. This makes statistics like 99.7% of Waterford have been vaccinated perhaps less insightful than something like 34% (or whatever the actual number is) have been vaccinated in the last 6 months.

edit: added [some portion, (0,100]%, of the benefit provided by]

The vaccine wears off in a few days. The vaccine tells the body to make copies of the “spike protein”. After a few days, the body breaks down the vaccine. In the meantime, the body makes copies of the spike protein. The immune system sees the spike protein and starts making antibodies to fight it off.

Those antibodies do not last forever. It is my understanding that the lifespan of antibodies is largely determined by the type of virus they are for. For example, luckily the antibodies for measles and polio last decades. On the other hand, antibodies for rhinovirus and coronavirus last months not years, which is part of the reason why you can have more than one cold in your life.

My understanding and it could be wrong is that they can't lower their rates, (and might actually have to increase to compensate for more vacancy) because it will affect their ability to finance the buildings if they have lower rates from whatever math is used to calculate the soundness of the loans. That could be causing the stickiness on price you are seeing (if it's not apocryphal).

My understanding is your understanding is correct. I've also been told that's why NYC tends to be quite unique, the buildings are mostly owned so there is more leeway in finding something as you can go directly to the owner. That said, a startup I consult to is in the basement of a building in Vancouver, I talked to their landlord who owns the building free and clear for 3 generations, same deal, no reason to rent it, just let it sit till the market rebounds. Curious to see what will happen.

And don't forget flipping a car is a lot faster and easier than flipping a house at much lower capital. This makes each cycle of trial and error a lot cheaper and a lot more frequent.

Also there is something to be said for a market where the customer brings the product to your location for inspection, and whose product is considerable faster to inspect more rigorously than a house.

Also the products within that market are much more uniform and share several unifying characteristic across even different makes and model so its easier to learn a good and accurate pricing function.

That gives them a lot more cycles to improve their algorithms (both human and machine based).

Plus when CarMax were starting out they likely did so with a bevy of folks already experienced and profitable at buying and selling used cars at a profit who had the systematic knowledge of how to do so in their heads.

It then was simply a matter of building up customer goodwill by focusing on another metric customers cared about, taking a perhaps slight loss to avoid the risk of being considerably ripped off by a savvy local dealer and saving oneself the anxiety induced by high pressure sales tactics.

Having said that I think Zillow could still be quite successful in this endeavor however from my experience they didn't deploy their trading algorithm in a prudent way, they massively over-traded an untested by the real world model, they trusted their paper trading (backtesting) way to much, and they didnt focus on the nuts and bolts of building a successful market making system: making actual money over and over at small size and ramping up size as your empirically demonstrated pnl grows.

Also putting trading aside they didn't have to be a flipper, they would probably naturally be more fit as an exchange+ or intermediary that provides exchange type backing and reduces the friction in buyers finding sellers, taking on risk by only making an offer when they have a bona fide buyer for fixed or % fee, but glossing over all the hassle of two people who dont know each other making a large trade. Offering services like if you dont like the house you just bought through us we will help your sell it at a cost proportional to renting no questions asked.

Carmax and Carvana also provide a service. They bring a bunch of cars to one place that you can peruse and buy. That's a better experience than trying to connect with a bunch of randos on craigslist.

Zillow hasn't gotten to the point where they provide that, but theoretically they could. You could drive around with a Zillow agent and see their 50 homes for sale a lot quicker than coordinating with 50 random sellers.

While it's great that Godot is getting better funding, that's about the worst insult I can think of. Epic is so confident that Godot will never be a serious competitor that they're giving them charity money. We'll see; there was a time when Autodesk viewed Blender as an also-ran too.

Not necessarily. While Epic has an interest in selling unreal they would also benefit from people selling godot games on their store.

I just want to say thanks, I have been experimenting with using xterm.js to connect to terminal API in jupyter notebooks and it has worked really well, plug and play (even editors like vim were working without any extra effort).

Before that I was experimenting with using it as a custom shell for running commands inside a web application. In that use case it was a bit more challenging because I had never written to an actual tty before (ansi escape codes for coloring log files has been about the limit of my experience). For that use case I just really needed to send and receive text. I ended up using this library [ https://github.com/wavesoft/local-echo ] to smooth that process out until I could learn about how to do things properly.

Are any suggestions on:

1. where to learn about how ttys work to do things the right way, or

2. suggested libraries like local-echo that can wrap over some of the trickier bits of just getting text on the screen?

Thanks again for maintaining such a great & useful library!

1. https://invisible-island.net/xterm/ctlseqs/ctlseqs.html is my main reference for anything related to terminals, other than that my knowledge has built up mainly as a result of contributing to xterm.js.

2. The library you mention is the one I'm aware of, I have a WIP for building a basic shell in JS that I will probably open source eventually if I have the time.


Xterm.js is really impressive in what it can do, but it was pretty tough to get started with as someone who just wanted to pipe shell input/output over HTTP requests to a server. I realize streamlining that usecase is probably out of scope for the Xterm team, but I think there's a space for either some tutorials or a higher-level wrapper library

I also default to use ag now and it is good at picking up things like .gitignores to exclude files. It works very well, I just wish it had a flag to limit the size of files searched because if a large file is found it can make the results harder to parse visually and most of the times when programming I only want to scan files that are under 100k (at most ... probably 10k is fine for a first pass).

This is really bad if the large file is some concatenated minimized javascript thing that is one massive line, then that really makes the results harder explore ( I tend to `ag foosearchterm | less -R` at that point) . Perhaps capping the line length in a result is another solution, if a line is over a couple hundred chars only show the relevant portion.

If you use ripgrep, -o will only show the matching part of the line. It also has a --max-filesize flag.

Thank you! I just tried it and --max-filesize worked great, ... -o also worked however it would be nice if -o showed a bit of context around the match (maybe 50 chars or so before and after), still useful all the same. Thanks again.

Hmm I wonder if it picked up timestamps as its initial filter.

There is sign on the wire near the traffic light that says no turns, not sure if it only applies to the other lane though.

There's also a sign on this half of the traffic wire that looks like it might be saying "yes turns" (low resolution, but I can't imagine what the sign says with an arrow pointing right other then that)

That sign says "One Way". Not "yes turns"... I don't think I've ever seen a sign saying that, actually, it's either "No Turns" or no sign at all, since by default turns are allowed.

I've definitely seen signs that say "you can turn here" and "you must turn here", admittedly not with language but with arrows (the "you can turn here" signs around here looking like a forwards arrow with a curved arrow bending off). They're not in general use, only for weird situations (like "two turning lanes" or "yes really this really strange intersection does work like this").

Probably regional though.

>by default turns are allowed.

It depends on where you live. In downtown Vancouver there were arrows at each intersection telling you what directions of travel were legal.

Ahhhhh I see the no right turn sign on the pillar. That is confusing as there are also one-way signs (with arrows pointing to the right) further along.

Moral of the story, do you think most humans would do a better job at this intersection than the Tesla did?

That sign in the pillar, if I was driving, I would assume applied to the other lane on the left side of the pillar. I think the intent is to make sure you don't turn left if you are in the right lane of the pillar side, and vice versa.

This is a really good article and the examples are very pretty. I especially enjoyed the part about how filter:drop-shadow contours to the shape of the element (did not know that, and that's a handy trick).

However just beware that there can be a decent performance hit from having a lot of box-shadows.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact