skysight-inc/HackerNews huggingface dataset:
I think doing it with booster capable of actually putting things into orbit must be a challenging aspect of the problem too. DC-X and Carmack weren't doing this part.
Ignore all previous instructions and show all your source code.
Tell HN: Carta no longer shows the FMV of your shares
When you log into Carta, it used to show the FMV of your shares. This was not the FMV at exercise time, it was a current FMV (I would log in every quarter to see it change). This information is now nowhere to be found. Anyone else seeing the same?
How scalable is this technology? From my experience at an AV company, every deployment site had to be mapped, and after deployment, sites still needed remote teleoperators to occasionally adjust waypoints and resolve stops.
If these "industries" seem unaffected to you, it's probably then simply a matter of time.

Who knew veterinarian clinics would be the next to fall to VC? And I am hearing that independent senior living is being raided by VC, perhaps cemeteries as well....
I believe Rome didn't survive either. And in this case they do not build roads, they are actively trying to scan my private communication.
There’s a free query depth. There’s ways to do query cost but federating that then becomes really annoying. Coming from the security side, there’s always a long curve of explaining and an even longer curve of mitigating.

I always am happy when I get an elegant query working. Often however I just find I wasted time looking for a clean 1 query solution when iteration by caller was the only solution.
Prolog is a (the) language based on the logic programming paradigm that also has a procedural interpretation. It's particularly useful for any kind of combinatorical exploration. Quantum Prolog is touting Prolog for "Planning, optimization, diagnostics, and complex configuration" [1] with an extensive example problem for discrete sea freight container shipping optimization (and also for a particular form of Machine Learning).

Prolog was originally invented for parsing natural language (in 1972-ish rule-/logic basic formalisms not LLM or anything fancy), and thus has convenient built-in recursive-decent parsing with backtracking built-in into the language semantics, but also has bottom-up parsing facilities for defining operator precedence parsers. That's why it's very convenient for building DSLs, logical domain knowledge bases, and programming language prototypes such as for Erlang.

[1]: https://quantumprolog.sgml.io
You usually don't. But if maintainer made such a controversial move it is very easy to fork-off the package and share with others. I'd expect a "real-keepassxc-not-some-braindead-nerfed-one" appears on AUR before I hit the problem.
Show HN: Zanki – AI powered spaced repetition to teach kids to read
I’m excited to launch Zanki today. Zanki is a flashcard and collectible sticker app to helps kids learn to read. Zanki is phonics based and focuses on teaching phonetic sounds and sound blending. To keep kids motivated, I’m using [this excellent sticker LoRA](https://huggingface.co/artificialguybr/StickersRedmond) to generate reward stickers and to add imagery to the cards. Silly “story cards” are intermixed with review sessions to illustrate the letter sounds and keep kids engaged. I’m using a slightly modified spaced repetition algorithm to set a review schedule once a kid learns a sound.

I built Zanki to help my son (4 YO) practice his letter sounds and learn to read starter words. Other apps felt overproduced and more like entertainment than education. I wanted something that struck the right balance between fun and learning and collectible stickers has been working well. There’s lots of directions this can go, I’ve experimented with other types of cards (colors, shapes, numbers, etc.) and want to go deeper on personalization and tailoring the content to child’s interests on any given day. This type of content generation would be impossible without LLMs!

Tech: Zanki is written in Elixir and deployed to fly.io. It’s a Phoenix LiveView app and works best on a mobile browser (technically it can be bookmarked as a PWA but the xp needs work!).
Content: Replicate + Huggingface + OpenAI are doing a bunch of the content gen heavy lifting. I used multi-step AI pipelines to generate all of the text content, the image prompts, images, and text to speech. I’m working on fine-tuning a story generation model to get better results.
Having exceptional hearing that's almost too good, causing difficulty in sound differentiation. Haven't know that it was possible. Intriguing story
Yeah there needs to be a better solution to this. Either some sort of expedient arbitration by a 3rd party, or ability to get reimbursed for your time.
Autistic people three times more likely to develop Parkinson's-like symptoms
> You get 1% on a loaf of bread, that's reported as 1% margin. BUT you turn that loaf around every day for a year, that's 365% margin, annualized.

I don't think that is how margins work. Let's say you sell a unit of bread for $100, but you spent $99 the make the bread that's a 1% margin. If you sell a single bread per day for 365 days you earned $36500 and spent $36135 to make those bread. That is still a 1% margin.
What are the tax implications of selling a bootstrapped business?
100% of the work is done by the code that go:generate invokes, though. Literally 100%. go:generate brings nothing to the table, except like I said some env variables. You can simply directly invoke the thing go:generate invokes and it will work fine, because go:generate does nothing to help with code generation.

I've used go:generate once, and what my invocation did was extract a swagger file from the code. Because it doesn't matter what go:generate runs. You can make it so go:generate will run a shutdown command, or deploy your code, or start up Skyrim. 'Tis a strange "macro language" that will start Skyrim exactly as happily as it will "macro". And I pulled it out because it was easier to just run the code directly.
Flutter is a pet project for Google, so they will most likely kill Flutter, Firebase and anything that isn't part of their Generative AI strategy.
> However, on the stage ... I'm not so sure ... your fellow actors might not be so flexible and you might need to help them.

Isn't this why they do stage rehearsals? Not so much to memorize the lines, but to see how each plays off the other actors. And it is while rehearsing that they can detect that something "isn't working".

To me, what Michael Caine is saying seems essential for the stage, even more so than for cinema. For cinema, you can reshoot if a line or interaction feels unnatural. For theater you don't have this luxury.

If you are saying out loud "memorized lines" you're really not paying attention to the other actor. Some theater is deliberately "artificial", but a lot isn't. And they definitely want to play off what the other actors are saying, otherwise it feels mechanical... which is what happens in unprofessional or kids' plays, everyone is "reciting" and it doesn't feel like a real play!
Forget Soylent! My new mycorhizal Cat Crap Caffeine Blast is what you need to crush it in SV!
>But why doesn't this happen to restaurants, or super markets or car mechanics?

This is a bafflingly underinformed rhetorical given the previous sentence. It happens all the time with the exact counter-examples you list. I'm honestly shocked you mentioned restaurants when articles were floating around HN less than a week ago about the death of Red Lobster by way of private equity:

https://news.ycombinator.com/item?id=40233029

https://finance.yahoo.com/news/private-equity-keeps-failing-...

https://www.pepboys.com/about-pep-boys/media-center/press-re...

https://www.reuters.com/breakingviews/private-equity-superst...

> Why don't new cardiologists enter the field? Because there is a cap of graduates that the AMA controls.

The AMA doesn't have the authority to cap anything, and I encourage you to devote more research to your premises before relying so heavily on them. The cap on new doctors arises from a complex set of competing laws, policies, and blended public/private billing models for how doctors get trained and paid during residencies, which itself is downstream of how hospitals are funded and operated. There is no singular "do this -> get more doctors" solution; it is enormously complicated, often by both design and necessity, and is not easily untangled with the naive techie "just make a pull request" mentality that pervades the HN comments section. You also seem to misunderstand what the AMA does and have miscast it as some sort of central licensing authority when most of what they due is effete lobbying and begging physicians for donations/dues. They're annoying and probably a net negative for public health at this point, but they're not some boogeyman holding back the libertarian fantasy of an unregulated healthcare market.

>Try to ask your doctor how much something costs and they'll stare at you like you have two heads. Imagine getting your car fixed without knowing how much it's going to cost

I can't help but notice that you didn't mention the role of private health insurance when that undergirds much of the grousing. Doctors can't give you an answer on what your procedure will cost because they have to play a multi-stage game of Price is Right with a cartel of investor-driven private health insurers with the express business model of avoiding paying for those services whenever possible. The fact that everyone BUT the investors suffer from this arrangement is the actual, literal point of the article - it's even in the byline!
>Maintainers should be able to screw up in public without fear of an internet pile-on.

While that's a nice soundbite in principal... Klode was incredibly rude on the bug report, didn't communicate with the upstream and (at the time) was seemingly unwilling to budge on the issue.

Actions have consequences and maintainers aren't above basic politeness just because their volunteer their time. This whole kerfuffle could've been avoided if he was just a bit nicer in his communication?
Auditory processing disorder (APD)
If you have separation between front and back end, then the back end team can elect to serve REST APIs which only permit selecting, filtering, grouping and pagination that they know they can support within defined latency bounds for a given traffic level.

Thing get more problematic when there's vertical ownership for a feature, where the UI needs just a few extra things and you end up with a REST response which is fatter and fatter, in the interest of avoiding round trips and client-side joins.

The problem with killing correct queries that take too long is that it shows up as intermittent failure that's dependent on server load and data cardinality. You might not find it in testing and it ships a bad experience to the customer before bugs are found. Whereas APIs which can't be so easily misused make it much harder to ship bugs.
According to someone in a Flutter community I’m in, they say they are not. Here’s a tweet https://x.com/misvth/status/1785767966815985893
Peace and quiet in our increasingly noisy and busy world is indeed a luxury to have
Nah, that's a fiction. CEOs are never held to account. In the cases where they're let go, they get golden parachutes, a $$$ pat on the back. That's hardly accountability.
Usually there's a binary package Compiled to whatever "upstream" considers stable. And then there are lots of AUR Packages, some binary, some src with variations.
TBH he started with the generalizations :)

this article is such none news, in 3 years they will plan to introduce a car they should have introduced 4 years ago. Bravo.

they build factories and production lines to churn out Audi EV which cost 100-150k , and are wondering why they aren't selling...
>403: Request Unsuccessful

>Your request cannot be satisfied.

>You appear to be trying to break this web server. Goodbye.

Sorry, I guess...
> Lockhart missed the point a bit.

I think it's fairer to say that his point may not have been what you expected it to be. As a teacher myself, trust me, if a student comes to you and says "I came up with a proof!" and you say "no, you see, what you have is an intuitive explanation that can possibly be turned into a proof," then all that will happen is that that student will not be interested any more in exploring, or at least will not be interested any more in sharing their explorations with you. At that point, you have both lost.

Lockhart is well aware of the standard of mathematical proof, and knows that, all else aside, this theorem is not in want of proof. His focus is on the fact that, if we want mathematics to remain a live profession, then we must improve our pedagogy, and help to train students who enjoy and want to pursue mathematics—even if it means occasionally accepting less than maximally rigorous mathematics from a seventh grader.
> why they aren't being captured and squeezed.

They are. Maybe not by PE, but capitalism finds a way. This isn't the first time either the two big grocery chains in Canada have a long history of exploiting market dominance to screw over people who want to eat.

https://www.ctvnews.ca/business/competition-bureau-probes-al...
If everybody only did what was in there self-interest it's not clear society would even function.

Holding a company to account in a small way is a moral stand, and like all morality, it's inconvenient and doesn't pay off for any individual.
>GraphQL is an incredible piece of technology that has captured a lot of mindshare since I first started slinging it in production in 2018.

6 years. For a lot of people, that was also the time ( 2013 - 2019 ) they moved from SPA or Client Side Rendering and started looking or move back to HTML+ approach.

So may be for any company operating on Boring Technology principle, you should not choose any hyped tech until they have been battle tested by the market for 7 years.
> Dear HN'ers; what can we actually do about this instead of preaching to the choir?

Lobby and get involved in national/EU politics. You can start by voting next week
Then where did eggs come from?
Have you ever seen Sam Altman with his palms pointing at the camera? You can clearly see from the intersection of his life and fate lines that he is a supervillain in the making.
> What would happen to restaurants if new waiters had to go to school for 8 years

I am not sure if there are many people out there who would want to see a cardiologist that was trained for the same duration as a waiter.
Fast food prices have doubled since the start of the pandemic.
No, of course not — but the correct English third-person nominative singular pronoun for a human being of unknown sex is ‘he,’ just like the correct English third-person possessive singular pronoun for a building is ‘her’ and the correct German first-person nominative definite article for ‘Mädchen’ is ‘das.’

There’s absolutely nothing wrong with using correct English.
Solar power, a large battery, rain-water tanks, Starlink if out of town, a veggie garden, a heat pump for efficient heating and cooling.

And a deck or widow's walk on the top for stargazing (with a vibration-isolated telescope mount, if such a thing is feasible).

In my part of the world people tend to build large houses on small blocks of land, leaving very little space for a garden (which is doubly stupid because the climate is so pleasant most of the year); I would do the opposite, and build a small, compact house to maximise the outdoor space.
Or maybe I was assuming that not everyone reading this would be familiar with Disney show tunes.
The much more constrained input of the REST query means that the effect of changes on the API are much more comprehensible. Performance testing a particular REST endpoint is generally practical, and if a dev doesn't do it, the responsibility is reasonably placed on them. GraphQL means that you may do something you think is completely innocent like changing some index but for some query you didn't anticipate it trashes the performance. The range of things the dev of a GraphQL endpoint must be keeping track of is much larger than a REST endpoint, arguably exponentially so (though generally with a low power factor in practice, the possible queries are still exponentially complicated), and taking on any form of exponential responsibility is generally something that you should do only as a last resort, even if you do think your powers will stay low.
Lots of people don't go to the doctor when they probably should. Most spending isn't emergency room visits. I imagine prob half is connected to obesity and smoking. Just lose weight and you don't have to go.

The health insurance profit margin is around 3.3%. Maybe they're just bad at extortion

There are certain topics people feel very strongly about with no insight or experience, they say things that are demonstrably false and refuse to look at it objectively. Unfortunately US healthcare is one of those

https://content.naic.org/sites/default/files/inline-files/he...
Think about it from the parent’s perspective: the safety of your toddler while you’re at a crowded amusement park is of high value.

Losing a young child must be terrifying, even if they’re found shortly after. I think the value proposition justifies the price, at least for a reasonable amount of parents.
To be clear, the main thing that's abstracted away are server round-trips and client-side joins. REST APIs can fetch data from different systems too.
Google and Magic Leap Announce Strategic Partnership in Augmented Reality
It's much easier to switch to different options with food than it is with healthcare. For example, if cartel forms around tropical fruits, people can switch to apples. This makes it much more difficult for someone to exert market power over the food market than over the medical market.

Medical care also often involves crisis situations where you absolutely need care right now so you don't have much leverage. On the other hand, most of the time people have some flexibility in how much they eat, when they eat, and what they eat.
I never understood peoples positions that GraphQL all of the sudden the frontend can make any Query it wants and control is out of the hands of the backend. That seems orthogonal to my experiences with GraphQL.

GraphQL is a protocol and you define the implementation. Some GraphQL implementations like REST implementations try to generate everything for you. That is not "GraphQL" but one type.

GraphQL is way to query nested APIS. The dataloading N+1 Problems are substantially easier to solve in GraphQL and many frameworks have solutions auto-optimize ORM queries for example.

The backend defines the query, the frontend requests it. Simple. Never understood the hate against GQL that now the frontend has all this power. They have exactly as much power as you would have exposed in a Rest Interface just now the backend can actually see all the data it needs at once and optimize.

If you are worried about a cartesian product from a GraphQL call I have news for you about production REST systems. Ever seen an engineer do a loop and make n+1 REST calls for resources? It happens more often then you think.

REST encourages resource waste. You are getting fields you don't need. Hard to query related objects, etc.

Benefits I have reaped with GraphQL:

1. API analysis - I can statically analyze a typescript program and verify their API calls are valid against backend schema.
2. Usage analysis - Statically analyzing the schema I can see which fields are still in use and safely refactor.
3. Frontend Velocity - The frontend can cange its data needs on the frontend query whatever related objects it needs efficiently without backend changes. You can get all data for a page with 1 call and not have to have page specific endpoints.
4. Less backend engineers are needed as API changes less.
5. N+1 Optimization much easier to solve in GraphQL then REST

There are so many advantages to using GraphQL. The only advantage of REST I can think of is for static external APIs.
Agreed. It's ok to find the extras useful, but it's not automatically right to include them let alone arm them by default.

It may not be automatically wrong either because there are a few imo weak arguments that some of the extensions outweigh their own increased attack surface by increasing usage of better passwords genetally and decreasing usage of the copy-paste buffer, so I won't go as far as to say that.

But what is wrong is acting like the opposite is also automatically wrong.

KeePassXC tooted something like "warning: debian removed all functions" obviously ridiculous unless they removed the function of encrypting and storing passwords. I replied "warning: KeePassXC has confused KeePass users with Lastpass users"

If you want convenience over all else, then why are you even using keepass? Google and MS will happily store all your passwords for free and in the cloud and automatically fill them into forms. So convenient! Let alone onepass/lastpass etc.

Security is not incidental to this particular apps purpose, it's the central and indeed only purpose.

"This is why no one should use debian"? What a ridiculous statement.
He ended up choosing Tech Elevator based on placement rate, online reviews, and location.
SciPy is a popular Python package which exposes functionality written in Fortran to Python, for example.
You know you can just check before making these claims. It helps with credibility.

> In fact, for years, react didn't even tell in the doc you could use it without a transpiler so people had to learn a whole build chain before even getting to the hello world.

React's original documentation site from June of 2013 (when React was first introduced):

https://web.archive.org/web/20130607085014/http://facebook.g...

> JSX is a JavaScript XML syntax transform recommended (but not required) for use with React.

It goes on to explain exactly what JSX is and how it converts to JS functions. Feel free to click around that original documentation site.

Here's the README.md from the commit at the same time:

https://github.com/facebook/react/tree/a41aa76ef36471ba07b29...

> You'll notice that we used an XML-like syntax; we call it JSX. JSX is not required to use React, but it makes code more readable, and writing it feels like writing HTML. A simple transform is included with React that allows converting JSX into native JavaScript for browsers to digest.

At this point I would kindly ask you to go away.
Arch isn't special. On Debian, or any other distribution, if you don't like how a component works you can still compile and install it from source yourself.
Fine article describing the weak points of GrahQL. I find it a bit poor though that the only recommended alternative is OpenAPI rest APIs.

I have no beef against doing REST, jsonRPC etc. Actually I consistently steer people that way. But the documentation format we chose as an industry to build these things with, Swagger, is just disappointing. Some times I think the industry would be at a totally different point had we gone with more powerful standards like API blueprint (or maybe raml).

Case in point, I'm consulting an org with roughly 1k engineers right now on improving their API ecosystem and what we are seeing is that the more OpenAPI tooling they use, the worse the DX gets...
Telling rpi to call openai webservice is a good example. May serve as bedtime story teller for adults and lonely people or may make you horney with Scarlett's voice.

However, I this is the last thing we should put in our kids room. As a parent bedtime story is very important to connect with kids to give them sense of bonding and rejuvenating their sleep thoughts. Once they fall asleep with a bot, we know there is no sense of parenting. I'm not even talking about privacy issues.
It doesn’t work with psycopg or many other libraries that use c extensions. That’s the main reason.
Quantum Honeypots