skysight-inc/HackerNews huggingface dataset:
When I decided to add plugins to Datasette I asked around and pluggy was pretty much the universal recommendation - with hindsight it's worked out really well so I'm happy to pass on the recommendation.
This is amusing to read. Language is a beautiful evolving thing. Personally I love seeing how people use it in new ways. New words or ways to add emphasis. Emojis are a interesting way of getting facial expressions across in a minimalst way
Could some of that be the difference between the principles that people advocate and how they act when the rubber meets the road? That is, it seems to me that most Republicans do not advocate anti-immigrant, racist, etc. opinions. However, when it comes to election day they are willing to vote in people who put those policies in place.
I'm curious what happens to people who live on the affected streets; do they now have to park a mile away from their house? Or if they were storing a boat on the side of their house, is that boat going to be trapped at their house?
>You may not be directly helped, but you will definitely feel the pain (eventually) when it goes down.

Inflating assets by printing dollars greatly hurts the lower socioeconomic classes by devaluing the only thing they have which is dollars.
I don't think anyone is going to sell you on something else, you seem very ingrained in the React ecosystem. More dollars doesn't equate to "better product" down the road. Angular came and is still a part of Google. Would anyone starting a new project use it over something like VueJS or React today? Probably not. Right? So that sort of tosses your argument out the window.

I don't do JavaScript professionally anymore, but I've worked with jQuery, BackboneJS, lots of AngularJS, some Elm, some VueJS, and some React, but being the curious person that I am, in search of greener pastures, I checked out Svelte, by first watching Rich Harris' video https://www.youtube.com/watch?v=AdNJ3fydeao on "Thinking Reactivity", then seeing the benchmarks: https://twitter.com/Rich_Harris/status/1200807516529147904, and watching Rich and Dan Abramov spar a bit over their challenges. From an outsider with no skin in the JS game, it is clear that Svelte seems far superior now and into the future...

1. it is a compiler (it's like comparing C/C++ to Python)
2. the joy of out-of-the-box animations that use the GPU in CSS (reminds me of the joy of using jQuery for the first time w/ it's OOB animations)
3. you can drop in any other JS lib (doesn't have to be in a particular JS framework ecosystem) and have it inter-op! This is huge! It's because it's literally like writing vanilla JS
4. no need to learn some new syntax like JSX (not a huge fan)

Just take a peek. If you don't like Svelte, so be it, but at least you know what it is that you don't like rather than turning a blind eye because you don't want to be convinced -- that's tunnel vision.

I was trying to decide between React/Vue/Svelte for a project I started recently, and after having attempted to build to-do apps in each, I landed on Svelte.
esoteric [programming] language.
Ask HN: What are your favorite developer-efficiency tips?
I recently started integrating tmux and vim into my workflows. Obviously, it was a huge efficiency booster. What are some other tools (custom built or off-the-shelf), hotkeys, workflows that were game-changing for you as a dev? I'm interested in hearing about anything and everything (stuff from ctrl+l to clear the terminal to little-known git commands to larger-scale strategies like CI/CD)
I didn't mean responsive in the CSS sense, I meant responsive as in the "not slow to load" sense, which is the point of this article.
How would one start with learning those concepts first? I've been wanting a good way to learn networking that I can code along to in my preferred language
30 to 40 cents.

Just kidding, 600 (USD I'm assuming) will get you a GPU instance for nearly a month. That might net you 100-200 if you pay attention and mine the most valuable cryptos
Thanks! Maybe the market maker I worked for was atypical. We definitely had opinions on where the market was going and made good money from that, especially in times of high volatility.
Consider a team of 8 who suck at estimation. Three questions:

1) is anybody aware the team sucks?

2) if yes are people open about it? If no, why not?

3) now what?
sure, for me the line is clearly on the side of "scrolling through boxes of text and basic commenting" = website, since that was the case in 1995. my point was that if you took a screenshot of facebook today and when it launched, other than some cosmetic improvements, you couldn't tell me which version warranted extreme dynamic application logic and which was just a dumb server generated HTML page. the point being that it shouldn't be necessary to do all the stuff in this post to get this result, but it is, because our field has failed to build better generalized solutions to these problems.
The risk of the second wave is precisely the indication that our indefinite containment strategy was fundamentally flawed. We didn't actually avoid mortality in a permanent sense, we just postponed it. Which is why many on the side that you are advocating for are beginning to express the notion that we need to be on guard for the next _months-years_. Not just the next _weeks_.

As briefly as possible: Containment only has real utility if we can develop a game-changer that drastically alters COVID-19 outcomes, and that we don't have to wait so long for it that lockdown-induced mortality eclipses the time-adjusted benefit. It's a risky strategy that requires waiting for an uncertain, temporally-unbounded event, which in turn means that the "indefinite postponement" strategy incurs unbounded cost. We simply don't know enough to make definitive predictions about upper bounds on time-to-discover-incredible-treatment.

Whereas in a no-lockdown, natural herd immunity strategy, we are experiencing a fairly well-bounded spike in short-medium term mortality. I've been using Ferguson's 2.2 million figure for the US which is based off 82% population infection with an IFR of 0.9%, with the population equally susceptible at the physical level (behavioral differences are modelled, I believe). That's an excellent upper bound, it's certainly not the mortality we should _expect_. So we have a much tighter certainty, we will experience somewhere between 200,000-2.2 million deaths due to COVID-19.

When weighed against the alternative, which again is to incur unbounded risk from lockdown-associated mortality, the correct path becomes quite clear in my opinion. A very marginal increase in all-cause mortality in the whole population could very easily offset the spike in COVID-19 mortality which is constrained to fairly limited subsets of the population overall.
I think social media is as social as sitting in a bar where everyone tries to get you to listen to their stories and look at their photos. To respond to someone in the bar you can send a text, which they might respond to somewhere in the future. Therefore, I am not planning to pay for it, since it is not adding (much) value to my life.
Deploying Cassandra on Kubernetes: faster isn’t always better
White-Collar Companies Race to Be Last to Return to the Office
TIL. Thank you for the links. I've got more studying to do now :-)
US has net positive immigration from most of the 'proper modern western countries'.
Yes, noise is bad when you’re trying to focus and it’s the worst when you’re trying to relax.
Good catch, that was a misphrasing in my comment. I meant to say _Zoom's_ investments in security, not security investments in general.
When Magic Eye Pictures Ruled the World–and Frustrated Millions of People
Way to protect the US electrical grid is with open source
I think there are levels:

Level 1: Garbage code with no or bad comment.

Level 2: Garbage code with good comments.

Level 3: Good code with comments

Level 4: Code good enough that it doesn't need comments, with rare exceptions.

Each level is better than the previous. You can't level up directly from 1 to 4.

Still, 4 is the best level. I know it sounds weird if you haven't seen it.
What happened with the drum set?
> but it turns out that COVID causes multiple organ failure, treating which needs a wider range of facilities, and can progress very quickly from respiratory symptoms to that, so they aren't actually much use.

Just to be clear, COVID-19 contributes to organ failure in very limited cases from a statistical sense. So this is absolutely something that is happening, but just wanted to be clear that we are not seeing hordes of people keeling over from strokes, organ failure, etc.

It's known that the complications that come into play when the body has entered a cytokine-storm type state are very far-reaching. For the same reason that inflammation is a critical part of the healing process, systemic inflammation can cause incredible damage to organs and other physiological systems.
I knew there's be at least one.

A similar thing happened here in the UK, we converted an exhibition centre (actually several in different cities) into Covid facilities. In the end we only used a few hundred beds and soon shut them down. What made the difference wasnt that we already had enough beds, but that other mitigating contingencies such as converting other smaller facilities into emergency hospitals happened fast enough, and moving patients out to less heavily hit areas softened the crunch more than anticipated.

I don't think preparing these extra facilities was a mistake at all. There are tons of unknowns and random variables in the progression of an epidemic, if we had needed those beds and din't have them more people would have died, possibly a lot of people. Complaining about waste is exactly like complaining about there being any empty beds in any hospital at any time. We plan for peak demand, including contingencies which may never come. It's like complaining that the military have any soldiers at all that never shot at an enemy, or bullets that never killed anyone. If we'd gone through the epidemic and there hadn't been any spare capacity, we'd used exactly as many beds as we had, that would have been bad preparation.
People should be scared. This isn't over, and this idiotic preemptive celebration/busines reopening is going to render a lot of our sacrifices in vain.
Exactly. I got downvoted for mentioning this elsewhere, but it has been noted over the last decade that modern political polarization is as bad in the 21st century as it was during the 1860's, which is opposite the thesis of this article.
A high-performance topological machine learning toolbox in Python
Be amazed, https://www.youtube.com/watch?v=UQiUP2Hd60Y

https://opencv.org/opencv-ported-to-google-chrome-nacl-and-p...
The problem is not the legitimacy of the issue; the problem is the approach. Grandparent comment said: "I sent an email that I was leaving and would not be returning for at least two weeks and pending further info about any spread."

If they had said that they have concerns about safety, and requested an urgent (possibly remote) discussion, the employer would have more options. By telling the employer that they were leaving immediately, and not coming back until they felt something had changed, they force an immediate decision of either treating it as a resignation, or accepting and condoning unilateral actions by employees.

Strikes are definitely ultimatums, though they generally have clearer objectives, and are usually preceded by a series of discussions. Strikes are not conducive to good relationships.
Apologies if I wasn't clear, but I was trying to defend you not offend you. In my experience, a lot of people hate on Airtable for being a toy, but I've had a great experience with it. I really like what you built!
The fiddle doesn't work on Safari.

TypeError: Intl.v8BreakIterator is not a function. (In 'Intl.v8BreakIterator(['ja-JP'], {type:'word'})', 'Intl.v8BreakIterator' is undefined)
Unfortunately the actually git "push"ing of code is slower. I'm a paying sr.ht member and that's the one thing I wish was faster.
I don't think the comparative death-rate of an attack is necessarily indicative of the magnitude of division that caused it.

I think your data simply illustrates that terrorists mostly changed their methods after Columbine.

Your source illustrates that the total number of incidents was way higher in the 70s.
Yes, that's exactly the point...it's meaningless to say (as you did) that the EIC wasn't motivated by money but instead motivated by goods. Even leaving aside that they sold those goods for money....the distinction is meaningless, as money is just a store of value and lubricant for the exchange of goods (and services).
I never said it wasn't impressive. I was saying that it's sad that this level of incidental complexity is necessary to run, what is for all intents and purposes, a website.
I don't think it's any of those. It's about interactivity in the webpage. Imagine you have the template for the HTML of comments implemented in PHP. Now if the user posts a comment and you want to show the comment on their screen before it gets to the server and back, then you need the template itself on the client. The template being on the server in PHP isn't any help. You could imagine the server filling the template in with dummy values, and then giving that to the client to fill in, but that only works for the simplest of templates where a few values need to be substituted in. You have to create another template language both the server and client understand if you have more complicated logic like many conditional or repeated parts. When you have one part of the UI the client needs to render on its own, it's easy to make a one-off solution for it, but in Facebook's case, I imagine they have a ton of UI that they want to be server-rendered but also renderable on the client. React is a template system that can run on both the server and client, and can live-update already rendered elements on the client as the user interacts with the page.
Funny I wrote a longer response that I trimmed down to just my broken windows fallacy jab where I talked about how building, stocking, and manning field hospitals that remain underutilized is wasting resources, akin to hoarding spare windows.
Lots of people that just lost their jobs & insurance (and can't afford COBRA) are deferring medical service.
Sure, but one of the biggest complications of COVID is that majority of transmission is asymptomatic.
Ebola is so deadly and symptoms so immediate it would likely burn itself out before going pandemic.
> People keep asking "how do we fix policing in America?!" Maybe start by following common sense guidelines written in 1829 that still apply today.

Stop training them like they're going to war and train them to "server and protect" instead.

The National Guard can come in if they're needed. Police don't need to handle that.
My antivirus went red.

>> We blocked this phishing page for your protection:

>> https://thetwentyminutevc.com/
A "bang" is a trigger signal. This is common in audio programming languages and I think the term originated from Max/MSP:

https://docs.cycling74.com/max8/tutorials/basicchapter02

Edit: removed incorrect assumption about audio processing, thanks vertex-four
Can't imagine it being difficult for Korean.
Sorry, I didn't mean to imply that you hadn't added anything interesting. I enjoyed those parts of your comment. It just sounded like you hadn't read the article, since you repeated its points as if they were new. I was trying to follow the site rule against saying "did you even read the article" (https://news.ycombinator.com/newsguidelines.html).
Soooo quicker publishing to YouTube then?
Definitely seems overreaching.

Broadening a definition and a metaphor are not the same thing. Basically every "metaphor" mentioned is just a word that has more than one definition. Sure, the origin of the new definition was likely at first someone making a metaphor, but now they're just words.
I'm trying to find an up to date graph of unemployment rate, over time, showing U1 thourgh U6 rates, which seems the "big picture".

Has anyone been able to find this?

Edit: oh well, I found the table. i'll make my own graph :p

https://www.bls.gov/news.release/empsit.t15.htm
that might well be, but just recently i got a crash report and it turned out the user had some "unsupported" version of Safari... and i'd rather transpile/polyfill than be that site that asks you to upgrade your browser to use it

(funnily enough, it actually parsed ES6 stuff fine, but was missing the `Object.fromEntries` method)
I've been saying this for years but marketing guys love carousels.

If you can afford to hide content why even put it in the first place? Specially on the most prominent part of your website.

If you want to deliver a message focus on essential content that cannot be hidden.
Interesting idea, I think this should be standalone product. On the other side when I see ChatRoullete it is very popular but for some reason not commercially successful.
Frank Herbert (Author of Dune) at UCLA (1985)
I think the problem with outsourcing is it adds a layer of indirection between the stakeholders and the developers. As a developer myself, I find it almost impossible to work effectively unless I have direct contact with the stakeholders.
You should bring him to an emergency room now.
Ask HN: What are the other websites you visit daily?
I'm curious over what others website, people regularly visit in addition to NewsYcombinator? As aggregator, I finds it great, especially for topic that are out of my area.
But is there similar websites in your daily feed or blog you follow?

Any insight would be appreciated.

Cheers.
For reference:

"MoltenVK is a Vulkan Portability implementation. It layers a subset of the high-performance, industry-standard Vulkan graphics and compute API over Apple's Metal graphics framework, enabling Vulkan applications to run on iOS and macOS." [1]

[0] https://moltengl.com/moltenvk/

[1] https://github.com/KhronosGroup/MoltenVK
Surely it's a very literal semantic connection? The backend is in back of (in the sense of behind, from the user's point of view) the frontend ….
You have not looked at Svelte. You've still the overhead of a virtual DOM and its diffing. People that turn a blind eye to Svelte will be blind-sided. It's like writing vanilla JS without all the baggage, because it's a compiler (think C++ versus Python).

I highly doubt that one can build a ReactJS app that loads faster than a Svelte one. I encourage you to try and share it. This is coming from someone that is a backend engineer that doesn't really do JS, but have had to for my own personal project and both perf and the subjective bit of expressiveness and joy of writing are important. Contrary to popular belief, people think that Svelte is trading perf for ugliness and lack of expressiveness.
Ask HN: Any legal problems working in the same field on the side?
More context

I was a freelancer for a medical website and I was trying to help develop this SaaS/online tool that ended up going nowhere. I am aware HIPPA/and all that.

I'm now a contractor/full time for a medical corporation, no relation to above(hiring manager not even aware of former "medical" experience). Pretty much a doctor hired me to try and build this tool he had in mind.

I have decided that due to how much time I sunk into the previous thing that currently has still gone nowhere(other than me getting paid hourly in the past)... I'm going to keep working on it unpaid.

There is no tech overlap, but I'm wondering is this legally okay. I mean I'm not receiving money for the side thing.
But I'm hoping, I can get it to become something so in the future when my contract ends I may have a job.

As mentioned conceptually there's no overlap/different tech/and all that. The only "overlap" is that both are medically related.
Some of this is due to local coronavirus lockdowns and the uncertainty around when they will be lifted, but there is also uncertainty about when schools and day cares will open again. Providing child care will keep a lot of people at home even if they aren't required to be.

On top of that, a lot of people won't want to go back to the office, not because they enjoy working from home, but because they will still be afraid of getting the virus. Being at the office probably won't feel normal anyway due to continued social distancing and the use of masks.

Combine that with concerns that the virus may surge again in the Fall, maybe necessitating another lockdown, and you have a recipe for working at home much longer than what might be legally required.
> Strikes are definitely ultimatums, though they generally have clearer objectives, and are usually preceded by a series of discussions. Strikes are not conducive to good relationships.

You do know that frequently the only reason these "discussions" are able to be had is because of the threat of a strike? What if the GP had these "discussions" and was told to go back to their desk and STFU? Then what?

Strikes are actually the result of employers abusing employees, which is what creates the bad relationships. You sound as though you believe the other way around, that strikes create bad relationships.
"She did not produce further ideas, perhaps being unable."
Show HN: Bolt: A language with finer-grained concurrency than Rust
24% of people choosing not to get a vaccine that doesn't even exist yet is significantly different from what was alleged in the parent comment, which was:

> People think that vaccines have killed more people than they help

A lot of people would choose not get a vaccine simply because they don't like needles, not because they think the vaccine is likely to kill them.
Check out wiki.js, it is open-source, modern yet quite mature, and has a lot of storage backends that you can choose from.
As of when? It was slow for a while, but we did a bunch of performance improvements and it's much better now.
And, that's almost the entire reason why lockdowns are necessary to prevent its spread. Remember how we had lockdowns when Ebola came to the US? Oh, yeah, we didn't, because it only spreads when symptoms are present.
I’ve heard that styled as “do project the document,
don’t document the project” but I don’t
know a source to attribute this to.

The idea is to write a rough draft that covers what the project is, what it does, the API structure, and how to
use the project, then write the code, “projecting the document”, and finally sort out the documentation -
comments in the source, everything else in a manual page,
article, or research paper.
If you can use a database, mediawiki which runs Wikipedia.

If you prefer flat text files, dokuwiki which I personally use at my company and at home.

If you already are in the atlassian stack and can't escape no matter what you do, use confluence wiki. But if you don't already have any atlassian products then stay far far away.
I agree with this assessment of the 'why' - and it's why I mentioned things like turbolinks and liveview. What you mention here seems like a convoluted solution to the problem, but I realize it's how it's done, and I've written thousands of lines of code doing it.

In fact, the original AJAX stuff in the early 00's typically did a primitive version of this since it was the most obvious solution during the era of server side rendering: just have the server render the new comment and slap it in as-is. Instead of extending the reach of that concept instead we shifted towards generic data access APIs and pushing all the complexity to the client, which has resulted in the gigantic mess we see.

I remember writing a basic client-side templating system in literally 2002 that naively regenerated the whole page in Javascript in response to AJAX API updates - you wouldn't notice unless you looked at the CPU being pegged and realize your computer was useless for multitasking if that site was open. It was clearly a bad idea. Little did I realize at the time that the next ~20 years of web software development would take that approach and just try to optimize it.