skysight-inc/HackerNews huggingface dataset:
This is going to sounds super hash and will probably ruin a lot of folks days, so I'm sorry, but...I love how these snooty elitist overgeneralized denunciations of "those typeless savages" pass for reasoned argument and justification within the hoards of the type zealots.

When I think in reality, it's just people who were forced to use TypeScript because their workplaces gave them "no choice" (always a choice folks), are expressing their pent up rage, through a sort of weird, Stockholm-syndrome projection response--"Those non-hostages have it way worse than us, they're actually beneath us: subhuman even. I'm thankful to our Typed overlords for giving us dignity, refinement, and superior codebases. All praise the ascetic self-flagellatory TS gods."
Don’t use your ORM entities for everything – embrace the SQL!
To hedge the next question then: Why was the universe expanding so quickly?

It seems that the expansion must have been so fast that it was going faster than light speed, right? Otherwise the very dense universe must have gone black-hole.
It seems like that may already be taking place as part of this launch. I downloaded it to try after asking this question and it mostly works. Just some aesthetic stuff. If I can read news and wikipedia I'm pretty happy with a browser. Maybe make everything beyond documents a PWA or app?
They avoid depending on specific DB implementation for standard.
Yes, but the Linux kernel is still "non-trivial". You said git is not tolerable for non-trivial projects. I think you just meant that it isn't tolerable for "incredibly large" repos, which I do think is right.

It's just a boring semantic point that I'm making, that "non-trivial" was a hyperbolic word choice.
Induction is twice as fast as gas.
Depending on your project, you may find that Dart+Flutter is a suitable alternative. The Dart syntax is simpler than Typescript, while meeting similar goals.
"Fetter this malefactor to the jagged rocks In adamantine bonds infrangible." -- Prometheus Bound
With LSP support VIM can do most of what you'd do in VSCode in terms of language specific refactoring. The plugin ecosystem is pretty rich.

Setting it up is still a nightmare, there are pre-made Neovim configs that I found helpful to start with (Nvchad, astrovim) but even then adding support for a new language is too much effort at times (as compared to VSCode where VSCode will suggest to download extensions the first time you open, say, a .go file and you just have to click)

VSCode with Vim bindings seems like a decent middle ground.
Origins of Color Coded Loot (2020)
There are alternatives to NPM, and high performance build tools. A lot of code-quality tools like linting are on the slower side though.

Ultimately people use TS on the back end because they want to simplify hiring and reduce context switching loss in developers mostly, and in some cases because their application is isomorphic. This choice works well when the ratio of front end to back end code is high (which is the case for most shops), since these benefits outweigh the downsides of developing services in Typescript compared to go (I wouldn't write most services in rust...).
Yes, and mitochondrial DNA integrity; and telomere length; and metabolic rate; and cancer surveillance efficiency; and stem cell exhaustion; and immune balance; and, and so on.

Let’s face it—-aging is wonderfully complex.
Why no mentions of Matrix.org, even if just to explain why it's not mentioned/considered?

A detailed comparison spreadsheet with ordered scoring: https://docs.google.com/spreadsheets/d/1-UlA4-tslROBDS9IqHal...
That point-to-point style is more reminiscent of 1940s-50s era radio construction than the 1970's post-transistor but pre-integrated-circuit PCB I was getting at. But very cool nonetheless.
Wait till you find out who owned the means of production in the USSR. Oof.
I get why it works this way because the alternative would be to force the fossil generators to sell at the renewable price and thereby making it uneconomical for them to operate which leads to brown-outs. I just think the societal costs the up very high because EVERYONE is paying a premium on power, and the total sum of that premium is only going to increase as we move more and more stuff over to electricity.

I therefore wonder if the market couldn't be structured in a better way which would still ensure that the fossil backup generators are adequately compensated but smoothes the extra cost over the remaining cheap GWh. Something like a meditating party which is aware of the production costs and buys up the daily power and sells it on at an averaged price. There are probably good reasons why this wouldn't work, but I am too stupid to figure them out.
Seriously. For some internal process tools, Django admin with custom models registered gets me 90% of what I need. The remaining 10% usually gets covered in a custom command that I can run from the shell
Nice puzzle. I found a 18 step solution but of course somebody posted one in the comments years ago.

Why not "one tree can be encoded into seven trees, or one of these 13 remaining cases"?

This direction is no problem, at least if we accept a graph with zero vertices as a tree which is probably non-standard as it should then have -1 edges. But if we allowed it, then a trivial mapping would be T -> (T,Ø,Ø,Ø,Ø,Ø,Ø). The other direction is much more problematic, one can easily map n trees into one, but then one gets stuck with either some trees that do not map back to any tuple or some tuples that have multiple representations. So now I am really curious what makes 7 special, so I will probably have to read the paper after all.
Reminds me of this beautiful 1964 paper by Janus Brzozowski where he applies differential calculus rules symbolically to regular expressions to derive a recogniser for it.

https://dl.acm.org/doi/pdf/10.1145/321239.321249
Notion Database Autoincrementing Ticket IDs
I've got a super useful tool to share with you: Notion Plus ID (https://notionplusid.app).

It helps solve the problem of a lack of incremental IDs in your Notion database with just three easy steps - installing the extension, permitting access to your database, and adding a numerical field called PlusID. It's completely free to use and respects your privacy (it doesn't collect any of your data). Plus, it's open source, so you can check out the source code for yourself (https://github.com/notionplusid/core). You can even run it on your infrastructure for free if you want.

We hope you'll find Notion Plus ID as helpful as we do, and if you have any feedback or suggestions, we'd love to hear them. Thanks for your support, and happy organizing!
I don't understand how "Black Lives Matter" and "BlackInTheIvory" is related to the content of this all. Why is this in there?

This reads like it was generated by ChatGPT with "Write a sad story about PhD qualifying exams but sprinkle in references to social movements about racial inequality"
That gets very ugly very quick for something as basic as e.g. memcpy or strcmp.
Say you're an indie game developer. In 2022 you'd pay someone on Fiverr to do a 'trailer' voiceover on your game trailer. This year, you'd use this - and also get a few more languages in there. Next year is gonna be an interesting year.
Listing all of these "techniques" doesn't address the important question: why are they necessary?

Why do you need to apply all of this conscious effort to "strengthen memory" if other people, or yourself previously, could easily remember the plot details of most movies you had watched, names of peoples you had met, etc. without ever having to think about it?
If you are autogenerating code you can generate it in JS and skip compilation altogether.
I think most consider it "somebody else's problem". I know some don't like to think there is anything to it beyond MHD, so they call anything involving plasma "MHD".

Are there other phenomena they see but don't like to talk about? Maybe?
My guess is that you don't have a PhD and didn't go through such a qualifying exam.

> I also don’t completely buy into the narrative that educated families make a difference in your PhD performance.

Your parents or people around you having a PhD makes a massive difference! Because they can tell you what to do if your advisor doesn't.

Most students who still need to deal with this system (most departments moved decades ago to written exams or to largely proforma quals) don't know that you need to: 1. Pick a committee based on their likelihood to pass you, not on their closeness to your field. The world is sadly full of assholes who want to prove a point. 2. Choose people who your don't want to screw over your advisor for some reason. It's important to ask your advisor "Oh, by chance, does X happen to hate your guts?" Because.. academic politics are nasty. 3. Choose an advisor with some pull, so that they can keep people in line.

All of these fields are so complicated with so many intricacies that if I want to fail any student, no matter how brilliant they are, rest assured I can easily ask questions that will lead to failure. This includes students who are much smarter than me.

I have guided many of my own students through this system. If you think your chances of success depend only on your ability and not your insider knowledge, well, you're wrong.

Also, on behalf of this poor student. This is not her failure. It is the failure of her advisor. Who was negligent for creating the conditions that lead to failure. Her advisor should have rehearsed her talk, her group should have grilled the student on related questions, and if the committee was asking totally inappropriate unrelated questions her advisor should have stepped in.
> My dad paid his own way through his PhD working part-time at Friendly's

Woah, in what field? There's no way a PI in STEM will have that happening today, or for the last 40 years really. Also, where was you dad having to pay for a PhD? In the US at least they are free and almost always have been.
Can confirm: Tweetbot suddenly stopped working for me, on macOS, a couple hours ago.
FWIW, none of this made any sense to me until I mentally ditched the concept of "tunnels." The metaphor was too physical for me?

Personally, the metaphor that made it work for me was "postcards going to a motel." As in AHA, when I'm doing SSH Tunnelling, Room 22 is the only one open and receiving mail, all the other rooms are locked. Now, there might be a website behind the door on locked room 443, and I can send my postcards to room 22 with the instructions to send them on over to 443 once they get there, and over at the motel they'll also know to do the reverse.
> I think its good to bring up SPAs in this context: fundamentally, they shouldn't exist, and you're using the browser wrong. They are the poster child of design smell when it comes to "web apps".

So a universal, cross platform, cross device, responsive, accessible UI stack that has simple distribution, avoids walled gardens and has excellent performance is a "design smell"?

> Do you need SEO to work, even though Google Search torpedoed effective SEO a long time ago? Search engines disfavor websites that are extremely opaque and are made of a single page or few pages.

Nope. I develop PWAs for healthcare and other industries. I rarely, if ever care about SEO. If I did, I agree that SPA is a poor choice, but for 99% of what I develop, the web app is a replacement for a desktop or mobile application. SEO isn't relevant.

> Do you need to be able to open content in new tabs, thus increasing productivity dramatically? Many SPAs will forget the app state and be unable to navigate back to where you were if you open it in a new tab. This also means you can't bookmark them either, and I've also seen browser tab/window restoration screw over SPA state.

Deep linking has been a solved problem for so long, it honestly makes me wonder why people keep bringing this up. Use a decent router. IMHO this is much easier to do in a web app than a native mobile app.

> Do you want browser performance? Using complex JS/TS to mangle the DOM and causing redraws outside of the initial page load is a good way to scare users off when their browser shits itself for 3+ seconds.

I'm not sure how you're developing web applications, or what stack you're using, but if you're seeing 3+ second DOM mutations I can tell you that you're doing something very wrong.

Web browsers are fantastically performant, I can't think of any other rendering stack that gives you so much capability with such performance.

There's a reason why XUL, Silverlight, Flex, XAML and all the others have disappeared or have such tiny market share compared to HTML + CSS.

The web has fantastic deployment and update capabilities coupled with a powerful rendering layer. It's easy to see why it's a popular choice for application development.
Diversity Doubletalk
The author was given multiple opportunities to pass a fairly clear bar of academic competence to hold the highest and thus the most difficult to attain qualification in the world, and they failed every time.

Exactly. If everyone could attain a PhD there would be no point to having a PhD because it wouldn't tell other people anything about your level of knowledge and competence.
The NIH and NIA support work of this type reasonably well. And they make risky investments. They have funded our work on aging genetics for 10 years.
A year on, we now know why the Tongan eruption was so violent
Oracle has zero customers but plenty of hostages
Ya, "tabs" are a misnomer coming from almost any other editor which is unfortunate. Vim doesn't have what most people think of as "tabs" (I guess you could think of them as "dynamic" tabs but I digress).

Vim has been my only code editor for the past 10+ years and I wish I used tabs a little better (ie, the way you describe). As it stands I have some plugins that open in a tab so they are easy to close (like gv.vim) and otherwise use my tabline as a secondary status line (it tells me my working directory and if I'm tracking a session or not).
Stuff like "isalpha", "tolower", and "strlen" long predates standardization of C, so they had to work with what they already had.
From my post: "If you’re paying a consultant, sure you want to get an hour work for an hour pay but an employee?"

It seems like we agree on the consulting bit but she wasn’t a consultant, she was an employee. Expecting 8 hours of work from an employee in an 8 hour day isn’t the way things work.
China executing a person is not an example I’m interested in modeling anything after.
You are basically saying that not abandoning c++ for Rust makes someone a bad developer. Sounds like suprematism to me. Not all programs are as critical and complex as web browsers. Not all code bases have the same security requirements, there are some legit use cases for trading performance or ease versus guaranteed memory safety.

And then even Rust is not a guarantee that an application has no vulnerabilities, as memory isn’t everything.

So please use rust if it make sense, but please also don’t force it upon every possible c++ software projects.
Breeder reactors are extremely fuel efficient. The cost is in building an actual breeder reactor itself, as it is an experimental technology. And the cost is not "widely prohibitive". The Wikipedia page says they are 25% more expensive than non breeder reactors.
Should mention this to the https://thisxdoesnotexist.com/ dev
A great point! Teamwork is important. This is also the reason having strong "soft skills" is more important than having strong "hard skills" about 85% of the time.
The examples are insanely good. Insanely good. I can barely believe we really live in a world where this is possible. I don't have anything constructive to add.. just wow.
Why isn’t this on the front page? I’ve been wondering what was going on, and had to actually search HN to find it. 11 upvotes in 18 minutes is definitely front page worthy.

Is HN actively nerfing Twitter posts?
yeah but that's borrowing trouble.

we can spend ages solving every theoretical.

and to be fair NOTAMs were rock solid until that happened, so if anything this failure was a good thing long-term
Which is inspired by the Powers of Ten 1977 short: https://youtu.be/0fKBhvDjuy0
I have an AI service from my mobile company that talks to scammers. Idea is to hold scammer on call as much as possible. Then you can listen or read transcribe of those calls.
Parroting the A player, B player cliche means that anybody you've hired has a choice of thinking either YOU are an A player, or they are a C player.
Yes, but generally only win the "do we have enough time for this" battle after a serious outage shines a light on the need for better tooling.
Leading underscore is only reserved if the following letter is uppercase. And it's fairly common for C++ code to have coding style that mandates that fields start with a lowercase letter anyway.
Not sure how big your team is but IME the larger team only increases the need for admin tools and makes lots of ad hoc bash/SQL console sessions more dangerous.

Even at a small size (a dozen or even fewer devs) I recommend doing what it takes for anything besides true one-offs to go through admin tools.

In general, I find that office staff want to be able to solve their own problems and will appreciate you giving them the tools to do it.
How it works with a team More than one person?

How many merge conflicts it gonna introduce with just a team of 4?

Mono repo also means that merging both frontend and backend into one, even with totally different languages? Should be fine with traditional web framework but how it will become for API+ SPAs?
This was very insightful and something I have to keep in mind! Thank you!
That would mean any interaction I initiate is a scam for the other party
The whole thing really comes down to this difference: If you want to change one piece of software, it's faster and easier with multirepo; If you want to change many pieces of software, it's faster and easier with monorepo.

All a repository really is, is a collection of files in one "bucket". No magic involved, no secret sauce, no woo-woo philosophical jargon to intone, no technical mastery to obtain. There are other features of a repository, like branches, tags, subrepos, LFS, etc. But you don't even really have to use any of those things. At its core it's just files in buckets.

The complexity comes in once you have to start working with these buckets of files. How do I change a lot of files in one bucket? How do I change a lot of files in a lot of buckets? When I want to perform an action with the files ("build", "test", "deploy", etc), in one or many buckets, how do I do that?

How do I do these things with multiple people simultaneously changing the same files? Or files that depend on files that depend on files? How do I coordinate the subsequent actions of the first actions on the buckets on the files with multiple people testing multiple changes simultaneously?

No matter what option you choose, there will be choices you have to make which require compromise. You will eventually have to work around the complicated consequences of these compromises. No matter what you choose, there is always a way to make things easier, but it always requires work to get there.

So really the question isn't monorepo or multirepo. It's what actions do you want to make easy first, and what consequences you want to spend engineering effort to fix first. But at the end of the line, assuming your product exists long enough, everybody ends up with basically the same system, because all of them, when people use them in complex ways, require complex solutions.
> He was hardly responsible for what that product actually was.

This is ridiculous. I'm not going to argue with you after this reply, because you're rewriting history.

> I'd suggest actually reading up the product release and what happened after.

I'd suggest not making assumptions. I don't have to "read up [sic] the product release and what happened after", because I was alive at the time. Were you?

"The Macintosh sold 50,000 units in 74 days, outselling every other computer" "Apple had sold 280,000 Macintoshes compared to IBM's first-year sales of fewer than 100,000 PCs" https://en.wikipedia.org/wiki/History_of_the_Macintosh#1985%...

>> Jobs was the leader of a team.

> Like Tim Cook.

No. As I already said, "Cook literally never led a software or hardware product team until he became CEO".

> Yes, and if you understand what happened there, it was the right thing to do.

It wasn't. Cook was purging a rival for power, and Maps was just an excuse. If it was right, then why didn't Jobs fire Forstall?

> By every account I've read, Jobs primary contribution was as an editor, saying "no" to bad ideas.

This is essential. I would love it if Cook said no to bad ideas. Soooooo many bad ideas lately. Terrible ideas.

> And again, by every "insider account" I've seen published, Tim Cook is doing the same.

Citations needed.
You’re right, I wrote too broadly but I was speaking specifically to being photographed and speaking specifically to US legal precedent on the matter.
Agreed, the intro and narrative ones are great. The news one is terrible.
Of course depending on how locale is set will effect the results of island() and iswater()
You can definitely stop working (in the traditional sense where someone pays you for your time).

This is a great thread from a 40yo lawyer who quit his job at the start of 2022. It took a lot of planning and patience but his account is a great one to follow if you aspire to do the same.

This was his recap of his first year as a very early retiree.

https://twitter.com/iamlandshark/status/1612912875068346368
>By definition, this is not having them do any computation.

If I ask you to compute the first million digits of pi to the power of 1.23456 and I already know the answer to validate it, how is this "by definition" not computation?
For small applications I avoid writing admin tools because I don't want to waste too much time. However though, an alternative to actually writing admin tools from day one is using django and then seeing if you need admin tools or not.
Lisa Marie Presley, singer and daughter of Elvis, dies at 54
For Session:

> Accounts can only be used on a single device, multi-device support is planned for the future

Can confirm that this is not true. I have multi device set up and it works just fine.

> Files are temporarily stored on a central server (encrypted) until the recipients retrieve them

Not just files, but also your messages. However, it's not as "centralized" as you think. The messages are stored across the Loki network, not just on one centralized server.

> Still new, bugs exists and features may change

Another con I would add is that it is painfully slow. There's often a delay of 10-15 or more seconds between sending a text message and receiving it. Interestingly, media files have about the same "lag". This makes faster conversations difficult, since I would send a message and an older message would backfill in making my message irrelevant. For example, I would receive "I have an idea", send back "what is the idea", but then a few seconds later a message would backfill in and appear before the message I just sent with clarification on the idea.

But that being said, I still think Session is one of the best truly-secure messengers out there. It's bug-free enough for daily use, very decentralized, solves the "offline message" issue. The only concern I have left is their weird crypto integration. The nodes in the Loki network are crypto nodes and it requires staking some $LOKI to join the pool. You do get rewarded for participating in some ways, however.
Now that I look more closely it was an April Fools joke. Whoops.

See the small note at the end:

> I just realized that this story was hosted on a blogger’s site, not the Beeb… and it was loaded on Wednesday, 1 April 2009… well done. You got me over two years later.
Twitter API appears to be down, breaking Tweetbot and third-party clients
Python without vscode and pylance is rough. And even then you need to keep up with the typehinting. Vim and python leaves me with all sorts of horrific runtime errors to debug.