skysight-inc/HackerNews huggingface dataset:
An explicit goal I would personally like to see from build tools in the JS world is long term stability. I don't want my build tools to have a new major version every year. Semantic configuration improvements simply aren't worth all the churn. Adding new functionality is fine and great, but keep it backward compatible for as long as you possibly can.

This is an area where we could learn something from the Golang ecosystem. You're always going to end up with some warts in your API. Tools with warts that are consistent, documented, predictable, and long-lasting are so much easier to manage than tools that are constantly applying cosmetic revamps.
My alert indicated the magnitude and I received it before I felt the quake
>Hijacking back buttons

There’s nothing that infuriates me more than trying to read an article and suddenly being forced to either spam the back button or close the tab entirely.
How can the same program produce multiple different results?
Kind of fantastical that a vat of (mostly) water molecules present in the environment without any insulation would be in some kind of quantum coherent state.
Is rollup still a thing?
the source code was very well laid put from what i remember, and tests were particularly helpful for understanding how to use library code. i just didn’t feel like i quite had the knowledge to architect low level code in general, you must have picked up on that naturally
There is also https://www.zdaemon.org/?CMD=downloads
Some of database tables I worked with had over 100 columns.
I use laptops and not dongles, but obviously they run Linux.
> Companies need to promote creative problem-solving spaces, and I'm not talking about a beanbag area with free lattes, but a sit-and-think, light, non-social way of working that promotes this kind of thing.

Would that really solve the problem? I feel like when you're standing in front of your computer screen searching for a solution, it's because you're switching to some different and unplanned activity that you are able to get an eureka! moment. Creating a specific place where employees can go to think would defeat the whole purpose IMHO, because then people would go there and would do the exact same thing as when they're in front of their computer screen.

What may work is promoting short breaks during which employees can do any activity of their liking, whether it be playing video games, walking, smoking a cigarette... Basically anything that takes their mind off work. That guarantees development in creativity.
My shakealert had a prediction of 4.9.
The AI is controlled by the user prompting it.
> it is always possible to compute BB(k) for a specific and arbitrary k

How do you do that once k is large enough that it admits Turing machines whose halting behavior is independent of our axioms?
The total fantasy is the part where someone thought this keyboard would be useable, and called Amstrad like cursor keys "gamepad" https://en.wikipedia.org/wiki/Amstrad_CPC#/media/File:Schnei...
South-East San Jose and I felt it. Received a notification on my Pixel phone as the house was shaking. Nothing broken, but for the 5-6 seconds it lasted I had the reflect to hold my monitors (on arms) because they were shaking.
No, but fortunately Java doesn’t do that. They have long running projects, when one is nearing completion it will be put in preview in the upcoming release. No rush to make it into anything, it’s ready when it’s ready. (Which should be copied by the rest of the industry as well)
Yes. We need much more incarceration that’s proportional to crime rate. We need Federal forces to step in and evacuate SF and Portland. They’re inhabitable.

This is not sustainable. The answer to increase in crime isn’t to become even softer on it. We’ve tried that since 1970’s.
While we're talking about old ships, let me toss in a plug (ha ha) for the Edwin Fox. Not quite so old, but still very interesting history.
https://en.wikipedia.org/wiki/Edwin_Fox
By definition, each program only produces the digits of one number. It's okay for more than one program to produce the same number. Am I misunderstanding your point?
> Not to impugn your character, but I feel the same way about the points you're making.

Again, the original post about function colors talks about runtime, so how could I be disingenuous about that?

> Not in any meaningful way, no. Again, the runtime representation of async vs sync functions is unavoidably different, and has nothing to do with the language. The fact that Zig lets you write one function definition that can be called in sync vs async contexts (unless you're specifically choosing to do sync vs async things) is what it means to be colorless!

I mean, this would be true if it were true. But I tried to use the "blue" function in my examples in both contexts, and it didn't work. In fact, it didn't even work to use the "red" function in both contexts.

> I dunno if that's accurate? Someone with more knowledge of Zig internals would have to confirm, but I assume if the same codebase uses a function in each context it'll be monomorphized into the specific version needed, same as generics. I don't think that's contradicted by what you quoted.

I worded this completely wrong, so let me fix that. I should have said,

> if an async function is used in a sync context, the compiler makes the context async and continues on its merry way, so there is only one runtime representation of the function that was the context.

But it means that the sync function that was the caller is made async no matter what because it calls an async function. So there is no monomorphization; there cannot be since there is a call to an async function that always makes an async context that always turns the caller async.
Because it interests us.
This is the kind of work and effort you have to put in when the legal system stops caring about small dollar value theft. This isn't some anti-california thing either, I don't believe the cops when they say they don't go after small dollar crimes because of the DA because cops having been ignoring small time crime my entire life. They're just too lazy.

When my job gives me a task that's hard and complicated and has lots of paperwork, I don't get to say "naw I don't want to".
There is the community around ZDeamon [1]. As a Doom port, it has its own server browser, Discord and a built-in IRC browser to get to their channel. Binarys are available for Win, Linux and MacOs. IME, especially popular there are gigantic megaWADs, which are played by fifteensomething players in coop mode simultaneously.

[1] https://www.zdaemon.org
99 times out of 100 whenever I see a new tech demo that absolutely blows my mind and makes me optimistic about the future of technology it's always some big model deep learning AI thing. When are we all going to admit that ML/AI is the final and ultimate paradigm shift of our time
> it is always possible to compute BB(k) for a specific and arbitrary k

but wouldn't this be equivalent to solve the Halting Problem?
Was very disappointed that my iOS device had no alerting.
Felt the first one in Central Marin.

Today is actually the 33 year anniversary of the Loma Prieta quake -- weird.
https://earthquake.usgs.gov/research/eqproc/grdmotion.php

Especially: https://histre.com/highlights/kirubakaran/5b7c1756
If you want to select an integer uniformly random from 0...n-1, you need an expected logn mutually independent random bits. What if you don't want it to be uniformly random, but some other distribution instead? That's where Markov chains help; they use random bits efficiently to draw from an interesting distribution.
Of all the reasons I might imagine someone feeling like C is easier to pick up than Zig, "hardware-software knowledge to know how to architect low level code in general" does not make a ton of sense to me. In what way do you feel this was easier in C?
wow thats really good!
Even if you could, not sure it'd be a good idea from a ux perspective.

I'm thinking the more info you provide, the longer it takes the brain to process, and split seconds matter here.
No, but you do have undiscussed conditions to enter...
As long as a game allows someone to run their own server, a community never truly dies. There are people who still play Half Life 2: Deathmatch and Counter Strike Source because we can run our own server
> So your code can go as fast as you like

I've been working on an (IMO) sophisticated tactical game with strong AI in Pico-8 for just about two years now, and I can say that this is not true.

> which would require some kind of CPU-cycle accounting tracking

This is pretty much what it does.

Pico-8 tracks an arbitrary "cycle" budget, which is used to calculate how much computation you're allowed to perform per frame. You're absolutely not going to compute at "bare metal" speed.

Here's some info in the (community) docs:

https://pico-8.fandom.com/wiki/CPU

I don't know how this does/does not compare to the 6502, because I unfortunately don't have any experience there. But you're absolutely not going to get bare-metal performance inside of Pico-8.

You're right about limiting code-size, though. For my own project, the code size limits have proven far more difficult to work around than the performance limits.

Tangent now, but these are some of the Pico-8 limitations:

- screen is 128x128 pixels

- only 16 colors are available (sort of... there's a "hidden palette" too)

- cartridge size may not exceed 32 kb

- cartridge may not exceed 65k characters

- Lua AST may not exceed 8192 tokens

That last one has been the hardest constraint for me to manage, by far.

Anyway, Pico-8 is a ton of fun. Try it out if you're inclined :)
There are numbers that god can't compute, but that supergod can compute. Of course, that also means there are numbers that supergod can't compute, but that superdupergod can compute. And from there it's turtles all the way up.
Well, spring is pretty much exactly that, and is probably used more than all the other mentioned projects combined.
> I think this is why computer science has been so successful at co-opting a lot of statistic's thunder. It's reorganizing a lot of concepts, and because everyone is interested in the results (image generation, computer vision, etc) it's getting a lot of adoption.

I think it's also that "computer science" can be perceived as having succeeded where statistics failed. And the terminology is frankly a lot more appealing: would you rather "train an AI algorithm", or "fit a model"?

Even the recasting of "model" as "algorithm" has a marketing benefit: models have uncertainty and uncertainty is scary, whereas algorithms are perceived as precise and correct.
I'm guessing you're in SF or Oakland?
No. It has a mini-pci-e shaped port and some nvme fit that size, but i believe it is for expansion boards (like the cellular module?) you could add NVME via USB port, but this thing is more like a raspberry pi, and not going to have the IO to use NVME much faster than SD card speeds.
Your comment just gave me an epic story idea. Where our society collapses and far into the future, there are only stories about our age. Then they manage to build a computer, and watch a movie about space (with aliens!) Thinking there are people waiting for them in space, all of humanity gets behind creating an interstellar civilization…

So thanks for that.
> While this might allow you to refine your search criteria (and probably have strong funnel metrics), it misses the point that most frameworks are easy to learn and ramp up on. Great engineers all have the capability to learn new languages and frameworks easily.

There is just such a disconnect with reality here I am having a hard time thinking the author has done any actual technical recruiting. Sure, any engineer can pick up any language and framework provided enough time. However, an expert in said language or framework is familiar with the nuance. More often than not if your problem is harder than slamming together off the shelf components to fleece the consumers of their money the nuance comes into play quickly.

> You really need to flip this on its head. As a startup, you need to be comfortable taking risks on hires but also parting ways if it isn’t working out after 2–3 months. This will feel hard, but in the medium-to-long run will feel a lot more sustainable. Some of the best companies I have ever worked with/for have operated this way and it leads a culture that doesn’t compromise on high-performance.

This advice works when you have infinite capital from VCs in a market flush with free money. You probably spend 30-50k to hire an engineer after paying for everything and all the labor involved. You're saying to just throw this money away? Slow to hire, slow to fire is the only sustainable way to run a company. If you want to "flip the funnel on it's head" hire contractors because the message I am getting here is "increase developer churn". Moreover what even defines "high performance"? I swear, these vulture capitalists are getting far too big for their own britches.
yes, I didn't think about it, but you're right! However, I liked the idea to have a constructive way to build an uncomputable number
Having been a generalist at several startups throughout my career , can totally agree the highest leverage folks are usually just the smartest, not the most specialized.
Reddit is home to hundreds if not more of porn subreddits, including some that the majority of people would consider vile/controversial (rape, race play, etc.). While Reddit sometimes goes on a subreddit-banning spree, they often don't touch the porn ones as they generate a lot of traffic and I guess revenue (via awards). They are also indirectly used for escort services.

I wonder if they'll be gone if they IPO.
If you're noticing that the numbers that form a list are right below each other in the same column, it kind of makes sense. Suddenly it seems a lot more ordered. Could be done differently though. Left alignment seems clearer:

*ValueError: ExceptionGroup('eg', [ValueError(1), ExceptionGroup('nested', [ValueError(6)])])
*OSError: ExceptionGroup('eg', [OSError(3), ExceptionGroup('nested', [OSError(4)])])
| ExceptionGroup: (2 sub-exceptions)
+-+- 1 -------------------------------
| Exception Group Traceback (most recent call last):
| File "<stdin>", line 15, in <module>
| File "<stdin>", line 2, in <module>
| ExceptionGroup: eg (2 sub-exceptions)
+-+- 1 -------------------------------
| ValueError: 1
+- 2 -------------------------------
| ExceptionGroup: nested (1 sub-exception)
+-+- 1 -------------------------------
| ValueError: 6
+------------------------------------
+- 2 -------------------------------
| Exception Group Traceback (most recent call last):
| File "<stdin>", line 2, in <module>
| ExceptionGroup: eg (3 sub-exceptions)
+-+- 1 -------------------------------
| TypeError: 2
+- 2 -------------------------------
| OSError: 3
+- 3 -------------------------------
| ExceptionGroup: nested (2 sub-exceptions)
+-+- 1 -------------------------------
| OSError: 4
+- 2 -------------------------------
| TypeError: 5
+------------------------------------
Ideally I’d want to be able to toggle between app mode (which would allow hijacking) and browse mode (which wouldn’t).
Are you asking: "why does the site with 'news' in it's name report news?"

Or are you asking: "how does this earthquake in the place where much tech is centered and a large number of HN users live pertain to HN?"

The answer turns out to be the same: it's relevant to a lot of people here and they upvoted it.
True.

Also true: Very few of the Twitter engagements mean anything at all. Clicking a Twitter link is extremely low cost. If you're not even willing to do that, you don't care about the topic or the person that tweeted it.
Twitter is losing its most active users, internal documents show
this is the default response to try to ignore child abuse
I'll second that. I never hired anyone who couldn't do the work. The only times things went badly were times when the person basically didn't want to do the work, due to some personal hangup. No amount of interviewing is going to weed out that guy who can code perfectly fine but deep down is yearning to be a psychologist instead. Like any other job that pays bills, you are vulnerable to paying his bills until they find what they really want.

> In my experience, they just drive out the qualified people that can see projects through, and leave you with ... the ones that are really well-practiced in short, academic exercises.

Yeah beats me how anyone thinks LC is useful, other than for weeding out the most unqualified people, like people who genuinely have never coded. I suppose what it really does is finds you people who are willing to put in the time to study all the hundreds of questions.
I edited that sentence when I was helping these guys with their text and it's possible I introduced a misleading connotation. The way I understood what they originally wrote is that they had observed such a billing lapse inside some organization, but not that they were responsible for it.

On the other hand, even if so, there's the classic proverb about 'expensive training' etc...
It was not in the least terrifying and actually a big yawn; no known damage or injuries; "near San Jose" is inaccurate, it was 14km east of San Jose up the (fairly sparsely-populated) foothills near Alum Rock, 6.9 km depth, 37.311°N 121.677°W, inside Joseph D. Grant Park, zipcode 95140, total population only a tiny 191. So, remote, not urban and nothing like all those San Andreas movies. We felt the floor ripple for a couple of seconds and that was all. All transit is still running, just at reduced speeds (standard practice just in case there's a big aftershock, which there almost never is).

You want to worry about something that's actually broken, then worry about whether the US MNT will get it together to call up leading goalscorer Jordan Pefok by 13 Nov deadline for the World Cup. Now that's worth losing sleep over. Or worry about Cuba, Haiti, Puerto Rico reconstruction from Hurricane Ian; Cuba got it bad.

USGS.gov has a page up near-instantaneously with the details including crowdsourced reports of perceived intensity by location, as they always do: https://earthquake.usgs.gov/earthquakes/eventpage/nc73799091...

PPS: in that area, Mt Hamilton (4265') and Lick Mill Observatory are worth a visit. And over west in Menlo Park visitors can visit the USGS station for free, that's a very fun and educational thing to do.
The Role of Nursing Research in Achieving Health Equity
Welcome to SW testing. Testing for limits is a no go. Testing for random input is a no go.
Yes, illegal or discouraged in some other way (taxed more heavily, for example), whatever works best. As the article points out, you can also push towards this by mandating higher minimum wages for people in this industry (currently they're very low), but I'm not convinced that's good enough.
Certainly not the same thing, but the 2 literally jaw-dropping moments I've experienced looking at "ships" in museums are the Vasa and the Space Shuttle Discovery (at the Smithsonian National Air and Space Museum's Udvar-Hazy Center outside of Washington).
The thing is I’ve met founders who implicitly don’t want to hire the best anything. The best are driven, intelligent and experienced which to some founders comes off as a threat. So they hire yes people instead who won’t push back.
Build tooling stability is one of the great undersold benefits of the ClojureScript ecosystem IMO.

The build process is defined by the compiler (using Google Closure tooling under the hood) and has not significantly changed since the introduction of ClojureScript in 2011.

Since all CLJS projects use the same compiler, the build process works the same everywhere, regardless of which actual build program is being used (Leiningen, shadow-cljs, etc).
So does this apply to 2022 paces paid in 2023 or will effect the next tax cycle?
One possible cost measure is thr number of evaluations of the probability function.
> It's not, your understanding of async in Zig is sound.

Then perhaps there is something wrong with the language reference?

> I don't even dare to describe Zig as colorless, in fact I say colorblind.

Doesn't that mean my blog post is right?

But my biggest beef is that people, including GP, used your blog post to then claim Zig is colorless. I mean, GP did it in GP.
Interesting point.

I guess the main difference for me is the extent of human involvement.

For example, with Adobe there is a huge amount of human interaction required to get from idea to end result.

With DALL-E, you basically go from idea to end result instantly.
My home office in Campbell (just south of SJ) is on the second floor so I got more of a shake than my wife downstairs got, though her MyShake app gave her a few seconds warning.

For those not in earthquake country, this was a moderate quake, not big enough to cause damage other than maybe knocking something over right near the center. The epicenter was in Joseph Grant Park to the east of San Jose, near Mount Hamilton.
Seemed even a bit longer before that on the peninsula coastside. The whole thing felt magical, to even know that much beforehand.
It's not accurate that there's only one representation of every function at runtime. Completely unrelated to async, Zig uses compile-time parameters to do stuff similar to templates which will get you lots and lots of monomorphized functions, and you obviously can't at runtime have a pointer to a function that takes a compile-time argument (just like you can't have a pointer to vector<T>::push, to which you would pass the type T at runtime, then a this pointer which is a vector<T>, then a T t to append, haha). Then, for async specifically, usually the way that the same function can be compiled to be async or non-async is for it to be generic over some other stuff at compile time and for that other stuff to either be async or not be async. For example, you could have a function that writes a websocket frame to a writer, and that function is async if the writer is async, but it's not async otherwise. But it's also specialized to each writer in other ways, so if you use it on a lot of types of writers, you'll get more than just 2 copies (one async and one non-async) of it in your compiled program.

In most programs you end up with all async functions or all non-async functions in a specific context, so if someone handed you a pointer you'd have no problem knowing which calling convention to use. But if you actually end up not knowing, because you really do have a mix of different types of pointers, you could call all of the pointers via the @asyncCall builtin. I have done this successfully, but I'm not actually sure whether it worked by having a pointer to a non-async function at runtime or by specializing the function that I was using that did not need to be async (because its body and callees did not use await or suspend) to use the async calling convention. Or you could use a tagged union of multiple function types and make your own `call` method for that union. This is pretty weird though, because you'll end up requiring the end user to provide storage for the async frame even when the function isn't async and doesn't actually need that storage.
Why would anyone use it if you can’t take advantage of the vast Java ecosystem? Why would I choose it over Graal for example, which has much bigger backing, stable and is language-agnostic.
> We demand that leadership does not discriminate against workers on the basis of their race, gender, disability, sexual orientation, or political beliefs.

Aren't they themselves discriminating their own users based on their political beliefs? (both of the users and the employees choosing how "the algorithm" works).
Perhaps in-person was the wrong word. "Present" is perhaps closer to what I meant. We want our presenters to have an audience. We want audience participation / questions / feedback. We want to create a buzz. ;)

Not saying that YC's format doesn't achieve that. It's just different.

But either way - totally see your point on posting it online afterwards.
Oh Great, Britain's New Prime Minister Is a Crypto Bro