skysight-inc/HackerNews huggingface dataset:
>Plenty of actual professional programmers can't manage this, how is it a fair standard to hold scientists to

That's a good point. On a tangential note, prototype code tends to be at a higher level than production code, so there is a higher chance 10 year old code will continue to run on the scientist side, as long as the libraries imported haven't vanished.
https://docs.microsoft.com/en-us/windows-hardware/design/min...

Devices that run Windows 10 for desktop editions require a 1 GHz or faster processor or SoC that meets the following requirements:

* Compatible with the x86* or x64 instruction set.

* Supports PAE, NX and SSE2.

* Supports CMPXCHG16b, LAHF/SAHF, and PrefetchW for 64-bit OS installation
If they are running a business, especially something at scale, and they are properly funded - they should be 'paying the right amount', there's really no excuses.

If they can snare people into driving for them, there are material switching costs for workers, and 'underpaying' on some level is actually something they can get away with.

At the 'low end of labour' workers generally have zero power, much less during covid, so it's not a 'marketplace' in the more broad sense. If it was, we wouldn't even need minimum wage laws, or Medicare for employed people etc..

If the technical challenge is 'insurmountable' then they need to figure something out: minimum guarnatees etc. , even over the aggregate, as you say.
It is disproportionately against Uber especially on HN. I haven't seen an article here about child labour in hardware companies in forever, but I definitely don't see them daily like Uber seems to have.
There's a ton of overlap, because science code might be a long running, multi-engineer distributed system and production code might be a script that supports a temporary business process. But let's assume production ready is a multi customer application and science ready is computations to reproduce results in a paper.

Here's a quick pass, I'm sure I'm missing stuff, but I've needed to code review a lot of science and production output and below is how I tend to think of it, especially taking efficiency of engineer/scientist time into account.

Production Ready?

* code well factored for extensibility, feature change, and multi-engineer contribution

* robust against hostile user input

* unit and integration tested

Science Ready?

* code well factored for readability and reproducibility (e.g. random numbers seeded, time calcs not set against 'now')

* robust against expected user input

* input data available? testing optional but desired, esp unit tests of algorithmic functions

* input data not available? a schema-correct facsimile of input data available in a unit test context to verify algorithms correct

Both?

* security needs assessed and met (science code might be dealing with highly secure data, as might production code)

* performance and stability needs met (production code more often requires long term stability, science sometimes needs performance within expected Big O to save compute time if it's a big calculation)
> completely inaccessible to the mobility-disabled?

Completely inaccessible to a mobility-disabled person without help.

However, I live in one of those European cities that has kind of quirky small places, sometimes inaccessible to a mobility-disabled person. I also got a good friend who is heavily disabled. Two weeks ago we set up to meet up in one of those places, and when I arrived, a few minutes too late, he was already sitting inside. How? one of the people there helped him get in.

Almost all places are normally accessible mobility-disabled persons, if you only dare to violate the impersonal principle upon which many cities are designed.
I'm astounded that this is the first outage I heard about this year.
How does it compare to Unreal in terms of ease of use and getting the job done? (I'm thinking Unreal is better performance wise; not very interested in that.)
I've been using Godot lately, and while it has many flaws (an over-reliance on strings as identifiers, for example), I think the fundamental design is sound and easy to work with: everything is a node in a scene tree.

The engine code, while not up to modern C++ standards, can be pretty easily understood, modified, and then fully recompiled in just a few minutes. It's not suitable for a AAA 3D game, but it's the first engine I've found for 2D C++ development which actually helps me more than it gets in my way.
If you want the evidence that this happens frequently read the MPD civilian oversight report[0] on the subject.

In my opinion the main issue is the "excited delirium" diagnosis. One of the main symptoms of "excited delirium" is "Police Noncompliance"[1] which makes the police an essential part of its diagnosis.

[0] https://lims.minneapolismn.gov/Download/File/1853/Pre-Hospit...

[1] https://www.prisonlegalnews.org/media/publications/acep_repo...
I read another article a few years ago, I think also in The Atlantic, that approached this from the angle of every coffee shop, hip restaurant, and, importantly, Airbnb looking the same everywhere.

Isn't this just the result of globalization? As people travel more, won't tastes naturally converge? And while I'll miss cities having their own distinct flavor, I'm also not sure it's inherently bad that things look more similar. What is bad is that the style and culture we're landing on is driven by the class of people who bounce between world-class cities.
Unfortunately there are a lot of places online that will recommend 5000 units a day or more. And at the store, one of the standard doses for Vit D is 5000 units. I have this dose in my medicine cabinet. And it's not a completely unreasonable dose. Shannon actually did need 5000 units daily - just not for five years. The problem is that no one knew to reconsider it, or look for elevated calcium.
Cannonball Run record set due to coronavirus after streets left free of traffic
> The extremely high failure rate indicates it is either a flawed concept entirely, […]

Are you sure? Maybe the flaw is the notion that the marriage partnership should be expected to last for life. There are real reasons why some personal partnerships benefit from a legal framework that allows for division of labor and joint decision-making powers.
Most researchers would agree with the first statement without significant qualification. Methods are at the end for a reason.
There's a place in Atlanta that's very similar as well!

Brother Moto - https://brothermoto.com/
No, that’s way too easy an answer. It’s also othering the problem away; essentially saying “non-nazis would never behave this way”. But they would, have, and do.

Since this is a programmer-rich forum, let’s talk about bug fixing for a moment. When you are looking for a bug, it’s easy to convince yourself a number of things, like: “It’s a random glitch, just restart it and it won’t happen again.”, or “It’s this library which is buggy, it’ll be fixed when we upgrade it to the latest patch.”. Now, of course, we programmers are then punished mightily for our arrogance when the bug keeps happening. But what would happen to bug fixing if this never happened? If we could just declare that the bug was this or that, and move on?
React is very very little, is not really a framework, l and honestly I think most folks are really either talking about JSX when they talk about React or they are talking Create-React-App and it’s ecosystem (which really is much more like a framework).

JSX comes down to being a convenient way to write HTML in your JS instead of JS in your HTML. After that, it’s just vanilla js.
And the boundary between them is permeable. Last generation's well spoken insane person can become the next generation's strong independent thinker, and vice versa.
Weird suggestion that might help:

My second reading of Test Driven Development, I literally did the entire book along with the author, front to back.

That's when it clicked. The actual manual mechanical kinesthetic activity somehow made it work for me.
Quick answers just for fun:
1. Technological abundance vs regulated scarcity
2. Complexity outpacing human understanding. Plus regulation/approvals.
3. Because the FOMC controls it.
4. Reduce legal barriers to entry.
5. Reduce central control.
6. Risk minimization.
7. Trust by common identity.
8. Maybe. Pace tracking classes.
9. Money is cheap enough now for investors to fund most science for profit.
10. No programming. AI queries (e.g. “Her”)
11. Audiobooks
12. Arxiv / citation ranking
13. No. Too easy to ignore ads on text.
14. Nobody’s paying for IDEs anymore.
15. See #7.
16. See #15.
17. See #7.
18. Political vs scientific incentives.
19. contra to #7.
20. See #7.
21. It’s more lucrative to fail than to succeed.
22. I’ve heard it was due to mass burning by humans. Fire/regrowth fixes more carbon than it releases.
> In my view countries should start to save what can be saved, and try to anticipate how the climate crisis will unfold.

This is the approach that I've advocated since the very beginning.

Humans are extremely adaptable, while organizing groups of human is difficult and unpredictable. Work toward reducing emissions, of course... but you have to assume that won't work and be ready to deal with changes as they come.

> The military will also have to adapt and anticipate. I'm genuinely scared about the future. It's unreal and ironic to realize the future might look like an hollywood apocalypse movie.

I seriously doubt that the US in particular will look anything like that. It looks like we'll likely see coastal area impacted in our lifetimes, and we may see the agricultural areas move further north... but that's not nearly as big a problem for society as a whole as it might sound. If sea levels rise significantly enough, I'm sure we'll see places like NYC start massive engineering projects to either raise the ground level or build flood walls sufficient to hold back the seas. Central Canada is already a rich agricultural area; moving corn and soybean production north wouldn't even make a blip on the radar of most people.

Some people will lose everything, some people will make fortunes. Some people will die, some people will be saved. It's all happened before and will all happen again.
good stuff, there is another really good GO online book: Go 101,https://go101.org/
a lot of details, has been really helpful for me to advance in Go
Isn't the American legal system the one where that kind of argument actually has weight? Why so many cases are thrown out on technicalities and litigation costs are so high.
Game development historically and consciously does not use Git so you’re fighting a losing battle. There’s good reason for that. Git remains not a great fit for managing large projects of assets despite extensions and work put in, so I’d be cognizant of your projection of Web-centric preferences on another vertical. That’s a recurring theme from the Web vertical (why don’t you do things our way) and I can tell you I’ve seen frustration with that firsthand.

Perforce and systems like it are the competition here (pay attention to how many games announce changelists in their logs), and AAA studios are quite comfortable with what they have.

If your problem with Unity is how it does source control it speaks more to your unfamiliarity with industry practice than it does a deficiency in Unity. They added Git ability because enough people complained about it, but as this thread points out, it took gymnastics to implement because it’s simply not how that market operates — web folks operate on a pile of text files and games don’t look anything like that. I’m not just talking about graphics, either. The AAA I’m working on has about 75 KB of code and 46 GB of binaries and a few hundred actively committing, so Git is very comfortably a nonstarter.
I love seeing people invest time in this area, kudos. One thing that’s a bit hard for me to justify though are the examples like “click to edit”. There is a very noticeable delay as you wait for the network request with the edit document, whereas you typically won’t see that with client-side view logic. Is this just not a problem that htmx is trying to solve?
You're right about bit-for-bit reproducibility possibly being overkill, but I don't think that invalidates the parent's point that Monte Carlo randomization doesn't obviate reproducibility concerns. It just means that e.g. your results shouldn't be hypersensitive to the details of the randomization. That is, reviewers should be able to take your code, feed it different random data from a similar distribution to what you claimed to use (perhaps by choosing a different seed), and get substantively similar results.
And who decides which is which? You?
This sort of scrutiny only matters once someone else has a totally different code that gives incompatible results, before that point there's no sense in looking for bugs because all you're proving is that there are no obvious mistakes: you don't say anything about the interesting questions since you only bother with codes for things with non-obvious answers.
I was surprised to see that this page itself doesn’t have an RSS feed to follow updates.
Yes.... Yes..... Consume, work, run in your hamster wheel. Mediocrity is okay, it's what your overlords desire. Enough to be useful, not enough to affect change.
In computer science a lot of researcher already publish their code (at least in the domain of software engineering) but my biggest problem is not the absence of tests but the absence of any documentation how to run it. In the best case you can open it in an IDE and it will figure out how to run it but I rarely see any indications what the dependencies are. So if you figure out how to run the code you run it until you get the first import exception, get the dependency until you get the next import exception and so on. I spent way too much time on that instead of doing real research.
Better just to get some sun. Your body will self regulate how much is produced in your skin from the ultraviolet that reaches it. Just don’t stay out so long you get burnt.
A cursory review of cultural and “critical” output of the past few decades shows a consistent onslaught on the institution of marriage. While difficult to quantify, it seems reasonable to consider the significant (if not critical) impact of these factors on the erosion of the institution of marriage.
There’s this: https://lnk.to/elif

I’ve seen artists use it a lot to link to music platforms from YouTube or other social media channels.
John Carmack, who did some small amount of work on the code, had a short rebuttal of the "Lockdown Skeptics" attack on the Imperial College code that probably mirrors the feelings of some of us here:

https://mobile.twitter.com/id_aa_carmack/status/125819213475...
Click through businessinsider to the sourced salon article, where they directly interview the driver. His initial case was a 75% underpayment, when he was paid for 1 mile on a 4-mile trip.

The interview seems to indicate it's an aggregate underpayment across all trips. The tool is available for examination if you are truly skeptical.

edit: also, you seem to have made your account just to comment on this thread. what's up?
Well wanting and raising children is A reason to get married, but it's far from the only reason.
Yeah I understand why there are rules to protect workers, the environment, disabled customers, city aesthetics and more. But it does end up making it a huge barrier for anyone to do anything. I'd like to think I'd do a good job starting a small business but the rulebook is so huge it seems insurmountable.
I really enjoyed using Go in my Distributed Systems course in college, and I've enjoyed using it as a replacement for Python for little scripts I've written since the typed aspect of it makes it easier for me to go back and read what I've done. But, I have not enjoyed the Go micro service we use at work. We went with Go thinking the coroutine thread implementation would significantly improve performance over a Java microservice, but the service turned out to be GC limited. And the overall lack of support for most language features has made this codebase much larger than it needed to be.

I wish I could convince my team to try Rust for our next service
Categories are created to distinguish between their members. If two things are in the same category, then they are by definition not the "same stuff". Otherwise they would be one thing.
> Unity doesn't mark old features as deprecated

Are you sure? My IDE (Rider) shows gives me a tooltip for any methods that Unity has declared deprecated. There's also console warnings and big notices at the top of the docs.

Package Manager also clearly marks certain packages as experimental or deprecated.
Of those only ADAS and autonomous driving sound particularly worrisome to me. Sure, a frozen instrument cluster would be inconvenient, but I'm more worried about the microcontrollers that control my breaks.
Uber is making it harder and harder to get on board with the idea that it's not an employer. Leveling out people's pay over multiple trips or retroactively adjusting the reward per job sure sounds like an employer having very strong control over the work conditions and compensation. And this almost brings back echoes of Doordash (?) when it was caught taking drivers' tips so that their pay was reduced to the minimum hourly promised "wage".

It's like Uber are trying to shoot themselves in the foot with all the cost squeezing and profit seeking at the same time they're in a fundamental legal fight defining what they are.

You would think they would go in the opposite direction and pay people such good rates during this controversy, you could hold that up and say, "see? People are clearly much better under this system". But I guess not.

On a separate note, I will say that this is pretty expected in terms of how software errors go. Of course programmers at a company will be checking quite diligently that they're not overpaying through their algorithms. But underpaying? Only those who can't easily check your code are harmed by that one. It is a rare company that spends money and resources on verifying from their users' point of view that they're being delivered what was promised -- unless that company actively cares about the user.
Vast majority of my experience is Java, but I'm in a C# role right now. I have to agree with you, having only used Go tangentially -- the tooling is more approachable and bootstrapping a project is more straightforward. I can go ;) from zero to _something_ in a much shorter time
Rust's future is beaming bright at Kraken
You can totally do asynchronous negotiation, and PGP has plenty of examples of it going wrong.

Edit: here's a beautiful recent example of in-band negotiation going wrong in an encryption at rest scheme.
https://github.com/google/security-research/security/advisor...
I like this idea very much. "Find your niche," in other words?
what bootstrap version?
Ugh, this has got to be one of my biggest bugbears with SPAs. This pattern fails far more than you obviously think it does, and when it does fail, it's usually handled so poorly it's worse than the 'cure' you're peddling.

Give me a clean, server-side form submission any day over the "has it worked, hasn't it?" inconsistency of SPAs.
I don’t see how that’s caused by their choice of license. I read your link, there is nothing related to their license either. MIT is permissive, as far as I know it is commonly used by 3rd party libraries for games, even on consoles.
I'm currently learning unity, and even for very, very basic stuff it's impossible to know what's the "correct" or "intended" way of using the engine
I think we have to hold scientists to higher standards for code quality because it has a direct impact on the findings of their results. How many off by one or other subtle errors that are found later in testing have most software engineers written in their career? Is it fine to just say eh, scientific results can be off by one because the standards should be lower?
> Fixing native software development will eventually mean making the web native, so that your OS is just a browser.

Frankly, it is hard to imagine a more hellish future for personal computing than that.
Unless you live in a northern hemisphere and have darker skin.

Probably best to ask PCP after getting some blood work.
I'm starting to wonder if I should quit my job, buff up on SQL, and go into data consulting. Everyone on HackerNews talks a big game about FAANG and their copycats trying to leverage machine learning techniques to increase profit margins, but the bulk of legacy businesses seem to not even have the facility to make sure that client_ID is stored properly across their massive realms of siloed databases.
Did you read my post? I know what a seed is. Setting one is typically not enough to ensure bit-for-bit identical results in high-performance code. I gave two examples of this: CUDA GPUs (which do non-deterministic accumulation) and asynchronous threads (which won't always run operations in the same order).
Why Uber's business model is doomed
I had an 18-year-old Python script. But it didn't work! And I couldn't make it work! Fortunately I had an even older version of the code in Perl, which did work after some very minor changes.

This wasn't scientific code. It was some snarly private code for generating the index for a book and I didn't look at it between one edition and the next. I hope I don't have to fix it again in another 18 years.

Applying some version of the "doomsday argument", Perl 5 might be a good choice if you're writing something now that you want to work (without a great tower of VMs) in 10 or 20 years' time. C would only be a reasonable choice if you have a way of checking that your program does not cause any undefined behaviour. A C program that causes undefined behaviour can quite easily stop working with a newer version of the compiler.
Show HN: Mys – an attempt to create a statically typed Python-like language
"... what of the COVID-19 pandemic? Why hadn’t we stockpiled key supplies and machines, built up hospital capacity, or ensured the robustness of our supply chains? The reason, of course, is that it would have been seen as inefficient and profit-robbing. Money spent on masks and gowns gathering dust in a warehouse could always be put to more ‘productive’ use in the marketplace."

This is what matters right now.
To clarify, nobody sees the code because they aren't allowed, or nobody ever ask to see it?
yes, although IIRC what I did was more like this:

const r_idx = {ax: 0, bx: 1...}
const registers = new Uint8Array([...])
add = (r1, r2) => registers[r_idx[r1]] = registers[r_idx[r1]] + registers[r_idx[r2]]

which lets you do:

add("ax", "bx")

which is one step closer to making it look a lot like asm syntax.
I worked in a Law Enforcment office that used Facial Recognition. Every single time we would give officers a potential match, it came with a disclaimer that it was a POTENTIAL match. It was up to the detectives and officers to actually do their job and find other pillars of information.

This isn't a failure of facial recognition, its a failure of
the stupidest people I went to high school with thinking its some sort of perfect system.