skysight-inc/HackerNews huggingface dataset:
I know, it’s one of the saddest aspects of existence in my opinion. I wish every child was planned for, had a job and housing lined up for them before birth. Instead we live in a random survival free-for-all. Sex is seen practically as a recreational activity, children as either unintentional accumulated byproducts or vague milestones of personal or economic achievement.
huh? cafes stay open late in LA. even most starbucks are open to 10 or 11pm. a number independent cafes stay open to 11pm or midnight, with some doing things like poetry/art/music/other events in the evenings. there are a bunch of independent theaters, resstaurants, and (outdoor) shopping areas that stay open late. even museums (e.g., the getty) have nightlife events going on.
In the context of a lawyer of a threatening to sue to stifle a legitimate news story that their client wants suppressed, yes, that really seems like a problem.
Given the subject matter I had to smile at the way the author bungled the detail within the first sentence:

> "A while ago, I read this amazing piece about building a ladder."
I like your analogy and do have a similar view in that the total consciousness level of all humans combined, at any given point in time, creates a separate universe of our own. This total consciousness level has its own rules and principles created by us which also evolves over time. It shapes all of our belief systems, actions, behaviors, etc. throughout various human civilizations in history.

It operates almost like a mind of the entire human race just hovering above all of us. This concept is pretty abstract but like you said, at any given point in time this total soul may not exist physically, but it does exist conceptually in our exclusive reality and it too constantly evolves together with us.
Submitting this every day for a week seems excessive.

https://news.ycombinator.com/from?site=console.substack.com
Over time, I've found Wikipedia to be quite biased in a subtle way. Articles about cities or countries tend to be written like advertorials, replete with rankings rather than facts. Articles about religious figures, philosophers or just controversial people in general tend to be more obviously biased, with certain facts highlighted and others buried or hidden.

This is pretty much just the nature of any publication - there is no such thing as an "unbiased" source of information. Having said that, I prefer the older, more academic ones like Britannica. They tend to be less caught up in the zeitgeist and more descriptive, if a little boring.

Compare these two articles to see what I'm referring to:

https://www.britannica.com/place/Vienna

https://en.wikipedia.org/wiki/Vienna
Ready at Dawn's (Lone Echo, The Order 1886) CTO said that going forwards everything new would be in Rust in 2018[1] (however, looking at their careers page all the dev jobs are asking for C++ and don't say anything about Rust). EA's SEED research division was also experimenting with Rust.

As someone who's poked around in the current Rust gamedev ecosystem a bit, the publicly available libraries and frameworks aren't quite there yet for mid-large games (and are probably 1-2 years away at least for serious 3D development), though recent developments like the Legion ECS[2] (Amethyst, imo the most promising Rust 3D game engine seems like it will be switching from specs to Legion[3]), and Ultraviolet[4] (linear algebra library specifically for games & graphics which is faster than the alternatives for both runtime and compile times) are very promising.

1. https://twitter.com/AndreaPessino/status/1021532074153394176

2. https://crates.io/crates/legion

3. https://github.com/amethyst/rfcs/issues/22 for a discussion about potentially moving from specs to Legion

4. https://crates.io/crates/ultraviolet
You’re quite right, but one thing to note here is that Haskell Stack refers to a specific build tool for Haskell. Not its “stack”. But your point still stands.
Yes. That list is pretty good. LXC or Docker Integrated with jail and bhyve would be awesome. Even just finishing BBR would be awesome.

ZFS is totally awesome. Iscsi can't yet do dual path and dual controller magic well I believe which is a bit of a shame.
It is interesting to see the parallels with my work with solid modeling in CAD. I'm constantly harping on the people I work with to think about what they are working on and structure it in a way that can be edited later (as well as stability). This often means a larger/less efficient feature tree, but it is actually maintainable. Just this week my insistence that we build the model to be flexible meant that we were able to fix something in 5 minutes instead of days.

Updating colleagues work without talking to them is something I often struggle with though. On one hand I absolutely hate it when others change my work without at least getting the history as to why I did it that way. Thus I try my very best to give others the courtesy of discussing it with them first. On the other hand, if something isn't being paid the proper attention, or they aren't making progress, sometimes it is a useful way to light a fire under certain people if asking politely hasn't worked.
Yeah, until your count goes above two.
reminds me of the dude who managed to parse TB with awk instead of whatever spark like product was trendy
Kyoto Is Rebuilding Itself as a Nanotech and Regenerative Medicine Powerhouse
After W3C approved DRM standard, much harder to make a functional indie browser
> I also find it incredibly disingenuous that everyone asking for The Statistics

If you're making claims then you need to present evidence.

> mutilation performed on intersex people,

Intersex people are not trans-people, intersex is a genetic defect. Don't conflate and insult intersex people.

> Geesh, I'm actually kind of mad about it... as someone that has given birth to a child and about due with another one, I would love for HN commenters to talk about pelvic pain, vulvodynia, 4th degree tears, incontinence, prolapse, and other incredibly common postpartum issues that might require surgical intervention to the same degree that gender affirming surgeries are being questioned.

I'm guessing from the fact you've given birth then you're a biological woman. The unfortunate side effects on your body has nothing to do with the discussion in hand, and is verging on a non-sequitur.
I'd love to see a suitably scaled 3d view to reinforce these elements of the constellation don't lie in a plane.
I had an account suspended that was linked to a YouTube account videoing marijuana cannabis dispensaries. April 2018 the site shut down non-Vice media cannabis content and suspended the Gmail account. It made it apparent how central my most sensitive email archive was housed on such a flimsy foundation.
man, growing up with Maya and Houdini, making a node editor and dataflow engine was probably my ultimate dream
Censorship never leads to good things
S3 is never the cheapest/most cost-effective way to backup anything.
> As an apropos to the article, and touched upon therein, checking in a fairly major change to de-duplicate some code without consulting the original author/team is a wee bit rude.

This sounds like the outcome of bad culture. Ownership of the code should be shared to the point where it should never be considered rude to improve the code. Any part of the code.

> Ask your colleagues first why such code still exists before barging in and making these changes,

If I had to synchronise with others all of my improvements to existing code (which was frequently written in a hurry to meet a deadline, so with shortcuts taken intentionally, or with incomplete knowledge of future use cases) I would get at most half as much done.

> they may already have some concerns as to why refactoring to a helper method or some abstraction isn't in their game plan yet.

If there are alluring "improvements" that don't work for such subtle reasons, this should be documented in the code. If it's not, one has only oneself to blame when someone goes in and changes it.

Edit: I realise now that I'm talking about teams where everyone is reasonably senior. It could be different with junior members on the team, to which many changes might look like improvements when a senior engineer would at most see the change as equivalent. In that case I think you're right, but for a different reason: junior engineers should always check in with senior engineers about things in order to learn more of the craft!
As that link states, HIPAA extends to "business associates". Google isn't a "covered entity" as that has a specific definition, but it is a business associate in relation to a covered entity (e.g. health care providers). The reason for the two different terms is because covered entities deal with patients directly, thus have certain rules that only apply to them in relation to interacting with said patients. Since Google is a business associate that does not directly interact with patients, only the rules specifically in relation to PHI and other business activities apply as others (e.g. patient interaction) are moot.

Protected Health Information is protected under HIPAA for both covered entities and business associates alike. Otherwise, HIPAA would be pointless if covered entities could just pass the PHI to business associates or shell companies unfettered.

Note: I would not consider myself a "HIPAA expert", but I'm a clinical researcher that has to ensure HIPAA compliance for my lab.
In genereal I find the wording "debt to society" very misleading. Does one have the right to commit a crime in exchange for punishment? I would say no. Punishment should serve as deterrant and as rehabilitation where possible, otherwise to keep society safe.
Would you be interested in an app that helps students look for university?
The following is not a particularly deep thought, and that is why it is stated simply:

The way to maintain the easy abstractions, or even increase the level of abstraction while still increasing performance is to ditch the proliferation of massive general purpose programming languages and adopt specific DSLs that fit the problem domain. I feel like the language-oriented programming paradigm that Felliesen of Racket champions is certainly in this spirit, but I would like to see a language core that is specifically tailored to performance concerns.

Not that this is important to the general concept, but this is the current focus of my language design efforts, hoping for first public showing in April 2020,
On cherry-pick dependencies: there is no way that any VCS can solve that problem for you, because dependencies can be (and often are, for the projects I've worked on) non-local.

That is, you can have a dependency even though the changes appear to be unrelated from a textual point of view.

I'm all for developing better tooling for digging into blame-history, which is more generally useful and would cover the textual dependencies between changes, but you shouldn't believe that that solves the dependency problem.
> a clean, well-lighted place

This brings back fond and sad memories...

https://www.sfgate.com/bayarea/article/SAN-FRANCISCO-Clean-W...
This reminds me of a story arc on "Hill St. Blues" where LaRue comes across a great stand-up comic and invests in his management... only to find that his full name is "Vic Hitler"... and further finds that Vic had made his father a deathbed promise that he wouldn't deny his surname or family "on account of that one unrelated lunatic".
> Reality is telcos have user enrollment almost on par with bank KYC, where everything else has great authN but with user asserted identity.

Are you sure? I don't mean that to sound hostile, genuinely asking. Because, at least in the States and Canada, I can get all of the +1 numbers I want on real SIMs for around a dollar apiece--or less if I work at it instead of just trotting down to Walgreens--and attach any name I want during the sign-up flow. In point of fact, I have a vanity 212 number I've owned for years. It is currently parked on a SIM registered to the name George Crabtree (that name even shows up on CID/CNAM).

Best part? The MVNO that provisioned the SIM is using a white-label service from one of the big four. Even the ICCID prefix is from the actual carrier and not the MVNO. That means that all of the automated API checks show it as a "normal" phone number provisioned on a "regular" SIM...and owned by Constable Crabtree.
I never had this religion imposed on me in my career, except recently. Originally I designed hardware. There, if you change something it might cost $1m in retooling a factory or throwing away a defective wafer batch. Then, I worked for years in teams producing production code, where job #1 was to not break something. Pretty soon you learned that even an innocuous tidying up change can end up breaking functionality seriously. You also learn that if code is not pretty that probably means paying users are relying on it.

I think the culture of turd polishing code so it looks pretty comes from academia and people who are control freaks. That, plus only deployment where if you screw something up you can just push a fix in seconds. Except if your bad but pretty code leaked sensitive data or lost data..
Doesn’t seem likely. According to your link, only a minority of Asians have this reaction.

Even if it was a larger percentage, with how dense Asian cities are, there would still be millions of people unaffected.
The tone of the comment was unnecessarily dismissive, and it is kinda expected that hw implementation beats sw implementations. If anything, it's pretty impressive how close blake3 gets without dedicated instructions.
Your boss made a good point. My boss also made the exact same good point. But between those two same good points, there isn't a great line. ;)
Ask HN: How do you guys stay motivated if you don’t feel like working?
Interactive explanation of a procedural music system
You could try janet
So long as an application needs to share state between worker processes, (database, redis cluster, etc) then Amdahl’s law still applies. There’s very few modern applications that can truly scale linearly.
I see this in Northern Chinese cities as well, which has snow for part of the year. I think it’s just how dense the cities are and how safe everything feels.

You can wander the steets alone at 3am and still feel completely safe. It’s an extremely strange feeling when you’ve lived in more dangerous cities.
Funnily enough, 'The Outer Worlds', an offline single-player RPG game, censors player names.

https://wireframe.raspberrypi.org/articles/banned-character-...
Show HN: Exploit farm for attack-defense CTF competitions
Since you claim that the reasons are know, it seems to miss that a major reason for successful suicide is untreated depression which are well know area in medicine known to discriminate against men.

You can blame masculinity, or you can blame society for how it react to men who seek help.
Or, if possible, split up the helper into smaller units of functionality that can be combined as appropriate for different requirements. That could possibly work for the original article's problem, too.
I think the author got the wrong message from this situation. Yes, the refactor is bad, but I think they misidentified WHY it is bad.

> Firstly, I didn’t talk to the person who wrote it. I rewrote the code and checked it in without their input. Even if it was an improvement (which I don’t believe anymore), this is a terrible way to go about it. A healthy engineering team is constantly building trust. Rewriting your teammate’s code without a discussion is a huge blow to your ability to effectively collaborate on a codebase together.

Yes, but that's a social problem not a code problem. It doesn't mean your code was wrong, it means the process by which you integrated that code was wrong.

> Secondly, nothing is free. My code traded the ability to change requirements for reduced duplication, and it was not a good trade. For example, we later needed many special cases and behaviors for different handles on different shapes. My abstraction would have to become several times more convoluted to afford that, whereas with the original “messy” version such changes stayed easy as cake.

It's telling that there isn't a code example for these "special cases". My guess is that allowing them as configuration points in the de-duplicated calls would not have been that complicated.

I have heard this "problem" brought up before, and in my experience, it's not nearly the problem people claim it is. Yes, there is a balance to be struck: you don't want to remove duplication before you understand what's really duplicated, hence the rule of three (and I'm even fine going well beyond three). But I've yet to work on a codebase that wasn't well on the "too much duplication" side of that.

The REAL problem I see with the refactor is that the new data structures don't correspond to business objects, the way the user thinks about them.
Everything in moderation, even moderation itself.
I felt a bit awkward about bringing my kindle into a bookstore, but ultimately nobody cared. I've gone a couple of times (SF location), the drink selection is limited but not bad and it is a cozy spot to read for a while.
obviously the whole "textually including header files" model introduces a lot of overhead in compilation, but as I understand it, optimizations are inherently expensive. if you want to do stuff like inlining across module boundaries, full rebuilds are inevitable when you touch commonly used code. I think it's reasonable to expect that compiling optimized builds of complex code will always hunger for more compute power.
Where does it say they have to make minimum wage? If someone was stupid enough to hire the guy again as an accountant, he could make whatever he made before. Hell, like most of the geniuses in this story, he could embezzle from the next guy to pay the last one!

Edit: I do think the system they have going on is absolutely ridiculous, especially considering the infrastructure costs when it's only being used for "more than 200 people" (which I'm assuming means less than 300). But some of the responses here from bleeding hearts are insane.
Asking for a friend, right?
Soaring SUV sales keep carmakers on collision course with climate policy
Java Concurrency Videos
This article doesn't seem to care all that much about accuracy. They just care about being dramatic.

For example: "glyphosate ... has been shown to be lethal to bees as well as cause cancer in humans"

Neither clause is true.

I don't feel like doing a line by line of the rest, but this is a garbage article.
Hm, it does make sense. Perhaps I should make another, gameplay trailer as well. Steam allows multiple trailers anyway. Thanks.
That seems harsh. The article runs ~ 1300 words, which is right for a short feature and how conclusive can an investigation into a "mystery" be? There's no claim they solved it
Alienware Reveals Nintendo Switch-Like Portable PC Prototype
> I would guess about 2,500 copies based on your Steam review count.

I have 4 games on Steam, and "review to sale number" ratio is all over the place, so it isn't that easy to use for estimation. You can get some idea, but 2500 is nowhere close really.

> Did you sell a lot more on Switch or something? I really would be surprised if an ASCII game could sell 20k on Switch.

About 2/3 of the sales were on Switch. I was surprised as well. I meant the game to be Steam-only, and then some of the players asked for a Switch version. I was blown away after the first month of release.

IMHO, turn based (or just slow paced) puzzle games are awesome for Switch because of the portability. In the evening when the kids have finished playing their Zeldas and Dragon Quests, you can lay back and solve a couple of puzzles until it's time to sleep. Looking at my personal play times, the game I play on Switch the most is "Baba is You".
> (They were right.)

I remember at first no one took js seriously. It was only after people started to realize that web pages were an incredibly compelling app-platform that that befan to change.

So I think if Brendan had gone with Scheme, Scheme would be taking over the world like js is now.

Basically, platforms make languages popular, not the other way around.
DCSS is ridiculously fun. I've spent more hours playing it than any other roguelike.
But is it a problem with the old laws (e.g. ITAR)?
Read the note carefully: "While improvements in calibration are an empirically recognized benefit of a Bayesian approach, the enormous potential for gains in accuracy through Bayesian marginalization with neural networks is a largely overlooked advantage." Because the different parameter settings correspond to different high performing models, averaging their predictions will lead to more accurate predictions.
> I don't want to ask of permission for an improvement. If there is a need to have formal authorization of maintainers responsible for parts of the code, they setup just that. Otherwise, I'm certainly going to improve "your" code, in some rare cases without even telling you (that's not a goal in itself to do it behind your back, obviously, and I also value collaboration -- but that should not be a problem). The question that remains is: is it really an improvement. If you are not sure, then maybe don't commit. If you are, do it (following your local rules), and if it ends up being a mistake, yes, it will be reverted, and so what?

The issue remains that "improvements" and "good code" are too a large extent subjective. And the issue with doing a major refactor of code someone else wrote just days before on your own without consulting the original author or the team late at night as is described in the article (and doing it repeatedly) is showing poor social skills at best and being actively dangerous at worst.

Here are some reasons that you should consult the team and or the original author before doing a large scale refactor of recent code:

* Start off with the principle of charity and assume that the person who wrote that code and the people who reviewed it aren't complete idiots and you aren't some kind of savant who is able to see something they didn't while working on it for a much longer period of time.

* Since that person has been working on it for days they might have a perfectly valid reason for writing the code the way they did. One example is that they are working with the stakeholder and this is the first of a series of changes to deliver specific functionality and the code is the way it is because it facilitates those upcoming changes that might only be days away.

* If you have a habit of doing this and your changes getting reverted "ask forgiveness than permission" as you said, the team will begin to lose trust in you and it is bad for team morale. Consulting people before you make a huge change to their recent code makes them feel part of the process as opposed to something that is being done around them with them as spectators. On any team where that happens with any degree of frequency is not going to be a happy team in the long run. And managers will prioritize a happy team with high morale as opposed to a "rockstar refactorer" on the team who is impacting morale regardless of whether their refactorings are error free or not.

* It is fundamentally against the spirit of collaboration. When someone releases some new code there is a degree of inherent collaboration in there, it might involve multiple developers, stakeholders, implied functionality that was not part of the original story and at the very least the code reviewer. You unilaterally making a change without even taking 10 mins of your time to discuss it with them is impolite at best and wasting company resources at worst if your "improvement" ends up being reverted and all that work and time could have been saved had you bothered to have a 10 min convo before starting.
Seems the problem is pesticide use, not necessarily almond cultivation. Perhaps I am splitting hairs, but there are few good protein sources available today and tree nuts are plentiful in my region. It is hard to imagine that those cow farms in the central valley and elsewhere are any more moral or sustainable.