skysight-inc/HackerNews huggingface dataset:
Yes, needing a fixed-sized array seems like a fairly common need to me.

a := [5]int32{0, 1, 2, 3, 4} // Go

let mut array: [i32; 5] = [0, 1, 2, 3, 4]; // Rust
Except that's not what they claim, at least not in the way you're claiming, which seems deny that there are men and women out there with sex genes other XY and XX and that intersex people don't exist. Because when people claim that "sex is a continuum" it's pointing out that while men and women cluster around having XY and XX chromosomes, the reality is more complicated.

People can be intersex, people can have sex gene aneuploidies, people can have male sex genes buy end up developing as females, as can the reverse happen. Such people are a minority, but they do exist, and that's what the spectrum is. And in case you're thinking the numbers are vanishingly small, they're not: intersex people alone are more common than red heads.
> It was announced on CNN today that we are in a full on proxy war with Russia which finally makes it official

CNN does not actually have the power to make things like that “official”, even if they did make that announcement (I have no knowledge either way), and even if “proxy war” was an official state in which one could be (it is not).
It's not true New England directions until you tell someone "turn left where the shop used to be."

But you're not going to give directions as "pass 15 intersections." If you want to get to, say, 55th and Cicero from the south, you'd say get off I-57 at 167th street, turn north onto Cicero, and, well, you can watch the streets count down. A savvy navigator would know that Chicago has 8 blocks to the mile (outside of downtown), so 55th is 14 miles north of 167th, but you don't need to know that: every major mile street will have a stoplight, and the stoplight will inform you which street it is.

Of course, 55th and Cicero is a bad example, since it's the intersection of two major streets (and the business there is a really, really obvious one that you can't possibly miss). If you're off of a minor street, you might instead say something like "it's the second left after Pulaski"--Pulaski is one of the big north-south mile streets, so one would have a rough idea of how far away that is, and you don't need to start counting until after crossing the main mile street.
> What a lot of SW codebases did to support AMD (see PyTorch code notably): codebase is still CUDA, have the conversion pass to HIP done at build time.

This is sort of echoed in AMD's stance on FSR2/upscaling, where they have explicitly stated they will not support any API that allows plugging, regardless of whether the API is open-source or not, or who owns it, because a pluggable API might allow plugging proprietary implementations. Their opinion is their solution is what's best for everyone, in every situation, so you don't really need DLLs or pluggability because why would you want to plug something worse? FSR2 is the best for everyone and you should really just be compiling it directly into your application.

https://youtu.be/8ve5dDQ6TQE?t=974

(this of course also makes it impossible to update versions of FSR2 if better ones come out subsequently - you can't do the DLSS thing where you swap in newer DLLs (at your own risk of course) and benefit from later improvements to a modular grouping of code. You know, sort of the whole concept of libraries in the first place...)

The HIP stuff is the same thing... AMD really wants you to convert once to HIP and be locked in forever, because Theirs Is The Best, Why Would You Need Anything Else? But of course HIP doesn't have a PTX-like concept so you really need to distribute as source and compile everything at runtime... because who would want library code or dynamic linking?

Anyway, like, I know it's not really a shocker but the "we love open-source!" thing is a bit of an act. They love it when it's an angle for them as the underdog to leverage their way into marketshare... and as the underdog when it's not favorable for them (like FSR) they'll abandon their pro-freeness stance. And they too have their closed, proprietary technologies (like their CXL alternative that only works with their CPU+peripherals and nobody else can use) that they don't open up either. Nor is AMD racing to open up chipsets (like the NForce or Abit days) either, that's all locked down and proprietary too.

I know that's not really a shocker when you put it like that, but, AMD really gets a ton of the benefit-of-the-doubt all the time. They have on multiple occasions shipped defective/marginal silicon at launch for example, and it all just gets brushed over and people forget all about it. Both Zen2 (low-quality silicon in the launch batch meant chips were missing advertised boost clocks by 10%+) and RDNA1 had massive incidents of the community downplaying very real problems because AMD Is Good Now, many of the affected users never had their problems resolved and they just kinda sighed and lived with it or sold the hardware and bought something better, and the fans swept it all under the rug and never talked of it again. Same for pandemic profiteering (while Intel cut prices), etc. There's just a ton of shit that people bend over backwards to find justifications for with AMD that just wouldn't fly with more reputable vendors.
> Live below your means.

To me, this is the hardest to do. In the U.S., this means going against society's narrative that more/better material things will make you happier. Beyond a certain amount of income, material gains lose their material benefit, but it's hard to detach yourself from society's thinking that you'll be happier if you have a $130k car instead of a $30k one.

One thing I like to remember is that billionaires are no happier than people who make a little more than ends meat. Bezos and Gates got divorced in the past few years. Musk is obviously searching for happiness and meaning to little avail. I know lots of people on fairly meager incomes who are much happier than these men.
PM here, and though I've only worked on delivering one web app, I was forced to follow this model because "we have a UX designer for a reason".

At some point the future vision of the UI was getting so unnecessarily bloated, our UX genius independently came up with Clippy, but if he were a fox...

Luckily we were sold and I got a new job because I knew I was gonna lose that fight
The difference between Cincinnati and St. Louis was stark to me; I grew up assuming that "north" meant "vaguely northeast until it gets inconvenient". The idea that a road can just go on in the same direction for miles and miles seemed like a sinister AI trap. Someplace like New Orleans or Montreal where the direction follows a natural feature makes way more sense in my head.
Thanks! Added a few:

C to Checked C by 3C - https://news.ycombinator.com/item?id=30857289 - March 2022 (1 comment)

A Formal Model of Checked C - https://news.ycombinator.com/item?id=30321535 - Feb 2022 (37 comments)

Why Checked C when there was Verona? - https://news.ycombinator.com/item?id=26499846 - March 2021 (2 comments)

Checked C - https://news.ycombinator.com/item?id=26190403 - Feb 2021 (133 comments)

Refactoring the FreeBSD Kernel with Checked C [pdf] - https://news.ycombinator.com/item?id=25989115 - Feb 2021 (41 comments)

Refactoring the FreeBSD Kernel with Checked C [pdf] - https://news.ycombinator.com/item?id=24019185 - Aug 2020 (13 comments)

Achieving Safety Incrementally with Checked C - https://news.ycombinator.com/item?id=19424106 - March 2019 (21 comments)

Checked C: Making C Safer by Extension - https://news.ycombinator.com/item?id=17939537 - Sept 2018 (55 comments)

Checked C: extension to C that adds static and dynamic checking - https://news.ycombinator.com/item?id=16588483 - March 2018 (92 comments)

Checked C - https://news.ycombinator.com/item?id=12049548 - July 2016 (3 comments)

Checked C – A Safer C/C++ from Microsoft - https://news.ycombinator.com/item?id=11936418 - June 2016 (3 comments)

Checked C - https://news.ycombinator.com/item?id=11899925 - June 2016 (156 comments)
Right. It's good advice.
Ah, Flash. Simulating a bouncing ball using keyframe-driven ActionScript that I only sort of understood was my “hello world” moment. Love to see it being used like this. If only I could find those old .fla files…
As many have pointed out, this is stretching the definition of "trained".

I could imagine some kind of smart watch for kids that would record every interaction they had for a year and build a model. Later as an adult they could have conversations with themselves as a child.
Parent is probably referring to the Tech Model Railroad Club at MIT, which is considered the first recognized group of hackers and predates Capt. Crunch by at least a decade.
Call me old fashioned but I kinda hope that buying a stake in the London Stock Exchange doesn’t count as a high risk investment these days…

Edit: ( though obviously it’s not as clear cut as it used to be :/ )
I think there's a lot of people with "F-Skills" in the workplace right now that don't yet realize this attitude isn't as conducive to stable employment as they think it is.
Why do you think that? I personally know grown adults who believe (or doubt) that dinosaurs did not exist.
One negative effect might be that you don't get to hear the music, read the book or view the art because you are not the wealthy patron or one of their friends. That's the way it used to work.
the irony is it is charged language thrown together single viewpoint videos that claim things like a "revolution" is really the problem.

The smart phone at the end of the day is a device, which isn't the problem, it is the content and culture of the content consumers and creators that are the problem.

I don't understand the mentality of instead of disciplining myself and my behavior, I will turn on something I can't moderate, and then try to convince or suggest that others are in mass doing the same.

There is no revolution here, it's a bit silly to even suggest there is.
They simply do not make them like they used to. Not after '83. Those frames were a real triumph of human engineering.
The GP comment about "easy to brute force" must be read in context with the remainder of the comment about "easy to brute force":

"Relies on human adherence to password best practices to maintain sufficient entropy. Learning from industry that this does not work in widespread adoption"

The GP's statement can be boiled down to: "users will choose poor passwords" (as in Password1!) because it has been shown time and again that "users will choose poor passwords" if left to their own devices to do so.

The 'easy to brute force' part then comes in as "for those users who choose poor passwords, this rig linked below will brute force their passwords pretty quickly":

https://gist.github.com/epixoip/a83d38f412b4737e99bbef804a27...

Note that the above performance page is a few years old, updating it for 8x of a newer Nvidia GPU should result in even more impressive performance numbers.

And in all fairness, any cryptography where a user chooses a poor password is then vulnerable to "easy to brute force" by a rig such as the one above. Not because the encryption algorithm is easy to brute force (usually it is not) but because the user picked a poor password, and that poor password itself is easy to brute force.
> It’s portable because: decrypting these secrets does not require special software! All you need is a browser.

No complex, million+ SLOC codebases to install, except the one browser. I'll stick with gpg signing my pass repo and call it a day.
I've already mentioned [Dialog](https://linusakesson.net/dialog/index.php) above; you seem primed to check it out; Dialog is a mix of ideas from Inform7 and Prolog. Crazy, and it seems to work.
You forgot to count plumbers, and everyone in the construction industry.

Also the guy that fills the milk bottles. My brother used to work in a milk bottling plant, but he was not filing the bottles by hand. A machine filled the bottles, someone overlook the machine, my brother was making the chemistry and biological test to ensure the milk was safe to drink. And there was some additional people they call in case the machine gets broken (or to build a new machine.)

You are forgetting to count a lot of people.
A reasoning is logically sound if it applies valid reasoning rules on well formed propositions.

Young earth can be both false and logically sound, in that case it would also be the case that some of its assumptions or models need to be wrong.

Another example of a logically sound yet wrong theory is the Ptolemaic model of the solar system, if nothing else because by Fourier analysis it follows that you can approximate well any periodic orbit using enough epicycles.
My suggestion:

The first step is casting on. This gets the first row of stitches on the needle and no matter what you have to start here. There's a ton of variations of it, but this is a nice basic cast-on:
https://www.youtube.com/watch?v=1vm6oaYzHyA

Cast on ~20 or so stitches and learn the knit stitch:
https://www.youtube.com/watch?v=Egp4NRhlMDg

Do this for a few inches until you can repeatedly go up and down without dropping/missing stitches and your work looks uniform. You'll probably have to pull it out and start over a few times. Also, about 98% of mistakes will either be dropped stitches, or things that can be fixed by intentionally dropping stitches and picking them back up correctly so this is a useful skill to work on here:
https://www.youtube.com/watch?v=9obiqiTAGNw

Then, do a basic 2-color scarf with the knit stitch:
https://www.youtube.com/watch?v=LsmHWRIo2UI

At this point, you'll have the basics down and a ton of muscle memory built up which lets you get more creative. A 1x1 Knit/Purl scarf would get you into purling (the "reversed" knit stitch, useful for patterning), or I jumped straight to socks which teaches knit/purl ribbing and some basic shaping.
I don't see why students need a seriously powerful device. Students are given chromebooks because all the applications they need are on the cloud.
Thinking about this at a higher level, the real problem is that we use C arrays at all. But we can't stop using C arrays, because libc and a huge body of other C libraries out there represent lists of data using C arrays.

As a useful counterexample, glib has GArray, GPtrArray, and GList, along with functions that you use to manipulate the lists. Those functions are presumably implemented correctly, and will prevent you from making out-of-bounds accesses.

But of course those things are not widely adopted, because they're not standardized, they're not in libc, and libc has not been reimagined such that all of its APIs take and return these safer list primitives instead of bare C arrays.

(And sure, GArray etc. are not necessarily suitable everywhere, as they require heap allocations. But I could imagine a safe abstraction that could allow for using stack or static allocations to back it.)

So I see something like Checked C as a band-aid, when the language and stdlib just needs a complete overhaul. Obviously that's incredibly unlikely to ever happen, so something like Checked C is a decent compromise, I guess.
Free speech is not in peril in America
If your argument requires a belief in the literal interpretation of Genesis, it's not a very robust argument since most people don't believe in a literal interpretation of Genesis.

If your argument requires a belief in an omnipotent omniscient God, it's a lot more robust because a small majority of people believe in an omnipotent omniscient God.
Liquidations listed in the Wyndham council area
I hand-wrote 'hello' on the freeform canvas. I tried command-F to search for the scribble, it couldn't find it. On an infinite canvas. What use is that to man or beast?
So you don't understand what's happening here. They are not "hashing a structure", they are digging into internal implementation to reuse code that runtime uses to hash the structure.

> Java had hashCode in 1.0, GvR added __hash__ to Python in March 1993 and shipped it in 0.9.9.

is not doing that. It is just providing an interface that happens to be filled for builtin types

Also Go is not object oriented language and types don't have default set of methods returning things so having type.hash() like Java or Python would make no sense. Whether that's a good or bad call is another discussion but writing generic Hash[T] is few lines of code and would be just encoding/gob into hash of your choosing.

There is a case for providing that in function doing what the dolt guys are doing but that would be "just" optimization.
That's a really nicely finished portable tool with great security in mind. I've built something like this a couple of months ago, trying to make it compatible with the OpenSSL lib encryption algo in case my GH account disappears one day. I never got to image encryption part though. It's nice to see that other people struggle with the same security concerns. https://github.com/doomhz/crypter
Using ChatGPT to make Bash palatable
Why did you buy it then? How could you not regret spending money on something you don't use?
Meeting at a point doesn’t count, so for example, blue could be recolored to be red.
The PMs, and the senior engineers. "Leave well enough alone" is never a winning pitch.

We see this phenomenon literally everywhere. The Patent and Trademark Office just replaced their perfectly usable Search page with something vastly more complicated, and incomprehensible at first glance.

When I was researching my article about Twitter and firing all those engineers, I looked at the R&D spending for Proctor & Gamble and other consumer products companies. It's usually 1-2% of revenue. They spend their money on marketing, where it belongs when your product is mature.
It costs a lot of time and money simply to keep a mission operating, and these are scarce resources that need to be used for every active mission, old or new. Missions are thus planned for very specific lifetimes. On an organizational level, missions that live too long past their due date cause a lot of problems, too.

This isn't cynicism- it's just the reality of trying to absolutely maximize the science return per scarce dollar spent. I personally would love it if ultimate lifespan was a feasible goal for every mission. So would pretty much everyone! But it isn't.
It depends on the context.

* If the package.json file can be satisfied by the lock file (i.e. if the two files match) then the lock file will be used unchanged, even if there are newer versions available. This is (mostly) identical to the `npm ci` command.

* If the package.json requires more recent versions of a particular package than are available in the lock file then this package will be updated (but other packages will remain the same) and a new lock file will be written. This happens if, for example, the package.json file has been changed by hand, and so the lock file is no longer in date. In contrast, the `npm ci` command exits and fails to install the dependencies.

* Similarly, if the package.json file has new dependencies that aren't in the lock file, it if dependencies exist in the lock file that are no longer present in package.json, then these packages will be installed or deleted and the lock file updated. Theoretically, only the relevant dependency and its dependencies will be affected, but because if the deduping algorithm, NPM may make other changes if it thinks it can simplify the dependency tree. Again, in this situation, `npm ci` will just fail.

There is one other minor exception. The `npm ci` command will never make any changes to the lock file, but `npm install` may still choose to update the lock file with additional metadata (for example if the lock file was created with an older version of npm). This will never change the versions, but it may look a bit messy in the commit history, particularly if different people on a team are using different versions of npm. As a result, I tend to use npm ci as my default anyway.

However, as a role of thumb, if `npm ci` is able to successfully install dependencies, then running `npm install` will always install the same dependencies. The only difference is when the package.json file disagrees with the lock file, in which case `npm install` will probably do what you want, unless you want some very specific results in which case you still have the npm ci command available.

(This has been true since at least npm v5, although I think there were some bugs in the initial implementation.)
It was perfect! Full of low-key wisdom and fun observations. Doesn’t feel like “content marketing” in the slightest.

I wish the Hapland series was coming to Mac, but I respect your decision to snub Apple.
NTSC encoding/decoding in C89 using only integers and fixed point math
I'd imagine lightspark would be useful here, rather than yet again reinvent a wheel.

https://lightspark.github.io/
i feel like its premature to discard the possibility of FTL travel and it should be taken into account when discussing the fermi paradox. if FTL travel / FTL communications exist, we have no means of detecting that
Never enough spotlight on Intel Management Engine.

Disgusting that Intel built a backdoor into everyone's computer and then only sold the U.S. government hardware without it.

https://www.bleepingcomputer.com/news/hardware/researchers-f...

More disgusting still, the backdoor has backdoors:

https://en.wikipedia.org/wiki/Intel_Management_Engine#Securi...
Algorithm Warfare: How Elon Musk Uses Twitter to Control Brains
Well thats unsettling
Those people don't hold an amount that's significant, though.
a real factor is that with larger organizations focussed primarily on squirting out glue, people with serious programming skills aren't really that useful anymore.

everyone hated putting up with the leet coder before, and now they don't really need one. they really just want people to consistently and pleasantly phone it in.
Besides youtube videos for the few basics you need for crochet, ravelry.com is a fantastic community and also has plenty of patterns. https://www.ravelry.com/patterns/search#craft=crochet&pa=pho...
I wonder if the confidence OP is detecting from their collegues is more due to unspoken 1, 2 and 3 rather than the explicitly mentioned 4. In our society it's considered kind of gauche to say something like "I could take a 100k pay cut and still pay the bills" or "I've got enough savings to go years without a job" but for many software engineers living well below their means these could easily be true. There are lots of people out there making $200k/year and spending less than $40k/year, particularly people without kids.
Try living, working, or shopping on Peachtree in Atlanta sometime.
I met Capt. Crunch at DEF CON 5-6 years ago.

I was so excited and even got a picture with him. Then I found out about his dark and sketchy past from others when I told people about it.

tl;dr = hes basically a sexual predator/creeper w young boys.
I tried Librispeech, a very common dataset for speech recognition, in both HF and TFDS.

TFDS performed extremely bad.

First it failed because the official hosting server only allows 5 simultaneous connections, and TFDS totally ignored that and makes up to 50 simultaneous downloads and that breaks. I wonder if anyone actually tested this?

Then you need to have some computer with 30GB to do the preparation, which might fail on your computer. This is where I stopped. https://github.com/tensorflow/datasets/issues/3887. It might be fixed now but it took them 8 months to respond to my issue.

On HF, it just worked. There was a smaller issue in how the dataset was split up but that is fixed now, and their response was very fast and great.
I specifically would prefer to live in a culture that 1) establishes societal expectations of a relatively even playing field, and 2) encourages companies that seek to add value, not rent seek.

Clear is a perfect example of a company that exists to extract value from a system, and and company that will fight to maintain the status quo of a shitty experience for everyone else. Every time I pass the Clear line, I wonder why some private enterprise was given this space, and handed this right to insert themselves in the security process.