skysight-inc/HackerNews huggingface dataset:
That's said, I totally agree with the author.

The fact is that Next.js is becoming complicated. It's not simple anymore. Now you have to use a app folder with "page.js" to make it as a route. It's not file system routing anymore. It's folder router.

Besides that, app folder is slower than pages.

The amount of complexity to build a simple react app is overwhelming. You need to know the conventions created by a so called convention free framework.

I've been building nextjs apps for 1+ years, but for the next one I will be looking for an alternative, maybe Remix, Redwood, I don't know.

Vercel became Apple. They really like to make great presentations, and events, to their releases, but, instead of increasing the developer experience, they are decreasing it. The only good thing about vercel, as said by the author, is the Next.js deploy, that is really easy to do.
I like your style, but it's not quite right:

$ echo /proc/[0-9]/status | wc
1 7 105
$ echo /proc/[1-9]*/status | wc
1 483 8778

It also will sporadically print error messages due to all the race conditions. Here's my stab at it:

$ cat dumbps
#!/bin/sh

case $# in
1)
;;
*)
echo "Usage: dumbps user" >&2
exit 2
;;
esac

2>&- find /proc -mindepth 2 -maxdepth 2 -type f -name status -user "$1" | awk '{
while ((getline li < $0) > 0) {
if (li ~ /^Name:/) {
split($0, fn, "/")
print fn[3], substr(li, 6)
break
}
}

close($0)
}'
$ ./dumbps "$USER" | grep -w 'bash$'
1616678 bash
$ ./dumbps 0 | grep -w 'systemd$'
1 systemd
$

It's pretty fast too:

$ ls -ld /proc/[1-9]*/status | awk '$3 == "root"' | wc
445 4005 29367
$ time ./dumbps >/dev/null
Usage: dumdps user

real 0m0.001s
user 0m0.000s
sys 0m0.001s
$
In ETL work I often come across a nightly job that is harder to implement than most for some snowflakey reason, and I just start my day doing it manually, which might just take a minute. At some point I will get so annoyed that I will take the time to figure it out properly.
I think this is also first principles thinking going wrong: calorie restriction increases rat longevity and (presumably) reduces rat movement, and there's no good way to make calorie-restricted rats voluntarily do more exercise without introducing confounding variables, but that doesn't show whether a calorie-restricted human would live longer if also doing some exercise.
I think a fairer comparison would be Toki Pona, a micro-language with ~120 words. you can express lots of things if you have a great deal of patience, Up-Goer Five style.

In logic there's also SKI combinator calculus, which is Turing-complete with three symbols, and unlike the Morse or A-Z examples, but like the Toki Pona example, each symbol has a semantic meaning.

If you just want to describe ideas in an abstract realm like sequences of colors, like this paper, it's not surprising you don't need many words.
> these rocks get in the way and they need to be removed [...] you will periodically/frequently come across old "abandoned" stone walls [made] from the stones that were handy because they were removed from their nearby fields

You didn't mention what size these rocks/stones are (to my non-native ears, a rock is at least several centimetres), but if you can build walls from them, I take it they're not sand-sized. If you click the link in the first paragraph of the article, leading to the source, it mentions in the introduction

> Crushed metabasalt and olivine soil amendments were used to investigate changes in soil pore water alkalinity as a proxy for bicarbonate production. The metabasalt (median grain size: 102 ± 22 μm) was selected because of its benign elemental composition and modest weathering potential (the parent volcanics includes felsic facies, yielding an overall silica content in the intermediate-to-felsic range). The olivine (median grain size: 83 ± 12 μm), in contrast, was chosen for its potential to weather rapidly

TL;DR the remains of the crushed rock they tested is measured in micrometers
Logistically that would be a nightmare, everything by boat. Not to mention its surrounded by Cuba.
Device-measured physical activity, sedentary time, & risk of all-cause mortality
Genson-js is used to merge JSON Schema objects. Essentially there are 5 schemas that we care about in each request - request bodies, request headers, response bodies, response headers, and query parameters. Each endpoint (which may or may not be parameterised) has only one schema for each of these values.

The idea for a crawler is a good one. The core logic that handles spec generation is decoupled from everything else, so it can be extracted into its own library.

But there are approaches that exist for this already, such as har-to-openapi.

https://github.com/jonluca/har-to-openapi
I never understood the stuff of calling you on weekends or during vacation. Just don't pick up? If confronted, you can claim you didn't see it because unknown numbers are automatically silenced.

I've never seen a business that would actually fire you for this. And if they do, good riddance.
The other thing is remembering it’s not one full time sysadmin but many and also things like security staffing. One dude running some Linux boxes isn’t going to give you the kinds of audit logging, monitoring, encryption, etc. which is table stakes in the cloud world. You can hire those people, buy HSMs, etc. but then you’re talking a much bigger gap before you break even.

Then you get a step function cost increase building and operating all of the services your developers aren’t getting out of the box.
I've been using Migadu for a while, and haven't experienced any headaches. Which features/services do you offer that Migadu doesn't which makes things easier?
It depends. For what you're suggesting, we have the cross join/cartesian join. That would be the correct thing to use in this case, not what you've put.

But actually you have a point in that half the problem is the predicate is not linked to the tables, but the other half is the predicate is not predictable, after all it is a RAND(). That compounds the issue.
This definitely works. There's lots of papers on this.

Heck, you can verify this with ChatGPT yourself... just ask it a couple questions, then (in a separate thread) ask the same questions but tell it to "think step by step" as an instruction. It performs visibly better.

The point is it fundamentally, at the end of the day, it's generating one token at a time with only its prompt and previously generated tokens for input. If you can inject other information/facts into the context, or even context from another model instance that have a different "train of thought", you can in theory get better results than the model itself generating a sequence.

Look up Chain of Thought / Tree of Thought / Graph of Thought for an intro, as well as basically anything on retrieval augmented generation (RAG) or LLM tool usage.
I did read the article, so I can see that nothing I said was wrong, given the content of the article.

Given one of the first things I said was that they don't drive in all conditions, and the first thing on Waymo's "lets hype self driving" site is that they don't operate in all conditions, I'm fairly sure I'm right here. Unless you can point to the part of the article where it talked about how they controlled for driving conditions and locations of accidents, rather than the part of the article complaining about how their data lumped together unrelated regions.
https://www.useoptic.com/ is another one, which is a little more tailored to building & updating OpenAPI specs. Works well on live traffic and/or tests.
Even the Tesla Cybertruck's Brake Lights Don't Make Sense
> Each of these problems looks like the sort of thing that you solve quickly once and move on from.

Erm, including the apparent signal race and the illegal instruction?
Yes. Sycophancy is an undesirable and very dangerous quality if you're
worried about the weaponisation of AI for targeted influence. The
ability to "tell someone what they want to hear" is characteristic of
the dark triad cluster for NPD and most "healthy" people are quite
vulnerable to having their expectations mirrored back at them.

But then, that was always there in Weizenbaum's Eliza;

"I am hungry and thinking about dinner"

"Interesting that you're hungry, tell me more about dinner"

It was quickly recognised as part of the Rogerian seduction that
sucked user in to almost addictive sessions with Eliza.

I think it should studied, and should definitely be bracketed aside
from more neutral "bias".
14.4kbps club, checking in...

Everything this neal.fun -guy does is golden.

His last HN forey [password game] left me bureaucratic for weeks.
No, the critique (as I understand it) is that it's not using the system library but building it from scratch. From the description it's not binding his BoringSSL .so or .dll that exists on the system and building it, it's compiling its own pinned version and using that.

If it was using the system library and a vulnerability was found in it and the distro shipped a fixed package, then the swift coding using it would benefit from that fix without any recompilation needed (for back-patching distros at least, which is from my experience what people use in production systems). Ideally, even if you manually compiled BoringSSL for your system and the distro wasn't providing it, you could build again from a newer version or at worst patch the source of the library you originally built and rebuild it. Automatically building a specific version of a library, which may not be (and likely won't be) the latest version of that library with the latest security fixes, is a real problem.

Now, I don't know if BoringSSL was pulled in from vapor, or a dependency vapor relies on, but it is problematic to have the language libraries do this, at least if there isn't an option to do otherwise (and maybe there was, and it just wasn't surfaced through the layers as vapor built its dependencies). This might very well also be a problem with vapor and not swift, as it could be other swift modules do the right thing.
This is giving me flashbacks to Lode Runner on the Mac.
supply chain security is super important in a lot of areas but seemingly quite a hard problem to broach/solve. hopefully awareness continues to be raised/more tooling/etc
I bought version 10 recently enough that I was emailed this week with a free upgrade to version 11 which I appreciated!

I mainly only use it for text expansion, but it has served me well for years.
Aside from any business/ philosophical reasons they might have, one concrete reason for this is that the App Store prohibits apps from asking for accessibility permissions, needed for recording keystrokes, which I imagine would basically make this app impossible!
I run BenkoPhone which is the only business mobile number app in Australia that supports voice, txt and picture messages, currently 211 paid users in 50 different companies and $100k ARR.

The very first version was an old Android phone sitting on my desk that I connected to Trello for messaging and Bria for voice calls, for a handful of clients.

We later launched an app, but we didn't build the app ourselves we licensed it from a 3rd party vendor who does white labelling, and we used their demo version to sell the first corporate customer, who's setup costs paid for the white label one-off licensing costs.

Then we developed a proprietary, scalable hardware platform to manage the connections so we don't have to use Android phones anymore, but we still don't have our own VoIP stack, so when customers express interest in a free trial, we have to firstly contact each one to make sure they're genuine (almost all free trial requests are from scammers). Once they have tried the product, they put their details into DIFFERENT TypeForm, then we have to manually enter those details into our VoIP reseller platform and create the users and devices in the PBX, then we have to email our mobile carrier to provision the numbers because we don't have a direct wholesale connection yet.

That whole process can be automated once we have a different VoIP platform and have wholesale carrier connections.
The only reason why attack works on all browsers is because Apple force all browsers on their platform to use Webkit. This is why it's Apple problem.
I probably should have mentioned I've built unikernels with some of the tooling you've described here. It just seems very academic and edge case compared to a single static user space Linux binary that while technically isn't a by the book unikernel, all I guess I meant was that it's diminishing returns beyond that.
EBCDIC is older than the GDPR by 60 years.

Give the plaintiff his/her money back and close all his/her accounts.
Does it cause plex to freeze for a minute or two randomly on startup or when hibernating ends?
Wouldn't be here today without it.
Don't get me wrong, I love using them too. They are great for getting something setup quickly when you are getting started. I use some cloud services that support my single datacenter rack I have today. For my expensive workloads, I run them off three beefy bare metal servers in my rack.

I'd argue you have less visibility on what is going on at a cloud provider than you did in the past with your Ops team. Support tickets without a massive yearly spend at a cloud provider are pain and suffering. Even with over 1 million/year spend at one of my previous companies, support and visibility on underlying issues was a very poor experience.
You have to ask yourself the question why would farmers allow you to spread crushed rock on their farmland? There is no positive benefit for them. The academics didn't study the long term effects of it on the land. The land is the tool the farmers use to make their living.
Sub-linear scaling is powerful. Think about how costs scale in relation to use of a service.

If you are paying someone else for the service as a package, the costs scale linearly, or some close approximation of that. AWS gives you a small discount if you have larger volumes for some services, but these are essentially a rounding error.

If instead you launch a similar service in house, your costs are often dramatically lower per unit the more units you use. You start with a small team supporting a system with some large capacity you're not using yet because you need room to grow, and you realize large steps along the way where you can handle tens or hundreds of times the volume you see at each staffing level. Buying hardware or developing custom software gets cheaper at volume. This is sub-linear scaling.
Actually, I suspect it might be because the original version mentioned that the way we do things was not going to be popular with profit-seekers. Its tone was a bit petty, and I removed it.

Otherwise, it is absolutely relevant to the topic at hand. I described:

1) Native iOS-only (not something that will necessarily scale. A large part of our demographic uses Android, and I am regretful that we don't Serve them, but I don't write Android, and don't want to use a hybrid system or PWA)

2) Uses "tricks" to improve performance (I mention these may not scale into the millions. An example is loading a fast list of minimal info on all the users on the system, so we don't have to do realtime searches)

3) We do sign up users manually (BTW: lots of other posts, here, say pretty much exactly the same thing).

But it could also be because I mention that we don't collect PID, and that I eschew dependencies. These postures don't play so well, in today's tech industry. Dependencies are how to scale, but they can also add risk; sometimes, big risk. If we screw up our data, it could put people's lives, careers, and families, in actual, physical danger, so we're kinda anal about that.

But our app will be great. It absolutely Serves its users well, and we're already getting a great deal of positive feedback (We've only been testing since Monday). My main concern is that we may have to scale sooner than I expected.
Many "journalists" (talking head reporters) are business, communications, poli-sci, or equally fluffy majors rather than English and/or journalism majors. And there is no qualification to be a blogger, other than often taking money from sponsors without disclosing it or pitching their own wares as "news".

That's a shame a system of one exam deters people from their dreams. Is there another exam or another path elsewhere?
Yet the BLM land is mainly distributed precisely in those western regions where also ranching is done. Campers don’t feel such a need to roam on ranching land, because they could plan a trip around the BLM land. Out east where there isn’t much BLM land, there isn’t much ranching either.

I definitely understand the harm that inconsiderate travelers can do. Throughout Latin America ranchers are quite accepting of cyclists crossing their land, but the one thing you hear them complaining about is those cyclists not closing gates behind them.
Hmm... so just off the top of my head, I'm thinking one service would have to forward to the other. Only problem with that is that the sending server would now be the relay and not the original sender. Since MX records only account for using one service, there would need to be some sort of intermediary to do this. Possibly have mail delivered to a common server which then sends it to both Mango and Google (giving each the same odds to detect spam).

If you do end up trying it, feel free to shoot me an email either at contact@mymangomail.com or my personal, steve@mymangomail.com
In other news the Mining industry rushes to produce 3000 trillion tons of crushed rock, causing 1b cubic tons of rock dust over the world.
I feel sorry for you if you think the answer is never
I tried out Swift + Vapor back in 2017 when I was still a Mac user and a Swift enthusiast. I remember that at the time, I had quite a positive experience with Vapor 2 on Swift 3. I built a backend websocket server[1] for a hobby project[2], and managed to get it mostly working even though I was quite inexperienced in general.

The pain came later. They eventually deprecated Vapor 2, and I found that the new version of Vapor required essentially a complete rewrite, using some kind of async paradigm I couldn't quite grok.
I kept using the program I wrote for longer than I anticipated, and more pain came when I could no longer figure out how to set up the toolchain needed to even build the thing. Eventually the only way to build and run it was to use an old Ubuntu 16.04 installation.

This experience left me with a distaste for modern tooling with lots of churn, so last year I decided to rewrite the thing in C with minimal dependencies, so it's guaranteed to compile with minimal modifications even in 30 years time. Really happy with the result[3]. I added new features, optimized the websocket messaging with binary messages and zlib compression, and generally made it way faster than needed.

It compiles in less than a second vs. the minutes it took to build the Vapor version, and the resulting binary is 324K with debug symbols, 144K when stripped + -Os, and 68K when UPX-compressed.
It also uses a local SQLite db instead of a separate MySQL server, which makes deployment quite trivial (git clone && make run). The web client is still built with React, I've been thinking of rebuilding it with a single .html file and minimal JavaScript.

[1] https://github.com/vkoskiv/NoMansCanvas

[2] https://pixel.vkoskiv.com

[3] https://github.com/vkoskiv/nmc2
It's typically easier to make money from concentrations of money (rich individuals and companies), and those tend have more gain opportunities than problems (because they've already monied-away their problems).
Does it have to be two lines? Going to try this from home.
Thank you! I'll take a look asap
I'm a bit confused, does this article just end like this or is there something I'm missing?

"The Bookmarks bar faded to the background more. Bookmarklets are still in use, and still quite useful, but they are …."

They are what?
IDK, but it's a loom video:

<iframe width="100%" height="315" src="https://www.loom.com/embed/591fd03b54d04a74a15995815de47c76" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen=""></iframe>

Maybe they checked our gyroscopes and thought based on that we wanted to watch it at double speed.

Edit: weird, if I click that link, it plays at normal speed.
I just started using a modal editor this summer. Started with vim, progressed to neovim and landed on helix. I love the batteries included features and minimal configuration. Using a scripting language (Lua) for configuration was bit too much overhead for me to get started with neovim. I felt immediately productive using helix. I also prefer the selection->action model as well as native multi-cursor support. I would definitely recommend it to anyone looking to start using a modal editor. Experienced vim users might find it irritating to adjust to helix. In my opinion, it has the best out-of-the-box experience of anything I have tried so far. Though I will admit that Intellij is paying the bills for now and I use helix for all my school work. I hope to get helix to be my daily driver eventually.
This is a good opportunity to point out this strategy of climate denial, and why it is not a rational approach to refuting climate change.

Let's suppose that all the other commenters are wrong, that the river has not changed course in the past. The implication, from a probabilistic perspective is that P(evidence|climate change) is the same as P(evidence| natural variation), and your implied assumption is that because your prior belief that no climate change is more likely than climate change, then this works ultimately as evidence in favor that there is no climate change.

The reason this does not yield interesting results, even if all these other assumptions we're making hold, is because the hypothesis of climate change doesn't simply explain this one observation, it explain an enormous range of phenomena.

To explain away all of the observations explained by climate change you end up building a huge list of different hypotheses to explain away each fact. Even if individually these alternate hypothesis do explain each piece of evidence better (which in practice they often don't), and even if your prior for all of these other hypotheses is higher than climate change, because climate change is a single hypothesis that explains many observations, the joint probability of the individual hypothesis quickly becomes much lower than the climate change hypothesis.

In order to effectively argue against climate change you would need a competing singular hypothesis (or small set of very likely hypotheses) that ultimate do a better job explaining all of the observations we have collected.

I don't know if this fallacy has a name, but it sure should since it comes up in a lot of arguments about systemic problems.
I love that trope honestly. It's a great way to discover bad developers without having to test them first.
Tokamak folks are bringing SwiftUI to web and also to Android via SDL
A friend of mine likes to point out that Formula 1 cars are very light and the drivers aren't emasculated. But somehow this detail doesn't make it to the car designers in Detroit.
Using swift feels like you are living in a house that once had a interior designer build it from the ground up, but then his meth head friends come over for a party one weekend and never left.

The direction of the language is of breaking changes that really should be breaking, secret development of features that then get thrown onto the community during a keynote and just an unfathomable amount of complexity and cruft building up in every corner. Seriously, I would hate to learn Swift now, I barely tolerate it having grown up with it.

Swift 3 was almost perfect. I loved it. If they had of added async/await to Swift 3 I would use it for everything.
> it's missing many many culturally specific things like accents and other diacritics

fun fact: some of the symbols included in ASCII were intended to be used as (non-spacing) diacritical marks, specifically the tilde/caret/backquote characters...

[too lazy to dig up a proper source at the moment but the Wikipedia ASCII article covers some of this]