skysight-inc/HackerNews huggingface dataset:
Anecdote: We _just_ fixed our last JDK11 blocker here at $corp (the groovy 2.x runtime was holding us on JDK8). Our new quality gates are likely going to keep us closer to the latest and greatest, so I don't see a lot of problems with us jumping to JDK17 sooner than later.
y %>% f(x, ., z) === f(x, y, z)

R lets you do macro-ish things at at runtime [1], and `.` is a valid variable name [2]. so %>% can just evaluate the AST of its right argument in an environment with `. = a`.

(it's probably a bit more involved because %>% also supports

a %>% f(b) === f(a, b)

in which case %>% has to do some AST surgery to splice another argument in front of `b`.)

---

[1] https://en.wikipedia.org/wiki/Fexpr

[2] think `_` in python etc. R uses dots instead of underscores
I am 28. A programmer with a sedentary lifestyle.

I was covid positive last October and kicked it fine (verified with a test).

I was tested 2 weeks ago for antibodies, my results were a “76” (I assume percentage?).

Why should I get vaccinated?
It's nice that the watch can tell how fast a tennis serve is, but I don't know anyone who wears a watch on the hand that they hold their racquet in.

Also, the watch presumably can't tell how fast the ball is served, which depends on the racquet speed and whether you make good contact with the ball.
> Thus, accidents were typically attributed to worker “carelessness.”

This attitude survives, not only in the workplace (where safety laws are often fought as "needless red tape") but outside it too (your poverty is due to carelessness, and is nobody else's responsibility).
> The productivity of minimum wage labor did not increase by that amount.

Maybe include a link?
>What's next?

They might say jab passports (once the unjabbed group is small enough to hold down), social credit score, and digital currency.
At least you aren't running an AirBnB. Not too long ago, I started a new job and quit within the week because the housing market in the area was completely oversubscribed. You couldn't even find a bedsit within driving distance in a month's time.

Some lady I was suggested to speak to had an AirBnB. Her suggestion was to live in the back of a U-haul truck while looking for something more permanent. The revolution can't come soon enough.
> Felix Lange found a security vulnerability that caused Travis CI to include secure environment variables of all public open source repositories that use Travis CI into pull request (PR) builds.

This is really bad. The most frustrating part is how predictable Travis CI's decline is, after having been bought by a private equity group. As many people on HN and elsewhere predicted, the days of Travis CI providing a quality service were numbered after being bought by Idera.
I get tired of hearing the term “unskilled labor” all labor is labor.
The advantage is that you don't have to name things. "v" is a bad name in a larger context, and it quikly becomes unwieldy if you use a full name.

let transformedData = transformFoo(data);
transformedData = transformBar(transformedData);
transformedData = transformBaz(transformedData);

vs.

const transformedData = data
|> transformFoo
|> transformBar
|> transformBaz

If you want have const's the first becomes even more unwieldy, and in general I'd recommend using const by default.

Just like lambda syntax makes it much easier and readable to write small functions, the pipe operator make it much easier and readable to write chains.
Most of Asia begs to differ, if not all of Asia.
Standard library? In javascript? You mean a keyword like `async` or `yield`, or a built-in object like Date or Math?
Good question. The metaphor though would be something like: ... and your soul cost you $1 M to obtain in the first place.

There's something special about seeing the future and investing on a team with a dream. It's not the cash flow analysis of growth equity they teach you in school.

This is one unsourced data point, but Axios says "bootstrapped startups typically grow slower and cap out lower than do VC-backed startups" https://www.axios.com/mailchimp-potential-sale-intuit-talks-...
That article was published on 4th December, 2020. Have the concerns expressed therein borne out in the 10 month interim?
I like it, I bought it! Lot's of nice features and a tweaky graph UI. Added bonus for implementing the "kissing nodes" connection idiom.

I would love see more prefabs, especially ones designed to emulate some classics synths.

It also might be time to add undo. Everyone (especially me) likes to save it for last.

Keep up the good work!
In the campaign you are expected to maintain a conveyour of promotion where you will hire some t1s, move t1s to t2s and t2s to t3s in every scenario but the last.

Playing with a select few of t2+t3 units is fragile and not very economical since they're expensive in upkeep. Sure you can recall their lot but then you run out of money quickly.
FYI, you can achieve the same thing with F# pipelines + partial application proposal [1]

input |> func(?, 2)
input |> func(1, ?)

While hack's placeholders work exclusively in pipelines, the partial application proposal can be used with any function

"123"
.split("")
.map(parseInt(?)) // make sure radix param is not set

[1] https://github.com/tc39/proposal-partial-application
Assume up front none of your measured latencies from a software networked system will be Gaussian, or <exaggereation> you will die a painful death </exaggeration>. Even ping times over the internet have no mean. The only good thing about means is you can combine them easily, but since they are probably a mathematical fiction, combining them is even worse. Use T-Digest or one of the other algorithms being highlighted here.
They will probably keep the Mini 13 around as their low tier model. However support will likely not be extended and will stay static.
Yeah, those were just random examples from my imagining an alternative universe in which minimum wage had kept pace with productivity.

You are quite right. Another counterargument is that a lot of household income goes into zero-sum, unproductive status signaling, a.k.a. "buying a house in a better neighbourhood", and "sending the kids to a better school".

Still, some of the extra income would be spent on things that employ other people.
Kotlin is my suggestion too.

Kotlin (or any other JVM variant that does non-nullability in a seamless way) and coding guidelines should get you 90% of the way to a null-free world.
I'd lean towards "probably not safe"; we only just found that teenage boys are at 6x more risk from heart problems from the vaccine than any risk from covid itself:

https://www.telegraph.co.uk/news/2021/09/09/teenage-boys-ris...

https://archive.is/ixG5G
It probably is, however that enhanced immunity can come at the cost of damaged organs.
On top of that, early on when the vaccine supply was constrained we didn't have enough data to know whether natural immunity was as effective as vaccination, and now vaccine supply in the US is in surplus[1], so there is no reason to be selective in who receives it.

So natural immunity didn't make sense to consider in the vaccination plan. It might make sense to consider in the booster plan though - if you've had a positive Covid test before or after being vaccinated, consider the later of those two actions to be a booster, and don't get another one. That would free up more doses for the rest of the world.

[1]We have a large amount of vaccine that has/is expiring shortly but there isn't enough time before the expiration date to redirect them overseas.
> E: Regarding this lancer issue -- sounds like a bad map, but even the biggest attack can only kill one unit per turn. Set your T1's up to block your good units. Then, get revenge on your turn. Plus, as a bonus, Charge works both ways -- some of your T1's might get some big hits in or even some kills.

No. One unit can kill one unit per turn.

One good lancer charge means my Elvish Champion (Tier3 highest HP infantry for the Elves) is dead, and the backline is now exposed. That is a cascading failure where my line is fully eaten up and I lose. When I place a unit in 60% evasion with 70+ HP (very high in Wesnoth), I'm doing so because I need the line to hold in that location.

What's the chance that the lancer is in range? Well, 100%. Lancers have the highest movement in the game.

Champions highest evasion is 60% in the forests. Cool, I put him there. Well, woops. The lancer hit three times (6% chance of happening). Champion is dead. That's not even that low of a chance.
If they catch you it's fraud. If they catch you much less often (or cheaper) than doing it the 'right' way then the for profit group will default to the cheaper option.
https://archive.is/zaWTc
damn, the audio wave visualization on the wires in the thing that's like the Bitwig grid editor is just BRILLIANT.

probably would be a bit much in a complex finished instrument but that's amazingly intuitive for the building phase, or for reading someone else's instrument.

i wish there a way to translate old Reaktor library stuff into more modern synth GUIs. there's some amazing gold in there but it is nigh impossible to understand between Reaktor's uh... challenging UI and the total lack of documentation for the signal paths to try and explain them to a relative novice. you can very easily see _what's_ built, but god help you try to understand why on your own without adding a ton of scopes everywhere manually
I generally agree with this analysis, but people who are looking for some sort of 'smoking gun' that our government is colluding with pharma to help them make money by forcing unnecessary vaccinations, are more interested in hearing sexy, exciting narratives about how Fauci is working for the devil.
> Fully agree on Pandas. R's native data frame + tidyverse is world's easier. Pandas' overly complex indexing system is a persistent source of annoyance no matter how much I use that library.

Is it just the syntax/readability that annoys you, or are there actually problems that need like n steps more to do the same with Pandas?
> Source? This hasn't been my experience. Going on 10 years of heavy Node.js ecosystem involvement, immutable data enthusiasts are exceedingly rare.

Immutable.js is relatively popular and immutable records and tuples are a stage 2 TC39 proposal. From what I've seen, immutability is mostly popular on the frontend, probably because functional programming had a huge impact there. It's also popular in other languages (FP or FP inspired generally, so OCaml, Haskell, Scala, Elm, Elixir, Rust) that are relatively close to the web ecosystem.

> Plus, this is const vs let, which is a reach to call "immutable data". We're not talking about object properties.

I'm not sure what you mean here.
It very obviously applies to the workers that saw the least share of productivity gains. What case would you make for raising the salaries of those paid more than their equivalent jobs were paid (adjusted for productivity growth) when the minimum wage began?
If you are previously infected or not in a vulnerable group its not selfish or stupid to avoid this vaccine. You can manage it with monoclonal antibodies if you do get a severe outcome.

Mass vaccinating the entire population for a respiratory virus that mutates so easily creates a whole host of other problems and a never ending pandemic of variants that may actually get more severe.
Wow - a lot of unsavory folks on that platform. Dump includes

All domain purchases
All domain transfers in/out
All whois history
All DNS changes
All email forwards, catch-alls, etc
Payment history (no credit card data)
Account credentials
Over 500,000 private keys

Not a good look for these "privacy" focused players.

I use AWS Route53 and Google for domain registration. Despite being "invaders" of privacy supposedly, so far they've done a pretty good job keeping my data from leaking - nothing too interesting anyways but.

One worry would be employers or others taking lists like this and doing some screening of candidates etc through it.
I watch this video once a year and send it to my co-workers whenever averages or medians shows up in a graph for public consumption.
I would love the pipeline operator in Ruby, but unfortunately the unstable feature [0] was removed:

1.. |> take 10 |> map {|e| e*2} |> (x)

> After experiments, |> have caused more confusion and controversy far more than I expected. I still value the chaining operator, but drawbacks are bigger than the benefit. So I just give up the idea now. Maybe we would revisit the idea in the future (with different operator appearance).

[0]: https://bugs.ruby-lang.org/issues/15799
You may want to check this out: https://www.foxbusiness.com/lifestyle/people-who-work-from-h...
> the dumbest guy in the room at the same time while actually being the sharpest

He would've won top prize on Millionaire but backed off before answering the last question from nerves.

https://millionaire.fandom.com/wiki/Norm_MacDonald

What a legend
1. I don't think there's a good argument for tying minimum wage to median productivity gains across the entire economy. Is an accountant today 5x more productive than an accountant in the 1960s? Perhaps. But is a dishwasher or a frycook 5x more productive? Probably not. I also think the biggest problem impacting lower income folks is housing costs and IMO minimum wage is not the best tool for fixing that issue.

2. 1968 as a start year is super mega cherrypicked. A lot of people say "if minimum wage had kept with with CPI inflation since 1968, it'd be $12/hour now!" They usually neglect to mention that if minimum wage had kept up with CPI inflation since 1948, it'd only be $4/hour. The only reason to use 1948 vs 1968 is to massage the data to match your preexisting hypothesis.
> I've spent about 1 month to test how scrapy could be a fit for our purposes. And, quite surprisingly, it was hard to design a distributed web crawler. Scrapy is great for those in-the-middle tasks where you need to crawl a bit + process data on the go.

I agree (but in my case I needed 3 months to understand that :) ).

I did start with plain "Scrapy" and it did work fine (maybe some parameters could be explained a bit better especially the ones involving concurrency) and it has been in general very helpful to initially understand some concepts related to web scraping.

But now, after having rewritten multiple parts like 50 times to be able to handle most of what can happen, having split the workload into a multi-staged pipeline involving different specialized programs, having implemented custom code to distribute domains to be scraped to dedicated subprocesses (to greatly improve performance), and much more... I am using Scrapy basically to only download the raw bytes and to take care of what's mentioned in "robots.txt" => my next step will most probably be to replace it (now I don't like a lot having it as a dependency for my program, I therefore started thinking that such a complicated lib is a bit a "risk") with "requests" and something that can help to interpret "robots.txt".

In my case ("wide" Internet scan involving so far ~8M webpages distributed over ~500K domains) I think that it might have been better to start straight with just using "requests".
Tianwen-1 attitude in Mars orbit
> Serology is a thing, as are records of positive test results.

Serology is a thing, sure. But two points:

Getting a serum test rather than getting the vaccine is not going to be cheaper, easier, or better studied. We are not constrained on vaccine supply. So the practical advantage of allowing a totally different pathway is not obvious.

Creating another pathway adds a lot of cognitive load and confusion. The bar bouncer checking vaccination status at the door is not likely to know anything about serology. The same goes for people eager not to get Covid and the people eager not to accidentally kill grandma. Every bit of complexity is met with complaints and confusion; every change in regulation makes it harder for people to know what to do and therefore less likely to do it.

In some future pandemic might we want to create a two-pathway system? E.g., such that there's a government-issued "safe to mingle" digital passport? Sure. That seems like a great thing to start preparing now so it's ready the next time a disease hops the species barrier. For now, though, I think we should stick with the current plan: vaccination for (almost) everybody.
Long history and baggage of object orientation, I suppose. There's nothing inherently mutable about dot-notation (indeed, F# uses it for accessors on immutable records as well as for "proper" object-orientation), but lots of object-oriented languages use the dot for accessing objects, and lots of object-oriented idioms involve mutation. If you're going to send a message to an object, you do kind of expect something to happen, and that's often a mutation somewhere.

Having said that, I actually don't know the history of the dot operator in any depth (https://cs.stackexchange.com/questions/89031/what-is-the-ori... suggests it arose in Simula).
you're not arguing in good faith and much of your argument is just illogical. There's no reason to do this, it won't convince anybody , in fact it will make most people just ignore you.
Tbh I don’t blame them all that much. Even as someone who is enthusiastic about Linux and has been a Linux user for many years I find it difficult to support other distros than the one I actually use. And lately I’ve been booting my main Linux box more and more rarely too, as my MBP M1 with macOS is suitable for almost everything of what I do.

So for example when I recently went to describe in a README how to install some software that I’m workin on, I relied mostly on my memory and secondary sources in order to try and give a pointer to users on various distros for how to install the dependencies in question. And for example from what I could find for openSUSE Leap 15.3, both of the pieces of software are/were not in the official package repos at the time so I simply stated that, linking to the relevant pages under software.opensuse.org that told me this, but not having run openSUSE myself for years I am not sure the reason for it or indeed if it’s even completely correct.

I guess there’d be room for some CI service where instead of a specific Docker image like many use you’d instead list the dependencies in a kind of meta format and the service would install the corresponding packages and run the tests across many distros. Then the service could generate scripts or readme instructions for each distro.

At the moment I think realistically in most cases it will need to be that people who run various distros take it upon themselves to sort it out and to submit pull requests to projects about how to install and use on any given distro.

My own preferred Linux distro for desktop is Debian-based too. KDE Neon.

But so, I think it may be worth it that you try and submit a PR to the OP for adding instructions or an install script adapted to your own distro of choice.

Although ultimately, if the software grows big enough eventually someone will add it to the package repositories of each distro and then there will be no need for manually or scriptually installing the deps, because the deps will be specified in the package repos. And for example if you use Arch I guess someone is bound to add it to AUR if it’s there already.
If you're an engineer, this will surprise you. but, the vast majority of people don't know how to normalize data or even why you'd do it in the first place. cost of a burger of 1/3 lbs vs cost of a burger over 1/4 lbs, ( i don't mean to sound insulting) but the fact is: that's waaayyyy to much thinking for most people (it just doesn't come naturally for people to think like that). Personally, I normalize nuritional data on a per 2000 calorie basis. I've even had a doctor question this, until I explained the concept of normalization. It's just not how non engineers/ non scientists are accustomed to thinking.
> Very interesting. A possible improvement could be some "knob linkable objects" (can't imagine the correct name) that could be tied to analog inputs (GPIOs, ADC connected to i2c or USB, etc). The purpose would be to be able to modify certain parameters live on the fly, should anyone want to create a physical synth out of this software and a *PI like small SBC.

This is usually called "MIDI mapping" or similar and is available in basically every DAW these days.

> Also, I like a lot the way it links inputs and outputs just by dragging the mouse. Does anyone know if there is any general purpose library to do that? I mean, Ideally I create some list nodes, then use that library to link them in a certain order by using the mouse.

Something like qjackctl (with Jack, obviously) could do this for you, as you can route things however you want in a drag-and-drop UI.
Any serious policy which brings natural immunity into the fold would include the need for an actual medical diagnosis. I don't see the issue to raise to be a valid one because there are easy solutions.
“Selfishness” is not how I would characterize the motivations of people who haven’t vaccinated.

By the way, I have been vaccinated for months, but I can understand that others may not want to for reasons other than those I would describe as “selfish”.
Most UXR is not the same as a rigorous (ie peer reviewed) study. Not every qual study is in person interviews, but based on the part about users bringing topics up unprompted I'm guessing that's what at least some of this was based on.
https://www.science.org/content/blog-post/new-antibody-depen...
Also replication studies for negative or null results in addition to positive ones (we don't have either).
Crying wolf repeatedly to cajole and coerce people is not a good long run strategy.
That's a change then. Before they use to aim for paying at about the 50th percentile. So Google and other companies would literally pay twice or more as much in salary in comparison.
There's a proposal for this: https://github.com/tc39/proposal-partial-application
You also get better NullPointerException messages, which to me have been super helpful during development. https://openjdk.java.net/jeps/358
Discussions from earlier today:

https://news.ycombinator.com/item?id=28523350

https://news.ycombinator.com/item?id=28524727
Comparing something completely in your control to a virus that you can still get even with the vaccine is inappropriate a best, disingenuous at worst.
Java could adopt swift-like `Object!` typing for non-nullable variables and spread that guarantee through the compiler and JVM runtime.

I don't think it's a technical impossibility, but it's more likely to be solved by a JVM-based language like Kotlin than it is to get it adopted into the Java mothership.
Yup, I have the 12Pro and don't feel like all the improvements to camera and apparently battery life are worth shelling out $250 (after trade in credit) is worth it, without also getting touchID which seems to be perpetually in next year's phone for the last 3 years.