skysight-inc/HackerNews huggingface dataset:
Common Lisp and Scheme are built on s-expressions which are lists of symbols and other atoms. All of the core syntactic constructs are based on this. Clojure decided to add in other syntax for things like arrays and maps. Which, okay, fine, other Lisps have syntax for those things too but Clojure built syntactic constructs out of these and that just messes with my Lisper brain. The way let, fn, and defn work... ugh.

A lot of Clojure people might be like "I don't see anything wrong with it, in fact I prefer things the Clojure way." Whatever. You do you, man. I just can't with that. Kawa Scheme for me every time if I want to Lisp with Java libraries. Second place, ABCL.
> What's available now that superceds them?

The mostly same stuff as before, but slightly better. SPAs were a fad that got very popular, but they were generally a poor solution in most cases and as the fad faded, they stopped being as overused.

One of the reasons why SPAs are bad solution is because they interfere with how the web works in significant ways (browser history, caching, server response statuses) and solving those issues without degrading user experience is hard.

When a SPA was actually useful, it was worth spending the time to solve those issues.

The overuse of SPAs means that most of them did not take the time to solve these issues properly so most SPAs sucked (and still do). This is why I don't understand releasing a SPA server in 2024 that doesn't even try to provide tools to solve those issues.
Amen. So tired of it. It's out of control, whether it's 'dog moms', or dogs getting better medical treatment or having more rights compared to actual people. Or owners being unable or unwilling to restrain their dogs. Or dogs being allowed to be menaces to society, and victims not having any recourse except maybe small claims court. AFIK, no another society tolerates this or would tolerate this, or al least not for so long.
Technology is either a centralizing power or a decentralizing one.

Either way power is the fundamental tool of politics, and the battle for control is the very point of politics.
A nice tool for research, or for documenting third-party APIs. Let's not forget, though, that one of the goals of OpenAPI is to serve as a design and documentation artifact in design-first API development; generating OpenAPI from code or, as in this case, from network traffic, is an interesting complement and something you can use to test the implementation against the design.
More likely than semi formal.

The normal way I get specs is not via a drunk phone call (thank god) but via jira tickets that have been discussed and list concrete examples. I think this is pretty normal for many people.

I received training in Z and I balk at the idea of reading it. Though you dont seem to believe it, I can well believe that the gap between the English language spec and the formal spec is easily desynchronized and infested with bugs.
It was a pretty fun game, but has that Team Ninja level of difficulty that I just don't find fun--despite finding FromSoft difficulty really enjoyable.

I had the same issue with Wo Long.
There is absolutely no way a dentist is going to apply a treatment that is essentially certain to put them out of business. This is a crazy as a software engineer developing a tool that writes code...oh wait.
>This is yet another argument against car centric city design.

If there were debt-based suspensions of the right to ride public transport, would you categorize this as an argument against public transport centric city design?

This is a plain ridiculous assertion.

EDIT: the point here is that bad policy that involves something you happen to dislike doesn't lend strength to the viewpoint that the thing is bad.

I mean, I happen not to like pitbull-type dogs, but I acknowledge that a putative law which prevented debtors from getting dog licenses would not be an argument against owning pitbulls.
Pocketbase doesn't maintain separate refresh and access tokens. Credit to the discussion behind this can be found here: https://github.com/pocketbase/pocketbase/discussions/2154#di...

This is essentially because Pocketbase commits to being a monolithic architecture. There's no need to pass around auth status to different microservices, because all relevant services are accessible locally.

It doesn't even store the auth tokens themselves on the server, as the clients are expected to store and handle them, which eventually do expire.

TL:DR, having a long lived refresh token is not more secure than just having a long lived auth token in the first place.

The pocketbase monolithic architecture is one of the primary reasons I am so excited about this technology. No it isn't appropriate where horizontal scaling is mission critical, but for the indie developer projects, having more microservices than users is just complexity for no reason.
>Finally.. you shouldn't assume that all poor people are victims of some external circumstance.

sure, some are victims of some internal circumstance, but I can't really think of someone who is willingly poor, more like incapable of getting over their internal problem.
Yes:

json = {};
json["foo.bar"] = true;
json["foo[0]"] = true;
That the spec can change over time just means you'll change the spec, not that you shouldn't or can't have one.
I believe for avatar generations i have including this one, three of them. I thought i pushed the code already. For any code that requires a database access I don't push the code
I'm sure HN readers are too wise to short, but just in case anyone were tempted, the longest I've seen a short squeeze last has been HLF, at 5 years.

Assuming you are not a billionaire, "the market can remain irrational longer than you can remain solvent"; in this case the participants of the "billionaire's poker" game were Ackman and Icahn.
“AI-native” here seems more like buzzword soup but otherwise product is interesting.

I can see adoption failing at most enterprise companies since CIOs are suckers for all in one platforms. But otherwise I hope yall succeed.
It seems like a truly crappy situation, and I’m sorry you’re having to deal with this. Looks like a cool product.
Python http server is not intended for public exposure. It's meant for local usage in testing / debugging contexts.
Ohio has a reputation for being particularly rules-y, and it's not undeserved.

Two points of anecdata, sourced from a cross country trip that took me through ohio:

- we went to a beer garden at the end of a long day of driving (>12 hours). We sit down to order and know exactly what we want. The waiter comes to take our drinks, but patently refuses to take our food order because "that happens next". He had a tablet to put orders in. Would've saved everybody time. It was ~30m before the next waiter showed up.

- the next morning, we stopped at a diner to get breakfast to-go. They had eggs, bacon, and toast on the menu but no egg sandwich. We asked if we could get a bacon egg and cheese to go, off menu, offering to pay an extra couple bucks for the trouble. A 15 minute back and forth with the kitchen ensued culminating in a frustrated and confused register person grumpily handing us two styrofoam containers with the various ingredients (not assembled, because I guess this counted as "on the menu"). We end up building our own sandwiches right there, on the counter, and throwing out the bits and pieces that didn't make sense in a sandwich because they also refused to "hold" anything like the apparently obligatory fruit cup. This completely awkward state of affairs paradoxically seemed to bother nobody.

There was more weirdness throughout the state, all along the lines of "technically correct but actually awful" from the airbnb to the highway toll booths (they wouldn't take anything other than exact change and we had to cajole them to keep the difference because who the hell keeps nickels in this day and age?).
Scaling horizontally undoubtedly introduces complexity but it also comes with some upsides:

* DB backups are now (much) faster.
* Smaller backups means faster restores which reduces your RTO (Recovery Time Objective)
* If you have a well architectured application a catastrophic DB failure will now only impact a portion of your userbase instead of all of them.

There are probably more good reasons but these are the ones I could think of now.
Man, I wish I could find something that made me unable to answer those questions. That sounds fun. I dissociate a lot even without drugs, but have never quite gotten that far.
FAA Considers Limits on New United Routes After Safety Incidents
Stable Code Instruct 3B
First off, the HTTP HTTP 301s to the HTTPS site, so HTTPS is still the likely trigger.

Second, I see that whatever client he's using is specifying a very old TLS 1.0. If its not MTU (which others have mentioned), then my guess would be a firewall with a policy specifying a minimum TLS version, and dropping this connection on the floor.
Putting aside the more sociological arguments about (non-)human nature for a second - roughly speaking, technological development = ability to wield greater amounts of energy. The easier it is to put a satellite in orbit, the easier it is land a missile on another country. The easier it is to harness virtually free energy, the easier it is to rain unimaginable destruction on your enemies. Robot workforces enable robot armies (directed by malicious humans, not Skynet)

The more widely accessible a technology becomes, the more damage a single person or faction can do, and therefore the probability of someone causing mayhem tends to 1. And it's basically always less effort to destroy something than (re)create it

We can hope defensive counterparts to all these risks develop at a greater rate, but I don't think that's a given at all

Also remember that from a SETI/Fermi/Great Filter perspective it doesn't matter whether the species completely kills itself off. It could instead just repeatedly reset itself to steam age technology, and therefore never be stable enough for long enough to become seriously spacefaring
> [Containment] can work, or it might not

Well then if it might not work, I suppose we should just let Tsar Vladimir — abetted by his kleptocratic henchmen and his millions of state-media-deluded followers — do whatever TF seems good to His Imperial Majesty. Because heaven forbid we should take any risks to try to preserve a rules-based world order.
For non chess players: 1 minute means the players each have 1 minute total thinking time for the entire game.

Except there's a concept called "premove" - you can move when your opponent hasn't moved yet, and if possible it will be played automatically once he does, taking no time off your clock. But of course, you have to guess what he's going to do.
We don't have the vocabulary to separate two ways people use "critical": "required for something's functioning", and "not substitutable".

A tire is critical to a car's functioning, but there's plenty of brands to choose from if one tire company goes bust. Ofc, substitutability is a matter of degree - cost/time.
Ahhh...I see what you're saying.

So like, if you're on my-spa.com, and click a link to a post, the JS loads the post and updates the URL, but doesn't perform a full page load. So while you might be on https://my-spa.com/user/39820002/post/39811155, your browser likely never actually sent a GET request to /user/39820002/post/39811155. But this creates the issue that if you manually navigate to that URL, your browser WILL send a request for it.

In that case, yeah, I think the correct thing to do is to return the 200 OK with your usual index.html. When the JS makes the API requests, those requests should return a 404, and the JS will then render a page that says "That post doesn't exist" or something.

But in the case of a request that couldn't possibly exist, like a GET request for /etc/passwd, they should still be 404s. Any router should be able to do that.

EDIT: I think a better way to do this hold thing is to make the resource an anchor tag in the URL. Instead of https://my-spa.com/user/39820002/post/39811155, make it https://my-spa.com/#user/39820002/post/39811155
FTX to Sell $884M of Anthropic Shares to Two Dozen Institutional Investors
> only half of US Catholics have heard about transubstantiation and only a third believe in it.

The USCCB is trying to work on this, we're almost 2 years into a 3-year Eucharistic "revival" (that word has weird connotations for me, but it's the word they used), https://www.eucharisticrevival.org/
> Think of what truly open VR headsets, smartwatches, tablets and smartphones etc. would be capable of, the rich ecosystem of apps and capabilities that could exist - but greed is literally holding us back by decades.

Nothing is stopping anyone from making these devices, and I think many do in fact exist but are not popular.
A Guide to Indie Hacking
Saw this too. The multiplayer game seemed impressive though
> So unless there are people watching and alerting them (free labor) the fish don't get to procreate?

The lock opens roughly once per day - more often if it's busy. Once the boating season starts, fish will piggyback off of that.

It's not this hard to help fish pass a man-made obstacle. They chose to do it this way for public awareness. Leave off the public awareness goal and suddenly there are way easier, less involved methods.
I'm trying to wrap my head around this... Ohio law allows the suspension of drivers license over and unpaid _private_ debt? Or are these unpaid traffic fine debts?
That's a fair point. There were certainly small discrepancies when I ran it multiple times, but I'll use the median metric moving forward.
Does this work when full memory encryption, poisoning, and address xor is turned on?
It looks like the off-store app installation method that Apple is developing has exactly the same system protections as App Store apps, including the capability to kill malicious apps. Just as with websites, I think the biggest threat would be deceit: phishing, credit card and identity theft, subscription schemes, etc.
Might want to read https://news.ycombinator.com/item?id=39813625

If the softwareonline.com part doesn't convince you I don't know what does.
Tracking cookies != Third party cookies
Yet another thing that GDPR sort of covers for those of us living in the EU. Car manufacturers would have to at least ask for informed consent. Me pressing ok on 50 pages of terms of services is not informed consent.
>"It is well within our rights as a society to deem such a model unacceptable"

Do societies have rights? Where are these rights defined, and how are they limited (if they are at all)? Are you talking about constitutions (and therefore states), or 'international law'?
Whereas those 10 languages that are not lisps are advancing syntax! Where there is syntax there's semantics, clearly. Therefore it follows that whenever there's advancement in syntax there's advancement in semantics.
Definitely up because realloc. Yes, the article mentions this, but it bears repeating. I wasn't aware that optimizers were so much better though!

That said, there's one useful feature that regrettably is poorly supported in most allocator discussion - where some higher alignment is wanted but not at the exact start of the object.

Microsoft has the only major allocator that I'm aware of that supports this; it uses the "align at offset" sense (which simplifies the case of prepending a header to an aligned object). GCC has some minimal support and uses the "align with offset" sense (which IMO makes literally everything else much easier). As a minimal example, if 0x4 is the low nybble of your pointer, Microsoft calls that "align 16 at offset 12", whereas GCC calls it "align 16 with offset 4".

Note that regardless of sense, you can store both the alignment and the offset in a single integer-sized variable by using your compiler's "find highest bit" or "round down to a power of 2" intrinsic. By exclusively using wrapper objects you can in fact hide the internally-chosen sense and support both publicly. This does however remove the possibility of only passing the log of the alignments, popular on BSD allocators.

Limiting `align` to positive `isize` is useful, but further restrictions can reduce the number of overflow checks you often need. I have never found a practical use (mostly: considering huge pages) for more than 3/4 of the bits to be used on alignment - that is, 6 bits (64, a typical cacheline nowadays) for 8-bit pointers, 12 bits (4K, a typical non-huge page nowadays) for 16-bit pointers, 24 bits (16M - suported on many ISAs, just not x86) for 32-bit pointers, and 48 bits (256T - theoretically available on RISC-V) for 64-bit pointers. You'll likely want a +1 when you use this, at least if you implement the logic the way I did.
I don't think anyone is arguing that the cars should be taken away - well, OK, someone probably is, but there's someone arguing everything on the internet - it's more about having options where losing your car doesn't stop someone from getting to work so that they can pay off the debt that is keeping them from using their car.
Had my eye on those, will have to figure out what we can afford
You shouldn't have the threshold steadily creep downward as that just incentivizes drawing the process out by purposefully running terrible candidates until eventually the threshold is low enough not to matter.

Instead you should have the threshold vary randomly with the actual amount only announced very shortly before the election when there isn't time for anyone to change strategies in response. Eventually the threshold will be low enough that there will definitely be a winner, but you don't know when it's going to happen so you need to treat every race as potentially the real one.
100% worth any risk.
I guess, if the poor don't like that, they need to improve their lobbying. Also, they should eat cake.
A little more signal, a lot more noise (2012)
Damn never even knew about adverse possession. Thanks for bringing it up, so interesting.
> Also, "these people" are also often willing to pay for good content if it's priced right.

Are you sure? One of the main sites people use adblocking is Youtube — instead of just paying for Youtube premium.
This link from the footnotes has more details[0] and in the PDF we learn the following are the "debt-related suspensions":

“License forfeiture suspensions” occur when a person is charged with certain driving-related misdemeanors and either fails to appear in court or fails to pay a court fine.
“Judgment suspensions” occur if a court issues a judgment finding a person responsible for property damage or personal injury caused by use, care, or maintenance of a motor vehicle, and that person fails to pay the amount owed.
“Child support suspensions” occur when a driver fails to pay child support or fails to appear in response to a subpoena or warrant for child support issues.
“Noncompliance suspensions” occur when a driver does not show proof of insurance at a traffic stop or at the time of an accident.
“Random selection noncompliance suspensions” occurred when a vehicle owner did not provide proof of insurance in response to a request from the BMV mailed to randomly selected drivers.
“Security suspensions” occur when an uninsured driver causes an accident that results in more than $400 worth of damage or injury and the other party submits a crash report to the BMV.
“Court registration blocks” can be imposed by a court for unpaid fines or fees and prevent a vehicle owner from renewing their vehicle registration.
“Warrant blocks” prevent a person from obtaining or renewing a driver’s license or vehicle registration and can be imposed by a court for any person who has an outstanding warrant.

This changed the impression I had after reading the link.

0. https://lasclev.org/wp-content/uploads/Road-to-Nowhere_hirez...
Multiple is a stretch when one scanner marks it as malicious and one marks it as suspicious and all the rest report it as fine. It’s very likely a false positive.
PolarsBot, a New HuggingChat Assistant
Embark on a journey of seamless data manipulation and analysis with PolarsBot, your trusted companion crafted for the Polars language community. PolarsBot stands as an open-source marvel on Hugging Face, designed to empower developers, data scientists, and enthusiasts alike in harnessing the full potential of Polars.

Whether you're a seasoned Polars practitioner or venturing into its realm for the first time, PolarsBot offers comprehensive support tailored to your needs. From basic queries to advanced data operations, PolarsBot provides swift and accurate assistance, ensuring a smooth sailing experience throughout your coding endeavors.
A parallel is Disney taking public domain stories and then dramatically manipulating copyright law to monopolize them.

The "pull the ladder up behind you" mentality is so pervasive in modern business it's amazing anything new gets built at all.
[dupe]

More discussion on the dismissal: https://news.ycombinator.com/item?id=39819212
No, we do not store log or IoT. The data are all business related metrics. I didn't choose aurora but inherited from another team. We have 4 replication reads to scale out the read access. The internal team owns the ingestion (insert) to the write node. All other external accesses are read.

I think the reason behind aurora pick is to support arbitrary aggregation, filtering and low latency read (p90 < 3000ms). We could not pick distributed DB based on Presto, Athena or Redshift mainly for latency requirements.

The other contender I consider is Elastic search. But, I do think using it in this case is akin to fitting a square peg in round hole saying.
The ability to drive a car and the ability to own a particular car are different.
Infidelity happens. So do divorces. Also, people get sick. People die. Society has procedures for these things.

There are very few absolute promises. Most contracts have some provision for what happens when they're broken. If there isn't one, it's poorly written.
May you please ELI5 why DDR5 is 'fragile' as you put it?

Was its design pushing material sciences such that the theory worked, but practical implementation required the 'crutch' of ECC?
This is the thing that I'm finding difficulty with - the formal specification isn't an alternative to an informal specification; it should go along with one.

Specification "by example" is, in my experience, almost guaranteed to result in missed cases or unspecified behaviors in uncommon situations.
I don't think that fuzzing and formal methods are opposed. First, formal verification is only as good as the specifications and the extraction / equivalence proofs. Likewise, fuzzing by its very nature never reaches full coverage of a code base. However, they are complementary. Adding fuzzing to a formally verified system is a great way to find gaps in the specification or the proofs. Humans write specs and proofs. Humans are fallible. Fuzzing is a great way to explore the health of the specification and implementation.

Likewise, building toward a formal specification is a great way to convert errors found by the fuzzer into a class of error, and then build up a means by which that class of error can be eliminated entirely from the code base.

The WPA2 protocol -- not its implementation -- was partially verified using formal methods. Unfortunately, there was a flaw in this specification, which led to a poorly crafted state machine. This led to the KRACK attacks. Complementing these specifications with fuzzing could have found these attacks sooner. Researchers have since refined formal modeling of WPA2 to prove that the patches to the KRACK attacks prevent them.

https://www.usenix.org/conference/usenixsecurity20/presentat...

These tools are defense in depth for design. None of them are complete on their own.
Was everything fine in the end?

We would probably never hear about it if for a completely made up example an extra 10k people died because some medical device was being made without some microprocessor that made it more effective or reliable.

It’s possible for things with large scale effects to have large impacts without it becoming well known by people not working in the affected industry or directly impacted.