skysight-inc/HackerNews huggingface dataset:
There was literally no other way to get in contact with anyone, other than ringing their doorbell if you already knew where they lived, or asking around. Getting unlisted was unusual, and for most, would defeat the point of having a phone in the first place.

At least where I was from, early 90s, exchanging contacts was not something people did casually either, only for business or love (email/ICQ changed this when they appeared). I had a handful of numbers memorized, but would use the phonebook even for extended family. You’d have their number highlighted or earmarked in the phonebook instead of keeping your own.
Well if your working set fits RAM your tables will be stored in memory in the shared buffers.
That "occasional weird problem" is because systemd is not designed to be used with other software. While you technically still have the choice to roll your own non-systemd initramfs, it will be an uphill battle.
This is basically our exact experience at readwise.io too. Originally, everything was through Heroku.

We started by moving our heroku redis and postgres to redislabs and crunchy respectively, which were 10x+ better in terms of support, reliability, performance, etc. Then our random addons.

We recently moved our background job workers (which were a majority of our Heroku hosting cost) to render.com with ~0 downtime. Render has been great.

We now just have our web servers running on Heroku (which we'll probably move to Render next year too)...

End of an era. Grateful for Heroku and the next generation of startups spawned by its slow decline :)
Really good points. LÖVE doesn't support https yet (that's coming in the next version) but for this I think pure http should suffice. I'm going to try to put this together with a tiny server shim to forward messages to each other. That way it should be robust to firewalls and so on.
I've seen people pay a yearly subscription for much less, so I'm not going to comment
There were "reverse" directories published by non-telco publishers indexed by telephone number and/or street address. Those were a lot more difficult to get your hands on.

When I was a kid I remember thinking about how cool it would have been to somehow scan the entire telephone book and have that data indexed differently. (I also thought it would make wardialing s ton easier since you could knock out all the known-residential numbers.)
What do you mean? Just venv your venv.
Bought this same oven and share the same quibbles but otherwise it's been great.

The criteria of knobs on an induction oven filters out quite a lot of options annoyingly.
I'm thinking a lot about these tools, and the biggest challenge in the space seems to be figuring out the right unit of work for AI to take on.

A signle class/function is too small to be that helpful, a whole app is too big and complex. A whole ticket is also still too big. What's inbetween? If you could divide projects into units of work of consistent complexity calibrated to AI's abilities, then you could probably get really good results.
Do you need oranges? Apples have seeds, skin, and grow on trees.

Redis has many niches where it is more suitable than a database. In particular, the low latency and simple concurrency model make it a perfect choice for building shared token buckets, for example. For simple operations that need to be executed many times at low latency, SQL is usually not the best choice. And sometimes, you really just need K/V and don't want to deal with schema migrations, DBA chores, debugging auto vacuum...

>Advisory locks allow you to leverage the same locking engine PostgreSQL uses internally for your own application-defined purposes.

That is like telling me that I can get across the river in a nuclear submarine instead of walking over the footbridge. PostgreSQL locks cause me plenty of headaches already without my application logic being dependent on them.
An extension or integration with https://mealie.io/ would be a neat thing have (we selfhost mealie but are still building out recipes).
.. and to maximize profit, make it live-updateable and subscription-based. And don't forget periodic online license checks which are mandatory for app to run.

/s
But the whole point here is that PostgreSQL will be used for other tasks e.g. storing all of your business data. So it will be fighting for the shared cache as well as the disk. And of course storage will still be involved as again you can't have in-memory only tables.

And having a locking system fluctuate in latency between milliseconds and seconds would cause all sorts of headaches.
I have only one that I use all the time "rcheckout". Since I use gitlab and it allows the creation of branches with a title like "ISSUE_NR-ISSUE_TITLE" I can do git rcheckout ISSUE_NR and checkout that branch without having to type the full title. I don't know where I got this from originally.

#!/bin/bash
git fetch

[ ${#} -ne 1 ] && { echo -e "Please provide one search string" ; exit 1 ; }
MATCHES=( $(git branch -a --color=never | sed -E 's|^[* ] (remotes/origin/)?||' | sort -u | grep -E "^((feature|bugfix|release|hotfix)/)?([A-Z]+-[1-9][0-9]*-)?${1}") )
case ${#MATCHES[@]} in
( 0 ) echo "No branches matched '${1}'" ; exit 1 ;;
( 1 ) git checkout "${MATCHES[0]}" ; exit $? ;;
esac
echo "Ambiguous search '${1}'; returned ${#MATCHES[@]} matches:"

for ITEM in "${MATCHES[@]}" ; do
echo -e " ${ITEM}"
done
exit 1
yup. it's gutting that nobody has put $ behind the bar to support it. the entirety of Reddit chat is/was built on Dendrite, but they (and many others) chose not to put money behind it, unfortunately.
When the mouse bricked itself, I was forced to switch to the trackpad. Maybe I could plug the mouse in, if I happened to bring my only cable from home (or maybe from the office) that day. But there was no way of knowing when the mouse was usable again short of interrupting myself to test it. Over time, I decided the mouse wasn't worth the mental overhead and switched full-time to the trackpad, which always works.

Plugging in a laptop is a nuisance, but at least I can do that every time I sit down to start working and it will manage itself all day.
My mate was good at extending a conversation when someone dialled a wrong number, pretending he is the kid of whoever they called :)
It's clear that there's some beginning of this in place. They reference it as initial in the docs there and it's missing quite a bit. I'm not a huge fan of what I'm seeing here where each actor is implicitly itself and a supervisor (i.e., ActorRef makes reference to the actor's children). I think I saw that first in Akka and while it makes sense in theory, I don't like the practice.

To me, your supervision tree should be dedicated to that purpose and forms a superstructure relating entirely to spawning, resource provisioning, restarting, shutdown. Part of what makes it nice in Erlang is that it's consistent and thoughtless, just part of designing your system instead of being behavior you have to write or worry about much.

Here with Ractor they've built a special monitoring channel and callbacks into Actor (`handle_supervisor_evt`). This implies at some point one might write a nice supervisor in their framework that hopefully has some of those properties.
What could possibly be the reason?
There are servers needed for the app to work, right? So I guess subscription makes sense?

Of course then there is the price of the subscription... But I'm talking about the model, not the cost.
> But I'd much rather just quickly tap a checkbox instead of press, press, press, press, press, press, press, press, press, press, press, press, press, press, press, press, press, press, press, press, press, press, press navigating the giant array of settings.

If I was making such an interface, that would be a dial or knob instead of buttons.
Thank you for answering a long standing question of mine.
Unfortunately, the Apple Developer account is not a one-time purchase and neither is the recurring payment to keep the server used by the app. People need to stop expecting one-time payments for online services
I can make your wine glass sing by rubbing the edge with my finger.
https://www.axios.com/2022/09/17/the-ultimate-billionaire-ta...

https://markets.businessinsider.com/news/stocks/warren-buffe...
what a weird comparison...
Not really. Because then once you restart that process you lose everything.

And it's far more likely you are continuously upgrading your process than Redis.
> ...according to some very deranged doomsayers including; The Verge...lousy predictions that were made by them.

Can you share the link to the article(s) where The Verge made that lousy prediction(s)?
Okay cool
Thank you for the feedback on the terminology - I agree there is a lot packed into that pricing. To answer these quickly,

“Apps” represent your application that you’d like to let your user extend. You’d want an App in XTP for each of your environments, e.g. “cart-manager (prod)” and “cart-manager (dev)”

“Extension Points” are the places within “Apps” where plugin code runs, and can be well specified with a schema. This is the interface between the host app and the guest plugin. It contains the definitions of the plugins functions that the host can call, the host apps functions the plugin can call, and the types that go across that boundary.

Yes, lots of XTP is open source - mainly the Schema definition as well as all of the code generators that make it easy for plugin developers to build against the Extension Point interfaces. This short example exercise will give you a good idea about all that:
https://github.com/dylibso/xtp-integration-exercise

As far as XTP vs. Extism, XTP provides both a DX lift on top of Extism via binding code generation based on our XTP Schema - as well as a production-ready platform to intake, host & deliver plugins.

We also have a very capable testing framework and simulation feature that is partially open source and runs online in XTP platform to guarantee plugin behavior and performance before you run it inside your own application.
I like your comment. Don't agree with your comparisons, but you write in a way adding to the discussion and bringing understanding.

In lack of better comparisons from myself, Santa Claus does not exist. As a concept and an idea he of course exists and has real impact on what people do and what they feel. But part of growing up is differentiating between what is real and what is lie. Enlightened adults shouldn't believe in "society", while still being aware and updated of the possible threats from people who believe in it.

Another example: "Courage" is an abstract idea, but also a very real description of acts by some people. But we all learn when we are kids to not let another kid manipulate us into doing something by saying "Do it or you're a coward!". Even kids learn this early.
> and to them USB-C is that weird connector where they never know what'll work today.

No? What world do you live in?

Both of my parents have used USB-C for years, and they're more careful with their charging blocks than they are with their cables. All they care about is plugging in their devices to charge and USB-C cables do that fine. Both Lightning and USB are replete with non-conformant counterfeit cables, it's a moot point since people throw away anything that is nonfunctional. 99% of consumers don't need Thunderbolt capabilities, so they don't actually care if it's there. That's why your mom and dad don't charge their phones with fully-specced cables either.

Considering that Lighting cables tend to max out their wattage at the USB-C minimum, I think these are some seriously bottom-barrel arguments. Even child-friendly manufacturers like Nintendo consider USB-C perfectly suitable to trust with children, because it's actually not that hard to deal with if you're just trying to charge a tablet. And so does Apple, if you don't consider the Mac a fully estranged business.
This is a big barrier for me replacing our gas stove with induction. I get why they use them (easy cleaning, flush profile) but I just find a knob 100x more pleasant to use.
100% agree with most of this. Most large organisations in Australia are just clueless about their needs and ride hype cycles with execs acting on FOMO. And they bought the lie that you need all these separate distinct engineers who are professionals in a niche. They think they are building a high end kitchen by having specialists and think they are hiring sous-chefs etc, but most of the time they are hiring line cooks, and in fact most of the time they should just be hiring short order cooks.

Most teams and businesses I know who are doing great things with data are mostly smaller companies and tech built up start-ups and hire one of two types of people. Generalists who can fill the gaps and are interested in everything, and staff software engineers who are amazing developers and asked to put together data pipelines with consideration of the whole infrastructure.

When I was looking for work, all the good companies were not hiring data engineers or machine learning engineers. They were hiring Senior Software Engineers with a remit to build data infrastructure, or build machine learning models. And they immediately removes 90% of the noise applicants.
Physical buttons allow for memorized action sequences, though. As long as the input layer has some kind of FIFO buffer, it doesn't really matter how much lag the actual application has. If "call home" is always just "button A, 3x button B, button C" it is absolutely trivial to repeat that without even looking at the screen.

Touchscreens don't work quite as well for this. Even if it allows for input queuing, you often still need the previous screen to finish drawing to have a frame-of-reference for your presses. Even the slightest delay turns into an annoyance, and when it involves some kind of drag-scrolling a 50ms delay already becomes unbearable.
For those of you that might be interested, the Rainbow was an attempt by DEC to make an IBM-compatible AND a CP/M compatible in one box - it was a very nice box, and made a great VT200 terminal, but the compatibility was just not there.

The Apricot was another attempt at an IBM PC compatible, this time from a UK company. It was awful. You could not fit an Ethernet card into it without using an expansion box, much like the RAM pack on a Sinclair ZX81, and with similar reliability.
It doesn't make sense, because "the top" is not defined.

Regurgitating dumb terms merely perpetuates their use; it doesn't make them informative.

Another great (non-tech) example: "red flag warning."
Man… fuuuuuck. I appreciate you summarizing the majority of bad stuff we’ve created and are exacerbating. I was already familiar or aware of all that but this will help me communicate with others, “here read this person’s comments”

I have young children. At this point I hope they have a society, fuck having a “better life”, that ain’t happening. But it does force me to focus on what’s important. If we regress to a lifestyle comparable to the first third of the 20th century, we can handle that. We’ll miss regularly working electricity and indoor plumbing but you gets used to it quick. Just go camping for a week

It certainly sucks, and it’s frustrating that it isn’t our fault.
heroku is giving a simplified devex but a lot of it you can reproduce for a lot cheaper on aws. there is some heavy lifting to build the pipelines at first but then it would be pretty similar
Nice idea. It would be great to plan a week's menu using something like this. Currently, we alternate weeks and it ends up being one week of the same 6 recipes and one week with slightly more variety. Then there is the kids who won't eat 80% the foods we'd like to. :-( Tough to please everyone.
But how do you know what position 5 option 2 is set to the person you voted for on the tabulation machine for a bubble fill? It's not like the counting machine is OCR'ing the choice to figure it out. In the end the pattern of dots on a scantron to what the computer thinks the ballot was is just as illegible as a collection of bar codes. It's practically the same thing.

I'm fine with it so long as the choices are also printed in a human readable way at the bottom. If it was just a giant bar code or whatever I wouldn't like it.
Definitely a thing on the other side of the pond.
Michael Bolton: Testing Is Not Quality; Quality Is Not Testing
GP did say they understand why. Doesn't mean it's compelling from the other side.

'Pay for what you use' (micropayments?) seems under-explored outside of cloudhosting to me. Some small cost per meal solves the same problem while seeming more reasonable (or more obviously reasonable) to the consumer, doesn't it?
before going through README start here: https://hsutter.github.io/cppfront/welcome/overview/
You can also use html5 as a display output for gtk applications.

https://docs.gtk.org/gtk4/broadway.html
It just demonstrates that there is a lot more natural complexity in writing UI than CRUD endpoints or small services.

Sure, the browser environment (DOM etc) introduce plenty of problems, but it's going to be more complex than slapping together CRUD endpoints regardless.
Back in the day, you had to pay to get an unlisted number but you could get a listed number listed in another name at no added cost.
How are you auditing what the machine actually rendered from the constellation of dots you filled in for its actual count?

A collection of dots and a collection of bars are the same to me in terms of trusting the computer actually read it right.
They might blackmail you to get at their higher level targets. Still not much you can do about it, unless you work at AT&T or Verizon or Lumen, or you report the blackmail to the FBI, something most people probably would be extremely uncomfortable doing given our security services tend to suspect anyone who reports anything to them as the first prime suspect. Maybe there is a statistical reason for that, but it also deters any cooperation. And going through channels often is blocked by business/profit concerns. Espionage probably often happens through relatives and friends of VIP's, though that's a guess.
UrbanSpoon (again)?
Pretty pointless benchmark since it does not use prepared statements (that much is obvious from the low TPS, plus I confirmed it with how he ran the benchmark). You need to pass "-M prepared" to pgbench. And it is very possible that the Redis benchmark is equally flawed.

If you have to parse and plan queries every time PostgreSQL is obviously much slower than Redis. It is much more interesting to see what happens if prepared statements are used.
All of this.

It really makes you wonder, and by that I mean it really makes me think unflattering things, about the monoculture of 26 year old infants who designed and built all of this.
I’m torn. I like that MLS lets me see the same set of properties regardless of using Zillow, Redfin, etc, but I’m also wary of monopolies and overregulation. This also has a classist vibe to it of making sure only the “right people” inquire about a home.
Good correction. In my experience, some people will say "It's society who is responsible to help the disabled person", and some people will say "It's I who am responsible to help the disabled person".
oh!
the site has been down due to new interfaces. i will fix it in just a sec. sorry for letting you down. i would be happy if you tried again :)
Why would you do 50k+ connections if they can't be active all at once either way? Unless you have 50k+ cores and IO beefy enough not to get overwhelmed due to that.

You can have as much connections as you want, but you'll have to trade it for having lower work mem numbers, which hurts performance. Traditional advice is to keep it below 500 per PostgreSQL instance (I'd say physical host).

I've ran dozens of micro services handling thousands of requests per second with a total connection limit of around 200 of which most was still unused - all without any server-side pooler.
So now you need another URL-based bookmark service to remember the URL.
> Every ballot should have a UUID that the voter takes with them (or make it a hash of their voter registration number or something). As soon as the ballot is processed, the results are posted to a public place. Voters can then confirm their ballot was recorded accurately.

Opening the door for vote bribery or voter intimidation.

$1,000 for every tag proving you voted for my candidate.

If you don't prove you voted for my candidate, expect some retaliation!
IIR it was $1.50 month for NY Tel in the mid 80s, about the same cost as a hamburger for this times.
So a modernized version of Spore.
RIP magazines. Sad to think that they will be replaced with half-assed Wikihow articles or one-size-fits-all OpenAI-hallucinated slop.
Hand in glove, the only distro with stack zero-initialized by default. As of yet, still no SSL integration in crypto library.
POV-Ray development is resuming
After a long break in releases of 3.8 beta test candidates, development is resuming, though not at the pace of past releases. That said, the team hope to have a 3.8 release ready before the end of the year.
We put 1M files into DVC, Git-LFS, and Oxen.ai
Hey all,
If you haven't seen the Oxen project yet, we have been building an open source unstructured data version control tool.

We were inspired by the idea of making large machine learning datasets living & breathing assets that people can collaborate on, rather than the static ones of the past. Lately we have been working hard on optimizing the underlying Merkle Trees and data structures with in Oxen.ai and just released v0.19.4 which provides a bunch of performance upgrades and stability to the internal APIs.

To put it all to the test, we decided to benchmark the tool on the 1 million+ images in the classic ImageNet dataset.

The TLDR is Oxen.ai is faster than raw uploads to S3, 13x faster than git-lfs, and 5x faster than DVC. The full breakdown can be found here.

https://docs.oxen.ai/features/performance

If you are in the ML/AI community, or rust aficionados, would love to get your feedback on both the tool and the codebase. We would love some community contribution when it comes to different storage backends and integrations into other data tools.
> Needing to constantly check if a specific return value is not nil just seems so sloppy but I have yet to come across a "better" way as it appears to just be a Golang convention. Is there a good post about better ways to handle errors in Go?

As others have identified, not in the Go language. In other languages which support disjoint unions with "right-biased" operations, such as Haskell's Either[0], Scala's version[1], amongst others, having to explicitly check for error conditions is not required when an Either (or equivalent) is used.

0 - https://hackage.haskell.org/package/base-4.20.0.1/docs/Data-...

1 - https://www.scala-lang.org/api/3.x/scala/util/Either.html
Or correctly invested, fuel the real good economy for 80years
ID requirements do practically nothing about duplicate voting.
Perhaps by 2126, Linux will no longer have C in it, but that's probably hugely optimistic.
what happened in gcp paris region then?
“Tool” may not be the right word; but being able to live monitor the vacuumer, to understand what table was taking how much space and why, to track min/mean/max execution time of queries, and, more generally, all the internal metrics that PgSQL exposes through a couple of SELECT has been a boon when debugging or optimizing.
Building My Resume in HTML Using Eleventy
It would be cool to be able to see what the other person has already swiped on or "favorited" so I can just look at that first to see if there is anything there I can immediately swipe on.
They were a thing well into the early 2010s until people began doing increasingly cruel “pranks” for Youtube views and wound up going to prison.
Get a Kobo and install KoReader.