skysight-inc/HackerNews huggingface dataset:
I will add an additional stipulation that I won’t age - the period of time I want to go back and witness is slightly longer than 2 human lifespans.

PS: I don’t know how accurate these dates are, don’t cite these dates. I didn’t perform even a cursory sanity check on these dates.

I’d travel back to 1453 and witness the fall of constantinople.

Then, I’d make my way to Europe to watch the start of the protestant reformation, the rise of the Tudors and maybe go to Uzbekistan and join the 11 year old Babur in 1494.

I’d love to stay and follow him till he becomes the first Mughal emperor in India later, but there’s a lot more to see.

I’d make my way over to Lisbon and hitch a ride with Vasco da Gama in 1497 as he starts on his historic voyage that will take him to the Indian Malabar coast in 1498. (I’m a One Piece fan btw, I am imagining sailing with Vasco da Gama would be as fun as the manga, but reality will probably be more brutally medieval).

I’d then make my way over to the court of the Vijayanagar empire and watch Krishnadevaraya ascend to the throne in 1509.

I wouldn’t mind staying in Hampi for the entire duration of Krishnadevaraya’s reign - but in 1526, I’d want to go watch Babur (whom I’d have last seen around 1494) defeat Ibrahim Lodi and become the first Mughal emperor. From there I’d go to the court of Suleiman the Magnificent and watch the Ottoman-Saffavid wars.

I’d try my best to go back to Europe to watch Michelangelo in Florence and later Rome. I’d probably take a short trip back to England to watch Henry VIII finally marry Anne Boleyn in 1532.

Around 1539, I’d travel to Copernicus and probably stay and watch him finalize his book where he proposed the heliocentric model of the universe.

I’d then hike around a bit, watch the Renaissance unfold, go back and watch Suleiman make his way till Vienna and make my way back to India to watch the Mughal empire firmly settle in.

I want to witness the 1565 battle of Talikota. Somehow, that’s important to me.

Not sure what I’d do most of next decade. In 1572 I’d watch the supernova with Tyco Brahe. Then follow him around for a while watching the science and religion in Europe forever change civilization. Along the way, I’d stop by in England to watch Shakespeare plays as they come about. In 1600, I’d want to witness the incorporation of the British East India Company.

Then I’d go to watch Kepler work on Tyco Brahe’s data and compile it into his laws of planetary motion (published 1609). I’d also be there to watch Galileo build his telescope in 1608 and between these two, define our understanding of earth and sky.

I could go on, but I’ll stop typing now. You get the picture. Eventually, I’d return after watching the Taj Mahal be completed in 1648 I guess, though I’d love to stay behind and watch Newton do his thing.
KFC Reveals Its Next-Gen Video Game Console and It’s as Weird as You’d Expect
There was a cottage industry of software to get around DOS' single-tasking limitations. DoubleDOS was another program that let you have multiple sessions. There were terminate and stay resident (TSR) program like Sidekick.
> There is a big difference between the product of one’s work and the profits of one’s work.

Of course. That's why you should face the fact that if no one puts in the money and the legwork to jump-start the company, there is no taxes to be made nor there is profit to be distributed.
One that wants to handle a million requests per second?

Or would you want to do that with a Raspberry Pi? :-)

> What "normal-sized Linux server" has 70GB of RAM?

Also, why are you "quoting" what I did not say?
In Canada, you can't call yourself an engineer unless you are a P.Eng.
Yeah, that one was weird. If you follow the link it leads to this [0] lecture about why you should exercise your 5th amendment right to remain silent if being interrogated by authorities. Which seems like more sensible advice than "DON'T TALK TO COPS", though still out of place on a list of general everyday life tips

[0]: https://www.youtube.com/watch?v=d-7o9xYp7eE
I would love to know which air sensors you use.
Laws around unionization already exist.
There is hashicorp vault pki, square certstrap, cloudflare’s cfssl... but none comes with acme.
You may believe so, but it's not true. Let me explain. There are two somewhat different use cases for rebasing:

1. You want to do the equivalent of a merge without creating a merge commit, which is what I was mostly talking about when I was contrasting a merge based with a rebase based workflow. There is precisely zero difference in guarantees of things working or building or whatever between you rebasing or merging a branch into master. In fact, funnily enough, if you actually do testing/CI correctly, issuing a "git merge feature-branch" command to land things in master will, with high likelihood do a rebase rather than creating a merge commit. This is because you will have pre-merged (or equivalently, as far as testing the right thins is concerned, rebased) master into your feature branch first. Because that's the only way to actually test the right thing (the state of the code as it will be once it lands it master).

2. You can use rebase to (potentially wildly) rewrite individual commits (splitting them up, re-arranging or melding or editing them etc.) on your feature branch. This is not what I'm talking about, but, I have the feeling, the thing you are actually objecting to. And yes, you can indeed mess up previously working commits this way. If you feel uncomfortable doing this, just don't -- you can still use (and profit from) a purely rebase based workflow.[+]

[+] As an aside: there are ways of doing this type of rewriting that give you guarantees of working and building -- e.g. just run git rebase --exec "make clean && make test" ... (each individual commit in the rebase is tested before landing and the rebase stops on anything that errors out)[++]. But as I mentioned, you can still get all the benefits of a rebase-based workflow without ever engaging in this type of rebasing, and similarly you can have a fully merge-based workflow (for landing things in master) and people might still wildly rebase-to-rewrite their commits on their feature branches (and if they are not even pushed, who's gonna stop them?). These things are really orthogonal. Also, whilst I agree that undisciplined rewriting of commits is a bad idea, and can mess up previously working non-HEAD commits, it should never mess up the final commit on a feature branch undetected. Because you're running CI, right?. And at the end of the day almost no workflow will run full tests/CI on every commit (too expensive for anything but small projects), so broken "intermediate" commits can even happen without rebasing and if you do in fact run CI on every commit, well even undisciplined rebasing is perfectly safe.

[++] Also: I'd recommend preferring git commit --fixup to wildy messing about with git rebase -i on the fly.
Machine Learning Up-to-Date #28
#28 of the weekly newsletter from lifewithdata.org
Yeah, seems one has to provide a png fallback for Safari, otherwise it will not render a icon at all.
> Alan Moore run of Utopia

s/Utopia/Miracleman/
This is a beautiful take on life. Thanks.
> Apple does not disclose to you who bought your app.

This is a feature.

The paid update thing is a bit of a challenge on both sides; it does seem like someone should have come up with a better way to do this.
https://fossil-scm.org/home/doc/trunk/www/wikitheory.wiki
> But with LV wouldn't you need to create both a LV and a regular controller? That's a huge amount of code duplication.

You just do LiveView instead of a regular controller. No duplication.

When you request a page, it is render on the server and all of the HTML is returned over HTTP as usual.

After the client has received the HTML updates, live updates can go over a websocket. For instance you start typing in a search field, this is sent to the server over websockets. Then the server might have a template for that page that adds search suggestions in a list under that search field. The server basically automatically figures out how the page should be rendered on the server side with the suggestions showing. By "re-rendering" the template with changed data used with the server side template. Then it sends back a diff to the client over websockets. The diff adds/changes the search suggestions to the page. The diff is very small and it's all very fast.
I'm aware that at some point the Sun will expand and engulf Earth, but I'm not terrified of it.
The best short descriptive word I can come up with is "absurd".

It was clearly part of a carefully crafted social image he was trying to portray. It included signing emails with "wise sayings", fortunes, and platitudes like "let your inner light shine the way for others" and other nonsense, long rambling speeches about how we're all each other's brother, and a bizarre need to try to protect the worst performing employees from even minimal levels of accountability.

In practice he was pure chaos to work with and never contributed anything meaningful to our work despite having a great looking resume (including stints at some FAANGs and top schools). When cornered about actual technical work he was supposed to be doing he just became annoyingly evasive and tried to redirect the conversation into some kind of drum-circle feelings session.

It was like a cheap con-artist, a yoga class, and a fortune cookie had a baby.
Engagement is engagement.
Comic Sans is the Britney Spears of fonts.

Overused/Overplayed. Legible/Catchy. Well crafted for its original purpose. Gets no respect. Probably deserves a little, but it makes you feel dirty to give it.
I disagree, at least in Rust. async is hard. Threading is easy.
IANAL. As far as I understand, the Securities Act of 1933 can be prosecuted criminally as well.

See for example https://files.klgates.com/files/upload/se_manual_chapter_8.p...
That must be some kind of purgatory where developers goes to slowly die inside.
SVGs are such a better choice for favicons that I hope they become so dominant that we can drop the rest.
That's a good counterexample, although I'll note that Andrew Wakefield is referred to as the founder of the "science by press conference" phenomenon - so not really his research paper that was the single thing that attracted attention.
I enjoyed the time I had with notion, but ultimately it didn't feel "worth it" to keep around. The free tier is too restrictive, and while I preferred the premium experience, the price was ultimately much too high to stomach.
I have immense compassion for you, inferior being.
In Texas, the roster lists 60 professional engineers who hold active licenses with “Software” as one of the branches. I expect some of these individuals took and passed the NCEES exam in software engineering, which was offered from 2013 until 2019, when it was discontinued due to low interest:

https://ncees.org/ncees-discontinuing-pe-software-engineerin...

I imagine the individuals who obtained these licenses did so for prestige or credibility, to support the idea of licensing for software engineers, or because their work is related to other, more closely regulated engineering disciplines.

Some states try to control the use of “engineer” as a title, at least in some contexts, but I don’t know of any U.S. state that regulates the practice of software engineering, as such, nor of any credible plans to change this.
Not really. Exchanges have circuit breakers so the closing price. An frequently be the bottom or top of the market during extreme events.
I did a disk speed test comparing the M1 MacBook Pro's internal SSD to a WD SN750 inside a Realtek RTL9210 USB-C case.

The internal SSD gets ~2,800-3,000 MB/s read/write.

The USB-C case gets ~800-900 MB/s read/write.

If I'm not wrong, the M1 Mac's "USB4" supports 10Gb/s max, so external drives will always be slower.
And they seem to be pushing customers very hard on moving from on-prem to cloud for Office and email stuff. I don't know if they're subsidising the cloud services for now, or what.
I always viewed Jupyter/Notebooks as a sort of powerpoint, where quite simple content is presented in a flashy manner.

That explains their popularity.
Well, this is still better than just keep accelerating if there is a bug in ECU module. I would take “engine dies” over “stuck throttle” anytime.
I’m surprised that’s happening to you. I’ve never gotten pushback when I ask them to give the first number.

Usually that comes with the offer letter, or comes with the numbers that the recruiter reads to you before the offer letter.
I think OpenBSD uses it on purpose in their slides so people won't take them seriously. Just a theory.
I had the same thing initially.

The upside of async over a simple event loop is, in my experience, when things become less simple, and you end up with hard-to-read little state machines all over the place.

With async, you can have your event loop, but the state machines are handled by the compiler. Code is like threaded code. That can be very convenient.

Threads, obviously, accomplish the same thing, and arguably more easily. But threads have a performance problem when they must interact heavily. Cross-thread communication is expensive. Single-threaded async task interaction is very cheap, comparatively (I use tokio only in single-threaded mode, as an event loop replacement; its multi-threaded scheduler performs terribly on serious I/O). I think the interaction problem is often more important than just the number of tasks.

As for the function coloring argument, I've started to see the async keyword as documentation. A non-async function is "regular logic", it must complete without blocking. An async function is a state machine; as such it must be part of a larger state machine (the event loop), and it can go down into smaller sub-state machines (i.e. call other async functions). If you make that distinction explicit, it all makes a lot of sense.
It could well be Steve Jobs was arrogant in general. I haven't studied him that much.

But I don't read "everything around you (...) was made up by people that were no smarter than you" as necessarily arrogant.

It could also be read as recognizing that we are all equally frail human beings. (Possibly my own bias is showing too)
I could smell the BS before reading the article.

The heading is pure click bait based on nothing. Then the article turns into a "look how bad Amazon is".
Dwindling minority of Mac users that want a low Apple experience
How many threads can you spawn before the system grinds to a halt? If you're processing thousands of requests per second and each request gets its own thread then you will start to queue on thread spawning. Don't forget that each thread gets its own stack taking up megabytes of memory.

The async concept has been used for decades in pretty much every product I've worked on professionally, from enterprise raid controllers to network protocol implementations and telephony software. An engineer I respect once told me that really it's the only way to write services at scale, and anything else is just a step on the road until you reinvent it. He was probably exaggerating, but it is very important, and nearly ubiquitous.

Having used custom frameworks for async code in C and C++, it's really refreshing to have it baked into the language and well supported. It's yet another arrow in Rust's fantastic quiver.
> Details aside,

Sure, it just strikes me that you're willing to sorta handwaive an entire body of work that you likely only have a passing understanding of when that looks eerily close to people waving off the body of work that is science, which they likely in turn only have a passing understanding of, if that. Hard to demand people hold a higher standard when you don't do the same.

You attempted to explain a social antagonism by posing some corrupting Other badly influencing the youth, figuratively speaking, that's no different than people being anti-science which appears to them to also either be some corrupting influence or controlled by such. Social problems require more rigor than that.
What’s everyone’s preferred auth library for NodeJS based server use? It’ll be interacting with both a React based front-end from desktop as well as a SwiftUI front end from mobile.
> You keep mentioning companies and brands instead of implementations

This doesn't make any logical sense. I was clearly referring to Facebook primarily as an implementation, not as a brand.

> Client side a-b testing is impossible to be decent

OK, so Netflix, Facebook, Instagram, AirBnB - all web app implementations - cannot decently A/B test, but you can. Gotcha.

> Your react app is 30% slower that anything decent

How would you know, anyway? The web apps I've worked on (not app, in singular) are faster than just about anything "decent", faster than many SSR industry peers or competitors, and objectively so under many industry-standard performance tests.

You further resort to a personal attack by questioning my implementation or engineering chops without any evidence of them - just my evidence-based opinion that SPAs are not inherently slow at all (they really aren't).

I've got nothing against SSR, it's got its use cases and I've personally used it too, but you on the other hand seem to be an SSR jihadist - surely that could be a telltale sign of a really poor engineer?
Exactly.. it would also be possible to design an app that never persists any messages or other information on the phone.. though at that point the whole thing is just a shell over a website.

There were applications that worked that way before mobile phones and the web.
I have! Not my cup of tea (^_^)
Most servers support at least 128GB; it isn't even very expensive. And if you want to handle a million concurrent users you also need to consider CPU and latency, so for most real-world workloads the memory probably won't even be your bottleneck.
Now who doesn't what?
> If you eliminate all hassle, you could just as much pay people to live instead of you.

There are still a lot of things to do even if you have eliminated all the hassles. Singing, writing, learning a new language, surfing, volunteering as a firefighter, just to name a few.

I get it. Some people likes fixing stuff, building stuff with their hands, and it's perfectly interesting to them. At the same time, it's not that interesting to other people. Just like not everyone cooks, and that doesn't mean they are not enjoying their meal.

Last week, I spent a few hours learning about plumbing, in an attempt to fix my disposal. My quest failed, and I had to call a plumber, who fixed it in under a minute.

Next time, I'll call her directly.
Cultivate compassion for people trapped in religious dogma driven politics
3 reasons:

1. Pytorch is getting better at deployment. The only reason to use TF until recently was its superior deployment capabilities.

2. Google itself finally realized what a clusterfuck TF has been, threw in the towel, and started fresh with Jax.

3. Pytorch is king in research. ML is still very much a research driven field, so whatever researchers choose is going to win sooner or later. Jax is a serious contender though.

Google invested a lot in TF development, and the inertia will keep it alive for a couple more years, but the writing on the wall is clear.
Work is in progress, but the situation hasn't improved yet for end users.
Mise à jour majeure de Telegram
If I recall correctly, project Alexandria had also the (aspirational)goal of making available every book ever published.

You know, like the great library of Alexandria.
> Likewise, wouldn’t you be baffled if you needed to click a “Start Editing” button in Word or Google Docs?

Word (and friends) kinda has that. I'm not sure what the heuristic is, but in some circumstances it will put a message in the window title saying you need to save a copy of the current file before you can begin editing. I know it happens for downloaded documents, and that's about it.
Yes, the standard library has a bunch of legacy blocking IO stuff. But in general, most modern libraries tend to stick to a convention of:

- async (or explicitly Future/Stream): external effects (I/O, interacts with synchronization, whatever)

- &mut: local effects

- otherwise: pure
> I guess I'm trying to understand if it's me who's missing something

No you’re not. There is a similar situation in Kotlin, which supports coroutines. Makes things more complicated and is often used for very questionable reasons.

This is why I’m excited about project Loom, which will use the same old thread abstraction but can be configured to use fibers under the hood instead. Java devs don’t even care that its not traditional threading, its the same API! This simultaneously solves the „coloredness“ problem of functions.
I was 4% basic. Feels pretty good to me. The AI had some strong, and frequently stated about me listening to Best Frenz's (Joywave + Sir Sly) first and only EP which came out this year haha.
I'm not sure I get it. If the project that uses lsos is entirely open-source, then any company that decides they don't want to play nice can just remove the dependency on it, and use the project for free.

If it depends on the compliance of the user, why not just bake it into the license?
<!-- wp:paragraph -->
<p>RUN mkdir -p /sysroot/usr /sysroot/opt /sysroot/lib</p>

it seems that article's formatting is having some issues
Impressive monumental structures like that have been built. The Albany Mall, New York,[1] Nelson Rockefeller's monument to brutalism, probably comes closest. The Raj Path in New Delhi is similar, built huge on purpose to intimidate the populace.

Sheer size to impress has gone out of fashion, since building very large structures isn't a big deal any more. Huge convention centers, air terminals, malls, and stadiums are normal now, and don't impress people much.

[1] https://earth.google.com/web/@42.6489482,-73.7611536,51.2061...
There's something very pleasing about the monospacing with this particular font.

Font people-- any idea why I would enjoy the aesthetics of the monospaced version so much more than the old variable-width version?
The ErgoDox EZ[1] is very cool. The split is nice on the shoulders and upper back. My favorite part is that they are fully programmable and easy to customize with the online configuration tool. You can see my setup for some of the crazy stuff you can do[2].

[1] https://ergodox-ez.com/
[2] https://configure.ergodox-ez.com/ergodox-ez/layouts/mlGrD/la...
The claim isn't really that the book as a whole is necessarily good or bad. It may be expressed as such, but Crichton was talking about the habits of readers.

Determining whether a source is trustworthy is an ongoing process: you're seeing one portion where you have some expertise or evidence and then another portion where you don't. You have to extrapolate from what you can validate to whether what you can't is valid.

The complaint behind Gell-Mann amnesia is that we're too quick to dismiss clear evidence that a source is untrustworthy, that we have a bias towards trust.

To put it in perspective, let's imagine the opposite, call it Crank Awareness. If you see a document and it's laid out poorly, uses weird boldface, all caps, colors and blinking text, you'll, at the very least, get the impression it's written by a crank before you even start reading.

> But believing they are always bad is the same logical fallacy as believing they are always good.

Again, this comes back to the problem of strict logical reasoning vs. treating trust as a larger process. We have limited resources to evaluate sources, so we're stuck making fallacious generalizations when we need to make a decision based on our sources. What we want in the long run is to incentivize authors to exercise care and diligence.

That would indicate we should punish known bad information by deprecating the authors. So another way of reading Gell-Mann amnesia is that readers aren't doing this. They're seeing stuff that they know is wrong and continuing to patronize the publications regardless, thus authors can be untrustworthy and still collect a paycheck.