skysight-inc/HackerNews huggingface dataset:
Nice, looks interesting, especially for the price points mentioned. Since using my RPi 4 with a passive heatsink as my daily desktop computer for a year now, I'm looking for slightly beefier options. I would love to be able to play SuperTuxCart again, it just doesn't work on my RPi.
Great project!
I can imagine this helps me get used to new codebases.

As others have already mentioned,
it's better if it ranks important files like main.js higher
than other util files.
models.js and dataUtils.js can be imported from 20 files,
but if dataUtils.js is created at the beginning of the project
and barely touched since then, it should be ranked lower.

I think it's nice to rank frequently updated files higher,
just like real page rank algorithms.
If models.js is imported from many files and updated frequently,
it should be ranked at the top.
main.js is imported nowhere but updated frequently; it should also be higher.
dataUtils.js is imported from many files but has not been updated for a long time; it should be lower.

It's much more complicated than normal static analysis.
Source code is no longer the single source of truth.
VCS' history should also be considered.
It has to manage those SEO scammers too.
We know those who commit again and again like
"Update, Fix bug, Fix typo, Fix lint, Update, Fix format, ..."
instead of a single meaningful commit message.

But if it's implemented properly,
it helps explore unfamiliar codebases much faster.
I’m working on building solutions for increasing the independence and productivity of visually impaired people.

Happy to colab!
I remember this was standard back in the day, and I think the time period was even shorter. Think it happened to me on Hotmail at 3 months.
The lawyer can control whether the opposing party settles in the same way I can control whether you retract you post and concede I was correct.
But they’re put together by amateurs, in non-static safe environments, operated with questionable cooling…
I disagree; I think that for many purposes, DSL will be good. It is not for all purposes, but sometimes it is very helpful for specific uses. However, using and implementing existing programming languages can also be good.

Sometimes, it is helpful to use another programming language and to use the full capabilities of other programming languages. Sometimes, other programming languages are unsuitable for various purposes, including that you do not want the full capabilities, or they do things which are undesirable for this use, etc. It depends on the program that uses them, probably. (Note also that, some programming languages will work better for the purpose of embedded DSL, than other ones will be, although it also depends on the specific use, too.)

However, some programming languages can be usable for multiple uses, e.g. PostScript is both general purpose and special purpose, as well as both text and binary format, and some people have said, also both esoteric and non-esoteric at the same time, too. And, many DSLs can be embedded in other programming languages and can be helpful, but that is not always the case; sometimes it isn't helpful.

Some game programs such as ZZT, MegaZeux, PuzzleScript, MESH:Hero Hearts, and Free Hero Mesh have their own programming languages. I invented Free Hero Mesh, and had designed it for this purpose. I also have idea of a format for Magic: the Gathering cards which can be executed in computer (a special design for this purpose may have many advantages including that AST-based text-changing effects can work).

There can also be data formats. JSON has some disadvantages (including: lack of comments, using Unicode, no optional trailing commas, no 64-bit integers, no directly blobs (they must be encoded), and other problems), so other formats can be helpful to be an improvement for some uses. RDF has some problem so I made up DRDF. And then, other format again, can be useful for different purposes; they will not all need the same things.
No, I think the quotation meant: «Chile has been investigating fog capture since the 1950s [...] [BUT] earlier attempts to turn the mist into usable water failed [UNTIL, (e.g.)] in 1990 fog nets at Chungungo, a fishing village north of Los Tomes, captured 8,000 litres a day. Villagers argued about how to share responsibility for maintaining the atrapanieblas».

They started attempting to obtain water from fog in the '50s, until in the '90s the first working atrapanieblas were successfully deployed. "The villagers regarded it as a collective critical success and conversely a common responsibility".
1. Linear reading: define things before talking about them.

2. Make documentation explicit, not implicit: no acronyms or assuming context.

3. No marketing or self-promotion: your code is not fast, efficient, reliable, convenient or secure because you say so.

4. No ego: nobody has time to read about you or a story from your life. Keep that to your blog.

5. No humor: if it's 3 AM and you are debugging a problem, and you are being forced to read lame jokes to understand what some code does, you are going to get frustrated as hell.

6. Punctuation, grammar, orthography.

7. No aggression: Nobody has time to read rants as they're trying to work on code.

8. Prefer simple English, leave local idioms and slang aside.

9. Conciseness.
I don't know if I'm using anything fancy, but Firefox currently is running 20 processes on my computer.

According to pstree:

3*[Isolated Web Co───28*[{Isolated Web Co}]]
3*[Isolated Web Co───29*[{Isolated Web Co}]]
2*[Isolated Web Co───26*[{Isolated Web Co}]]
Isolated Web Co───27*[{Isolated Web Co}]
Privileged Cont───25*[{Privileged Cont}]
RDD Process───2*[{RDD Process}]
Socket Process───4*[{Socket Process}]
Utility Process───2*[{Utility Process}]
2*[Web Content───9*[{Web Content}]]
Web Content───10*[{Web Content}]
WebExtensions───28*[{WebExtensions}]
chrome-gnome-sh───2*[{chrome-gnome-sh}]
firefox-bin
129\*[{firefox-bin}]
Most state management libraries help you deal with the problem of sharing state between multiple components. In modern React, most components are just functions, so this boils down to passing state through deep call stacks.

If you have a component A, which renders component B, which in turn renders component C, without a state management library you'd have to pass state from A to B to C (this is often called prop drilling). The longer the call stack, the more irritating this becomes.

State management libraries allow component C and component A to modify, and subscribe to a shared state store. Redux et al. are effectively the reactive version of global variables.
This site was particularly egregious.
Software Engineer Nerd Cave Setup Tour (10% Skill 90% Gear) [video]
Terms of Service don't override the law or CC networks' rules.
I think this is a really interesting thought about using package managers, although I would want to consider a few different models.

Trying to just break down the problem a bit:
1. End users don't necessarily donate. This is plausibly due to friction, that it's not worth / risky managing a bunch of small donations.
2. Corporations / Large users, are not well structured to make lots of small donations. The engineers selecting software are disconnected from finance, and pushing through payments is a barrier, with likely some exceptions that can be noted (like companies with individual $ allocations per engineer that they can direct).

Linking this to distribution / hosting services to me makes a lot of sense. I don't agree with the licensing model suggested. Something more like Youtube premium immediately jumped out at me, where I pay x dollars a month to the service, and a portion of that get's split up and allocated to the content creators. On youtube, this sounds somewhat equitable, as I understand it to be a distribution by watch time. On the package manager / software side, this seems way more difficult to allocate in an equitable way.

I like the core of the idea, that if you want to donate, you point your distribution at a service that tracks usage and divides/allocates revenue. And that service manages the allocation of donations, so reduce the friction on individuals and companies, and see the funding for opensource go up.
machine learning would be really good at overfitting in this context.
I've been using Pullstate for medium-sized apps for a couple years and it's fantastic: uses Immer under the hood (so it's all immutable even if it look as it wasn't), it's API and mental model are vulgarly simple, and my impression is that it's quite performant. I also like that the store is disentangled from the component tree, which allows for plenty of flexibility. Totally recommended!

https://lostpebble.github.io/pullstate/
Do they specify what kind of masks ?

It seems like masks, plus ventilation plus air filtering is ideal.
I have an Ice Lake Xeon W. It’s ok, compiles are pretty decent. Chromium takes a long time though, even with 24 cores/48 threads. If you want a lesson in how not to organize your source repo, the chromium project would be it. It’s kind of mind boggling how bloated browsers have become.
If Linkedin decided they wanted to put you out of business the lawyer would not be able to arrange a settlement. A lawyer does not even control whether their own client settles.
I work 40-55 hours a week and my house is paid off. There are busy times and slow times.
It would be great if I could pay package managers to take care of the security side of things.

Don’t bother with per package deals though, at least let the package manager deal with that, I want a single predictable invoice giving full access to all packages.

I would consider paying extra to be the last to receive non-security updates though.
Unfortunately this misses the difference in taxation vs. the US. You pay almost nothing for healthcare at any tech company and pay much lower taxes (both income and sales tax). So European offers are still much less competitive than the US.
> it was already recorded way before we had modern and industrial societies

This doesn't falsify the claim at all. Diabetes was first recorded 3500 years ago, and none of the other diseases on the list were literally invented by industrialization. Diseases of civilization refers (essentially) to diseases whose casualty rates dominate in societies of abundance and industrialization, by contrast to the predominance of (eg) infectious diseases in pre-industrial societies.

I do agree that it stands slightly apart from the rest of the examples, in that (eg) a contemporary hunter-gatherer still has a fair chance of getting cancer while they have a very low chance of diabetes/obesity. But it's pedantry to claim flatly that it doesn't qualify, especially given plenty of scientific usage[1][2][3] that contradicts the claim.

[1] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6362881/#:~:tex....
[2] https://link.springer.com/article/10.1007/BF00933491
[3] https://www.karger.com/Article/Abstract/323926
If its really an issue, then Higgs could ask for it be called some thing more descriptive such as the integral (spin) mass field/particle/mechanism.
I guess I don't buy this - there are systems which offer a lot of freedom and are still popular.

Legos, Jeeps, Cooking. HTML, Minecraft, some real-world, software options.

"Usability" can be something you buy on top of the simple system, or it can be free, depending. These aren't diametrically opposite properties of systems.
What about their parents?
The article mentioned that it’s possible - likely the kids contracted covid while outside of school. So it’s like saying if you only put up your umbrella to avoid getting rained on on mondays but the rest of the week you don’t have / use an umbrella, then you say “people still got wet so that means umbrellas don’t work”.. so if there was a way to say “did the kids catch COVID while at school” this data would be interesting but without controlling for other possible sources of infection this is not super useful data.. like if the data showed masks help, I would say this data also would be suspicious for the same reasons..
Orms are a huge mistake.

SQL is already a very high level API that compiles to low level algorithms? Why put another very high level API on top of that?

To top it off SQL is a leaky abstraction by nature. Two high level SQL queries with equivalent results can both compile into algorithms with COMPLETELY different performance profiles. You have to manipulate the SQL query to generate the correct performance profile. This means understanding things below the SQL abstraction.

You put a ORM or any new abstraction on top of that guess what? That abstraction must compile into hacked SQL. You have to be able to manipulate the ORM such that it generates the correct SQL such that the correct SQL generates the algorithm with the correct performance profile. The leak from the sql abstraction must propogate into the ORM layer which in itself must be a leaky abstraction. It's like dealing with a leaky pipe embedded within another leaky pipe.

Optimizing SQL is already a domain knowledge thing. Now you have to use new tricks to optimize the abstraction on top of it. Two Leaky abstractions on top of each other and both very high level is a bit of a head scratcher.

Why do people even make these abstractions that only make life harder? I think it's an illusion. It's to satisfy an OCD thing but people don't realize the OCD is an illusion. People want to deal with a single language, not have strings of another language living in the code. For example, SQL strings are seemingly kind of ugly in something like GO code.

Databases are the classic bottleneck of web development in terms of speed. Optimization is a very important part of writing SQL queries as a result. Having orms and other high level abstractions on top of this area is much much more harmful then it otherwise would be if databases did not exist in this bottle-necked area of web development.

In actuality it's also questionable whether or not a leaky abstraction in the first place was the right design decision. Is SQL the right abstraction for database queries? Or should we design another high level API that has a more 1 to 1 correspondence with optimization as in a High level API that's not leaky, like What Rust is to systems programming.
Those single processes are still mostly single threaded.

Don’t get me wrong, it’s still a huge leap forward to have a single webpage running in its own process, but there’s ample room for improvement.

That’s what GP is referring to.
I didn't ask about the "market value", and I wasn't asking you.
Editors are the key for any good writing. I've learned to assume that all good writing has a good editor/editing process, even if it's the author switching modes from creating to editing. David Sedaris writes amazingly well, and he says his "secret" is that every sentence has been edited and rewritten 19-20 times before it makes it into a book.

One of the reasons documentation sucks is because we expect people to write well without editors.
Isn't the Gunslinger effect actually distinct from drilling movements to become automatic/second nature?

Imagine two equally trained gunslingers. Both have drilled the drawing movements endlessly to the point where they're fluid motions that require no conscious decision-making. But the gunslinger who draws first ends up losing because the one who draws second is actually reacting, as opposed to making the conscious decision to draw first.
Hm? I meant the exact opposite. The barrister in the GP's anecdote had intricate theoretical knowledge of a very technical subject matter, despite not being able (or not bothering) to debug a simple Wi-Fi problem, which surprised the GP.
Actually C++ could be bridged thru Objective-C++ which at the same time can be bridged to Swift. A little bit manual, but possible
Splitting it evenly among the world population seems completely irrelevant for this conversation.
After we discovered the particle in June 2012, there was a large summer conference in Stockholm (a good few months before the Nobel announcement). In the spirit of jubilation the Municipality had arranged a classical “Nobel” reception at the Mayor’s Hall and banquet at the Vasa Museum in the evening.

As a good friend of the chair of the organizing committee, I was asked to help that evening, collecting invitations as people entered. After greeting the first 100 or so, up came this elderly man who has lost his invitation. He was very sorry, and asked if there was any way for him to prove he in fact was invited. I told the gentleman, that he could have mine in case there was any trouble. As Peter Higgs was allowed to enter the little dress rehearsal for what was to befall him in autumn, there was a warm chuckle around us.

I have met him on other occasions and perhaps it is exactly his non-selfish personality that has allowed the particle to carry his name in the first place. The rest of particle physics is luckily void of attributing eternal properties of nature to individuals.
One of the reasons why I never studied Geology and instead did Computer Science.

I collected rocks - had books on rocks - orientation day at the Geology Dept and the dude told me I am not going to be driving a Landrover but will be working in a mine.

I looked up the deepest mine in the world - recalled a childhood memory of spelunking in the Cango Caves.

Decision made.
Yes, precisely. I looked into bridging to C++ initially, but it was impractical.
Taption is an online AI transcription software, we take care of the whole workflow for you and is specialized in creating videos & audios with captions. Its built-in powerful and clean editing platform helps you speed up through these workflows.

Check out some of the features below:
1) Supports 50+ language transcriptions and 30+ language translation.
2) Labeling for managing your uploaded videos and transcriptions.
3) Personal dictionary to minimize future editing. (https://youtu.be/tITbtHTeN64)
4) Customized editing platform to give the layout you need.
5) Time-stamped editing platform and story timeline that allows you to adjust the time for transcriptions (https://youtu.be/7XqmsAaJHKY)
6) Directly trim the video by removing the transcription content (How cool is that?)
7) Output different formats (srt, txt, pdf, vtt, mp4)
8) Output MP4 with subtitles. (Support 30+ translations and bilingual subtitles)
9) Allow organization owners and administrators to invite users to their workspace to share videos and minutes.
It's called a behavioral question.[1] Many interviewers do it wrong. I even had a "job coach" swear to me that it was ok to ask hypothetical questions. So it may seem like BS because your interviewers don't know what they're doing.

It's not possible to detect skilled liars with these questions, so if you're one of those, answer however you like. If you're one of the rest of us, tell an actual story about you - the point is to get to know you.

Also, use the STAR method[2]. Some interviewers look for those explicit steps. And some interviewers don't know what to look for, so it can help for you to be explicit about each of those stages by name.

[1] https://resources.careerbuilder.com/recruiting-solutions/bes...

[2] https://www.mindtools.com/pages/article/STAR-method.htm
> I'd rather see small projects come and go as time permits,

What this really amounts to is that you/large companies like the work you get for free.

> OSS is one of the few remaining examples of actual public cooperation without a profit motive. Injecting capitalism into it is just going to ruin it.

This is so far off the mark. The profit motive made OSS what it is today. The only issue right now is many OSS devs aren't being paid/appreciated for their efforts.

> Having the funding model ("is it sustainable") be a separate concern from the codebase ("what's the best way I can make this library/framework") is a GOOD thing to keep separate, almost like the editorial vs advertisement/sales divide in journalism.

Agreed, but remember what you're paying for is the service of packaging. The idea is the package maintainer can keep the garbage out. That's what you're paying them for.

OSS is in many ways a market distortion. And that's good for some and horrible for others (e.g. grade school teachers used to get paid much, much less in real terms than they do today). A small fee for commercial, production use of Ubuntu's packaging service, a portion of which funds devs? I'm not certain that's a bad idea.
I have no vested interests (other than being a RescueTime user who likes apps that can also create global keystrokes) and I also think it's a bad model. I as a user should be able to trust a piece of GUI software to have privileged access to certain things; that usually means running as root. If there were a way to define a role which was privileged but only in certain areas (such as RescueTime getting access to all window titles and perhaps some contents but that's it), then that would be a possible argument against running as root, but no such thing has been proposed here.
Similarly, take anonymity, non-fame, low responsibilities away from your life suddenly and you'll realise how much you were taking it for granted.
Article headline is

"Nuclear power can play a major role in enabling secure transitions to low emissions energy systems"

Title is contained in the article under the following paragraph

> “However, a new era for nuclear power is by no means guaranteed. It will depend on governments putting in place robust policies to ensure safe and sustainable operation of nuclear plants for years to come – and to mobilise the necessary investments including in new technologies. And the nuclear industry must quickly address the issues of cost overruns and project delays that have bedevilled the construction of new plants in advanced economies. As a result, advanced economies have lost market leadership, as 27 out of 31 reactors that started construction since 2017 are Russian or Chinese designs.”
a professional drummer (full-kit) told me something very similar; the topic came up many times since we both did tutoring
That is correct. Let's now take the road of ignore the issues and act like they dont exist.
I thought the same. We’re not comparing old workstations to new workstations, we’re comparing old workstations to current day desktop computers.

An average build is more likely in the range of $1250 +/- 250$
I have a dual 2697 v3 and it's still remarkably capable. Single core perf is "not great" but for my use cases it works fantastically all things considered. Current specs:

- 512GB ECC
- x8 16TB spinning rust
- x8 4TB NVMe
- 1TB Intel P3600 for EFI boot and "misc"
- Nvidia RTX 3090 (rare dual slot)
- Dual 10gig ethernet + onboard 1gig ethernet

It performs well with just about anything I throw at it - even concurrently. 512GB of RAM really helps.

While this is more-or-less maxed out for my configuration I still couldn't imagine having three of them in my house!
> win this argument

Sounds like you've an abrasive personality. With emotional intelligence as lacking as yours, it's no wonder you think you've figured out the next three generations of cutting edge technology — you've left many requirements on the floor!

Try solving for problems as though other people actually have rich internal lives (and that their ostensibly petty hangups actually matter), and you'll discover that the technology industry is much more difficult than you think.
I like the spirit of this post.
I think there may be different types of barriers it conflicts with but having conversations like these are important.
I do sometimes think about the distinction of a non-business entity vs a business entity.
Is there a way to allow for individuals computing for the sake of computing (or using open source to create open source) to have free access, while enforcing that any entity making money from the use of the code having to pay for the usage?

Just thinking out loud, I don't know how naive that is (see gpl violations) or how something like that would even be economically structured.