skysight-inc/HackerNews huggingface dataset:
The paper:

https://www.antlr.org/papers/allstar-techreport.pdf

Has the important detail why it scored good in benchmarks against other parsers:

"7.3 Effect of lookahead DFA on performance

The lookahead DFA cache is critical to ALL(*) performance.
To demonstrate the cache’s effect on parsing speed, we disabled
the DFA and repeated our Java experiments. Consider the 3.73s
parse time from Figure 9 to reparse the Java corpus with pure
cache hits. With the lookahead DFA cache disabled completely,
the parser took 12 minutes (717.6s)."

I'd still most probably hand-roll, at least when making something for a long-term project, and not some "demo" -- there the stability and ease of maintenance is more important than fast availability of initial results.
without all of the "fixed the thing I forgot to add" messages

This is why you use rebase --interactive or other ways of amending commits before submitting a PR. It is not an argument for commit squashing.
SEEKING WORK | EU/US | Remote | Part-time

Backend developer, SQL expert, Technical lead, Architecture consultant (CTO for hire), DevOps engineer with 10+ years of experience on various projects..

Some Skills:

* C, C++, Go, Java, Perl, Shell, PHP, Python, Lua, NodeJS...

* SQL, PostgreSQL, MySQL, Oracle, Redis...

* Fulltext search, SOLR, ElasticSearch, Nginx+Lua (OpenResty)

* Web Scrapping, XML+XSLT, ETL pipelines, DWH building, BI reporting

* Automation, Ansible/Terraform

Areas of expertise:

* Building of performant and scalable fulltext search systems, with autocomplete, REST/GraphQL API (PostgreSQL,SOLR, Nginx...)

* Setting up of an easily configurable monitoring systems build on top of various open source components like iTop CMDB, Prometheus, Alertmanager, Grafana, Fluentd, TimescaleDB.
With reporting, self-service operations, inventory synchronization, etc...

* ETL pipelines (data collection, transformation, reporting...)

Github: https://github.com/samsk/

Email: ja.hn3[at]mailnull.com
Open source pandemic ventilator (strongly suggested to not actually build or use by medical professionals in thread.) https://news.ycombinator.com/item?id=22453100
I don't trust that this number is proving what you're saying it does. It's a meta point, but I found myself trusting such "data" less and less.

"Do you have data?" or "Do you have a peer-reviewed paper about it?" is an Internet meme at this point. Bringing some numbers or DOIs is table stakes now, in anything but dumbest of discussions.

These values - "0.076 per 1000 miles", "13158 miles on average" - have a history behind them. They're pulled out of a set of test drives. But how did the drives look? Was it a collection of similar drives, or a bunch of longer drives with significant disengagement plus a lot of short and easy drives to lower the average? To understand the true meaning of the numbers, you'd need to see (among other things) the distribution of distances covered by test drives.

I wish we had a way to require and embed context with the data, inline with the data. So that when I see "0.0076 per 1000 miles", I know it's:

SELECT 1000
* (SELECT sum(disengagements) FROM drives)
/ (SELECT sum(distance) FROM drives)

And so that I could click around and turn it into e.g. a probability distribution of:

SELECT distance FROM drives

Or view a cumulative distribution of disengagements per distance:

SELECT t1.distance, SUM(t2.disengagements)
FROM drives t1
INNER JOIN drives t2 ON t1.distance >= t2.distance
GROUP BY t1.distance
ORDER BY t1.distance

Now the problem usually is, this data is often not available - people release aggregate summaries instead of full data sets (whether that's the case with Waymo, I don't know - I didn't check, because I don't care about this particular case). But it should be made available, because point summaries of distributions are the easiest way to derive bullshit conclusions (and/or intentionally mislead people). And conversely, I don't trust point summaries unless I either a) review the underlying data (or at least know the shape of its distribution), or b) can trust that the person giving me the summary reviewed the underlying data (or knows the shape of its distribution) and isn't trying to mislead.

So there are two problems here: getting people to release more data, and creating tech infrastructure so that this data can be explored inline (preferably with nice UX that doesn't require user to type in SQL).

</end-of-meta-rant>
I am wondering: shouldn't the head be a solenoid? If the head is permanent magnetic it would destroy the stored information.
Debian package maintainers who allow malware to slip through are likely to be forced out of their post by the community backlash. Similar accountability for Mozilla/Google addon reviewers isn't there. The addon gets taken off but what is the accountability from the employee who allowed it to pass review? A company apology is fine from a PR point of view but it also means that employees will not take their job as seriously as a real demotion or consequence.
Whether it's specifically SVN doesn't matter really, the point is that no other version control system in history required so much mental effort to be "learned" like git. And the worst thing is that new people who don't know anything else than git think that this is normal.

What's happening under the hood is mostly fine (mostly, because git completely breaks down with large binary files, and solutions like git lfs don't help much with this problem).

What's really bad is the git "frontend", that there's no obvious standard workflow, instead there's a thousand ways to do the same thing. That's great if you have a lot of time for tinkering and meddling with the tools layer, but not when you simply need to get shit done. The version control system should essentially 'disappear' and never require attention.
New GCP Regions Announced: Delhi, Doha (Qatar), Melbourne, Toronto
I work third shift, but switch to daylight schedules on weekends and trips often. I've just learned to plan my sleep about 24-36 hours in advance, and do anything necessary to ensure I get sufficient sleep before any planned activity (workout/stay up late/sleep short amounts to induce sleepiness at the correct time to get a good, long sleep before engagements). I'm pretty independent of circadian rhythm now. As a side effect, as someone who used to consider themselves a night owl, I now prefer to wake up around sunrise whenever possible (assuming I'll be able to do it for a few days in a row)
I would recommend not to use the soundcloud logo for "uncloud your data" unless you have asked https://soundcloud.com wether it is ok :)
They also want to feel superior and special. That they've 'won'.
You are the one who has been entirely disingenuous... the previous post made a very good point which you have not contradicted.
I don’t know if Uber would be permitted to do that, I just know that in some cases it’s allowed. The term used is “concurrence déloyale” or “unfair competition”. In practice, if there was a dispute, the courts would decide if a part-time employee driving for another platform constitutes an act of “concurrence déloyale”.

In any case, I read in Le Monde this morning that this recent decision by France’s highest court may mean that Uber will just stop doing business in France (although it’s too soon to know for sure).

Here’s the link to the article in Le Monde for those who read French:

https://www.lemonde.fr/economie/article/2020/03/05/pour-la-c...

Edit: Punctuation. Also, the article is behind a paywall. Sorry about that, I didn’t notice, as I have a subscription.
The first table (image) in this post https://gathering.tweakers.net/forum/list_messages/1735517 shows this issue.

It's in Dutch, but the most important columns are the first (gross income), the second to last (net income, including benefits) and the last (effective tax rate on the 1000 gross income increase).

Note the last column tells us that making 1000 gross extra will increase your net income about 100 between 32K and 31K gross income. Going from 31K to 32K will even make you lose money.
I know that the evidence in this case is very clear, and that consistent, low prices didn't work. In fact I think there are a few instances of other people attempting similar strategies like Brandless. But Intuitively I feel like there must be a place for the consistent low prices model. Maybe intuition is just dead wrong in this case, or maybe we're just waiting for some visionary to turn up and everyone will be talking about how crazy it is no one managed to do that strategy before.
A friend tried this in the last week and was frustrated that there seemed to be no way to limit CPU/GPU use to only work relaed to Covid.

Is there a way to limit work to Covid?
This is important now more than ever as we are at the mercy of external factors in getting infected by corona virus.
Counterpoint: I used to "and I stopped reading" when I ran into grammar issues. I gradually realized that it's worth the effort to focus on the underlying ideas and evaluate that, rather than someone's 2nd language ability. People are smart, even when they talk funny, y'all.

(The worth/validity of the underlying ideas is a separate matter.)

Counterpoint 2: Automated grammar corrections are risky unless you're a native speaker. Ironic.
I interview open source maintainers at sourcesort.com, the interviews aren't usually highly technical but it depends on how they approach the questions.
ELI5 please. So billions of dollars spent on cancer research, and the solution this entire time, is to simply spike the IV drip with some lemon juice?
The article specifically calls out their radar being able to detect stationary objects, which is unique for automotive radar.
And the people that remember take notice of how google/apple are doing a lot worse in that space.
the new site for testing here: https://radiooooo.app
;)
Oh look, yet another Apache real time/batch/big data/stream processing/ingestion/workflow/whatever product.

Apache Druid
Apache Spark
Apache Storm
Apache Flink
Apache Beam
Apache Apex
Apache Airavata
Apache Samza
Apache TEZ
Apache Hama

It's basically a terrible joke at this point. There's no single Apache page helping you to decide which one you want, and they all seem to have such large overlap. Most of them seem to have bad documentation, and give the appearence of not really being maintained.

This puts me off even trying to use them. If there's this much scope creep/NIH/reinventing the wheel happening across the board, I can't imagine how bad each product is individually.

Apache Kafka seems to be the only exception.
Outline link for anyone who is not willing to fight with techcrunchs cookie monster.

https://outline.com/Lpu8GE
> [...] unit tests that demonstrate that it works

I'm going on a bit of a tangent here, but unit tests don't demonstrate that it works – acceptance tests demonstrate that it works. Unit tests help reduce the time to narrow down problems and in some cases help with refactoring (if refactoring is limited to the inside of methods).
They aren’t trying to sell their cars to the general public.
My takeaway from this is that more articles should include a 'this works in x situation, probably also works in y, but is not suitable for a, b, c' discussion. Applying the right techniques in the right places is an important part of engineering - some authors talk about it more than others and it's very useful.
Except for when you change from JIRA to some other project tracking tool. I think this is worth considering since project and people management trends tend to suffer from more churn than version control systems.

In my book, it's easier to auto-import sensible git logs into JIRA than trying to do the reverse. Then again, I'm of the opinion that git history matters, specifically for commit messages. Otherwise, you might as well create a pre-commit hook pointing to http://whatthecommit.com
I find the idea of legislating how businesses operate based on the idea that people aren't expected to have personal responsibility highly distasteful.
Permanent magnets don't do much to hard drives[0]. Well, with a strong enough magnet, it will, but the magnet will mechanically damagethe internals before they affect the actual data.

Anyways, it can't be a solenoid because solenoids are unidirectional. They actuate in one direction, and have a spring return in the other. The actuator in hard drives needs to be able to actuate in both directions, so they use a magnet for the coil to repel and/or attract.

https://www.kjmagnetics.com/blog.asp?p=hard-drive-destructio...
MLOps – Git is not enough, you need Time-Travel Query Support
The fact that one is checked statically and the other is only enforced at runtime is a significant different between them, since the static approach will reject some programs that are dynamically safe. The term duck typing when employed by dynamic languages like Ruby is misleading since it's a consequence of not having a type system at all.
I'd rather say that the solution is constantly contested by people who can't shake off their intuition.
This picture show the benefit cliffs in a very clear way: https://sacredcowchips.files.wordpress.com/2015/08/welfare-c...

Most important part of that picture: "The single mom is better off earning gross income of $29,000 with $57,327 in net income & benefits than to earn gross income of $69,000 with net income & benefits of $57,045."
Because if you are not contracted to work a certain number of hours per week, you don't have a "regular paycheck"?
This is cool.
Just super super cool
Wow!
It's not just good for developers. Coordinating any plans across timezones always requires the timezone to be explicit, one universal timezone doesn't. It wouldn't be hard at all for people to get accustomed to the numbers associated with their local daylight cycle, and travellers can use a phone or website to lookup sunrise/sunset in any location, as is already possible.

Maybe we could even eliminate hours and minutes and just use percents and thousandths of a percent of a day (14.4 minutes and 864 ms respectively), to avoid factors of 60 or 24 or 3600 or 1440.
Dirty streaming: The internet's big secret
There is a lot to not like about the current state of the legal industry besides "poor tooling".
I run Linux on a ThinkPad P51: powerful hardware, good 4K screen, excellent keyboard, all the ports. Not small. You could also just put Linux on a Mac, alright you'd be paying the Mac premium for sort of not a Mac, and you'd be stuck in dongle land.
use this new adress: https://radiooooo.app
it fix a lot of bugs !
> 99.99% of the code snippets in that realm work great with 64b floating point, without the author having invested any thought at all into "numerical analysis"

In the accident that they "work great" (really, great?) it's only because:

- The code depends on properties of IEEE FP which were designed exactly so that it's harder for a casual user to shoot himself in the foot -- ant these properties were intentionally designed for IEEE FP by the people who DID invest a lot in "numerical analysis" and the practical consequences of potential bad decisions.

- The code depends on libraries that were designed with much more effort than the author of the above statement can imagine.

In short, yes, we do need all features of IEEE FP. And to produce anything non-trivial one should indeed learn more about all that, and care.

> Summary: use SSE2 or SSE, and if you can't, configure the FP CSR to use 64b intermediates and avoid 32b floats. Even the latter solution works passably in practice, as long as everybody is aware of it.

That was, and I guess it hasn't changed, the default with Microsoft's compilers on Windows for decades already, and probably sensible default for non-Microsoft scenarios, especially needed for the "consistency" across the compilers, which matches the title of the article. Oh, and make sure that the compiler doesn't do any optimization that produces unstable results.

That's about the "production" default. However, I still believe that during the development of anything non-trivial the evaluation of the results using different numbers of bits is worth doing.
The logo is the last thing you will be talking about when you see the new BMW grill design.
He should've gone to jail, like people are supposed to when they commit fraud.
> They got rid of their loyal, long-serving, housekeeper instead of caring that she's sick/supporting her through it.

From their point of view, she hid her very contagious and dangerous sickness from them and knowingly endangered them and their children with tuberculosis just to keep her job. What kind of loyalty is that?

> They "forced" their helpers to show up on Sunday.

I watched the movie in September, so I must admit, I don't remember that part really well, but then you're quote the phrase...

> "You're getting paid extra for this!".

...which means, they're paid overtime - so, while outright forcing someone to come out on a weekend is a bad thing to do, it's not even unpaid overtime (which is so common, unfortunately). And it's certainly not even in the same league as literal murder.

> On the topic of work ethic, I didn't really see the rich dad ... working hard

I think it's obvious he's not in the position where he has to work hard - it's working smart that counts.

> the mom doesn't even work!

That's dad's decision - he earned his money, and he decided (for better or for worse) that he wants to provide for his wife. Many (me included) would not take this decision even if we had the resources, but everyone has the freedom to do whatever with the money they earned.

> Just like many of us in this forum, the dad probably got lucky to end up in a high-paying position, luck doesn't mean work ethic!

I can't judge you personally, but I've seen many other talented software engineers and other tech workers come to the same conclusions after they've been in the bubble too long. They got accustomed to level of intelligence and abstract thinking of their social group and naturally assume that all the other people are basically the same. I don't think that they realize what the "outer world" and people who inhabit it are really like. (I grew up pretty poor in not a particuarly elite neighbourhood of Moscow during a decade-long economic and system crysis, and my opinion of the "proletariat" is based on a very intimate first-hand experience).

> You're probably a believer in the meritocracy

No, not quite - I'm not a believer in any kind of system or a systematic truth about this, not the meritoracy, nor the opposite.
Ampere Altra is the First 80-core ARM-based Server Processor
> no one is reading the commit log line by line, there are 100 commits per day.

I hardly ever refer to the commit log. However, I do often run `git blame` to figure out what changes were done to the code base together with a specific modification to a specific line of code. That works so much better if people have actually spent some effort to make sure related work is in a single commit.

(Note that this doesn't mean "squash every PR together" - it means rebasing before submitting a PR to make sure the commits also work as documentation. The result of that rebase might very well be several commits.)
Show HN: HiddenVM – Use any desktop OS without leaving a trace
So far the best I have seen is https://thisstartupdoesnotexist.com/
Full-disclosure: I co-founded a company that's building a developer tool for K8s (and distributed systems in general).

But we've had a lot of success with running on GKE. The tool that we're making takes away the complexity of building, testing and deploying the stack, and GKE takes care of running it.

In fact we use GKE for both our development and staging/prod environments.

There are a lot of great tools out there that vastly improve the K8s developer experience[1] and the cloud providers take away of the pain of operating it. And with tools like Terraform and Pulumi you can codify the whole setup.

Here's an example of how you can quite easily get started on GKE: https://medium.com/garden-io/gke-and-cloud-sql-a-complete-wo...

Here's a video of the same workflow: https://www.youtube.com/watch?v=iHyeD97GrE4.

[1]

https://github.com/GoogleContainerTools/skaffold

https://github.com/garden-io/garden

https://github.com/windmilleng/tilt
> These kinds of posts always focus on the complexity of running k8s...

Yes but that is also the worst already that you could criticize about k8s.

Complexity is dangerous because if things are growing beyond a certain threshold X you will have side effects that nobody can predict, a very steep learning curve and therefor many people screwing up something in their (first) setups as well as maintainability nightmares.

Probably some day someone will prove me wrong but right now one of my biggest goals to improve security, reliability and people being able to contribute is reducing complexity.

After all this is what many of us do when they refactor systems.

I am sticking with the UNIX philosophy at this point and in the foreseeable future I will not have a big dev-team at my disposal as companies like Alphabet have to maintain and safe-guard all of this complexity.
Their wiki page lists a handful of them: https://en.wikipedia.org/wiki/Folding%40home#Examples_of_app...

Do keep in mind that 1. very few drug candidates make it through drug trials (iirc it's something around 1 in 1000), and 2. these trials takes 10+ years, and FAH has been around for only 19 years. It's very likely that a bunch of its results are in trial right now, and we'd only hear about it 10-20 years in the future
you are a genius, you should start girlfriend coach or somthing like that.
Careful there. You’re about to be called a shill, and downvoted, or labeled an apologist, for writing anything positive or supportive, about China’s handling of the crisis. It appears HN has become just the same as the braindead Reddit crowd, since most people visit both sites.
This.

Git is a glorious tool, but such tremendous power implies a lot of complexity and a lot of different ways that you can work with it. You can have 10 engineers and find they have 10 different opinions and everything ends in ego fightings. The best way is to have an owner of this, make the team understand the governance issues being resolved with the flow and disagree and commit (pun intended ;)
> apparently, this technique works quite well for "customer retention"--you feel "safe", for everything that is presented to you is cosy, cartoonish, kid-oriented staff

It has the opposite effect on me. I feel like I'm being patronised. Maybe it's generational (I'm old).
Exactly, all these articles seem to come from operational novices, who think in terms of 1-2 click solutions. K8s is not a 1-2 click solution, and clearly isn't designed to be; it's solving particular tough operational problems that if you don't know exist in the first place you won't really be able to evaluate these kinds of things properly.

If a group literally doesn't have the need to answer questions like the ones you posed, then OK, don't bother with these tools. But that's all that needs to be said - no need for a new article every week on it.
I dont think author claims bright colors are infantile on themselves. She is claiming that bright colors are used to distract from complexity. That word is always used in conjunction with other words like "patronizing you while hiding it in bright, friendly colours and the technique of infantilization". The bad stuff there is "patronizing" and "infantilization" bright colors just help to hide that.
It would be nice to upscale by auto-redrawing with a simulated brush and paint.
As a passable but not amazing swimmer I tried to swim not too far from an anchored boat to the beach while carrying my 1.5 year-old, and it was fine for the first 30–50 meters until he freaked out and started flailing his limbs in a way that made it really hard for me to keep his head above water while also keeping us both afloat and moving forward.

Thankfully some other people were also going from boat to shore with us, on a raft, and were close enough that I could shout at them to come pick us up.

I don’t plan on ever trying that again!