skysight-inc/HackerNews huggingface dataset:
In my experience they mostly don't get maintenance; they're just built extremely cheaply and treated as disposable. Various parts that are easy to break (derailleurs) are elided by using Internally-Geared Hubs (IGH). The wheels are non-pneumatic and just a solid piece of rubber, so they never go flat.
Committing to it could be done within the NASA budget. This currently is not even the majority of the NASA budget. Its only bit more then half of the human budget.

So the argument that 'you can only do this when the government gives NASA military budget' is just nonsense.
The scary part about the EARN IT act is that I've written both my congressman and my senator (both Democrats), and they're completely on board with the "Think of the children!" bullshit justification for this. I really expected better out of Mark Warner.
Show HN: Byteconf React, free remote React conf streaming on YouTube [video]
There was a point where it seemed like Apple was going to throw its support behind eGPUs. Unfortunately it looks like they kinda half-assed it (new OS releases don't even work with modern Nvidia GPUs because Apple won't let them update the drivers)
That's depend your threat model, isn't it? All Android phones rely on black box baseband blobs from the hardware manufacturers. If there is an exploit hidden there, I believe they won't use it just for blanket data collection like this, but only use it for targeted attacks on high value targets (politicians, journalists, magacorp execs, etc). Hopefully they won't bother to use that kind of low level exploits on normal plebs like me. I'm not even sure if iPhones are safe enough when your threat model requires trusting the low level hardware. The only way to avoid it is by using a phone with fully trusted stacks like pine phone or librem 5.
What if it's the chain that's broken or a wheel is not straight or a brake cable needs replacing or the bike spent a few years in a cellar and it's not clear to the owner if it's roadworthy or not?

Almost everyone has a bike but they are convenience vehicle, not everyone is a hobbyist or has the proper tools to repair it outside of patching inner tubes.
Should have gone with Queery
Forced anything will polarize opinions. It largely depends on personalities and how you have your personal life arranged. After over a month of WFH I can't wait until this thing is over.

Personally I feel best when both are the option but the office set in a way that it does not drive people out.
Product Management Career Ladder Archive
sweetgreen (https://www.sweetgreen.com) | Culver City, CA or Irvine, CA | Full Time | https://grnh.se/e2e8c5091

At sweetgreen our business evolves every day as do the solutions we invent to meet those emerging needs. We believe that it’s a mix of individual skill and collaboration that leads to successful outcomes. There is no standard definition of what an Engineer is or does, and depending on where you’re coming from things might look a little different.

We’re technology agnostic, but we have a propensity to leverage lean tools that are best suited to get the job done. Our most popular choices are Node and Ruby, and are often deployed to either a severless or container orchestrated platform. Our frontend clients leverage a variety of frameworks, including React. We try not to over index on the latest tech and to instead focus on the tools that allow for the greatest development experience, quality of work, and productivity.

We value, encourage, and support diversity in backgrounds and opinions. We are human, fallible, life-long learners - we make mistakes from which we learn and grow. We partner with Product, Design, Data, IT, Operations, and Business stakeholders in long-term ownership of the solutions we build to improve the lives of our customers.

Our mission within Engineering is to create, operate, and continually improve upon software critical to the overall sweetgreen mission. We provide technical expertise, guidance, and vision to our partners and stakeholders in order to inform sustainable thinking across sweetgreen.

Our sincere vision is to be a world-class engineering organization leading the food experience revolution.

Jobs:

https://grnh.se/e2e8c5091

- Enterprise Data Warehouse Architect (Culver City, CA)

- Lead Engineer/Architect - Full Stack (Customer Relationship Platform) (Culver City, CA)

- Lead Software Engineer, Full Stack - Store + Operations (Orange County, CA)

- Senior Engineer - Full Stack (Customer Relationship Platform) (Culver City, CA)

- Senior QA Engineer (Culver City, CA)

- Senior Software Engineer - Store + Operations (Orange County, CA)

- Software Engineer, Full Stack (OC) (Irvine, CA)
> there is no way to tell dgraph what the UID should be.

There is. You can lease UIDs from Zero, and do your own assignment. Look at /assign endpoint [1]

> doing an XID->UID lookup in order to create edges.

Also, you can use upserts to do an XID lookup, before creating a new node. Which is practically what other DBs do too.

> there is a bulk loader but that's only available in HA mode

Don't know what that means. Bulk Loader is a single process (not distributed), and can be used to bootstrap a Dgraph cluster. The cluster can be a 2-node cluster, or an HA cluster, that doesn't matter.

> where even smallish batches of 100 hit some unspecified gRPC limit

Never heard of that. Grpc does have a 4GB per message limit. But, I doubt you'd hit that with 100 records.

[1]: https://dgraph.io/docs/deploy/#more-about-dgraph-zero
It does, thank you for the in-depth response! I'll refer to this comment if I ever see that post brought up again.
SEEKING FREELANCER, NYC, Remote

We are a small NYC based publishing company running a custom CMS. We are looking for help migrating Wordpress sites to our CMS.

We're full stack Javascript (Node API, React CMS, static articles). You must be comfortable with Node. Familiarity with Wordpress is a plus.

The Wordpress migration is the most pressing task, but if we find the right person we have plenty of work in the months to come.

Please reach out to john at distractify.com if that sounds interesting to you.
Because we don't/can't do perfect lock-downs -- everyone literally stays home for two-to-six weeks and doesn't move from their home -- you can really think of lock-downs as doing two things.

1. It effectively reduces your population.

Not everyone can stay home, because we still have stuff that has to get done, but say 80-90% of your population can stay home, because they're retired or they have a white collar job that allows them to work from home or because they're children and school is closed or because they've been fired because no one is buying what their job is selling.

This means that instead of 85% of your population needing to catch the disease for it to burn itself out, you're only waiting for it to go through 85% of 10% of your population before it burns itself out. (Unfortunately, because that 10% includes the people who take care of the 0.5% of the population that is most vulnerable, this still kind of sucks for that 0.5%, and you're really waiting for it to go through like 10.5% of your population.)

You'll still see increasing deaths during a lock-down until all of the grocery store workers and doctors and firefighters who are still pretty exposed out in the world catch it and some of them die. This also sucks and is kind of unfair, especially since some of the jobs which are pretty essential weren't particularly great before the pandemic.

2. It effectively reduces the R0 of the disease even among the essential personnel.

The R0 of a disease (last estimated at 5.7 for the coronavirus) is not constant, but depends on the conditions it is spreading in. Even among the essential personnel still out there risking exposure, the R0 is lower with everything shut down than it would be without the lock down, because the lock down still reduces the number of people each essential worker comes into contact with on a given day. Dropping off packages at a hundred doors a day puts you in marginal contact with a lot of people, but it's still less than if you did that and then went out to a bar and a restaurant and a movie afterwards.

Suppose the lock down is dropping the R0 among the active population from 5.7 to 2; that's still not great, but that means that instead of 85% of the 10% of the population still out in the world catching the disease, only 50% of the 10% will be expected to catch it. This is more awesome and less unfair, and also protects the vulnerable populations that come into contact with the essential workforce.

So our imperfect lock downs don't stop the disease cold in its tracks, but it does probably reduce the number of people we expect to catch it from 85% of the population to -- if we're lucky -- 5% of the population.
Coronavirus has destroyed the myth of the deficit
A Linked Hashmap in Solidity
I'd love to see the general magic / next family tree and companies that were built from the teams.
>We don't need to excise all humor from our discussions on HN.

This isn't really relevant here, unless you are trying to create a strawman or frame this as a false dilemma of extremes. You can have a sense of humor while also keeping the conversation substantive.

[Edit: Assuming solar is correct: ]

Comments like the above are cancer when they inspire more of the same, and not long ago would have been appropriately dis-incentivized by the community.

[And if solar turns out to be wrong, then replying in earnest is still a good response.]
Once a year is plenty unless you're having unexpected failures or a poor experience. If you're riding enough to go through parts faster than that, you'd know it.
You should also consider open sourcing your cloud service in the event of shutdown. A repo with a Dockerfile should be sufficient, that could be turned into Digital Ocean droplet configs and similar one-click launches.
It holds a special place in my heart as well. In 2002, my parents gave me a book "Multitool Linux" [1] which wasn't a spectacularly well received one, containing a mix of wildly different topics, but this was exactly what I needed as a teen experimenting with Linux for the first time. One of the chapters was about POV-Ray, and I remember being amazed with this newly-discovered canvas. I spend hours looking at images others had created and wondering how they'd pulled it off. I think I never got much further than rendering small animations on my (if I recall correctly) 400Mhz pc. Good times.

(As an aside, I'd completely forgotten the title of the book, although vaguely remembering the cover and time frame. It's so hard to find older stuff using Google when only having some vague descriptions. I found it by remembering that I read a book review years later and after some digging around could locate the review back to https://www.linux.com/news/book-review-multitool-linux/ based on the style of writing, which I remembered. I must have read that book to pieces. The chapter using Wireshark was also amazing to me.)

[1] https://books.google.be/books?id=g0CPF6MEFcUC&printsec=front...
hey all! byteconf is a two-day remote React conference streaming for free on youtube. ton of great speakers – kent c. dodds, ali spittel, shawn wang, and many others. we're about halfway through day one and the reception so far has been awesome. tune in!
Yeah I probably should have lead with that.
I suspect that only going ARM on a few models could be detrimental. The risk is creating a niche within a niche. If they move everything, as with previous arch moves, it's "do or die" for third-parties.

But if, eg, MacBook Air turns into MacBook ARM but MacBook Pro remains Intel - this would be a very difficult schism. Many publishers might look at it as being pro customers staying on Intel and cost-sensitive customers on ARM, which could damage adoption.

The risk is having no carrot and no stick - not entirely dissimilar to Itanium's problem.
The beautiful thing about trading is that you're either right or you're wrong. It's unforgiving in a way that punditry isn't. When you trade you have skin in the game, since past failures leave a permanent record on your portfolio, and people quickly learn that overconfidence is a liability.
Yes. You have to pay for insurance.

And in terms of performance, you could have totally hedged out a portfolio for under 50bps (often well under) pretty much all the way through this market.

Universa did this but in a more sophisticated way...afaik, they created a portfolio where you got paid to hedge.

If this isn't clear: this is the kind of thing that people look back on and can't believe that it occurred. This is CLO manager in 2005 stuff. Literally incomprehensible. All because people cannot resist strategies that show small gains consistently. Retail investors cannot and won't ever understand that you will underperform, that is what a hedge is for, and that is how you reduce risk and end up with returns that crush the market. If you try to chase returns, you will get owned.
Ask HN: What is the hardest part about finding high quality content online?
Hello all,
Whether it be sifting through SEO links or not trusting you are getting the best resource available, What is the hardest part about finding high-quality content online?
Depends on the riding conditions. The pads on my road bike lasted about 10,000km. In 12,000km my mountain bike has needed 6 sets of pads and 1 set of rotors.
No, it tanked because we’re in a bear market and there is a massive recession in progress. Who’s gonna buy a Tesla?
Indigo Agriculture | Principal Front End Engineer & Sr Software Engineer | Boston, MA | Full-time | On-site OR REMOTE | https://www.indigoag.com/join-us

================

I usually post this long thing about why we're a great company to work for and I realized that nothing compared to mission and purpose. You can read our accolades and I'll reference them below, but the truth is nothing matters more than why we exist:

We're fighting climate change by building better apps for farmers and the agricultural economy. Our farmers are able to produce better quality crops with fewer resources and less land. For example, we piloted a program with Anheiser-Busch and saved 2 BILLION gallons of water in the last year.

If I didn't believe this was one of the most important problems of our generation to help future generations, I wouldn't put so much emphasis on this. If you want a mission you can tell your grandchildren about in hopes of creating a better environment for farmers (and really the whole world), we're working on it right here, right now.

I'd love to hear from you and learn more about how you can work with us. Our stack is JavaScript (React & Apollo front end, some Node on back end) and Python (Flask for the back end).

For reference, we're a Unicorn company:

https://www.builtinboston.com/2017/09/26/agtech-startup-indi....

We work on the most under-hyped sector in startups today (agtech) 2 years in a row:

http://stateofstartups.firstround.com/2018/#trends-and-takes

https://stateofstartups2019.firstround.com/

CNBC named us the Most Disruptive Company in the world, beating out Flexport, Airbnb, and other companies you've seen here on HN:

https://www.cnbc.com/2019/05/15/meet-the-2019-cnbc-disruptor....

And our big climate goal is to use regenerative agriculture to sequester 1 TRILLION tons of carbon from the atmosphere:

https://www.indigoag.com/the-terraton-initiative
If they're comparing themselves to YC their monetization model is probably investing... right?
Sorry about that. I haven't gotten back to everyone - we're working on improving process so that we give everyone a firm answer.
Excellent opportunity to join a highly talented team that is addressing the long standing inefficiencies with databases using flash storage
> We have NICs with 32 or 64 queues in boxes having 88 or 128 CPUs.

Doesn't that mean that you should have more NICs?

From my recollection, the main thing that's made a computer a server or mainframe for the last 50 years has been that such systems have enough IO channels to saturate the CPU (i.e. they're intended to be CPU-bound, not IO-bound, under heavily-concurrent workloads.) If you take all the IO-offload cards out of a mainframe, it's just a regular computer.
On the task pages, click the column header:

https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
I think the Jepsen comment might be confusing. The point is that Dgraph can ingest data in either a Triple format, or a JSON format. Internally, Dgraph stores it in its own binary format. See [1] for more details.

> Naively, I'd think that one would cluster by entity and what an entity is connected to

In a distributed system, that approach leads high-fanout and network broadcasts, which kills query latency. Ideally, you want to do a traversal / join in one network call (max), not more. Because of this design, Dgraph can execute arbitrary depth queries in a much faster way. More details are in [1].

[1]: https://dgraph.io/paper
Hey HN,

A few months ago I started an experiment called “hacker time,” living on alternatives to the 24-hour clock. The system that won divided the waking day into 10 blocks of 100 minutes each. It is like a metric system for time that starts when I wake up at 0.00 and ends at 9.99 when I should be sleeping.

Throughout quarantine I’ve been building newDay, a calendar/planner that uses this system. Here are a few things you can do with it:

- Set up hourly intentions for each of the 10 newHours (takes me <10 min each night).

- Monitor weather / sun level data throughout the day

- Navigate with vim-like hotkeys

- Import/Export from Google calendar

Many of today’s tech companies have an abusive relationship with their users’ attention and data. newDay strives to earn your usage by helping guide you on the path you choose while holding your time, attention, and data as sacred.

I am committed to transparency when it comes to the use of your data. You can use newDay in an anonymous cookie-only mode. More details here: https://newdaynew.me/privacy. I know there is still room for improvement and I welcome community feedback.

newDay has helped me build a fulfilling life while quarantined, and I hope that it works well for you, too. All thoughts, feedbacks, rants, and nitpicks are welcome.

- esc
GrubHub leaves restaurant owner with 30% of order revenue
New 247k semantic similarity dataset: Image-Image, Image-Text, and Text-Text
True. Good distinctions. To re-iterate the above, the approximation to AWS Lambda would require dynamic AWS Lambda functions -- as in code that creates a Lambda with specific state embedded in it -- then tracks each of those by their unique Lambda identifier and ... yeah, that's where this breaks down because it's not all that similar to Lambda if the best use for a Lambda is repeated invocations of the same code. And Lambda IDs presumably aren't based on a hash of their contents and variables the way this is. But dynamic AWS Lambda functions are possible, so there's that. You could write this in Lambda, it just might be expensive if API calls to create and destroy one-time Lambdas are expensive enough. It's a lot cheaper and faster to build functions and store references to them in a hash table in memory.

Another similarity to this use of hashing the scope of a function would be in memoization of a function, to cache the output based on the input, such that you hash a function's inputs and assign to that hash a copy of the output of the function when run with those inputs. Then you can hash the inputs and skip re-running the function. You have to be sure the function has no side-effects nor any changes in behaviour or inputs not specified in the memoization hash, though. "Pure" functions are best for this use case.
> With fewer consumers purchasing and leasing vehicles and drivers on the road, we unfortunately do not see a path forward for our business.

Said like nobody will ever drive cars again.

I'm perplexed at how quickly these businesses are deciding to fold.
Hi. When it's ready, and it will be delivered piecemeal. It will also probably be in Preview, first, so you'll know before it lands in GA.
Other similar government initiatives always lead to the providers hiking the price of all repairs and maintenance work by €50...

I'm not sure quite why, since presumably market forces should still work to make people go to the cheapest bike shop to get as much value as possible for their €50, but that never seems to happen...

Example: grants to give discounts of ~£300 to install EV charging points in people's houses simply led to the price of installation rising by £300 overnight.
Promoting an independent browser today is hard. They may've fared better with a more modest offering of an extension. I hope that Ghostery, acquired, survives.
>Without access to your backend, there's no way for anyone to steal sensitive data or deface your website.

No way? At all? Why could they not deface or alter the static version? Of course there's a lot less attack surface but that doesn't mean it's invulnerable.
Does any host get safe harbour, or just the big ones with lawyers?

In any case, encryption schemes have keys, distinct from data and generated during encryption. In this case, there are two sets of data, either of which could be key or data, and one of which could of been generated before, and independently of the other. In fact, for any data block A, and random data X - there is a block Y that combines with X to produce A - any/all A, any/all X.
The thing is, prior to Gödel, one might have said "a probability of the existence of a proof of the decidability of Peano arithmetic will ALAWYS be greater than zero", and, by your argument here, that would have been correct - but, of course, one would have been mistaken.

It is your persistent and insistent use of the word 'ALAWYS' that is complicating things, and things would have been simpler if you had written of possibilities rather than certainties in the first place. You have written a great deal arguing for something that is not in doubt.

>>Furthermore, you were originally objecting to the statement that "the solution can be as simple as the problem but no simpler", but this is a reasonable statement given that, as we both seem to agree,

>No I don't agree. The statement is easily disproven with an example of a problem that is more complex than the solution:

>Problem: reduce -> 1*2*3*4*5*6*7*2*38*3432*0*232*22*33453*221*334/2*3929330:

>Solution: 0.

(By the way, it is rather amusing how you cut off my sentence in the middle in order to give it a meaning that the original does not have!)

Here we have an additional confusion. The solution to a travelling salesman problem is just an ordered list of vertices, but doing what you are doing here - just writing down the solution - completely misses the point.

> So to keep in line with the overall topic. Can more complexity always be destroyed for a given solution? Can complexity always be reduced for a given statement?

> The formal answer is: We can absolutely never know.

It is probably just as well that your "Solution: 0" example is beside the point, for if it were not, I would doubt your assertion that we can absolutely never know whether more complexity could always be destroyed for this given solution.
The massive plunge in share price coinciding exactly with the timing of the Tweet begs to differ.
I seem to remember that 386s couldn't decode and play MP3 files. In this project they're using the 80188 to control a separate MP3 decoder chip (the MAS3507D). Looks like an exciting project for an EE course.
Prediction:
It's only a matter of time they come up with a monitoring suite named ODOMETER !