skysight-inc/HackerNews huggingface dataset:
> I think what you describe is the shortcoming of the initial grpc spec. It was for some reason decided to define it on top of features which are barely implemented outside of HTTP/2 and special libraries (especially: Trailers). But it would have been possible to just define things on top of common HTTP semantics. This is what grpc-web now fixes according to my understanding.

This is also my understanding (minus the Trailers bit) -- there's stuff like grpc-gateway[0] that I've considered using before so I know there's a mapping (whether it's easy to use is another thing) from grpc to HTTP/1.1 ...

> I think even streaming should have been possible with HTTP/1.1. Bodies can be streamed there just fine, if libraries support it (for browsers the issue was up to now that the APIs don't support access to bodies as streams). The only thing I'm not sure if there is an issue in HTTP/1.1 with request streams still running while the response stream has already finished.

For streaming I was thinking mostly of the duplex streams, i.e. what Websockets brought to the table, everything else would be pretty hacky. I suspect that grpc translates to regular browser-ready HTTP/1.1 REST pretty easily (outside of trying to decide how), minus the streaming bit, since you'd have to do some sort of comet/long polling/sse/websockets approach.

[0]: https://github.com/grpc-ecosystem/grpc-gateway
It is still practical in some cases, like moving the world border at will.
> The transition to python 3 is more more a matter about a migration execution rather than a technical aspect related to strings (which I don’t find that terrible, especially given all facilities provided to make the migration easier to the new incompatible runtime).

That's political talk. In practice I never have seen a python library that do not blow up when migrated in Python 3 with a Unicode related error, because one of the dev was using python2 string as binary vector.
Wow that’s looks pretty cool!
I recently created this full-stack project generator, based on previous ones I had: https://github.com/tiangolo/full-stack-fastapi-couchbase

FastAPI as the Python backend.
Couchbase as the database.
Vue.js with TypeScript, Vuex, etc. as the frontend.
Celery for asynchronous jobs.
All managed with Docker (including frontend compilation from source).
All integrated with Traefik, so, automatic HTTPS.

Up to a month ago, I used my previous project generators based on Flask and several plugins, but now I'm doing all the backends with FastAPI as it's about 3 times faster to develop, and about 5 times or so faster (better performance).
You just gave me another reason to like Stripe.
Remember that Homebrew by default records some of your usage data via Google Analytics. Disable that if you are not comfortable, or switch to MacPorts.
I'll agree that non-Americans will probably not have the most accurate picture of the US, but saying that it's a common idea that they have to dodge bullets from shooters once a month sounds like you also have a bad idea about the life of non-Americans.
Is studying for a MCSD certification worth it?
Pupil Invisible: eye tracking glasses powered by deep learning
In French, there is a space before exclamation and question marks. Based on the author's name, I'd also guess that they are French.
Maybe that's your life, just soldier on no matter what life throws at you, but in my life, it's ok to feel sad about sad things since that's how humans deal with them.
This is a fair question, I would advise not listening to anybody who says they have a "one size solution" for all data.

For searchable structured data, I'd probably go with elasticsearch. It scales very well and you can turn off indexing and use it as a document store.

I am a huge fan of postgresql and the more I use it the more awesome I find it, so I'd probably use postgresql's JSONB column type for unstructured data if that's a requirement. You can pair it with citus and make it scale quite well.

For pure document storing there's RethinkDB which performs well and does not lose your data as MongoDB does.
Systemd cve in journald – local privilege escalation
I wasn't really laughing at you, more so at your way of explaining those people you interacted with. You just had some funny prose -- which is hardly a bad thing.

So you'll scrape lots of web data, run it through your 'meaning algorithm' and then provide a search bar to search said data? So, like your idea is like Google, but it understands english sentences close to like a human would? Did I understand that correctly?
Reminds me of Gigapixels of Andromeda [4K]: https://www.youtube.com/watch?v=udAL48P5NJU (listening with sound is a plus).
Now imagine there are at least as many galaxies as dots of stars in these images from Hubble...
Microsoft is big and the contacts I have there tell me that the open source policies vary by department.
For phone calls, good old call redirect is still a thing :P

No idea about whatsapp though.
I've seen this often claimed, and buy it in the long run based on experiences I've heard from employees that work at these kind of companies, but I also feel like there's missing context and subconscious assumptions by writers who claim this.

There is an alternative to both informal and formal power structures. It's "everybody does what they think best". Who approves new product launches? Nobody does, you just push code to the live site. Who handles time-off requests? What, you thought you'd get time off? Who handles resource allocation? Everybody basically has control of their own time and nothing else. If you're lucky you might actually be able to get rough consensus, but basically totally anarchy reigns.

Most people would say, correctly, that this is a disaster in the making. Think of the product chaos as each new feature breaks the last one! The burnout! The privacy violations in the making! The employees that are sleeping with one another! The laws that are being broken! And all of these happen, and they actually are real problems that can potentially sink the company. But hypergrowth (temporarily) solves all known problems - if people are really desperate for your product, they'll put up with anything that is borderline functional, and if you hire smart people who are passionate about the problem you're solving, most of your employees will be capable of putting out something borderline functional on their own volition.

It's probably no accident that the companies that have experimented with flat hierarchies - Google in 2001, GitHub ~2010, Zappos in 2013 - are ones that were undergoing hypergrowth at the time. Many of them rolled it back after the eventual problems became apparent, but it may actually have been appropriate for circumstances at the time.
I think this (a bit long) 1970 read should be mandatory for anyone who wants to abolish hierarchies and make an organization that works "differently":

THE TYRANNY of STRUCTURELESSNESS : https://www.jofreeman.com/joreen/tyranny.htm

tl;dr: in the 70s feminist groups started organizing but they did not want to reproduce typical hierarchical structures. So many opted for "structurlessness" which led to implicit structures that the author claim were at least as oppressive as explicit ones.

It is possible to have an enjoyable flat organization and oppressive hierarchies are avoidable. But if you want to have a different kind of hierarchy, understand the organizational needs of your group, the balance of inherent powers within it, and create a hierarchy designed by taking all this into account, because otherwise these things will organize spontaneously anyway.
I hope you are trolling.
Im not homeless and I wouldn't be able to use it.
Ask HN: Which tool have changed your life recently?
Any app, tool, service, product that has changed your life recently.
For what it's worth when it comes to choosing a hosted ElasticSearch provider I would go to Elastic over AWS Elasticsearch Service.
Non-Exercise Activity Thermogenesis can account for hundreds of cal a day from what I remember.
No demo? And the pricing is insane.
I don't even wonder.

It's not just Open Source who will get nasty signs from amazon. They already have too much power for one company and the more power they'll have the less they have to abide by rules normal companies/humans have to abide by.
Seriously. This is like when 2048 was posted on HN.
I sincerely wrote that to make the PP author to reflect to his situation, but of course read it as you prefer
Fructose is literally poison. Also not being more harmful than sugar is not much of a compliment, there are very few things that brought more harm to humans than sugar.
Links? Please.

Thanks!
> not answering a simple yes or no question

Here you go:

> Do you have published security reviews of your infrastructure?

Beyond https://hackerone.com/homebrew/hacktivity, https://brew.sh/2018/08/05/security-incident-disclosure/: no.

> Otherwise you're asking us to just trust you.

Yes.

> it's not clear who has access to it

A subset of the documented Homebrew maintainers who manage our ops/infrastructure.

> such as who reviews the commits

The maintainers and additional trusted users.

> the precautions taken by bintray to prevent and detect tampering with packages

packages require a manual publishing step, are checksummed and frozen on their CDN a while after publishing.

> most formula pull requests need to be reviewer but does not go over what this entails

This is part of the on boarding and training of new maintainers.

> Is there a set of maintainers who handle security sensitive formula, like openssl, gnupg, and tor?

Not a specific set but they receive extra time, review and attention to their source URLs.

---

I expect some of that will not be good enough for you in which case: please either get involved to help us make it better (we are unpaid volunteers) or use another tool. This is how open source works.
Personal Finance Lessons for Technology Professionals
SEEKING WORK - Russia, REMOTE

I’m specialized in development and management of large complex web-based projects (on LAMP(PHP)/Yii/Symfony/React stack) with a size of several hundreds functional components. This experience includes active work with large poorly documented code bases created by other developers. Other half of my background consists of self-financed self-studies in social sciences, biology, and arts.

My CV: http://kamil-rafik.com/docs/Kamil_Rafikov__2019.pdf

Email: mailbox@kamil-rafik.com

Skype: kamil.rafikov
> It seems it would be quite easy to slip in an attack via brew.

You can put your money where your mouth is and consider submitting one to our HackerOne. Otherwise: perhaps it's not "quite easy" after all.
Fins approval.
Just use `from os import nil` and you'll be only able to use that module with "os" prefix.
Location: Russia

Remote: yes

Willing to relocate: to be discussed (flexible hours and really great office are required in such case)

Technologies: I’m specialized in development and management of large complex web-based projects (on LAMP(PHP)/Yii/Symfony/React stack) with a size of several hundreds functional components. This experience includes active work with large poorly documented code bases created by other developers. Other half of my background consists of self-financed self-studies in social sciences, biology, and arts.

Resume/CV: http://kamil-rafik.com/docs/Kamil_Rafikov__2019.pdf

Email: mailbox@kamil-rafik.com
May be the permission should be flipped - the company has to ask the employee for approval to stop the opensource project.

It would work by having the employee list their projects, and the company will, when they find a conflict or some shared interest, ask for the employee to volunteer to stop their project. The employee can refuse, but typically won't.
Thanks for the kind words.

For what it's worth, I really do value this stuff which is why we have release notes at all, a Discourse forum, etc. most of which I've setup and run :)
They're basically killing a company behind an open-source project.
Thanks for the kind words.

> Hopefully these changes will allow you more time to focus on adding value to the vast majority of users. If a small subset of folks need the marginal functionality, it should be up to them to step up to the plate and make it happen.

100% agree.
> A systemically unreliable database would never be popular

1. Correctness and popularity are different

2. Not everyone looks for correctness, even when looking for a database. See: MySQL.

> as its not a piece of your architecture that you can tolerate having constant outages with

Reliability and correctness are not binary scales of 'works' vs. 'does not work'. Again, see MySQL.

> there is no evidence of MongoDB being systemically unreliable

There is plenty of evidence of MongoDB losing writes because of its (honestly) stupid design: writing to memory maps instead of files, never fsyncing, sharding and distributing without confirming disk flush.

---

MySQL: For a long time, one needed to be aware of certain caveats and corners and limitations of MySQL or be surprised with data inconsistency and loss. That is not to say that MySQL could not be operated reliably; it could, just that the barrier was higher than it appeared.

From truncating data (with a warning) to not accepting and silently (i.e., without warnings) ignoring CHECK constraints, I've had clients who lost business data and realized it only too late to go back to the original data source.

I used to think MySQL was an bad database due to its concessions of correctness and poor documentation, until MongoDB came along with their lofty marketing and high-and-mighty "Nobody needs SQL anymore, we are Web-scale" blare-horn and failed to deliver on even keeping the data it claimed to have saved.
KADE NA BOLU – Latest Haryanvi Songs Haryanavi 2019
It's really shadowing. The type can change and it isn't declared mutable.
I used Overleaf for my PhD thesis without any issues, including a lot of figures, etc. In fact, I almost only use Overleaf when it comes to LaTeX - it takes care of most of the pain points and is a great service that I pay for.
Easily. Which focal length/field of view lens is on that camera?
I just saw that well written comment and was thinking it's a crazy thing - that an astronomer at a large gathering of astronomers, surrounded by so many interesting people, discussing so many interesting things, takes a timeout to go and post an elaborate comment on reddit.

What is that crazy need we have to put in work, for no great gain, to keep utterly random people around the world updated in real time of whatever is going on?

These days, I seem to stop myself reading the news article , just head over to the right forum, and look for such comments. It's like the news industry has become more or less irrelevant, other than in surfacing a list of headlines, which then seed my "find best comment" search algorithm.
Data Analytics and Financial Planning
Review scores of it's an app is one way.
I guess, stuff that is getting automated, should become a part of the education curriculum. That way, the hire will have the relevant know how, and start doing useful work on joining.
I am really excited by this.

Now google just need to add support for this in their smart lock app...
I used to run a Microsoft Exchange Server for my family, just switched to Mailcow-Dockerized, which is really awesome.

https://mailcow.email/
Same here in Europe (France), there is a dramatic increase in the consumption of Starbucks like sugary drinks in the recent years. And yes plus a whole range of "healthy" fruit/soy juices which are full of sugar.
Leisa Reichelt – Opening Keynote – Operating in Context
Why Scaling Agile Doesn't Work • Jez Humble
A lot of people are focusing on the bitchiness, but to me this is actually interesting from the perspective of (F)OSS evolution.

This scenario is one of the many where (F)OSS explicitly protects downstream users: company reduces availability, user forks. It just so happens that the traditional players (the small, indie user va the big, bad corp) are actually mirrored (big, bad user vs small, indie corp). This has been the ugly reality of OSS for more than a decade now, and there seems to be no way to align the interests of “big users” more closely with upstream. Before the switch last year, MongoDB already used the most “aggressively collectivist” license available, and still it didn’t protect them from rich freeloaders.

This is also the other side of the coin in the Google vs Oracle debate about apis and copyright.
Seems more to me that people are realizing how replaceable their jobs are and that many are dead end career paths. If they look into the future a bit, what will they really have from working there? Is the experience of a job that is going to disappear in 15 years worth anything? Is it going to provide an appreciable amount of income that can be put towards retirement investments? Why would you choose a path that has the high potential of you still being poor 10 years later, especially during the prime of your life? Some might see the potential for better opportunities arising if they are patient and are ready to jump at just the right moment.
Yeah, it's pretty restrictive for FP people, but I think that's fine. I think it's easier for FP people to deal with that amount of restriction, than it is for the average JS developer to quickly understand how to wield as much power as e.g. PureScript gives you.

Also a little surprised you mentioned do notation; it's just syntax sugar after all :)
In order from most realistic to pipe dream: Meetings don't happen without agendas and needing input from everyone. Hard problems where half-baked solutions genuinely can't work for the business (this is why I gravitated to ads and payments). If I conduct interviews, attract a good portion of strong candidates I'll be excited to work with, and filter out the ones who can't code at all. Don't put me on call for stuff I didn't write with no runbook (corollary: get runbooks written before the whole team moves on). Windows of undisturbed time for deep work. Support DSL design; don't limit me to blub languages and libraries that the median candidate can handle. Let me ramp up on formal methods and start using them.
By that argument google's index of data isn't the user's data it's google's but the right to be forgotten is specifically about deleting other people's copies of data about a person.

In particular the NYTimes reports on Joe Baddy doing something bad. That article arguably belongs to the NYTimes. Google indexes that article with permission from NYTimes. Right to be forgotten requires Google remove the link to NYTimes even though neither Google's index nor the article at NYTimes belong to user.
The insider perspective on the event-stream compromise
It's very unlikely to be. The Fairphone is one of the only phones making an effort, and it's a lot of work [1] and even then they're still long ways of from being actually fair. I can't imagine Purism to have the time to invest in this, nor to do that without even so much as mentioning it.

[1] https://www.fairphone.com/en/blog/
> poor general performance

By poor performance, I assume you mean IO? AWS Elasticsearch has supported i3 instance type (nvme on-instance storage) for well over a year now [0]. Additionally, you could enable slow-logs to catch perf issues yourself [1]

> very slow to make cluster changes

Scale-out and access-policy changes happen in-place now and so happen much faster than they used to be.

> launch new clusters

In my experience, it depends on the cluster size, but usually, I see cluster being up in 20m. That's nice given that it sets up pretty much everything (spin up instances, apply access policies, run health checks, enable cloudwatch monitoring, snapshots, create route53 records, integrate with cognito, enc-at-rest via KMS, spin up load balancers, setup vpc resources etc) on my behalf.

[0] https://docs.aws.amazon.com/elasticsearch-service/latest/dev...

[1] https://aws.amazon.com/blogs/database/analyzing-amazon-elast...
Their published code (https://github.com/awni/ecg/tree/master/ecg) uses Keras. It's a pity they didn't cite it though.
I got it, but if you're hunting to feed, you don't harm and let it there.
Not in East Europe it is not.
Hehe. I started learning Prolog a few weeks ago - not sure why. Maybe after seeing one more story about it on here, and seeing it on lists of languages that're good to learn. But didn't know anything much at all....

What a surprise. I really like it. It's really sooo different from any other language I've tried (C, C++, Python, JS, SmallTalk, Lisp, bash, AWK etc etc) - Most programming consists of telling the computer how to go about doing something. None of that in Prolog. You 'just' describe how the solution will look.[0] And secondly, it's unexpectedly Functional - it's impossible to change variable values, or iterate.[1] Recursion only. 'Data' is same form as 'program', the program can change the data/program while running etc. And even Lispier than Lisp in some ways.

I think I'll be regularly using it in an AWK-like way - and already have been - quickly writing programs of a couple of dozen lines or less to do things that would take longer to do otherwise. And there's something cute about it that AWK has too, maybe it's that it does well in its own unique world. Just starting that book on how Erlang was 'grown' using Prolog...

I don't know why I wrote this. Prolog was just surprisingly FPish, and if I hadn't learnt about that stuff, I wouldn't have recognized it, or appreciated it.

[0] Really, you need a new vocabulary to describe what it's doing. [1] Ok, not impossible.
Long time ago I played around with gimp+mathmap[1]. For some reason I needed the second derivative of a Perlin noise layer and I kind of surprised when the underlying grid structure revealed itself. I didn't know anything about the Perlin noise algorithm at the time. AFAIK there are variations of the algorithm that are continuous in the Nth derivative (for various values of N). Maybe the article's implementation is continuous in the 2nd derivative.

[1] https://www.complang.tuwien.ac.at/schani/mathmap/
To emphasise, I think this is far less work than it would be to actually get UBPorts to a point where you could reasonably ship it on your device to match customer expectations.
Elm is fascinating since it shows that with the right architecture functional programming for GUI is possible without hatches like monads or hiding state in closures or green thread stacks.

Another things is that in Elm the state of the whole application is very visible. Typically just by looking at data structures and message types one gets how things work. The code just fills details.
> An HTTP/JSON protocol doesn't have to replace the standard one.

So, two protocols? Two standard protocols is rarely better than one.

> having such a standard protocol makes sense in the age of web apps

Only if the existing standard protocol cannot work with the "web", and we have plenty of history proving otherwise. Replacing the existing standard with the loose JSON would be, strictly, a downgrade; and unnecessary, because we already do interoperate JSON and SQL. See: PostgREST and the many REST & GraphQL frontends on PostgreSQL.

> particularly when NoSQL offerings that are perceived by the market as competitors (leaving aside whether they really are - perception matters more here) do that already

This is really more of going into a pig's pen and wrestling with them. A database should do the job of a database. Competing for perception in a market that cannot make sane decisions for itself is how we get MongoDB.
Both projects are funded simultaneously as part of the same grant. If it is worth doing once, it is worth replicating. Vice versa: If it isn't worth funding the replication then the project isn't worth doing.
it's not entertainment, it's about not overpowering, I used bow as an example, maybe it's still too strong (you can kill from afar) but compared to a gun, at least it requires skills to actually kill. Anybody can pull a trigger.