skysight-inc/HackerNews huggingface dataset:
Yup, right now we use GROBID, do some post processing and combine the output with other extraction techniques. For instance, we use a model to extract document figures[1], so that we can render them in the resulting HTML document.

Also, we're working hard on a new extraction mechanism that should allow us to replace GROBID [2].

There's a lot of really smart people at AI2 working on this, I'm excited to see the resulting improvements and the cool things (like this) that we build with the results!

[1]: https://api.semanticscholar.org/CorpusID:4698432

[2]: https://api.semanticscholar.org/CorpusID:235265639
I regularly write Go code and I mostly enjoy programming in the language, but this post captures nothing important about what makes writing code in Go pleasurable.

Having biultin library features is nice but is not the reason. Python also has a lot of builtin library features, but I don't enjoy working with it.

Static typing matters a great deal, but Java is also statically typed yet I don't enjoy working with it.

For me I think what makes Go pleasurable to write in is that it has structs with value semantics and it also has pointers, and it also has none of the recent (incorrectly labeled "modern") ideas such as enfoced null-checking or enforced error handling.

I can write the code in a very direct and straight forward way. I can decide myself how much abstraction to introduce. I can decide myself which errors are worth handling and which are not.

I can write functions that take complicated arguments as structs without worrying about how it will degrade performance. Because structs have value semantics, creating an instance of a struct will not trigger a heap allocation unless you return a pointer to it or let it escape the current scope via other means.

This matters a lot because a lot of performance degradation in other languages comes not only from being interpreted but from the model of programming that requires lots of tiny allocation.

Another thing that makes go pleasurable is that a package is well defined and you can import packages written by other people. But that's only secondary IMO.

Go's performance is reasonable but it's far from C/C++ level. I think a well written server in C/C++ can outperform a go webserver by a factor of 10. That said, Go is about 40x faster than Python so that's great, and it means you can write a program in Go and run it on a single machine to get the same performance to a website written in Python and hosted on 40 web servers with an insane infrastructure and requires an entire team to manage.

That said, the language also has some warts, such as lack of real typed enums that can be introspected. For example, there's currently no way to dynamically introspect an enum type and find out all the defined values/constants. You must resort to code generation.

Also the lack of generics, but hopefully those will land soon (within a year from now, if nothing goes wrong).

But, what the language lacks in features, it compensates for in tooling.

No where else have I seen a language that makes it such a breeze to cross compile. I can write code on my macbook and compile it for linux to get a valid linux executable binary that I can then `scp` to a server and have it running right away.

The compiler speed is not the greatest but it's reasonable compared to pretty much everything else out there.
Both mypy and pyright/pylance do the right thing when things are guarded with explicit None checks and the wrong thing with “or”, so even though I prefer “or” otherwise when its gated upstrean so that None is the only falsey value it should get, I’ve taken recently to using explicit checks to make typecheckers happy.
The complexity of Apple's product offerings is not that new. iPod consisted of a bunch of random variants over the years (Shuffle, Mini, Nano, Color, etc.) and people were complaining about conflicting product features back in the day (Now it's USB-C vs. Lightning, back then it was Firewire vs. USB).
I used them for technical reasons. It was amazing what crap you could hang off a user port podule. At one point I had a home security system running off a limping A420. This was until the power supply exploded and nearly burned my house down when I was out. It was never replaced.
Sounds like that team should define a style guide and stick to it. Either Brenda or Bob is going to be disappointed for a bit, but the code will be more consistent in the end.
Sometimes when I read these things, I wonder if I've just gotten really lucky and selected positions at places with well-adjusted, mature, talented software developers? This is in no way representative of any of my experiences both giving and receiving code reviews. I've experienced them in a variety of "ways" -- senior's reviewing mid/juniors "by policy", dedicated teams reviewing certain types of code for certain purposes[0], "randomly distributed" reviews among people of similar skill levels, two-person I review you, you review me always and on and on.

I have been doing this work for far longer than I care to admit. My rejections/non-approvals (both received and provided) land in one of the following categories: (a) Did you notice that? (Oops, D'Oh!), (b) Did you know about that? (Educational), (c) Did you think about that? (Edge Cases), and (d) Why? I work with these men and women day-to-day, so we don't often need to butter up negative responses, we have established that "I trust you can do your job" and my comments do not imply otherwise.

The best way I've heard it said is "We do code reviews because errors in software development are common, regardless of proficiency. I don't write perfect code and having a second set of eyes on my work will only make it better/me look better. Reading a growing code-base by reviewing each other's work benefits everyone."

Of the ways those land, the (b) category is the one that requires a little care (if your goal isn't just to bully/shit on someone's gap in knowledge). I find the way to take the sting out of it is to start off with "Hey, I came across an approach to solving this using (whatever); have you done anything with that? It would be an improvement ... (comment goes on)". I didn't say I came across that approach 15 years ago, that it's what I have decided is "Kindergarten in C# School". Guess what? Someone's read my code and thought the exact same thing. I know this because I've thought them about code I've written as early as 6 months prior. Of course, it's a matter of perspective. I thought that over the one thing I saw that made my toes curl up, never mind that the rest of it was perfectly fine, just like the code I'm currently reviewing.

My favorite, though, is the occasional class/implementation that lands in "Why?". Usually those look like the previous -- a WTF-worthy implementation that the only comment I can send with is "Why was this particular implementation used?" -- and often it requires refactoring ... but every once in a while there's that gem. Some edge case that was cleverly discovered, covered and the developer was left with "This is, literally, the only way that this can be done (given the constraints)." It's the code that's both frighteningly ugly/really cool once you realize why it had to be that way.

[0] I was one of two (but really, one of one) doing the entirety of secure code review for a large multi-national telecom for one brief, terrifying, point.
> An email chain from 2010 has an impact on what phone you want to buy?

Why shouldn't it? It could reveal their true colors in starker terms than one has seen before. It's one thing to know, abstractly, that they're an amoral self-serving entity. It's quite another to see it demonstrated so openly.
Travel on an airplane or public transportation. No.

Earn a living? Better find an employer not under a mandate.

The store? Well, if they require vaccines to step on the property, you better get one.

If you want to act like Typhoid Mary, then feel free to be treated like her.
Simply testing in multiple external populations already rejects this hypothesis, unless you think they all had the same scanners with the same stuck pixels.

They also tested several variants of noise.
>How those people put up with it, I don't understand.

People en masse are willfully gullible when it comes for propaganda. Just look at the vaccine mandates.

I myself is from USSR, and when i see photos from NK i see that my past, and i really don't know how they today (or we back then) could get out of that situation until the system crumbles on its own.

>Could others do the same if left unchecked?

Do you see any other way for Afghanistan for example?
Start from the beginning! Manfred Part 1 and Part 2 are great.
I had a completely different response to this article then all of the other commenters. Yes, he is a smug, insufferable asshole who takes pleasure in putting his colleagues down. On the other hand, he is publicly acknowledging his poor behavior and apologizing for it. I thought this was a raw, vulnerable thing to write - he says that his poor behavior arises from a need to feel superior. We've all met people like that - but how many would publicly acknowledge and try to do better? A lot of posters are tearing into this guy for his confession. I suggest that we instead thank him for sharing and encourage him to do better in the future.

His post reminds me a bit of this religious group, Filhos da Mente de Cristo, that appears in Orson Scott Card's novel Speaker for the Dead. All members of this group take names that reflect their resolve to overcome their greatest flaw, for example: "I will put others before myself" or "I will listen carefully before speaking", etc.
I was impressed by the Slime brand bike tire tubes. They're thicker rubber than the stock tubes and pre-filled with Slime self-sealing compound.
The FTC has been asleep at the wheel with tech companies in the 21st century and consumers have suffered as a result. Apple's locking consumers into their platform, Google's steering traffic towards its sites, Amazon's forcing its merchants to give them preferential treatment. These companies have too much power and we need a government who's willing to take bold steps to curb them.
Facebook under fire over secret teen research
Biden administration moves to avoid shortages of Covid-19 monoclonal antibody
Java and Flash are great comparisons, as web / applet Java is pretty much the same market.

My point being that Java felt like they were stewarding a platform seriously (admittedly, mostly towards enterprise priorities).

Whereas Flash felt like they were saying yes to whatever their designer customers asked, and worrying about the details later.

And IE is just being deprecated in many places. 14 years to EOL is a snap of the fingers on enterprise timescales.
Linux has never been scale-able, starting from the days of the Tanenbaum–Torvalds debate. You can't grow a monolithic kernel indefinitely. It's amusing how it managed to reach the state it is now.
Checked it out. I think this is a great idea! Why do think it's stayed niche? There IS real money at stake, albeit philanthropic donations.

My personal feeling: people do not want accountability, and to paraphrase Jack Nicholson in A Few Good Men, they can't handle the truth. I think that's the real reason the Google prediction markets died: managers prefer to do what they want to do, regardless of whether it's going to work or not. Perhaps someone can theorize as to why that's a good thing? I can't.
>> JEDI black eye

>How much of that is due to the new administration not liking the previous one?

"According to a New York Times report, after President Joe Biden took over this year, his administration examined the status of the contract and came to two conclusions– that the legal challenges could continue to stall JEDI for several years, and that the technological concept had already become outdated.

The DoD will now have a new system called the Joint Warfighter Cloud Capability (JWCC), in which both Amazon and Microsoft are expected to win contracts, and possibly more cloud players. Unlike the Trump administration, which wanted a single cloud provider, the Biden administration will be dividing the contract between multiple companies, allowing the US military to not get locked into a single vendor." [1]

It sounds as if there was a political component, but mostly that they didn't care for the deal. It was a bad look, but there is no evidence there was failure to perform on Microsoft's part.

> slow attrition of frustrated developers/CIOs
That was speaking from pure anecdotal evidence on my part. A friend who ran cloud migrations for SMBs at an MSP share a huge amount of frustration with instability, incomplete services, and poor support. I've also heard from others in the cloud architecture community about concerns about products being less feature-complete, as well as concerns with Cosmos DB specifically. Personally I had some negative experiences with Azure 2015-17 but it seems like quality and UX has improved significantly since then.

>> Moreover the torture that is Teams has got to have consequences as millions have had to suffer

>Then why not use one of the 10 competitors for chat apps?

Many orgs are tied to O365 and have made the decision to centralize services around it. Adding a new app like Slack would require enterprise services to support SAML for user provisioning and new tooling for management. Most complaints I've come across center around rampant UI glitches and concerns with video conference quality relative to other options. My son was forced to use it during the pandemic and had plenty of his own complaints about it, along with those of his teachers. Here's a thread from other user reports[2].

None of this is to that that MS hasn't had wins or happy customers; any large company will have its share of blemishes. Azure's growth story has been really strong, but it seems to be slowing down and investors are taking note[3]. I'm grouchy about some issues with Windows recently and took this opportunity to compile all of the negative stuff I've been seeing about them, but that isn't to say that they are irredeemable - just not invulnerable.

1. https://indianexpress.com/article/explained/biden-government...

2. https://www.reddit.com/r/MicrosoftTeams/comments/mcx4oy/why_...

3. https://www.bloomberg.com/news/articles/2021-07-27/microsoft...
Yeh no it doesn't.

"this work was supported by PayPal" - lol

Anytime research is done by an incumbent under threat, probably not worth the paper it's printed on.

Guess how much the current banking system uses when you calculate worldwide all the physical money and coin printing, the servers, the electricity and environmental impacts of buildings and ATM's, the staff commutes, the marketing collateral and advertisements, the pamphlets and the brochures etc.

Oh that's right, we're not allowed to talk about that because narrative = bitcoin bad/energy use.
"It's a kind of magic."
Probably studying axonal transport, the ability of some neuroinvasive viruses to spread from one neuron to the next via the axon & its connection to other cells.
They’re pretty well spaced out.
Are you really comparing people to a thing ?
Time is being bought from employers. Years of life that can never be taken back or used to something else.
We are not products.
As social being the price our time is being compensated define a part of our intrinsic value. Otherwise everyone would be paid the same right ?
So if our value is publicly displayed in the eyes of everyone to see, a new door opens.
Will I be judged by others based on that ?
Will I be able to change company with no leverage because they know my actual worth and won’t pay me from what they are ready to pay someone ?
Will other people in the company or society treat me differently based on this public « worth » ?
Transparency could also reveal inequalities and fix them.

Of course we are interchangeable in jobs, but what about a junior developer and senior one with the exact same job. Should the junior have a senior pay or the senior being stuck at a junior pay until the next carrer change ?

maybe part of the solution is that companies should be transparent from the start. What their envelope is and no more bargaining. Everyone the same amount.
There have been a bunch of surveys similar to this that are all strong evidence of how disgraceful the messaging has been from politicians, health departments, media, etc. But the real problem with surveys like this are asking people what the "average" chance of death or hospitalizations are. We know that the risk from COVID are highly stratified by things like age and obesity and pre-existing conditions, so "average" is wildly inadequate as a measure to describe the real world. A statistics course explaining the difference between normal and Pareto distributions would go a long way in bringing many people back to reality. Alas...
In medicine there is an accepted definition which is used by, for example, the national institutes for health in the US. They use that to define "health disparities" between different racial groups.

That definition is what the researchers used here. Race as a social construct, self-reported by the patient.
I'm not sure what I'm writing above that isn't objective

I would love to hear responses vs downvotes to the floor

Do you think that we can regulate crypto into lower energy use?

Change hearts and minds?
The Romans held Greek culture in high regard. It was unthinkable for an educated man to not know Greek.

And of course the "Greek" part of the Empire survived for a thousand years after the Western part petered out.
How does potential insider trading in any way validate NFTs being ridiculous?
Yeah, the discussion made it clear that this is a configurable problem. I think the puzzling part for me is that a new network service got so little review – after Microsoft’s decades trying to recover from bad calls in the 90s I’d have expected that to trigger more review.
I am always careful to prioritize my comments during code review so I don't come off like that too often.

I'll say things like, "I would have done that like this because of this reason, but as long as it works"

or "This needs to change right now because it's a security hole"

or "We should find a more efficient way to do this, because as the data fills up, the users will start to notice it"

I am definitely harder on new people, and people who ask me for help when they should have been able to figure it out on their own.
Thanks for the pointer. Will take some time to digest the content. Have you considered in making a library, so whoever wants a session replay can manually initiate a recording? So you don't have to maintain a browser fork. I am asking without fully understanding the technical detail. Please forgive my ignorance
OTOH, Ruby has a very similar footgun with mutable defaults, just with default values of Hashes, not default method arguments.
> The pipe in F# is slightly different in that most of the time it has no intermediate lambdas and is compiled in a more performant form

I believe the point made in the discussion is that the F# proposal leads to intermediate lambda if the function does not have the right arity. JS also don't do HM so that point is moot.

The people supporting the Hack proposal made the point that their expressions do not desugar to lambda and has no runtime cost, no idea how it works though.
He was vegetarian, not vegan. So at the least, apparently you misunderstood him. The jury is still out on vegans.
> Should we tell people to get their BMI under 25 too?

Japan does this and has a 3.6% obesity rate compared to our 42%. Doesn’t seem that terrible of a slope to slip down.

https://www.nytimes.com/2008/06/13/world/asia/13fat.html
macOS UI > Linux UI > Windows UI

but macOS has weird quirks that bumps them down in the CLI space.

Linux CLI > macOS CLI > Windows CLI

Linux CLI and macOS CLI are really close, I think but Linux beats it.
An astounding number of people flocked to Yellowstone in August
Paul Romer: Lancet Booster paper "is advocacy that pretends to be science"
It's not about liking it. It's about having abilities to support your value proposition.
No link but our internal API for mobile apps returns a 418 if the installed version is too old.
Seconded, predictive quality of markets is not at all a given. For example, financial markets can have real arbitrage opportunities in size open that no-one removes (if capital requirements are high/volatile) - so no unique predictive state then
They did remove the ability to control ordering for TLS 1.2 cipher suites, but that’s only because there’s no logical reason anyone should change it. TLS 1.3 never allowed controlling this because it is unnecessary.

When it comes to a crypto library, you really, really do not want configuration options beyond what is necessary. More configuration options is more opportunities for misconfigurations, and given the knowledge and skills required to fully understand the implications of these decisions as well as the consequences for doing it wrong, it is better to go without.

These are lessons learned from the bad old days of crypto libraries. If the cipher ordering needs to be (objectively) suboptimal in your use case, it sounds like something is broken and you should actually expect to need to vendor that.

The only reason you can even still control TLS 1.2 cipher suites is because of the fact that it might sometimes still be useful for legacy reasons to enable known-broken ciphers. There’s really no other logical reason to keep that option.
You do know go is adding generics right?
Dude. 100%.
The entire crypto world is like this.

MtGox pumping and wash trading with Willy bot. Bitmex trading against and liquidating customers. Coinbase hiring Litecoin creator Charlie Lee and having him frequently wash trading 99% of LTC volume. Each of these has been _the_ preeminent exchange at some point in time, just as OpenSea is for NFT.

FTX was born from one of if not the largest crypto trader/market maker, and one of two known Tether customers (who apparently account for a large majority of Tethers). Alameda was the only/largest liquidity provider on FTX for some time. Binance has been similarly accused (without solid proof) of trading against customers. Of course they claim to have walls between these relationships. But then again, so did Mt Gox, Bitmex, Coinbase, OpenSea and loads of others that would take too long to mention.

Crypto is a casino where there are a handful of dealers that are running thousands of tables. They are all colluding. The grift is to exchange real fiat currency for chips at their casino.

It has been proven at a shocking number of blue chip institutions (dare I say a majority). Given our expected likelihood of uncovering these things, it seems highly probable that it’s happening everywhere.
Ah I shouldn't have stopped reading. Then as one of the rare browser replay experts (there's gotta be at least like... 7 of us right?) I can certify your project as the real deal.
DARPA plans thousands-strong satellite constellation Space-BACN sandwich
> spiped looks like netcat with symmetric encryption

True. But to be more specific, it does symmetric encryption and authentication.

> If your SSH server has password auth disabled, then all you're doing is moving the attack surface from one thing to another.

I get what you're saying. But I see spiped as port-knocking with a 256bits combination. So basically, you are reducing the attack surface. In order for the attacker to get through, they need a vulnerability in spiped and in openssh-server. (If these probabilities are 50-50 each, that means the overall probability is 0.25)

At the end of the day, spiped should run in a chroot, as a user, so the attack surface of spiped is really low. If it gets compromised, the only thing the attacker can do is "be able to try to establish a connection to the SSH server".

The goal of spiped for me is to eliminate the need for constant monitoring of openssh vulnerabilities, and for installing fail2ban/blacklistd (which can lock legitimate users out)