skysight-inc/HackerNews huggingface dataset:
They could have followed the Craig's List model of monetizing just enough to cover all the costs and keep the site running, without overly focusing on revenue growth sacrificing what made the site great in the first place.
I like the limited choices - it's much less overwhelming, and it's nice to have an opinionated curation.
I don't know where this perception comes from but it's not true. Collective bargaining isn't about the entire employee pool being represented as one skilled homogeneous block. It's about giving employees a voice at the decision-making tables in a company.

I'm sure you've heard the myriad stories about where the decision makers at a company have done some damn boneheaded thing, something so rock stupid that could only come from never having worked on whatever ground floor the business has. And what can the employees do? Nothing. They have to comply because they don't have a voice, because if they argue, they're fired. If they don't do it, they're fired.

THAT is what a union can fix, among tons of other problems. A smart boss is one that listens to his employees when they speak up about problems; a boss working with a union doesn't have a choice.

And that's not to say that unions are perfect, like anything else made by humans and run by humans they have flaws. But IMO, problematic representation is better than no representation.
And 99% would pick "Love thy neighbor"
Their velocity might have been slowed by figuring out how to manage 4,000 containers effectively. If they had dealt with managing concurrency effectively sooner, they would need 30x less containers-- 133.
rich white guy who is exxon movile executive says please don't stop him and his friends from ruining everbody's lives by hoarding wealth.
This was the problem that turned me from a music major to a math major and eventually led me down the path to computer science. It's a beautiful and cold problem and I love to see any progress made on it.
Show HN: How to email automatic status reports from Jira
They write (somewhere in the middle)

> Since V8 implements a stop-the-world GC, new tasks will inevitably receive less CPU time, reducing the worker’s throughput

But there is this Google blog post vom January 2019:

https://v8.dev/blog/trash-talk

> Over the past years the V8 garbage collector (GC) has changed a lot. The Orinoco project has taken a sequential, stop-the-world garbage collector and transformed it into a mostly parallel and concurrent collector with incremental fallback.

So I guess they used an older node.js version. The current LTS version is 12.x and it is from around the middle of this year.

---

PS: If the blog author reads this, there is an accessibility problem with the Google-hosted inline images. If I try - without ad blocker - in an anonymous window I see none of the inline images. Logged into Google with my own account I can see some but not all the images. Apparently which images I can see depends on being logged in to my Google account? I also tried IE Edge just to see if the browser makes a difference - no inline images visible there either.
My guess is because their system is primarily issuing HTTP requests and extracting data out of responses: html, xml, json, plaintext, etc. Web scraping is a messy business and using a language that allows you to be flexible with string manipulation and types goes a long way toward sanity.
> If your insurance company or bank is allowed to use all data it collects to make model of you, it leads to Kafkaesque world.

I reflexively agreed with what you wrote then I started thinking more about it, playing some likely scenarios through in my head, and now I'm not sure it necessarily ends in too bad of a place.

My reasoning: Ultimately, risk estimation has to actually reflect reality to be economically sustainable. Insurance is a highly competitive marketplace with low switching costs and relatively low barriers to entry. I've been driving for several decades and have only been involved in a couple of accidents, none of which were remotely attributable to me. I think I'm very low risk, yet I pay what seems to be fairly high premiums. I suspect low-risk drivers like myself are subsidizing higher-risk drivers due to the expense and inaccuracy of more accurately pricing forward risk.

So, taken as a general concept, more accurate risk assessment done more efficiently enables the actual risk component of insurance priced more fairly and higher efficiency actuarial estimation reduces the overhead cost of providing the overall insurance 'product' to a consumer. Broadly speaking, these are net positives. In terms of how it's done, I think that the market will react to pricing changes such that there will be insurance companies who promote the fact that they don't use XYZ risk estimation process, much as some Las Vegas casinos advertise that they only use single decks in blackjack vs six decks, increasing the appeal to card counters.
Hard questions: Are millennials dangerous?
I wonder how much it costs to get a thousand bot accounts to subscribe to your account.
To be fair, NPM really doesn't do a great job at project scripts
Many of the smartest mathematicians who have ever lived have spent collective man-decades thinking about this problem. Any idea any of us can come up with in an hour of thought will have been considered and rejected a thousand times already by others.

This is partly why it's such a trap. It's like trisecting an angle or squaring a circle -- easy to state the problem, easy to start playing around with it. In my amateur opinion, any proof related to Collatz would be similar in complexity and non-obviousness as the proof of Fermat by Wiles, if such a proof is even possible.
In the past I've used a tool to aggregate those PRs: https://github.com/acsone/git-aggregator
Eve Online is produced here in Iceland and much of the language and norse mythology is worked into the game. Eve online uses ISK, we use ISK here.
Nice visualization! I wish there was a way to share the graphs.

An interesting thing to notice is how the previous (hard to find) optimal solution is lost when adding a node at the opposite side of the graph (which is far enough to be irrelevant in most cases). I would therefore just insert the new point between the two closest nodes, and keep the same path as the starting point for the optimization. Of course, the risk with that methodology is to fall into a hard-to-escape local maxima.

There is probably a way to infer how much a new point will affect every given node, so maybe a better way to proceed would be to identify those that are likely to be affected, and only re-run the optimization from scratch for those.

Of course, where you position the limit itself is an optimization problem...

(edit: or just persist pheromones, regardless of the new points?)
Can you suggest something a little more concrete? What should I add to my project so that if I die tomorrow the project can continue without me?

I work on a small project. I didn't add a CoC when the big push came about because I concluded that it was if I say it is bad it is bad, otherwise it is good - that is no CoC and so there is no point. (I did consider asking some large project - KDE for example - to be arbitrator, but I didn't bother)
I’d be curious to hear more about the circumstances that ended up with a blocked runloop. Are there hundreds of junior engineers, or perhaps third parties writing code that you don’t control? I have seen people accidentally write blocking code, but not at such an egregious rate that we couldn’t catch it in code review, or at worst the runloop detector would alert on it in prod and we would roll back the deploy.

For instances where you actually know you need lots of CPU, there are now strategies for offloading that specific work, although they have taken a while to get nice and easy to use.
Our integrations are primarily written in Node, which was the original language used for everything at Plaid. Almost all of those original services (except for integrations) have been migrated to Go or Python at this point. We've standardized on gRPC as our wire format, so we stayed consistent and used gRPC in Node.

With perfect hindsight, it's a fair point that all the pros and cons could net out to another language being best for our integrations. Integrations are the largest and most quickly-changing codebase at Plaid, so such a migration would be a massive undertaking. We definitely didn't want to block scalability improvements on doing a language migration.
The layperson used to use WordPerfect 5, a non-WYSIWYG word processor which required typing 'codes' using modified function keys to change styles. It came with keyboard templates so you could remember which key did what.

IRC and USENET are simpler than that.
Well said.

Despite all the valid criticism of Apple in general, you can still be reasonably sure there's not an admin panel with an admin:admin login sitting there with all your child's data. That's part of what you're paying for.
This is true. I just don't think Machiavelli was well known for his positive humanitarian outlook towards things. I suppose it's assuming bad faith. You do make a good point though, and it's probably better to try and take a positive message out of it.
And Wikipedia? And email? AOL? Compuserve? Citadel BBS? Finger?
Google literally sells the top spots on results pages to advertisers. Come on. A little notation many will ignore doesn’t make it not a sale of the top spot.
Perhaps another problem with strategy is that we expect too much from it, because we neglect and devalue tactics. I often hear "strategic thinking" lauded and "tactical thinking" looked down upon by managerial types. But a strategy alone achieves nothing--you need good tactics to execute on it.
I admit this source isn't very reliable, but craigslist does more than just "get by," in fact if you're comparing it to any company besides FAANG it is extremely successful. It does so well the investors didn't even push for an IPO, they happily accept dividends.

https://www.businessinsider.com/craig-newmark-craigslist-fou...
> in brute economic terms, mis-priced

Is this necessarily a bad thing? Or are you saying this is basically an arbitrage opportunity waiting for someone to exploit it?

How would we structure something free that provides value, and keep it free in the long term without degradation?
I took my first SuperShuttle on my last conference trip to SF. I didn't talk about payment until I was already at destination, at which point he told me he didn't have a machine. I thought it odd, and just gave him cash. He told me $19 even though the guy at the airport told me $18. Gave him a $20 and went on my way.

Also the ride was very odd. The guy mentioned how he wished he could drive a tank, and even had tank models in the shuttle. And he drove very aggressively and angrily. I couldn't help but thinking he was in the wrong business...
At some point you have to take a step back and realize you've grown beyond your tech and reach out for something else. Elixir sounds like a great fit for these problems.

For example Discord reached out to Rust and built tiny Rust components that are called from Elixir for their server user list. Some servers have 200,000+ people online, and Elixir wasn't cutting it performance wise. Rust, boom now it works.
StackOverflow? LinkedIn? Is any website with user accounts "social media"?
No it doesn’t. We’ve had good models for concurrency in single-threaded systems for a while now.
A hacker accessed ring camera and harassed a 8-year-old
> And at that time there was also a lot of controversy about their competitors selling search positions, so you could outright buy the #1 slot, for example. Google never did this, and always maintained a policy of maintaining a clear distinction between organic results versus ads. The line may have become less bright over time, but it's always been possible to discern which items on the results page were "real" and which weren't.

They do exactly that on mobile, and if you watch non-geeks use Google they cannot reliably spot the ad versus the "natural" results. Hell, I tap the ad about half the time, because I'm in a hurry and don't look closely enough, and they've extorted the owner of whatever company I'm searching for to pay for their own name so the top result is an ad for the thing I obviously wanted to find anyway.
Man this sounds like the rant of someone hopped up on goofballs.

Tell me what transpires when society loses the tradition of staying amped on uppers for the sake of success?

Let's say society kind of forgets that all success depends on speed, and the next generation isn't clued in on the reality that all prior achievements were the result of maxing out doses?

They try to do it sober, and can't, and don't understand why.

What then?
But you need to know if you can do that something first, or if you've done that something too many times in the last N minutes (and could get blocked, forcing thousands of other somethings to get endlessly queued). Or if that something could take too long, and actually you could be doing 200 other somethings in the same time etc. It's not that simple.
It's possible to migrate software without driving off all your users. It's soft, after all. When the 8-bit wave crested, that didn't mean Apple was done as a company.

Why do we accept that such a short-lived company (less than one human generation) is "a good run", just because it's software? If Tesla turned into a "classic pump and dump scheme", nobody would say "Well, Tesla is 16 years old. They've had a good run."
Cool site - bothers me though that “This sections hues” is missing an apostrophe...

Also, is this a clever ad for Webflow? If so, I’m not complaining...

useful ads >
I’ve never seen a fist fight in an office. Probably not a good idea from a legal or liability standpoint.

But if two consenting adults want to physically fight in a controlled, fair environment, zero problems with that. And I could see how it could be therapeutic to release the resentment towards the other.

Maybe an office boxing league?
About $90ish after some cursory searching. I wouldn't do it, though, seems like a great way to get a nasty surprise in the future when the bots get terminated.
Well it's hard to guess what the admins are planning. They said it would stay around for the foreseeable future but I agree their changes are becoming increasingly adversarial. (EDIT: Though new reddit has brought about a number of good improvements to the moderating experience. Sadly at this point the mod community had already implemented all of them and more via 3rd party browser extensions...)

Our community might have a slight old-reddit bias -- we have a core group that doesn't like change -- but I have a hard time believing it could have a terribly large effect once the numbers are in the millions.
Love this idea! It's definitely something I would use more if I could create my own palettes or view popular palettes
Pipenv uses hashes to make sure the files are really the same, not just packages with the same version number.
seriously, the difference between google and everyone else was vast.

You had a lot of services that were literally amalgamations of all the other searches. They would would automatically go search 3, 4, 5+ other search engines because they all sucked in their own way.

And then google came along. Google was good enough that the approach of sifting through multiple search engines wasn't necessary. All those other search engines disappeared practically overnight. No one who experienced google would touch anything else.

google today might not be as technically superior anymore since we as a species understand the search space better, but at the time? google was absolutely game changing.
It is used as package manager often enough -- stick "git clone", or ExternalProject into the CMakefile and you have the (bad) equivalent of "pip install" for C++.

For example, I mentioned "kitware superbuild" above. It describes itself [0] as:

> It is basically a poor man’s package manager that you make consistently work across your target build platforms

[0] https://blog.kitware.com/cmake-superbuilds-git-submodules/
The frustration over unaffordable housing is completely understandable, although making it about the landlords as people, rather than the system, is unhelpful and likely to backfire.

If you don't understand why things are unaffordable, then you won't be able to fix it. A combination of issues are at play, but primarily there are two causes... land speculation and regulations that impede supply. The first category can be solved with a land value tax, and the second category requires overcoming the NIMBY lobby, but also ironically overcoming the anti-landlord lobby itself whenever rent control is in play.
Which means the business never should have taken VC funding, because it just puts the whole venture at risk while adding zero value.
YouTube is definitely doing this. If you watch a video without being signed in, it now displays a popover (over the video) that says "You're signed out of YouTube. Sign in to like videos, comment, and subscribe. [GOT IT]"
In a similar vein, it's always amusing to see the Conservatives attacked for misogyny: which of the two main parties has had two female PMs, versus none?
Google buying your company is probably the biggest win (financially) you could wish for.
Header only fixes the lack of build system/module system as part of the language. Some popular build systems include: make, cmake, Visual Studio, Xcode project. Each has a different format for specifying source/header/libraries - and even if you provide project files for all of the above, then what about the other 1,000 build systems?

Header only is nice and easy, dump file in the project, #include and your job is done.
Alison Harcourt
Barman 2.10 – Recovery of partial WAL files
Yet this is the case mentioned in the article.

> We were running 4,000 Node containers (or "workers") for our bank integration service.
That's a great comparison that I never thought of! Thanks!
Oh, their recent way to make money with hotel/flight bookings, restaurant reviews, etc is even scarier.

They essentially use their search engine market domination to find out who else makes money off the biggest searches, and then clone those products and show the clones on top of the originals. Good luck competing with that...
I kidnapped a baby crow thinking it was injured. My neighbor helped me capture it as the crow parents were honking at us from the trees.

At the animal clinic, i learned it couldn’t fly because it was a baby, not due to an injury, so i offered to reunite it with its parents.

The minute i released the baby, the parents flew over and started barking. It seemed almost like they were trying to guide the baby away from me.

For the rest of the summer the crows would yell at my neighbor and I if they saw us.

That fall, I was walking my newborn outside and was dive bombed by one of the crows. I got the sense it was payback for kidnapping the baby crow.

They hold grudges.
First, they can offer both http and https endpoints. Second, you can send HTTP request if you set NSAllowsArbitraryLoads=true.
I'd say creating the surveillance state is on par with weapons systems, drones, etc. The fact that every American is spied on (I know they accepted the T&Cs) and has zero privacy anymore is not "don't be evil".
How do I declare packages needed for development/testing but not production?

Yes, pipenv is mostly just a frontend to pip+venv, but that doesn't mean it isn't useful.
I don't remember this time at all. But I've never found much value in the big subreddits because of the incentives to game them for karma and traffic. The most interesting communities have always seemed like the small ones since there are more people interested in a conversation vs. a popularity contest.
Google Achieves Its Goal of Erasing the WWW Subdomain from Chrome
I think you may have misinterpreted earthboundkid; the claim isn't that it worked in the 90s, the claim is that it was already broken in the 90s.

You are otherwise on the right track, though Node does technically have one advantage, which is that it is a cooperatively-scheduled island in a preemptively-scheluded overall OS. In the 1990s, when the cooperatively-scheduled program was not cooperative, you locked the machine, not the process [1]. There is a reason why Apple went very aggressive with the OSX rewrite; the previous Systems had basically written themselves into a corner where they had to use cooperative multitasking because so much code made use of the implicit promises it provides, yet they could no longer afford to compete with Microsoft if they didn't get off it it, because the complexity just kept going up, up, up and the problem was going to continue getting exponentially worse.

For a Node program, you only have to account for the Node program itself, not everything running on the computer. Still, you're in the same exponentially-growing-complexity trap (with a very initially-safe-seeming low exponent, but it still gets you in the end), you just reset yourself back to a point earlier on the curve.

[1] There are various details, caveats, interrupts, etc, the picture is more complicated than one sentence can convey, but the principle still held and it was still possible to wedge the machine fairly badly for varying periods of time with simple bad code.
now that is sarcasm with a big 'S'. Love it.
Are you seriously arguing against event loops as a category? Blocking in non-blocking code is going to be an issue whether the language is C or JavaScript (duh).
Just went to voat, and it keeps redirecting me to the sign in page regardless of where I go, so looks like they've beaten reddit in terms of unfriendly accessibility.
> In terms of what issues caused us to move away from parallelism in the first place, it was all the CPU-bound stuff that you might expect: ReDoS-style issues, post-processing arrays in very large edge cases, programmer error, etc.

But these are not parallelism problems. These are single threading problems, which the core problem with Node.js, not parallelism in general. Hence I think the question stands: why did you choose node for this?
Didn't see it mentioned: SSL tickets. If you were running a NLB and nginx in a pool of instances, you can use an Openresty-based inplementation of SSL tickets to dramatically speed up negotiation of reconnecting clients. You will need a Redis server to store the rotating ticket keys but that's easy with AWS Elasticache. You will also need to generate the random keys every so often and store them in Redis, removing the oldest ones as you do. This is a task that I accomplished by writing a small Go service.

If you serve a latency-critical service, tickets are a must.
Lebanon electricity crisis: Stealing power to survive
Yes, it is possible, and actually works - unless one of your threads blocks the event loop and prevents all others from running. This way it takes a single locking thread to halt the whole system, whereas with standard threads a single stalling thread does not cause all others to starve. This is a risk in Node that multiple other runtimes of other languages do not have.
In general academia is competitive and productivity matters. You are evaluated relative to other academics at similar stages of their career.

Finding a good mentor will be tough if you cannot commit full time. Advisors basically have to decide which students Will have their limited time for mentoring.

So you’re competing with full time students who often have no family and willing to work every waking hour of their life.

I think going part time route will depend on how much more productive you think you can be compared to other PhD students.