skysight-inc/HackerNews huggingface dataset:
I feel that the structural components of these large gaming publishers are actively working against them creating an environment to discover any new thing, let alone a new game genre. For instance I just do not believe that these large companies have the logistical bandwidth/incentive to not chase a 100MM hit, and these larger publishers have clearly learned from the post-MMO, post-Kickstarter, F2P/DLC landscape. It was quite a few years ago when I heard the anecdote that all new proposals should have a DLC/loot box hook for projects, and it just makes so much sense. Valve and others trailblazed the concept that you could convince people to part with their money for a chance of getting something of perceived value. Everything they have been doing is to create ecosystems of engagement to create those long relationship/impulse opportunities. To me, this is optimizing for the fact that most consumers in the market seem to have less free money for the traditional model that they are used to, but are willing to leak out a few dollars here and there en masse. From the platform side the console churn/complexity that was there in the 90's is lessened, slowed, and standardized.

The organizations themselves feel like they can't handle 100 1MM projects compared to a single 100MM project just from leadership and management but that's not something I blame wholly on these companies, it's a structural thing in most public companies right now. From a simple analysis it is so much less risky for them to just acquire a new development firm with a sure thing/hit that can be shoved down their sales funnel. You gain the best parts of the corpse too: the employees, the IP, the proven product, and the future and recurring sales. Sure they'll lose the employees, but the rest of it will carry weight until the IP is forgotten. Even right now the IP for both EA/Activision is probably still worth a ton if they had to part it out.

In a more theory kind of sense I just feel like this is one of the problems with how public companies work right now. Once you are of a certain size and exist primarily in the B2C space, the mindset becomes optimize, reduce costs, and make GAAP profits. While I feel like historically this may have been a healthy transition from companies at (today's dollars) 50MM-150MM AR to take them to 500MM+ AR it doesn't translate as well when a 100MM revenue increase is the only way to even move the needle when the majority of the company's revenue steals the attention.
> That is why we have a system of courts and warrants and checks and balances etc.

The problem is that those are worth nothing if judges and courts do not understand (or don't want to) the full consequences of carelessly signing those warrants.

In Germany we have some local courts which are "famous" for being very near to the police and will often rule against your personal freedom or accept half-cooked "evidence" from copyright holders (rather their shady lawyers) for purposes of spamigation and alike.

You can't trust in the court system to rule in favor of freedom here.
Anyone know how to access the paper? My university has subscription for PNAS, but I can't open the pnas.org links found on Google.
Maybe I should make myself a bit clearer here:

I am not against an index or library in addition to the file hierarchy, but I am against a library or index replacing a directory listing.

Both perspectives are very valuable!

Also a full text search (grep) or (more or less simple) file search (find) are useful in addition to a library.

To reiterate, for me it seems that itunes and ebook reader generation of devices and applications don't seem to value custom directory organization.

> Those applications exist. Calibre even comes with one out of the box. Not their fault if you just start the library and not the reader.

While the library part of calibre is very good, the reader part is not so great, but that just might be because a library application is much more difficult to implement than the reader, so bad UI can be looked over there, but not in the reader. Otherwise I agree that this the application of choice for reading ebooks on Linux desktop.
As an objective third party, I think your chronic disease, your vast research of it all, and your corresponding frustration has warped your ability to have conversations with people who are less knowledgeable than you are. Where there is no ill intent, insults should not be taken. The insults are your own interpretation, there is no reason to take insult where none exists, especially when someone is trying to be helpful. Best to just shrug and say, "yeah, thanks, but researched this."

When my users are trying to tell me what is causing a bug and they're drastically wrong, I don't feel insulted that they think I don't know my own system. I just smile and have a nice conversation with them. There is no point in picking fights, and the person trying to help is not the one picking the fight.

I'm sorry for your chronic disease, and I can't imagine what it's like. I can't speak to that. But I believe you're taking it too negatively too personally when there's no need to do so. I imagine that isn't too great for personal happiness either.
"Perpetual Guardian, a New Zealand financial services company, switched its 240 staff from a five-day week to a four-day week last November and maintained their pay."
"I'm now a full time roboticist and a part time cook, people mover, negotiator, lab manager, construction foreman, fitness coach, gym spotter, goalie, wanderer, professional wrestler, cleaner, etc."

This reminds me of that write-up that tried to put a price on a stay-at-home parent by listing all the activities they do, looking at the price of a specialist, and adding it up. I'm bookmarking yours for future conversations like that since it's shorter, has more activities, and is more fun to read. :)
That schedule is called a 4-10 - 4, 10 hour work days, and every Friday off.

9/80 is that you work 9 hours a day, and every other Friday is off.

They're both popular in defense and aerospace.
Which is invasive and also about as relevant to actual work as "butts-in-seat" metric is for meatspace offices.
MicroUI: Tiny, Portable, Immediate-Mode UI Library Written in ANSI C
I think it would be reasonable to include a note in the HN guidelines about not complaining about "magazine-style" writing like this. I see it over and over here, and it's really boring and trite at this point. Many people don't like more expressive forms of writing, especially the HN crowd, but it's a legitimate style which many people enjoy. Why can't people just ignore (or even flag) and move on?

Actually, maybe the guidelines do eschew this complaint:

Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.
> If you add your CA to the trust store then you can sign your localhost certs.

Not necessarily. Google have decided that Android users can't be trusted to install their own certificates. I don't know if Apple will permit it, either.
If you want to work at Big4/5/whatever, you need to do a lot of leetcode or be naturally talented at solving algorithmic problems. It's not as hard as you think, though. Google, for example, really does not ask many leetcode "hard" questions IME. It depends on where you are looking to interview. In general, the most you really need to know is graph traversal algorithms like BFS and DFS and know data structures well. Basic implementations can be bruteforced, and to further optimize you can do things like sliding window algorithms or two pointer algorithms. Dynamic programming usually will not come up. Memoization is something you should know how to do though, and usually is a pretty natural optimization.

Of course, if you don't want to work at companies that do leetcode style interviews, there is no point in going much further than knowing data structures well and knowing basic algorithms (probably learn a sort better than bubble sort though... merge sort is pretty easy). You should know about trees, but I really doubt if you are applying for a company with sane hiring practices they will ever ask you to implement auto balancing trees.

In my experience interviewing with non-leetcode style interviews, I did get a lot more language trivia. For example, for a position primarily using Java, they ask about polymorphism, final vs finally, stuff like that. On onsites the focus is a lot more on STAR, past experience, and designing things. I personally actually like the former style of interview :)
Some thoughts on my experiments with SIMD Programming:

1. AVX2 is good, but tedious to use manually. The difficulty problem with AVX2 is that it is SIMD of SIMD: Its 2-way SIMD of 128-bit. Going "across" the lanes of the 128-bit bunches can only be done with rare instructions... or through L1 cache (write to memory, then read back in another register).

2. "#pragma OpenMP SIMD" seems to be the most portable way to attempt to "force" autovectorization. Its compatible across GCC, CLang, and ICC, and other compilers. Visual Studio unfortunately does NOT support this feature, but VSC++ has well documented auto-vectorization features.

3. If you are sticking to Visual C++, its auto-vectorization capabilities are pretty good. Enable compiler warnings so that you know which loops fail to auto-vectorize. Be sure to read those warnings carefully. https://docs.microsoft.com/en-us/cpp/parallel/auto-paralleli...

4. If you keep reaching for the SIMD button, the GPU Programming model seems superior. If you must use a CPU, try the ISPC: Intel's SPMD Program Compiler (https://ispc.github.io/) so that your "programming model" is at least correct.

5. If a huge portion of your code is SIMD-style, a dedicated GPU is better. GPUs have more flops and memory bandwidth. GPUs have faster local memory (aka "shared memory" on NVidia, or "LDS" on AMD) and faster thread-group communications than a CPU. Know how amazing vpshufb is? Well, GPUs will knock your socks off with ballot(), CUDA __shfl(), AMD Cross-lane operations and more (https://gpuopen.com/amd-gcn-assembly-cross-lane-operations/).

6. To elaborate on point #5: GPUs simply have better gather/scatter capabilities. The GPU's "shared" or "LDS" memory (just 64kB or so) is very small, but provides arbitrary gather/scatter capabilities across "lanes" of GPU SIMD units. They even support relatively efficient atomic operations. Yes, even vpshufb seems relatively limited compared to what is available on GPUs.

7. Raw AVX2 assembly seems "easy" if what you need is a 128-bit or 256-bit register. For example, if you are writing Complex-Doubles (real+imaginary number), then it is very straightforward to write 128-bit SIMD code to handle your arithmetic. But if you are writing "true SIMD" code, such as the style in the 1986 Seminal Paper "Data Parallel Algorithms" (https://dl.acm.org/citation.cfm?id=7903), then stick with ISPC or GPU-style coding instead.

8. Be sure to read that paper: "Data Parallel Algorithms" to get insight into true SIMD Programming. GPU programmers already know what is in there, but its still cool to read one of the first papers on the subject (in 1986 nonetheless!)
6th of April 2019 – The Day Some GPS Modules Might Stop Working? [video]
Geophysicist Wallace Smith Broecker (November 29, 1931 – February 18, 2019)
> Managing AWS resources is not "free" either, or the market for people to handle devops work on AWS related to ongoing operations would be non-existent.

The costs of finding an AWS admin is much lower. This is, generally speaking, why many orgs still use SAP for ERP since there are a plethora of blue-chip consultancies that support those systems.
It's also pretty self-defeating at all other layers of privacy.

There are, obviously, a lot of ways to get away with a crime: you can try to ensure people don't know anything happened; that they don't know what happened was a crime; that they don't know you did it; or that they can't prove you did it. If you want to commit a crime for which you will be suspected but escape conviction, plausible deniability (which this isn't) can be a reasonable approach. If you want to live your life without undue surveillance and intrusion, generating 'chaff' like this is ludicrously counterproductive. It amounts to making your search patterns more unusual and adding search terms which might be suspicious in all sorts of ways you didn't foresee.

If I search "hot car how long milk safe to drink", it's pretty obvious what I'm thinking. If the extension adds "hot car safety" and "hot car how long", those are more ambiguous. And if it grabs popular suggested searches and picks "hot car kid safety", now it's adding potential surveillance triggers to an innocuous search. Less hypothetically, we already know that the NSA runs full-take collection against people who make certain searches relating to Tails Linux. If you make a non-tracked search on the topic, this could easily permute it into one of the tracked searches.

Even philosophically, I'm pretty baffled by the idea that I should improve my privacy by adding an extension which does unpredictable things in my name online...
Math checks out. You want quality food? You want the grower and its employees to earn a living wage? You have to pay for that.
I type with two fingers. Would that be dynamic typing? :)
A lot of offices and insurance companies have a nurse's hotline available in the off hours too to handle these sorts of requests. Though I'm not really sure what kind of advice they can offer other than "go to the ER."
Governance by reason and logic of whatever kind doesn't work: whether theocracy, socialism or something else. Corruption can't be stopped by logic. Venezuela was and is governance by reason (in theory) "chavismo" - but it isn't simply socialism; rather a very weird mix of retained rentiers and socialism, the very worst of both worlds.
The third party seller stuff has really killed my faith in Amazon. If I wanted to have to read reviews for the entity selling the good and have some expectation of getting a counterfeit/broken good, I would go to eBay. I used to go to Amazon because I could trust them, but that trust is lonnng gone. These days I'm shopping more and more locally, because I can actually see the thing I'm buying.

Side note: I'm sad to see NewEgg headed in this same eBay-clone direction.
MLIR: A Compiler Infrastructure for the End of Moore’s Law
You need to not work more. The bug numbers out of Luquillo are terrifying: 98% gone in the forest floor, 80% gone in the canopy. These are supported by numbers elsewhere.

Productivity is a self-destructive idea. Forget climate change; if the bug numbers are correct, we're going to lose the pollinators within a few years, and all your money won't another minute buy.

We all need to do the absolute minimum necessary to survive and stop reproducing until our numbers and lifestyle return to a sustainable level. This is now a dire and desperate matter of survival of our species.
This is probably the most sensible comment that sums up most of what the article stands for. Too bad it’s sliding down the comment list, I’m sure it could do a lot of good to anyone who just got hit with the bad news and thinks they are alone or that nobody understands what they go through.
Good read, thanks for sharing. For chrome users I'd advise using these extensions: I use Surfshark chrome extension for a VPN, PrivacyBadger, cookieautodelete, HTTPS everywhere, User Agent switcher if you're being sort of paranoid. I have CCleaner installed too, but usually there's nothing to clean since extensions handle most of it.
You should really know what you're doing all day. If you can't even summarize what you were doing all day, that sounds like a bad thing. The evidence is your story about what you actually did.

Here's a perfectly great update that didn't result in a quick win:

"I spent all day debugging that null pointer issue like we discussed. I thought maybe it was because the API was sending nulls across, but I looked at the logs and couldn't find any instance of that happening. I thought maybe it was a type coercion issue too, but I wrote a few tests to rule that out and it turned out not to be the case. Then I remembered reading about a memory corruption issue that sometimes happens in our runtime version, so I spent the rest of the day reading about the situations where that occurs and figuring out if it applies to us, but didn't get enough time to finish that up completely."
"Static typing tends to be used in areas where legal regulations create needs that outweigh programmer productivity."

This is rather a broad generalization that doesn't seem accurate to me. It's at least misleadingly phrased if it's not intended to imply that this is the main reason or primary domain where static typing is used. Performance is a major reason static typing is preferred in many domains like games development for example where legal regulations are largely irrelevant.
Option types do not defy the purpose of typing. Optionality as a type constraint is a reason for static typing.
Most companies only let you bank so many pto (Paid Time Off) hours and carry them over year to year. I think this came about because of accounting change where employee hours are considered a liability (Hours/Money owed for nothing in return), but I might be wrong on that.

As a result employees can't just bank their vacation hours and get a big payday when they leave. It tends to only take a couple years to get up to the max, and you end up with "use it or loose it" pto.
I agree with you that static typing can create more work on the boundries of a system.

However, the problems you describe also happen in dynamic languages and they have just as much potential to cause problems. The biggest issue with dynamic languages is that you don't get immediate errors when something changes. The system will just keep doing its thing, until it doesn't and you discover that something has changed and has already been propagated to other parts of the system.

I don't think dynamic languages are always better in these cases. They basically let you defer the error/change handling, but with the potential of much bigger data integrity/quality problems when things eventualy do go wrong because of changes in an integration.
The whole article is full of those. The best part is that the author tried calling out other fallacies in the article.
> What could the state of the art in demosaic, noise, latitude, color accuracy be with that kind of speed and tools?

Do you shoot JPEGs exclusively? I shoot RAW, so the only thing I care about post image capture is being able to preview my photos, show a histogram, zoom in to check for focus accuracy and delete images. Everything else I can do on my desktop, which will always be much more capable than whatever I can put on-device.
To me it looks pretty nice.

https://www.qt.io/qt-for-python
In Memoriam – Remembering Karl Lagerfeld
The API problems you cite aren’t prevented in dynamically typed systems. If anything they are worse, because they could lead to silent failures, whereas a statically typed API statically checks and guarantees the contract. Contrary to what you imply, a statically typed API can’t return an unexpected type. That’s an advantage.

> It always seems to end up in types where every field is optional

“Always”? Not by a long shot. These situations where this is the case can be isolated and dealt with explicitly. You may object to the explicitness but — again, for reasons of robustness — proponents of static typing prefer this.
It's a fallacy to think that all statically typed languages are the same, and all libraries in the statically typed languages are the same. It seems the author is making these fallacies. My experience programming C, Java, and Haskell---all statically typed languages---is vastly different.
Autonomous Visualization System
Wasn't schizophrenia fairly recently attributed to an off-by-one error in the brain while deleting old brain cells, taking more than necessary, essentially a natural algorithm gone wrong?
One thing that is fascinating is that the Danes are supposedly the happiest people on earth. I wonder what their microbiomes are?
I wouldn't trust that GPS is actually off for the baseband processor when you set it off. This is key for the real time location tracking by phone number.
> nothing impressive at all when it comes to RL in the real world

Apparently, many people on this website think Go and StarCraft qualify as "the real world". Majority of them probably never even heard of blocks world and SHRDLU.

AFAIK, the biggest problem in reinforcement learning still is connecting the final outcome with individual actions you took to achieve it. This hits you hard when you move from toy domains to real-world problems, because you can't replay real-world scenarios thousands of times, and even if you do, you can can get completely different results due to various random and external factors.

This can be somewhat mitigated by taking Marvin Minsky approach and building / using a simulation of the problem instead of the real thing. However, in many domains building a realistic simulation of the domain is significantly harder than supervising learning.
If there's no intent to insult, only to help, maybe it's your responsibility that you get so offended.
Sorry, I realise this could have sounded very precious :) In the context of big tech companies in Silicon Valley, free lunch is so common, not having it is worthy of being talked about in such a conversation!
> i don't see a lot of good faith in your arguments if you keep sticking to 4tx/sec and measuring bitcoin costs in per-transaction terms.

edit - I haven't, and my last comment contained nothing to do with per-transaction figures.

I've asked what basis you made your initial claim on, and provided several options where I've looked - transaction rate as currently happens with bitcoin, market cap and daily volume of transactions. None look even vaguely reasonable - so again, what was your initial claim calculated on? What measure were you using and where did you get your numbers? Have you actually tried to work it out?

> i'll repeat and lets see how much good faith you have: payment channels encapsulate potentially unlimited amount of transactions which completely refutes all your calculations.

We have current use, how does that actually compare to the current banking system you were saying uses more energy?
I think all this articles miss the point, sure early strongly type lang like Java were a chore

Current static typing is a lot better and bring a lot of benefits to the table without the oppressive feeling of early Java. Rust, Swift, C# even Typescript are excellent implementations of typed langs.
They're not really tricking Amazon when Amazon is giving a conscienscious zero fucks about any of these things. This is all happening at a rate they must find acceptable or they'd be acting to reduce these problems to a level they do find acceptable.
You and the parent both "get it." I just hope that Apple gets it before it is too late.