skysight-inc/HackerNews huggingface dataset:
My gripe with your comment is painting NuScale and other SMNRs as “practical” or being representative of “new nuclear”.

People with expertise in building plants have been trying to dispel the idea that SMNRs will ever manage to be cost effective.

Even if you could manage to build them cheaply, which is a massive if, that doesn’t mean that the electricity they produce will be cheap. This is a classic example of horizontal scaling, which is tried and tested way of producing an expensive final product.

The nuclear power plant isn’t the product it’s the factory, electricity is the product. The smaller your factory/process, the less scaling laws work in your favor.

Take solar for example; solar panels are not the factory, a whole solar farm is the factory. Residential rooftop solar produces more expensive electricity than commercial rooftop solar, which produces electricity more expensive than utility scale solar. The panels can be the same, it’s all the other stuff, the “balance of plant”, that has a more fixed cost which you don’t get to spread out over as many panels. Same problem for SMNRs.
Also the rest of your body: especially head and shoulders, but core, hips, even feet are well worth attending to.
Its one of my top software role models. Minimal UI thats easy on the eyes and loads instantly, adaptive behavior thats ubobstrusive, really useful reports.
Same goes for XBox and PlayStation, but you don't see them using anything other than a closed environment.
Refer to the actual relevant pages: https://www.fairwork.gov.au/find-help-for/independent-contra...

This said, referring to the section 'sham contracting', actually covers, by far, the majority of contractors, which are effectively full time staff.
40 years in prison for digitally altering some pictures and videos. I can't help thinking that what is punished here is the sexual deviance per se, much more than any actual harm done.
Color theory is about the ratios between frequencies of light. That's what our brains respond to, along with cultural connotations.

Because color theory works on pretty much everyone, we can be sure that we all perceive the relative difference in colors the same way. But what green is is a figment of your consciousness. What you think color, sight, and all your other senses mean exists only in your mind. Not as a physical process in the brain, but purely as a part of whatever metaphysical process that results in consciousness.

A color is not a real, tangible thing. It's just the way your brain perceives light of a certain frequency. There is no way to describe what that experience is because there's no universal reference. You can't describe color to a blind man, after all.
Can I use my own el-cheapo SIM with it?
There is leetscrape [0]

For project Euler [1]

[0] https://pypi.org/project/leetscrape/

[1] https://github.com/csu/project-euler-offline
Actually, it's not that annoying at all - TIL about `git range-diff`.
It also does a number on your coronary arteries.

https://www.hopkinsmedicine.org/health/conditions-and-diseas...
It is still the Linux of statistical software. Rstanarm is getting quite good though for R users.
Far, far less.... they likely saved 75% or more. It started out as a 40 hour/week job, by the end, things got reliable enough that I spent most of my time waiting for things to do.
TLS is only transport encryption. The password will be transmitted in clear before and and after that transport.

This is not at all comparable to other "store my passwords inside the cloud"-systems, where the passwords are encrypted and decrypted on the users' devices, without the encryption key going to the cloud provider - that's the way it's handled in Password Managers, Chrome Auto-Fill etc.

And I would expect Microsoft asking the user for explicit consent "May we take your IMAP password and transfer it and store it in our cloud?" in easy to understand wording so people understand the consequences (for example getting fired for having punched a gapping hole into your employers security policies like "Don't share this password with anyone")

That expectation would match the law in the EU.

And in addition, inside the EU it would also have to guarantee that the password will only be stored on servers inside the EU, and not end up, for example, with the NSA. And even then it still might not be legal.

And from a user's perspective: Certainly a big chunk of users that have been using email software for the last decades would assume that an email client installed on your PC is doing the IMAP access locally. There is no need for your IMAP credentials to go to Microsoft. Merging your local mail store from multiple sources inside the client is what email clients have been doing for the last 20 years. There is absolutely no need to move this to the cloud. Yes, my computer can handle merging email folders.
> People are thinking about the form factor after the cell phone.

That presumes there is one. There's not yet a "form factor after the car" for example. Just refinement of the same basic 4-wheeled template, with a few oddball vehicles for niche uses.

A possible indicator here is the apparent lack of demand for small screen phones. To me it suggests that screen real estate is more valuable than portability for most people.
Ruby != Rails. There are a lot of bang! methods that will raise on error in Rails. But in general Ruby is just like Python in that it is indeed common to use exceptions for control flow.
Just a lil' nitpick, you absolutely do have to deal with office politics. Everything else you said was accurate though.
If those 20-somethings are journalists, yes. I understood and gave my perspective. The irony is that these writers/journalists are writing about news that matters to them that they hear from TikTok.
Show HN: Prtm – Protein Models in PyTorch
prtm brings together some of the most popular deep learning models for proteins. Currently covered use cases include folding, inverse folding, structure design, and sequence language modeling. The hope is that prtm will make building protein science workflows that incorporate these state-of-the-art models much faster and more enjoyable. Any feedback is very appreciated!
I appreciate it and do it myself. If HN supported hyperlinks of our words the way html does we could just do that, but footnotes are the next best thing. Big unreadable links in the middle of what you're saying, even just one sentence, muddy the message.
This a bunch of emotional responses, if you pardon my bluntness. It it a matter of opinion and has nothing to do with the word "objectivity".

I would call for some historical data and do some data-backed comparisons, but given your emotional responses it likely will be pointless.
I've actually seen this work quite well, in terms of voice recognition. The commands are specific enough and a lavalier / directed microphone can filter out most of the surrounding noise. Whether other people will be as happy with you speaking gibberish, that I can't say.
> The human body is very strange.

And clearly sometimes quite resilient! Congrats on the recovery
It depends; I write docs because I forget how to do things, so I write everything I'll need to know next time in the wiki, plus a little bit more to help me hand off to someone else so they can do the work too. And this apparently produces docs that other people find useful, because I get very positive feedback.
TorchRL: An open-source Reinforcement Learning (RL) library for PyTorch
It feels like the flow of useful research out of US military spending has slowed down considerably. You notice people are still pointing at the internet here.

The main advantage the US has had historically is just a much larger budget. If you can throw ten times as many darts, you'll hit the bulls eye ten times as often.
Here in Norway our IRS has long had very good web pages, including ability to edit you tax return (pre-filled), unlike most other agencies.

Turns out they do most development in-house. Most other use consultants, both for project planning, management and development. Go figure.
As a parent of a kid in a well-run Common Core program, yes. The goal appears to be to teach numeracy and concepts beyond just the rote application of formulaic solutions. When it's done well, you get students who can come at a problem from multiple directions, allowing progress even when they can't necessarily apply one solution correctly.
I disagree. Smartphones are very entrenched and a personal fashion statement in some ways. It's near impossible to get even a basis point marketshare in the global smartphone market. A wearable form factor is the right approach, though a pin feels like a weird choice - as opposed to a watch, earbuds, glasses etc.
This stuff is really worth of taking the effort to learn at least once.

I didn't actually write this up per se :P Technically, I dictated it and there's probably some gnarly typos with homophones in there that I haven't totally eliminated because it was a bit of a fire and forget piece, where I was just dumping my thoughts on a topic.
Ya, I'm guessing you would actually get better care in a country like Thailand, the Phillippinnes, India, or China. It might make more sense to retire in a LCOL place with good affordable healthcare rather than rely on Medicare. Heck, just get a good policy with evac to the USA if anything major happens you can't handle out of pocket (and at that point, it is probably cancer or something anyways). As I get older, it becomes more appealing to consider.

I had private insurance in China and it was wonderful. I could get an appointment quickly for whatever, the waiting room was really plushy, the deductibles were like 100-400 kuai, mostly the former. The biggest problem is that private insurance in China has a payout limit (around $100k/year for the policy Microsoft gave me)...which...well...whatever.
Did you expect a HN commenter to actually research the thing they're commenting on? :P
So this utilizes the tree-sitter AST and performs operations on the "parts" of the buffer? This, then, is very similar to textobjects in vim / evil, but with a spoken component.

I can see a lot of promise in this. Particularly if this integrates a sort of "record and perform" feature. Say I'm doing action X with my keyboard, and I know I need to do Y after, and 1) I can see all the required text on the screen, 2) it's a simple operation. I could then speak the command for Y while executing X, and then press the button to execute the voice command after I finish X. Much better than having to alternate between typing and speaking.

Alternately typing and speaking would lead to using different parts of our cognition, and writing software isn't very verbal once you've grokked the syntax. Instead, if one can type and speak at the same time, it'll work everything and make achieving a flow state much easier. Sort of like rubber ducking on steroids.

One could take notes, too...

I see an Emacs package coming lol.
That's not a sphere.
imagine how much worse it'd be if they weren't torx.
If I want to ask ChatGPT about something I will, and the speech-to-text is a lot faster than typing on my phone. There's no voice incantation needed, rather a button press, but people still raise their eyebrows and make me feel self-conscious. I wish I could subvocalize to it like I remember reading about in the book series Artemis Fowl.
The latency will make or break this. I run all the models on-device as much as possible.
We figured a way around that. On a PDP, you could detach your session, go about your business, then attach it when you came back.
> 15ms is about the threshold humans can detect latency

I think this is an oversimplification. We can detect latency, meaning a difference between input and screen response, at around 13ms.

But that doesn't equate to a new frame every 13ms being perfect, latency-wise. First, it ignores all the other sources of latency such as from input devices. Assume 6ms latency on the controller, that means you have to get a new frame out within 7ms from receiving the controller input.

That aside, there's a lot more than latency involved in creating beautiful smooth images on screen. For example, humans can detect visual change unrelated to input at about 500hz or even higher, especially in grayscale. I've heard that about 0.5m, or 2000hz, gray to gray is about the limit at which further improvements would be meaningless.

Of course the law of diminishing returns applies here. The fastest screen I've tested is 360hz and I can't say that I see any benefits over a 144hz screen, although I can see the difference in artificial benchmarks on blur busters.
I think Russia has mostly lost the perks of its USSR legacy in space to time, and I would argue has even less current experience than China on making new systems. Most of the USSR stuff would've been like NASA's stuff from that period, extremely reliant on the experience and intuitions built up by the engineers of the time such that reusing the designs from that time now is almost as much work as just designing a new thing from scratch. Russia hasn't invested in propagating that knowledge to younger generations, and the people from that time are quickly aging out of the workforce. So the only institutional knowledge they really have left at this point would be Soyuz, which, while a workhorse, is certainly not enough on its own to cover the systems needed on a space station/base of any sort.

JAXA, ESA are considered partners on the Artemis program (at least based on Wikipedia, there does not seem to be an explicit list of partners on NASA's site), they're training astronauts to eventually be sent to the Moon in a similar arrangement as with the ISS. JAXA and ESA (along with the Canadian Space Agency) are also contributing various key components for the Gateway space station. Plus, the ESA is an important player with the Orion capsule which Congress-critters seem committed to forcing to be the center of the program regardless of technical and financial sense.

As for ISRO, I think I mixed things up a little. I think I had heard talk about the potential for an arrangement to fly a vyomanaut to the ISS on Dragon, assumed that it was about the agreement having been made and then mixed it up with Artemis. Turns out none of that was real, there does not appear to be any talk of sending an vyomanaut to the ISS.
Spot on.

I am a bit puzzled that I have not been reading about this in any big US media, not even IT ones. How did you first learn about it?

This IS a big deal and should be a scandal people are educated about, and Microsoft should be forced to stop this immediately. It's interesting that Microsoft appears to have managed to stay under the radar with these deceptive tactics...
That I don’t know Windows well is certainly a factor, but I think it’s at most 40% of the problem. Several notable issues, not all:

- Competing msvc and gnu toolchains and ABIs, with native and Windows-first dependencies working better or exclusively with msvc, and *ix-first dependencies working better or exclusively with gnu, is a uniquely Windows situation. Which is which for a given build is also not clearly labeled most of the time. (You might mention glibc vs musl, but there’s basically nothing uniquely musl, and when you’re compiling for musl you can almost always get/compile everything for musl from the ground up.)

- Confusing coexistence of x86 and x64 is another thing largely unique to Windows. (amd64 and arm64 are much more clearly separated in Apple land.)

- Package management is a complete mess. Choco, scoop, win-get, nuget, vcpkg, ad hoc msi, ad hoc exe installer, ad hoc zip, etc. etc. There’s no pkg-config telling you where to look and which compiler flags to use. If you want to pick up a user-installed dep, you special case everything (e.g. looking in vcpkg path) and/or ask user to supply the search path(s) in env var(s).

Anyway, shit mostly(tm) just work(tm) on *ix if you follow the happy path. There’s no happy path on Windows more often than not.
Author here. This is a topic that fascinates me to no end, and I have a million questions for you that are off-topic here. Do you mind sending me an email to a@xkqr.org so I can reply with the things I'm curious about?

(Anyone who wants to discuss it can send me an email and I'll try to hook everyone up to the same email thread.)
Let me ask a more foundational question then, what is the virtue of a "stable" system?

In my mind, it's that updating a dependency doesn't break existing installations, or knowing that an existing install isn't going to get borked by an update.

And this is not something that is applicable to ecosystems like Rust, where it's not really possible to break a Rust program because another Rust program needs a newer version of the same dependency that happens to be incompatible with the older version. In fact, you can compile one Rust program that links against multiple versions of the same dependency at incompatible versions without issue.

So the entire notion of the Debian model of package management doesn't really apply to Rust, and there's not any benefit to keeping an older version of the toolchain around. There are only negatives.

And Rust has strong stability guarantees. A newer toolchain will not break compiles of older code. Nor will Cargo's cache break compiles with an existing lockfile because another package needed different incompatible versions of the same dependency. It's designed to be stable from first principles, in a way that C and C++ builds are not.

This is kind of why you're only going to have a bad time if you want to use the system package manager to manage your Rust packages. It's not built for the same problem domain, and over constrained for the design space.
For things that do not require more expressiveness than what Stan offers, I have found the speed and quality of sampling is outstanding. Furthermore, thanks to static typing, complex models are easy to write. To be fair, Pyro is also great and is my go-to for massive models where MCMC is unfeasible or for those requiring more expressiveness and/or deep components. I have less experience with PyMC.
It's a meme that's best resolved by using an ergonomic keyboard, or by moving the modifier keys.
Hardware divide has little to do with it. Historically, it is just the register width. Division is too complex and variable even within an ISA.

On a side note, there are still micros in common use today, such as low end Cortex that don't have any hardware divider. And the lifecycles of embedded devices mean that even older architectures, but still less than 20 years old such as ARMv5 without hardware dividers are still being maintained. It's not that historic.

The performance of hardware divide isn't something that follows simply from the "natural" register width of the processor anyway, it depends on the real estate and implementation given to it.

> I think older processors didn't have say a divide instruction at a bunch of different widths

But the common ones did, for example PPC and even the 8086. The reason for this is because division is slow and you get a benefit by using the smallest width possible.

> special width that was one-to-one with underlying instructions

That's usually just the width of the general purpose registers.

Of course 64-bit came along and threw this out the window.
there's nothing stopping you from doing this but its a real game changer for an early stage startup to need a new service and the steps to getting that out is one file and an extra line in your config.
Another reason to use something else than passwords with IMAP for authentication.
Woz is the almost-forgotten heart of Silicon Valley of days gone by, that has gotten stepped on and almost ruthlessly thrown out.

But we need him. I hope he recovers fully.
No. Basically the further the nerve is away from the spine, the better it's able to heal. Central nerves in the spine and brain have almost no ability to heal, but those in the face and hands can usually heal if they're cut.

Even if you physically put spinal nerves back together, they just don't reconnect. We can put them back together, but that's not enough.
Learn how to configure the Linux kernel using the intuitive make menuconfig interface and add new functionality with step-by-step instructions.
SRE brings a laser focus to system reliability, ensuring proactive management and a comprehensive understanding of the system's robustness.

In comparison, 'plain' DevOps might sometimes lack that specialized attention, potentially leaving blind spots in foreseeing complex system interactions. SRE is all about that extra layer of assurance for smoother, more resilient operations!
> McKinsey

Oh, fuck me. Fuck the McKinsey kids in particular.
Yes. The technical cost of having to backfill what they know needs to be strongly considered against the morale cost of the rest of the team observing that the company has chosen to keep a known harasser on the team for one more day.

If management is concerned about losing someone with a bus factor of one, how concerned should they be about "the whole team walked because they realized the company sucks and protects abusers?" People in this business are tired of technically competent assholes getting a pass.
Some very famous programmers I know are hunt and peckers.

(Lack of) Typing speed has not hindered their career.
The problem isn't "resistance". Reactors are just too expensive. The great hope of the pro-nuclear crowd is SMRs, and the current one being built in the US got canceled due to cost.

Until the cost problem is solved, nuclear power is dead on arrival. The existing plants were only built because of massive subsidies and the government placing a cap on the maximum liability from nuclear accidents.
It doesn't matter what they believed. Philosophy never involves rigorous proofs. By adding them you would just end up doing math. A partially finished proof is still math and not equivalent to 20 pages of worthless babble about human understanding. Throwing darts at the page and putting equations where they land will not change that. Philosophers constantly pull from the same small bag of tricks - inserting "science" or "philosophy of <science>" or "meta<science>" into their titles, Sokaling in random disconnected bits of scientific terminology to sound more credible, and trying to claim criticizing philosophy is philosophy to avoid criticism. It's unconvincing and embarrassing to hear from the self declared intellectuals responsible for some of the biggest false beliefs about science in history.
Host language is rarely ever declarative. Declarative languages are often necessary because they don’t leave any escape hatches that tempt you into writing incorrect code. Build system dependency graphs one common example. It’s also needed to pass data between different systems without recompiling and to constrain the usage boundaries, especially around security.

Imagine how absurd it would be if mongodb queries were written in the host language C++ instead of json.

For in-house stuff agree. There is no point to make excessive config layers if only developers will touch it anyway.