skysight-inc/HackerNews huggingface dataset:
Mainly by making motorists responsible for killing pedestrians. Instead, in America you mostly don't even get fined for running over a pedestrian, as "it's just an unfortunate accident", even when you have chosen to purchase a vehicle that makes it harder to safely navigate around pedestrians.

Consider: Do other countries even have the concept of "Jaywalking", which was explicitly an attempt by vehicle manufacturers to blame pedestrian deaths on pedestrians.
I don't think it is farfetched to say that, for the good and bad, modern software development is moving away from a single project having to handle "1200 tables". As we see the growth of "services" (gasp, microservices!), the scope for codebases is reduced, hence why the pattern in my post (OP here) is so common to see in Go. Are Go developers masochists? No... But when you're working on (micro)services and your immediate work only touches 5 tables and the relationship between them, it's really not inconceivable to just reach for a database adapter and simple abstractions.
That's a nice goal, but the site doesn't deliver the promise of the headline. You don't cite a single study or back up that headline on the site. The site title doesn't match the headline.

It's spammy to bait-and-switch with a submission that says one thing and then takes me to a page that tries to sell me a hat and make a donation - and utterly fails to provide any substance to back up the claim.
Thank you for sharing! DiskANN was published in 2019 and SpeedANN in 2022. DiskANN is specialized in disk based ANNS solution, and it's focus on the scenario where the vectors don't fit into memory. SpeedANN is in-memory solution and specialize in low latency query, which is the scenario we want to tackle for now. We can further extend our engine to support DiskANN and other index algorithms based on our customer's requirements
Thanks for pointing out the benchmark figure, we just fixed it to have consistent colors
This is horrible too, and I agree :)
No need to call unchecked_deallocate directly, unless one isn't using controlled types, and even better SPARK features.

No UB to worry about.
I would also be interested in it. As far as I know editions only allow for syntax changes, the semantics will change if incompatible, especially that Rust doesn't link across different versions in the same way as C++ does.
I also don't know how accurate that description is, but this comic comes to mind:

https://xkcd.com/2205/

But I mean, space is really, really big and we are observing from one single spot with (on cosmological scale probably) primitive technology. So of course most of it is guessing and when you "guess" a lot of things, it maybe does not matter a lot, if you have 3.41 Pi or 1, when the data you have are rough estimates anyway. But sure, when you do sloppy math, when you could have precision - that would be just wrong and unscientific.
> In the end the heavily traumatized and retired controller Nielsen was brutally stabbed because the modern diffusion of responsibility of companies only operates on the culture of financial compensation and is blissfully ignorant of a desperate man losing his whole family trying to restore his honor.

Well yeah. I’d still take innocent until proven guilty over any of the blood debt and honour killing cultures. Particularly when the victim sacrificed to restore someone’s “honour” is not responsible. Desperation is no excuse, and of course we should not base our judicial systems on it.

As usual, the real culprits got nothing. As usual, this is unacceptable and, as usual, nothing has been or will be done to change this.
https://docs.aws.amazon.com/lambda/latest/dg/invocation-retr... Lambda retry docs. I still would strongly not advice intentionally disabling the GC and explicitly said not to above for the same reasons you're concerned.
I hope you are right but I fear it will become a process of boiling the frog. Companies that are in the business of renting access to your data will get increasingly clever at moving in this direction in small incremental steps, providing some user benefit along the way.

We can agree that Zoom did a terrible job of rolling out their new terms, regardless of what their intention was. What other companies will learn from this is to improve the roll out.

Once local/private inference becomes more viable, there will be even more of an incentive for the companies who store unencrypted data to use it as a competitive advantage.
That's a great explanation for why Airbnb was pushing out open source torture software like their eslint preset (I still have nightmares about it) while having the slowest and clunkiest frontend ever.

I started using booking.com first because of how bad that website was working and I had the latest MacBook.
If by "enterprise-friendly licensing nailed down" you mean "it's free if you buy something else".

People use it only because someone up the chain sees it's included in Office and they're like "we're not paying for something else if we get this for free". I hope Slack and others bring MS to court to stop this, this is exactly what happened during the browser wars.
Is it increasing per capita?

I think we are definitely under investing in infrastructure.

Amazon builds an empire on cheap-to-use interstate highways and we can’t take a train across the country in less than 3 days.

Bridges falling down, power grids starting wildfires, levees failing, towns with abysmal drinking water quality.

We spend more on healthcare with worse results than other countries, with private profits being skimmed at every step.

We have normalized needing a college degree on your resume for “entry level” jobs and graduating with tens of thousands in debt to achieve this checkmark.

I think it’s an indication because if you were paying back society as you prospered, these black-hole pockets of increasing wealth wouldn’t be so large or common.

Economic prosperity is great. But that was generated in the framework of our society and should be re-invested in it.
Perhaps this somewhat publicly unsupported rollout will serve to highlight the as yet unsolved problems with self driving in a city environment, and the rest of the world can take note and act accordingly. Unfortunately of course it is the local residents who will have to suffer.
What's crazy to me is how common this line of thinking was from way back. Thomas Jefferson was borderline obsessed with basically this same concept. There's a really excellent letter from Jefferson to Madison from 1789 describing the importance of usufruct. [1]

My favorite chunk of this thing / the meat of the argument:

> I set out on this ground, which I suppose to be self-evident, ‘that the earth belongs in usufruct to the living’: that the dead have neither powers nor rights over it.

> ...

> For if [a man], during his own life, eat[s] up the usufruct of the lands for several generations to come, & then the lands would belong to the dead, & not to the living, which would be the reverse of our principle.

[1] https://founders.archives.gov/documents/Madison/01-12-02-024...
> you are actively sacrificing what makes it desirable in the first place

Amazing how the carrying capacity of every location just happens to be exactly the number of people who live there at this moment in time.

> I also think in general you should listen to what local people want and not advocate for things against their interests. Just as a rule of thumb. The alternative is basically colonization (pushing an agenda against the interests of the people who live somewhere).

The local people quoted in the article want to be able to live somewhere. Building enough housing for them to live in gives them that, even if they don't understand it because their heads are full of xenophobic nonsense.

The guy who I quoted above is a renter, he will eventually be priced out. The guy who owns the house he was renting will build a new house or sell to someone else and they will rent it at a much higher rate.
You seem to think that only made up words can be trademarked. You are wrong in every jurisdiction.
Two differences:

(1) This feature only requires regex-guided generation. We have a PR for BNF sampling that is about to be merged.
(2) ggml loops over the entire vocabulary (~50k tokens) at each step, which introduces a noticeable overhead, and makes it unusable for complex grammars. Our method works by building an index at initialization, and build the masks at each step with a dictionary lookup. Once the index is built, generation is just as fast as standard generation. Doesn't depend on the complexity of the grammar, the size of the LLM or its vocabulary size.
And it gives the feeling anytime one can self/diy. Like kubernetes. Most can't aa it is too complex(and unnecessary) but gives a safety feeling.
I am a massive hermit. I still benefit from living right in our city, because now instead of getting in my car to go get takeout, I walk from my apartment to the restaurant to get takeout. This is regular exercise I never had before.

Sure, I'm not out clubbing every night, but I am still better off in a walkable environment than I was before.
It's basically a much more featured, flexible, extendable, and usable version of editions. Anything you could do with editions you could do with this; you could implemented "editions" via this functionality.
Given that this extension is not very easy to install, I suggest adding a screenshot showing some actual captured network events. The current screenshot hides the most interesting feature.
Linus Torvalds doesn’t own all the copyright on Linux — Linux doesn’t require copyright assignment from contributors.

> You're playing a dumb game

For what it’s worth I’m not a lawyer and surely get some things wrong but licensing is an area where I have a certain amount of practical experience.

There’s some interesting ground to cover on this topic but we aren’t getting there and the incivility isn’t helping. Please consider this passage from the HN guidelines:

https://news.ycombinator.com/newsguidelines.html

> When disagreeing, please reply to the argument instead of calling names. "That is idiotic; 1 + 1 is 2, not 3" can be shortened to "1 + 1 is 2, not 3."
My understanding is that the characteristc smell of industrial acetylene is a result of sulfur compounds added as odorants (a common practice with odorless gases that create hazards, to make them noticeable.)
How is that much different than just using malloc and then letting the OS clean up when the process exits?
> When historian Charles Weiner looked over a pile of Richard Feynman’s notebooks, he called them a wonderful ‘record of his day-to-day work’.

> “No, no!”, Feynman objected strongly.

> “They aren’t a record of my thinking process. They are my thinking process. I actually did the work on the paper.”

> “Well,” Weiner said, “The work was done in your head, but the record of it is still here.”

> “No, it’s not a record, not really. It’s working. You have to work on paper and this is the paper. Okay?”, Feynman explained.
.io has been used as a sort of general-purpose tld to signal sort of… I dunno, hip, dev-focused sites, right? It is at least slightly less novel than gg.
Great point, and a great reminder.
I really like Gleam, and I am a huge fan of more being built on the EVM.

Personally I want the EVM to (eventually) get the same level of adoption and mindshare as the JVM.

And currently wider Elixir use/education seems like the path to that.
He was referring to the political right in the states. Historically speaking, in 70s/80s, even Nixon, passed laws for conserving the nature, protectionism and etc. At some point there was a switch into “nah, screw the environment” to align with the voter base.
Let's say the house that burned was $500k (i have no idea). Insurance pays out $500k. Now, those people have to live for, what, maybe two three years while their house is rebuilt due to how many are destroyed? They have to use some of that $500k to pay rent some place. Many may not be able to then afford the newly rebuild house which will then get sold off to some off-island investor, because, well, then new house will inevitably be more expensive and they've use some of the payout from their old house.
Lambad definitions don't take arguments, they jump straight to argument matching.

Take:

case value do
true -> "true"
false -> "false"
_ -> "uh..."
end

vs

fn
true -> "true"
false -> "false"
_ -> "uh..."
end

`do` is simply syntactic sugar for a keyword list argument containing a `:do` key:

if(true, [{:do, "hi there"}])

So it wouldn't make sense for `fn` to take a `do`.
> Isn't that what documentation is for?

I would agree, if everything was documented. The issue at-hand is what is not explicitly documented. What constitutes a guard-worthy function? ie A pure javadoc without any notation about what the API does, is not sufficient.
One thing that I am hoping to get introduced to is better sources for the data points I use. I think they are mostly ok but I am no expert, so I could easily be citing something that is generally understood to be incorrect. Also, I could be citing very biased sources without even knowing it.

In particularly, this number of 24mpg (as an American) seems pretty in line with my expectations, so I decided to use it.
> 2. Dropping support for Ukraine would signal to China that we wouldn’t have the stamina to support Taiwan if they were attacked. It was only a few years ago that a massive chip shortage hamstrung our economy and nobody wants to repeat that. Dropping support won’t have much significant fiscal impact, either. Most of the billions spent thus far is really the US clearing out older inventories.

It's even worse than this IMO. What this acquiescence would signal to "lesser" nuclear powers is that Pax Americana is truly over. That is a problem. I believe the most likely outbreak of nuclear war is between Pakistan/China/India instead of the classic USA/Russia/China. If you want peace, keep Pax Americana. It's the least evil of all evils.
You should try to sell your "Windows" operating system. I'm sure it will work out. Or maybe ask how it worked out for the wxWindows GUI library.
fn do
true -> "true"
false -> "false"
_ -> "uh..."
end
Indeed, both languages have plenty positives and quite a few warts as well. While I do prefer Java personally, I consider C# an absolutely fine choice for almost every usecase.

Go on the other hand, I'm much less forgiving about.
> This can be a misleading statistic. A lot of people use credit cards as a substitute for cash, and pay off the balance every month. This is accounted as "debt" but in a practical sense it is not.

Indeed, this is annoying nonsensical. They should not count credit card balance as debt until it has rolled over at least one payment cycle.

Every summer my credit score drops ~40-50 points when I put the upcoming school year payment on the credit card (they give a nice-enough discount for prepaying) and then a month later bounces right back up after I pay it.
1-year equity cliff, 3-year reputation cliff?
Argon wouldn't work, it has a stronger narcotic effect than Nitrogen
If you know ThePrimeagen on Twitter/YouTube, he worked on Falcor (the precursor to this GraphQL change) and he talks more about it [0].

GraphQL is very useful, it removes whole classes of bugs. You can even use a Result/Either type where if you don't handle both the success and error cases, the GraphQL request won't even compile, so you can get type safety at both the client and the server while also not having to use purely TypeScript like with tRPC, allowing multiple clients like mobile and web. Pothos does this very well as an error extension [1], where, given the schema:

type Error {
message: String!
}

type Query {
hello(name: String!): QueryHelloResult
}

union QueryHelloResult = Error | QueryHelloSuccess

type QueryHelloSuccess {
data: String!
}

you can then query it with

query {
hello(name: "World") {
__typename
... on Error {
message
}
... on QueryHelloSuccess {
data
}
}
}

If you forget `... on Error` the query will simply fail.

I should also add that most people use GraphQL incorrectly, to get the benefits of not over/underfetching, the Relay approach using fragments is the only viable way currently. Otherwise it's not too much better than REST. You define the exact data required for a specific React component in GraphQL fragments, then the Relay compiler will stitch those fragments together into one and only one request. This is a great (if long) overview on the problems Relay solves and why everyone else uses GraphQL incorrectly (then complain that GraphQL sucks) [2]. Hint, Apollo is not the way.

[0] https://www.youtube.com/watch?v=yab6i9lrEv0

[1] https://pothos-graphql.dev/docs/plugins/errors

[2] https://alan.norbauer.com/articles/relay-style-graphql
What if you have 3.14Pi?
"Cruise blamed cellphone carriers for the problem."

"As I understand it, outside lands impacted LTE cell connectivity and ability for RA advisors to route cars."

I'm sorry, in what world is stopping in the road an acceptable response to losing cell service? How the f are we expected to trust a company that thinks this is not their fault, and that designing their "self driving" cars around 100% cell service or random(), is "safe"?

If you are putting "self driving" software on the road, and it behaves badly, then just like a human driver would be, you are responsible. Until Cruise, Waymo, Tesla, etc are directly, and non-transferrably liable for all "mistakes" made by their "self driving" systems we're just going to get more of this BS.
i'd argue that everyone's device should be secure against nation-state-level actors, so that those who actually need it won't stand out from the crowd at all
Done. Well, issue opened.
Thanks for building this. The mechanics are such an obvious idea that it's astounding that the first-party platforms haven't done this yet. I would be interested to see how this could be used for other tasks outside of JSON that require structured input.
We can extend our approach to grammar-based sampling, as explained in the paper linked above. Relevant PR: https://github.com/normal-computing/outlines/pull/178

Our method is much more efficient. llama.cpp loops over the entire vocabulary (~50k tokens) at each step to generate the mask. We generate an index at initialization, and building the masks at each step only requires a dictionary lookup (trade speed for memory). Sampling is just as fast as standard sampling.
Ok so when I've never used a 3rd party discord service I'm safe.
I got scared there for a moment, but then I thought what would I lose? Nothing at all. Nothing that can't be replaced.
No contacts worth keeping.
> Won't a photon climbing out of a huge gravity well have a huge redshift

It depends; the key factor is not how "huge" the gravity well is (in terms of how massive the object is), but how close to the black hole horizon the light is emitted. The vast majority of the light JWST is seeing from black holes is not from very close to the horizon. It's from the accretion disk, which is much further from the horizon and so the gravitational redshift is much smaller.
Yup, this hits a bunch of the basics.

There are details, of course, but just like every "housing crisis" in the past, the parameters that need adjusting are fundamentally the same.

Which way to adjust always changes. And, in part thus, always becomes the basis for the next crisis.

For example, zoning requirements were mostly positive and useful at a time when some jerk might open up a steel mill right next to my house just because I happened to live on some useful waterway and near some rail that had been built...* and, this fostered development of land that was arguably underutilized in the economic landscape of the time (... "suburbia").

Of course, as happens with markets in general (and, especially, when you produce "professional businesspeople" and have laws regarding "fiduciary responsibility"), once primary development of new markets / "opportunities" is largely exhausted, then, the less net-positive behavior starts. I.e., when you hit a degree of "market saturation". The resistance of market participants to change in what they have "staked out". So, all the NIMBY crap. Some, for reasons most might empathize with. Some, by the greediest and most psychopathic (including in "big corporate" contexts), to stop any further development simply to maximize prices of assets they "own".**

Right now, I'd say we're in a period of unusual disruption, even as disruptions go. Maybe more of a 1:50 year or even 1:100 year disruption. Changes related to the sudden significant increase in population that can potentially work from just about anywhere ... etc. Quite an upending of a relative status quo of, really, centuries ... and, of course, not having nearly as positive an impact on certain communities that formerly suffered more from people leaving than from people clamoring to move in ...

In any case, as pressure increases, changes will be made - more and more rapid and large-scale. Unfortunately, it always takes years (and will basically guaranteed set up the next "trouble(s)"). But, fundamentally - more houses, change in permitting requirements towards "lower", rebalancing (decreasing) "institutional ownership", etc.

* https://youtu.be/9mLu5jOUmws

** Own in quotes because that's a whole other area of sort of human absurdity that I'm not even going to get into - but, just interpret in whatever way you usually do
Most do SaaS or dynamodb or lambda type app engine. Once it grows significantly then administration will need oracle etc. But hey these can be done by external contractors
Perf is almost irrelevant for promotions beyond level 5.
Maybe the decline of desktop applications (Java, C#) and Android (Java)? And then Go coming out with some killer frameworks? I have to stretch my imagination to imagine anything causing Go to outpace C# or Javas ecosystem.
Central Coast health food pioneer who popularized Apple cider vinegar dead at 94
You are right. We designed our storage in a segment-based way, with configurable segment size, so it can horizontally scale in the future cross multiple workers in one machine, and cross multiple machine cluster. And the search will become a two-stage search: find top K in each segment, then a global merger (can also be horizontally scaled) to merge the results from all segments
It took some iterations but I've managed to get the OpenAI API to give me valid JSON 100% of the time now(based on my testing). I think I put in the prompt to never use newlines because it was causing issues lol.
As you yourself pointed out, California's Prop 13 does not give anyone absolute right to live somewhere.

If you cannot pay the taxes, you cannot live there. If you cannot pay the water/power/maintenance you cannot live there.

Just like if you can't pay the rent, even in country like Sweden with strong renter protections, you can be evicted.

Limited allodial title is rare. True allodial title is very rare. In the US the federal government can always assert eminent domain.