skysight-inc/HackerNews huggingface dataset:
Their goal might not even be to build a high growth high revenue business. Sustainable yes. So perhaps low growth, low - med revenue and who knows potentially high revenue.

If anyone else had done this, I'd be very skeptical but give Andrej's penchant for teaching and how good he is really at it, I am super excited about this endeavour.

Let's not forget the inbound and organic interest this would drive. For the intro LLM Course, people are already submitting PRs and Andrej is requesting them not to. Imagine that!

https://github.com/karpathy/LLM101n

Update June 25. To clarify, the course will take some time to build. There is no specific timeline. Thank you for your interest but please do not submit Issues/PRs.
Just a side note, async JDBC was a thing way before Loom came about, and it failed miserably. I'm not sure why, but my guess would be is that most enterprise software is not web-scale, so JDBC worked well as it was.

Also, all the database vendors provided their drivers implementing the JDBC API - good luck getting Oracle or IBM contribute to R2DBC.. (Actually, I stand corrected: there is an Oracle R2DBC driver now - it was released fairly recently though.)

EDIT: "failed miserably" is maybe too strong - but R2DBC certainly doesn't have the support and acceptance of JDBC.
Just had a quick read not sure why it's supposed to be so good ...

I love the section on documentation: https://tailcall.run/blog/graphql-schema/#step-10-document-y...

The most useless documentation is followed by:

> Good documentation helps both your team and API consumers understand the purpose and usage of each type and field.
how do i donate to the mozilla foundation to support this amazing development?
To my knowledge, if there were no people in Europe, there would be nobody to sink the boats full of 500 children - not even robots.
> Margarine has always been pretty popular

Has it? There are people who use it for ethical or cost saving reasons, but I've never seen anyone say that they actually prefer the taste over butter.
free trial available!
The most profitable thing you can do with captured carbon is probably either burning it or turning it into plastic. The problem is that it is orders of magnitude cheaper to pump carbon from the ground instead of capturing it from the air. The second problem is that burning the captured carbon is forbidden if you want to use carbon capture to reverse global warming.
Also the URL "security scanner" things on corporate email systems. The user can't see the URL by hovering over it.
OKay, that 's good feedback mechanism. thx.
There are quite a few tools cropping up trying to solve this problem. Multiplayer.app is one example - they use OTel to gather distributed traces from your system and ensure you automatically get notified when there's drift.
Yes, we should all live in reality and use our best judgement. If estimating based on story point velocity is literally useless, then no one should be doing it. However if it does help make planning more accurate, even by a little, then it might be worth the cost of doing so. It’s a conversation to be had between different functions, hopefully based on empirical evidence.

I feel like a lot of engineers overlook that there’s more to a viable business than just producing high-quality software. People don’t ask for estimates just to annoy developers.
I would say the issue is more it's not a real butter, because it could be sold cheap as a byproduct of the process
Can you answer the question? No, you can't.
I really really feel that every temptation to do a "cool idea + AI" play should have a good amount of consideration for whether it'll cut jobs.

This can play out in two ways:

- Teachers free up time/make time to give more personal tutoring to kids

- Teachers do this but schools start hiring fewer of them in the expectation of doing more

I don't think you will find anywhere on earth where teaching is a job with a great job market, perks or benefits. It's underpaid, underappreciated and understaffed.

People wielding AI like a bulldog at a glass store should be more mindful of the socioeconomics. But I'm not gonna hold my breath for that.
They indeed optimize thread context switching. Taking the thread on and off the CPU is becoming expensive when there are thousands of threads.

You are right that everything blocks, even when going to L1 cache you have to wait 1 nanoseconds. But blocking in this context means waiting for “real” IO like a network request or spinning disk access. Virtual threads take away the problem that the thread sits there doing nothing for a while as it is waiting for data, before it is context switched.

Virtual threads won’t improve CPU-bound blocking. There the thread is actually occupying the CPU, so there is no problem of the thread doing nothing as with IO-bound blocking.
i hope they'll eventually support Mermaid (https://github.com/mermaid-js/mermaid) for creating diagrams directly within documents. i've been using it a lot for my markdown files and it works amazingly well with LLMs (e.g. asking LLM to generate the diagram representation of something using Mermaidjs)
I would argue that coordinating efforts of thousands of people is freakishly complicated. People aren't machines and respond to incentives in nontrivial ways.

Anyone who is physically healthy can carry a stone, but few places in the world built the pyramids.

Analogically, anyone with two hands can type something on a keyboard, the hard part is getting a useful software product out of this typing.

Even outside the commercial sphere, leaders of such complicated projects are famous, such as Linus Torvalds.
Stashpad - Google Docs Alternative
Yawn. GraphSQL company promotes their blog. How does this make the front page?
An article which was posted on HN a few months ago, "Why, after 6 years, I’m over GraphQL":

https://news.ycombinator.com/item?id=40521518
Mozilla and telemetry opinions that zero people asked for
Unfortunately, Platonov could not stand the torture and in the second half of his life turned into a de facto mouthpiece of the regime.

However, he was not the only one, and in the end there were no others at all.

In any translation, his texts lose their meaning; now he is interesting only as another example of the work of the totalitarian selection of the “new useful people”.
(Press the little crossed-out eye icon ("Show more for all") at the top to more easily read everything.)
Tl;Dr: if you force RTO and other such measures, you'll be left with the lowest performing employees since the best have better employment options and will jump ship to where they get the work conditions they're looking for
I don't think the gift analogy really works here.

When you "give" open-source software, by placing it online, it's more analogous to placing a piece of furniture on your door-step with a sign that says "help yourself".

If you come along and take it, you've laid the expectation on yourself. Should you knock on my door and say, "I want this piece of furniture you're giving away, but I want you to deliver it and set it up in my home, since I have no means", I might decide to do so, but that's entirely out of the goodness of my heart, or I might tell you to fuck off, and that's entirely reasonable too.

If you decide to come along and use my open-source library (for example), you did your due-dil and set the expectation on yourself if it appears unsustainable and you decide to take it anyway.
That is no guarantee of future results.

Nokia, another company which was very strong a decade ago, is de facto gone.
I don't know how it's working, but I imagine a "killer app" could be in space stations by capturing CO2 emitted by astronauts and produce stuff.
After a lot of crying no longer using GraphQL, just REST API-s
Apple does it right: it shares only if you press the button and only with your own devices (the share prompt will show up if your other device is currently facing Wi-Fi password prompt and your current device knows the password)
This strategy is called CCUS (Carbon Capture, Utilization, and Storage), as opposed to CCS (without the U). As someone who as previously worked in the field, I think it’s a bad idea.

Carbon capture is expensive. Even if you capture at concentrated point sources like power plants or factories, and capture only between 80-95% of the emitted CO2, it’s still quite expensive (e.g. natural gas power can be roughly 25% more expensive when you add carbon capture), and it’s already hard enough to build the capture capacity that we would need to make an impact on global warming.

The goal of paying for all that should be to remove those emissions from the world, whereas most utilization processes end up with some or all of that CO2 in the atmosphere in the end. In which case you have wasted energy and money while not saving the environment.
Check out https://www.multiplayer.app/
The author is one of the co-founders, but I understand not wanting to just promote his tool and just have a conversation about the problem.
Yep, sometimes Russophobia is incurable.
This does illustrate a problem when talking about complex topics or mechanisms is the need for specificity. Using short, simple sentences comes at the risk of making things seem overly vague and hand wavey, or worse, misrepresent the concept.

In continental philosophy or mathematical papers this gets all too apparent, as alot of argument hinge on very fine differences and nuances that need to specified else people get the wrong idea.
I hadn't even realised that sites like TUAW had closed down. I recall seeing them over the past couple of decades, and if someone linked to them now, I'd read the post in the full belief it was the same entity.

And I would believe that the article was written by the name attached, if that name had been writing for the site for a decade.

Shady as!

And while the AI companies are completely to blame, it's grossly unethical, I feel the owners of IP like those blogs should only sell with contract conditions retaining good reputation for the name. It's like when a business owner names their business after themselves (famous example in Australia: Dick Smith's Electronics) and when selling, they're incentivized to ensure their name and reputation remain untarnished.
That becomes a problem when Google Chrome limits the number of filter rules extensions can add. https://developer.chrome.com/docs/extensions/develop/concept...
.. but they are manual. It's great to have history, diff, comments, etc. But why do I have to spend time manually creating a diagram and updating it every time I add a new dependency when it can be automatically done for me?
Butchering and elephant and cutting down enough wood without steel or iron seem pretty hard. But I guess if you have enough people you can do it.
Interesting announcement. Feels like some of it is just copy-pasted from a PRD. Not necessarily a bad thing (it's clearer than press release style), just the first time I've noticed it in a "bigtech" announcement.
But if I can get rid of most of the stupid over-paid prima donnas, then expenses will be cut even further, and I'll be able to ...

</phb>
It's like anything else that makes the job worse: The people that are first to leave are those with the best alternatives elsewhere, which are often your strongest workers. When some of those leave, your workplace becomes worse for anyone learning from them, which can cause a domino effect.

It doesn't matter what it is that makes the job worse: You either provide counterbalancing incentives to your best workers (see retention bonuses after an acquisition) or you are gambling
Has anyone studied what drives RTO?
https://archive.is/TlCSu
Litlyx: Dev-Centric, Self-Hostable Analytics
All these examples of "scaling CSS" tends to end with "don't write CSS".

Relying on HTML attributes to describe presentation could have its neat uses, but suggesting it as a new generic paradigm that everybody should jump on regardless of problem space is not the way to go. HTML is not the escape hatch out of CSS.

The main issue is that it's just not better than a class soup of Tailwind classes. It maybe a bit more readable, but if you stuff a DIV with endless `data-junk` then it will be just as bloated as the rest of these specifications if used without care and if you avoid writing CSS it will be pretty bloated.
> backend APIs
Using GraphQL for service-to-service communication isn’t the sweet spot if you can deploy both services together. Rather, it’s great if the services are deployed on their own schedule. This is the case if one service is someone’s browser, where forcing a refresh whenever the backend is redeployed isn’t tenable. For service-to-service communication, where you can deploy both together, gRPC or something is a better option.
Similar as plumbum for python

https://pypi.org/project/plumbum/

(also supports dispatching commands to SSH sessions)
When I was younger I was eager to experiment with things, abstractions, etc, now I want to write (in the web development context) as much html, vanilla js and raw sql.
Fair enough. I do use ublock on Firefox mobile. Just enabled all the filters not enabled by default and I'm not seeing it anymore. Modern Internet is a dumpster fire.
My experience has been that it falls into the category of making easy things hard. I had a previous team that adopted it, and it turned into a huge time sink. These days, I'm just using PostgREST, and life feels easy again.
> but 1:1 tutoring is just so much more effective than basically any other kind of educational context

Do we know how much of that effect is the "personalization " of 1:1 learning (something AI can replicate) vs the effect of interacting with another human (which AI might not be able to replicate)?
Consider trans fats in partially hydrogenated margarines.
I avoid touching Apple devices but anything that can expose a Linux shell can run the BEAM. There are two main projects for small devices, https://nerves-project.org/ for more ordinary SoC-computers and https://www.atomvm.net/ for stuff like ESP32-chips.

On Android you've got Termux in F-Droid and can pull in whatever BEAM-setup you want. That's how I first started dabbling with the BEAM, I was using a tablet for most of my recreational programming and happened to try it out and got hooked.

Erlang is pretty weird, but it just clicks for some people so it's worth spending some time checking it out. Elixir is a really nice Python-/Ruby-like on the BEAM, but with pattern matching, real macros and all the absurdly powerful stuff in the Open Telecom Platform.
Excalidraw is great for brainstorming and sketching. But I don't exclude pairing it with a tool that also automatically shows me all the metadata of system components, automatically detects architecture drift, etc.
Give managers an "offsite worker budget." Let them have some % of their staff outside the office.
> trivial features

Four features were announced:

1. Convert Markdown to Docs content on paste

2. Copy Docs content as Markdown

3. Export a Doc as Markdown (from File > Download)

4. Import Markdown as a Doc (from File > Open or "Open with Google Docs" from Drive)

Which of these do you see as trivial? These all seem quite complex to me with many edge cases , incompatibilities and ambiguities, especially if there's an expectation that you can round trip losslessly.
In my experience the focus should be on avoiding incidental complexity. Essential complexity born from business problems are counter intuitively often better left complex.
Honestly, why are people so bad at devising two phrases saying who is this for and what problem does it solve?

I don't want to do homework just to know whether this is useful for me. Though it's also probably true that if you have the problem this thing solves you'd recognize it right away. Still, I feel most projects suck at making a proper sales pitch.
Well yes, how else will you

> The setup in this documentation will help you recover X% more measurement signals on your website.
I think this is over-simplified and possibly misunderstood. I haven't read the book this article references but if I am understanding the main proposal correctly then it can be summarised as "cortical activity produces spatial patterns which somehow 'compete' and the 'winner' is chosen which is then reinforced through a 'reward'".

'Compete', 'winner', and 'reward' are all left undefined in the article. Even given that, the theory is not new information and seems incredibly analogous to Hebbian learning which is a long-standing theory in neuroscience. Additionally, the metaphor of evolution within the brain does not seem apt. Essentially what is said is that given a sensory input, we will see patterns emerge that correspond to a behaviour deemed successful. Other brain patterns may arise but are ignored or not reinforced by a reward. This is almost tautological, and the 'evolutionary process' (input -> brain activity -> behaviour -> reward) lacks explanatory power. This is exactly what we would expect to see. If we observe a behaviour that has been reinforced in some way, it would obviously correlate with the brain producing a specific activity pattern. I don't see any evidence that the brain will always produce several candidate activity patterns before judging a winner based on consensus. The tangent of cortical columns ignores key deep brain structures and is also almost irrelevant, the brain could use the proposed 'evolutionary' process with any architecture.
> in space stations by capturing CO2 emitted by astronauts and produce stuff

You mean all ten of them?

https://www.howmanypeopleareinspacerightnow.com/
Comparing with the worst won't get you far. There's Apple doing these things, then there's MS, which dedicated huge resources and some of its best engineers to make sure as many programs from Windows 95 can still work in their original form today.
I see a lot of negativity in this thread about GraphQL. As someone that's gonna be building a backend API soon, what's your favourite article/guide to build a REST API at scale assuming that GraphQL is overly complicated for our use case? I'm probably going to have to explain the main differences or at least contribute my own opinion so any link would be appreciated.

We mainly use python and we're probably stuck with MSSQL. I've built simple stuff with FastAPI and even Flask before but nothing serious.
> This leaks session cookies for your domain to Google in a way GTM did not previously capture.

Only if you set up your session handler to emit cookies that apply to all subdomains instead of using the __Host- prefix and the SameSite=strict attribute [1].

[1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Se...
the rifle cost ~$1500 including 25%vat, which is on the cheaper end of stuff you can buy (new) in my country. What I did however not pay for is more fancy wooden stock, I got the basic. I splurged on an absolute top end scope yes, because I wanted equipment I can count on :)

as for ammo, i Used the cheapest training ammo the store had (Sellier & Bellot fmj), which many people complain about not being super good, but works extremely well for me. I have noticed that some different boxes has a SLIGHT offset in where the hit is, but groupings are more or less equally good.

edit: I should note that the rifle manufacturer gives a 1MOA garantuee, but most are way better, and for about $1000 more they would take like 10 barrels and test, and give you the best of them. I choose NOT to pay the extra fee
You prefer an automatically generated read receipt that basically means "this person clicked somewhere in their client, it happened to open the email, maybe they read it, maybe it was an accident" to "this person read your email and consciously decided to acknowledge it and chose a particular 'reaction' to hint at what they mean"? Really?
This is an excellent point. You need to pull all the information about a system in a single place so that then you can choose what level of abstraction or deep dive into the details you need.

Projects like Multiplayer.app are in their early days, but I can see the potential of focusing on concentrating this info and automating the maintenance of docs and diagrams.
It was beautiful before they did this. You could introspect the entire Instagram API surface and write queries to scrape precisely what you wanted.
This, to me, doesn't sound believable, as conceptually, it such a trivial problem, that I don't believe Meta can not handle it. Maybe in 2016 when that article was written that was the case, but even then I doubt it.

Yes, for your average small team that hasn't figured out how to do resource- and subresource-level permissions, this will be tricky. That will also be tricky regardless of whether you are using GraphQL or REST (though with REST, the "solution" is often to write permission checks on a more coarse level and hope that they align correctly with the data you are querying).

However with the advent of Zanzibar and derivative solution and policy languages (Rego for OPA or Polar for Oso), it has gotten quite easy to do (sub)resource permissions without that being a huge burden on complexity and your codebase.
Show HN: I graded HN on a11y wall of shame
There's a strong correlation between accessible content and machine-readable content, so a11y should also be on-topic for hacking. Many large tech companies treat a11y as a legal obligation. Many disabled people have enough of being viewed and talked about as a legal burden that has to be resolved. If you want to see more apps or websites being graded, please submit suggestions via feedback form or HN comments.
In case you haven't realized, you're the odd one out, today, in 2024. I don't mean this in a negative way - I just mean that you're out of what's usual.
Sixth Saved Customers over $3M by Securing Payment APIs
Hopefully. The CEOs act so irrationally (at least in communication to employees) I can imagine they will ignore Gartner, too.
I tried the examples on iOS Safari and the performance seems really bad. Even scrolling is super choppy. Could this just be the examples page?
Guess people can actually get fat via breathing and drinking water now.
Check out https://www.multiplayer.app/
That's the project the author is working on.
Fast-food for education.

In my opinion, the whole AI trend is another round of industrialization making low-quality options for the poor.

- You're too poor for meat? Here is some hyper-processed, growth-hormoned burgers.

- You're too poor for a proper house? Here's a shitty pre-fab with walls so thin you can smash through them with your bare fists.

- You're too poor for fancy clothes? Here's a Bangladesh-sweatshopped T-shirt that won't make it past 3 washing cycles.

- You're too poor for school? Here's a computer with an LLM on it.

You could say that at least poor people have houses, steaks and education, but in the end, it's just a way of paying people less, cause they don't need much to send their kids to college anymore...

In any case, you can be sure that Harvard kids won't get any of that crap.