skysight-inc/HackerNews huggingface dataset:
Recurve | Software Engineer | REMOTE ONLY (US/Canada) | Full time

Recurve’s mission is to accelerate the transition to a clean energy economy. We do this by helping them utilities put their data to work to plan, procure, and deploy energy efficiency, solar, demand response, storage, and electrification resources into the emerging carbon-free energy grid.

We're hiring a mission-driven, security-aware engineer to help build our data ingestion, infrastructure, and downstream analytics products.

You'll be joining a fully distributed company of 17, of whom 8 are primarily engineers. We hire great people from a wide variety of backgrounds.

Stack: Application: Python/Django/Postgres + Vue. Cloud data infrastructure: Google Cloud Platform using primarily Cloud Dataflow (Apache Beam), BigQuery, Cloud Composer (Apache Airflow). We like Jupyter and BI tools for exploration and ad-hoc analysis.

Please apply on angelist (https://angel.co/company/recurve-analytics-inc/jobs/930499-s... - includes full job description, hiring process, etc), or reach out to me directly at [phil at recurve d com] with intro and resume.
It’s cheaper in the sense that it is faster to write and maintain those 20 lines of code. Because someone has to evaluate the library, understand it well enough to actually call it and then make sure it stays up to date. And often there are a few lines of code to translate your data into a form that the library requires etc.
One, since state lives within each component and can be passed as props.
ECS has been used relatively heavily in game dev since like late 90's.
Codebases follow evolutionary paths. If the code isn't going to be needed for long, there's no point in refactoring. If it does have a long lifespan, then every change, every addition, has the potential to increase complexity and make it harder to adapt. That's ok for a while, but in the longer term requires a counterbalancing pressure in order to be sustainable.

Whether that pressure is provided by regular developers, or partly or wholly by dedicated people, depends on the interests and skills of the people on hand. Carving off a Fred is one successful strategy. So is having core developers actively maintaining the integrity of the overall system as they make changes.

You have to pick, or stumble upon, the right strategy for your situation and staff.
Just a note that data-driven is not the same as data-oriented-design [1].

I was trying to see how Bevy embraced data-orientation, but I think it doesn't necessarily do so, since data orientation is more about reducing indirection, for ex., reducing or removing excessive data hierarchies. I think dod is also related to "mechanical sympathy" [2].

Edit: maybe the ECS part is the dod part? I saw the tree demo and it did not look very ECS to me. Maybe it is just the UI? :-)

1: https://meetingcpp.com/mcpp/slides/2018/Data-oriented%20desi...

2: https://mechanical-sympathy.blogspot.com/2011/07/why-mechani...
Smaller Rust is more like OCaml than Go IMO. Go has an entirely different design philosophy.
Computational Causal Inference at Netflix
Cycling is great and has a relatively low risk of injury (if you avoid getting hit by a car). But people who only ride bikes tend to end up with lower bone density and weak core muscles. If you want to stay fit for the long term you need to mix in some high impact and resistance training.
Some Humans Are Carrying DNA from an Unknown Ancient Ancestor
Wikipedia does not require anything like the technical staff that Mozilla requires, and even Wikipedia has struggled to get by with only donations. Wikipedia does not run on end-user devices and does not have to deal with all the things that entails. A critical vulnerability in Wikipedia is a problem for Wikipedia; a critical vulnerability in Firefox is a problem for everyone who uses Firefox, and it needs to be fixed by someone who is not going to suddenly be swamped at their day job. Wikipedia can ignore new web standards that are not useful for Wikipedia itself; Firefox has to support most web standards to remain useful as a web browser.

The best case for a community-driven Firefox would be for big companies to provide support, either in the form of money or in the form of labor. That is more or less the model that has propelled the Linux kernel. Unlike the Linux kernel, there are few if any companies out there who can point to Firefox as a strategically important project that they are prepared to pay someone to work on, especially given the existence of good, actively-developed alternatives (including Chromium for those who require open source).
Yeah, I once implemented a very simple AR tag mechanism -- using Binary Golay codes [1] which are super simple to understand.

It turns out that you need a mask, otherwise you can too easily get a tag that is entirely (or close to) white or black. I was fortunate with a small code space (only 12 bit) that I could get away with a single mask, it never occurred to me that I could have used multiple masks (at the cost of a the bits to encode the choice)

I looks like extra complexity, but it solves a very pragmatic problem

[1] https://en.wikipedia.org/wiki/Binary_Golay_code
Why not use double phone? I’m afraid you need a bit cash to afford privacy but you can use a cheap smart phone to install this app then put it to faraday cage throughout your travels. Basically a travel only phone.
CuriosityStream to Go Public via $330M Merger
hey bserial, I'm part of the team working on Dagster.

While there are many things we're working on, there are 3 goals that got me excited about working on this system:

1. Local development: most modern workflow orchestration systems don't have a good local development story. We want to provide a seamless end-to-end dev experience from your laptop to CI to dev to prod for authoring data workflows.

2. Complexity: the Airflow deployments I've worked on or otherwise encountered have hundreds of DAGs and thousands of tasks scheduled on an hourly or daily cadence. We aim to provide abstractions to better support managing and wrangling that complexity.

3. Testability: Most modern data platforms are poorly tested. Many orchestration systems, like Airflow, tend to hardcode deployment concerns the business logic, e.g. EmrAddStepsOperator. With Dagster, we aim to separate the business logic from environmental concerns to make it easy to swap out an external resource implementation for a mock, dev version, etc.

Hope that makes sense!
It's just not worth doing business in the EU because regulation and taxes are too high there.
Free, and they already have gmail. Android pushes it. Seems super-popular in schools. Ties in with their education offerings, I think, and lots of schools use chrome books.
You don't edit the "state machine" at all. As long as the component is reflecting the state (which happens automatically), you wouldn't have to make any changes other than the moving of the checkbox.
>...as John Maynard Keynes said, “the markets can remain irrational longer than you can remain solvent.”

That really explains a lot with what's going on in the current economy.
Obviously.

...but the point being made is at 10% reduction, a 9MB and a 10MB binary are indistinguishable.

They scale almost identically.

so... it seems a bit like premature optimisation to devote such a large amount of effort to what appears to be a win that affects virtually no one except those few (FANG) who deploy to thousands of services daily.
> What happens if you want to move the confirmation checkbox from the modal back to the main view? Do you have to edit 2 state machines or 1?

Could be either, it's up to the dev to decide at what level handle that state.

Often with redux you use a single global state
You could read the link I attached to my comment.

I've personally experienced problems with reviews before where negative reviews never showed up, and have stopped using AirBnB as a result. I also know this is an extremely well-known problem, and if you aren't aware of it it's because you haven't looked for it (a few minutes on Google is all it takes).
>on the job market.

That's a very nebulous term, as this whole thread bears out. I feel sometimes like my comments are abducted by aliens.
HTTPS Everywhere will block a site if it does not have HTTPS available iirc. Chrome/Firefox don't do that by default.
It may not be JSON but it’s out there in the wild. A lot.

Let’s say I’m scraping a website. I can:

1) complain to the owner that “it’s not JSON”.

2) write a parser for a syntax that has no spec, (it’s not JSON, but it sure looks an awful lot like JSON with unquoted keys.)

or

3) Set ALLOW_UNQUOTED_FIELD_NAMES to true in the Jackson library.
Maybe. But, as a general rule, I advise against arrays of unbounded size on documents (arrays of a known bounded size, say, containing enums to act as a multi-value flag, or email addresses on a user's account, or something like that, are fine).

One example: We used mongodb to track the state of a general CSV import system. So, we'd have a document for each csv file a user imported, and on that document, we were storing errors which occurred during the import to later display to the user. Of course, in an array. Worked great for years, until one day, a user uploaded a very bad CSV, non-maliciously, with hundreds of thousands of lines, with dozens of errors on each line, generating an array millions of items large. The failure condition here was wild: the import just got slower, and slower, and slower, until eventually the (modestly provisioned) db cluster started failing. We immediately normalized that array into its own collection, re-ran the import, still generated millions of errors, but with no problem.

As always, a general rule doesn't apply in every situation, but in my experience, unless you have a really strong grasp on how a system's use will scale, years into the future, unbounded arrays are icky. Lookups across two collections are only a modest performance loss over a direct query, and if the arrays get up there in size, they can actually be faster.
I re-read your comment and yes, I think I ended up confirming your point. However, I do not agree with the conclusion that its not possible or desirable to compete with an IDE, not at all. A functioning LSP, which is completely achievable, will cure mine and probably many other's IDE envy, and that is why I think its a crucial project.
That's interesting. But, IMO it has a lot of room for improvement to compete with frameworks like React, Vue, and Svelte.

Isn't it?
I always thought the Pentagon has had a robust global satellite communications network for decades already.

(I don't know whether it is Internet-protocol based. My guess is yes.)
It need not be stable. The OS could provide each application with the system call table it expects to see (with most of them getting the standard one)

Determining what table a program expects likely would be a black art, but I don’t think that would stop Microsoft from trying that for programs deemed important for the platform.
I love your paintings ;).
Again my general rule - you (generic you) are no special snowflake. What are the chances that you come across a bug in a library that has had 2,176,677 (in the case of Dapper) or Entity Framework (supported by MS) that no one else has come across, found a workaround, and posted the answer somewhere on the Internet compared to your code where you didn’t think about a corner case?
Is anyone really surprised by this? I guess the people who use tiktok won't care though.
> So it seems to me there's something else in play that explains your observation.

There is, and with apologies for the late reply, I'll unpack one term I used, which is diversity. I've lived and worked all over the EU and feel comfortable observing that practically all EU national, regional, and local governments are politically clustered within one deviation of the International Standard Social Democracy. What's more, they actively work together at the top level to promote harmonisation of processes and industrial/commercial/technical/legal/administrative standards.

I'll contrast this with the US where the political window is splattered all over the compass, process & technical standards are driven by corporations that actively seek to differentiate themselves from one another, and regional and local political groupings will take a deliberately contrarian tack on a diverse policy spectrum in order to more clearly disambiguate themselves from opposing forces and to segment and cement their constituencies.

I believe the latter drives more innovation through competition, but distributes it more unevenly. And I'm neither a US citizen or (currently) resident, just a frequent visitor both for work and play, but I also think that the greatest single quality of the US is being the only country where practically anyone, regardless of cultural backdrop or however divergent their social/political preferences, might hope to find a community of like-minded individuals. What that isn't: a recipe for harmony.
I cannot, for the life of me, fathom wanting this feature.

1. I don't want to pay a damned subscription for functionality in a product that I have already purchased at great cost. It should be all-in, once, and done.

2. Why would I want a "self-driving" function that still requires that I keep my hands on the wheel and my eyes on the road? What does it mean that the system disengages if I look away? Doesn't that mean it's going to potentially do a stupid thing right at the very worst moment? If I look away when the system is bringing me around a gentle highway curve at 100 km/hr, will it all of a sudden just straighten out like as though I had let go of the wheel?

It's all so immature and so pointless. I'd way sooner just have a more comfortable seat inside the car and more adjustments for the steering wheel, etc. so that long trips are more comfortable.
Check out https://www.mrmoneymustache.com/ for one possible alternative that is working for a lot of people that live in the US. The FIRE movement is about working for a short amount of time and living frugally but well for the whole of your life. You have to give up keeping up with the Joneses and most people will think you are a bit weird, but many people feel that is a great trade.
Just a heads up, this is an old comparison (over 1 year ago) that hasn't been updated since TimescaleDB now supports native compression. (Blog post references TimescaleDB 1.2.2, the product is now on 1.7.2).
Starlink would have to violate international laws, via the ITU, to serve other countries. If they violate it, and the US allows it, causing the ITU to collapse, there’s nothing to stop foreign companies from broadcasting/jamming signals over here.

There are some specific exemptions for government/military (eg GPS), but Starlink won’t help here.
My company runs Go and Java programs that locally compile in seconds to binaries / JARs that weigh tens of megabytes. But for production, we insist on spending tens of minutes building and copying around Docker containers that weigh gigabytes.
DDoS Attacks Triple in Q2 of 2020 to Target Covid-19 Home Workers
The problem with totp is it's really just a second password. It eg doesn't protect you from phishing in the way that a yubikey does.
OP is half correct. There was no toxic environment. NYTimes really decided to go after Uber because they don't like how the drivers have the freedom to work as they see fit. That's why they hired Susan Fowler.

At the same time, the execs truly didn't see the rise of SJW culture and were caught off guard. That was their true downfall.

Source: I worked at Uber when this was all going down.
Haven't touched it at all, but I strongly suspect that the hired corporation is treated like a blackbox.

Middleman: OK, hand us the encrypted data and 125% of whatever the ransomeware is asking.

Middleman: Outcome A: Here's your data back. Outcome B: We were unable to get your data back, here's your full refund.
Does HTTPS Everywhere actually work for you? It's utterly useless for me as far as I can tell. Try going to some site (say, example.net) in Chrome and watch it just load HTTP.
Transparent OLEDs
> Intelligent societies would, by definition, be determined by non-genetic learning transmitted via culture.

This is inherently Darwinian as well. In fact, cultural evolution is usually smarter than we are; indigenous pre-industrial cultures typically have an excellent practical understanding of how to thrive in their immediate environment even without having anything close to a theoretical scientific understanding of why their own cultural practices work in the first place.

More to the point, cultures that expand and grow, do so at the expense of cultures that don’t. So through natural selection, we would expect to see more expansionary cultures than non-expansionary cultures.

And, even setting aside the argument, you still have the much tougher task of explaining the notion that no extraterrestrial cultures are expansionary, which is what your side of this argument would require.

> I'm not at all sure that, even assuming your estimate, ETI would be 'fairly obvious'.

It would be eventually if it were growing exponentially. On the timescale of the galaxy and by all probability, eventually has already happened unless humanity is an extreme, extreme, extreme outlier early bloomer.
If anyone's looking for the meat of this one, it's the second half, in relation to the App Library feature. As it turns out, all the things the App Library is supposed to improve, it just reinforces.
The internet should be a public utility. Google should not. This would be insanity.

The article even mentions how the government regulates e.g. movie ratings... Only that's a lie. The MPAA is not a governmental body. It's voluntary.
Go 1.15 Release Notes
I could build his example in 2-3kb of vanilla JS unminified :)
I'm getting security warnings visiting the site, on both Firefox and Chrome (though chrome's could be due to an external check, redirects me to malware.opendns.com). "Error code: SEC_ERROR_UNKNOWN_ISSUER" on FF at least.

edit: and seems like I'm not the only one, as there's at least one upvote already. probably worth checking!
> Things that we do not worry about anymore: Javascript, controllers, CORS, JSON, HTTP status codes, API documentation, 3rd party dependencies.

That's a good looking list of things not to worry about. Especially CORS, the bane of my life.. the fact it's pre-flight has caused me so many problems in my (tiny) UI responsibility.
How a Twitter clone heralded a no-code boom
You Require a Numbers Table
And the new tree style tabs is quite unstable compared to the old 'bad' plug in which results in it sometimes being very handy that the other tabs are still visible. I'd love for them to be gone too, they take up vertical space which is at a premium but then Mozilla should first give extension developers a chance to get the kinks ironed out. Such unforced errors are really annoying.
If you’re going to reply to me, please reply to me instead of editing.
I think you're identifying something important to talk about. If I understand correctly from the PodClip, really the idea is to give your brain a small reward for making progress.

I think many of us on HN are familiar with being able to work 10-12 hours if we're feeling like we're on the track to success. However, even then, at 10-12 hours, eventually the brain gets tired. That's something that I'm also interested in learning about.
Watch out, it will be trans-piled to JavaScript, so there's a chance you might be learning it while debugging!
Because that would take precious jobs away from the private sector and the rich couldn’t get richer /s
Kind of cherry-picked there from the set of things 60 is too old to start. What about having 30 more years to fix a wrong you once committed, repay a debt, help give some worthy person or cause a boost?
Except for the growing list of techy or popular firms that are all going WFH into 2021 or permanently?
I often find data scientist (from python persuasion) come into engineering organizations with this mindset and undo alot of progress. They end up realizing that engineering really does have value and isn't just engineering for engineering's sake and end up layering on a thousand hacks that replicate what was already there. Simplicity for simplicities sake is just as dangerous as complexity for complexities sake. There is a reason major enterprise organizations (LinkedIn, Facebook, etc) have java backends. Also it's not a matter of misappropriation. Some of what they do does apply outside the enterprise. You see a ton of python libraries make this mistake, like dask by saying "it's just pandas that runs on multiple machines". "It's just" is usually a sign that there is some complexity they are ignoring or don't have (that most others will)
It's true that WebAssembly makes web apps more opaque, since it's a compiled binary vs JavaScript code.

However, ad blocking should the same as for JavaScript single page apps. The Rust code in this article hooks into JavaScript APIs to create a standard webpage, using standard HTML elements and updating the DOM - just like a JS app would.
For a long long time, science fiction movies have used transparent displays to seem more "futuristic." However, actual transparent displays have been underwhelming in practice.

This technology is being use by Xaomi to make a "transparent TV"[1] which in theory you will be able to buy. (I realize that not all of these sorts of announcements survive until actual product shipment).

It will be interesting to see one of these "in the flesh" as it were, I'm at a loss what you'd have behind it that wouldn't make it really really annoying to watch, but the cool factor could be right up there.

[1] https://www.theverge.com/2020/8/11/21363861/xiaomi-oled-tv-t...
No people didn’t choose to have Microsoft. Microsoft forced OEMs to bundle Windows with all of their computers. Even if the OEM decided not to bundle Windows, they still had to pay a license fee.

No personal computer comes with Chrome installed by default unless the OEM made a deal with Google to bundle it along with other crapware. Users have to explicitly download Chrome.

It’s a lot easier to change your default search engine than change your operating system.

The proof is in Google’s dominance. Google became popular when IE was the default browser on PCs and Safari was the default browser on Macs.
> I think a LibreOffice-style hard fork will be necessary at some point with a nonprofit carrying Firefox forward.

It doesn't have to be a hard fork.

A new community could do a soft-fork of the Firefox codebase, like Ubuntu does with Debian. (Or even like Seamonkey!)

There have been several attempts at this, but they never consolidated into a clearly-presented single alternative (like LibreOffice, Ubuntu, or Glimpse image editor).

If there is enough interest in maintaining a viable browser that isn't controlled by a large corporation, would funding for the new project emerge from the likes of Red Hat?
Thanks to AI you can SEO Analysis without a consultant
So do you feel that none of the money losing startups deserve to exist either?
It's also a great way to debug.

I've written video/image codecs and when things go subtly wrong, decoding the raw bitstream by hand and comparing carefully with the decoder output has been the best way to figure out the problem. It can be quite tedious, but as the phrase goes, definitely "builds character".

Or as someone else put it, "How can you tell the computer what to do, if you can't do it yourself?"