skysight-inc/HackerNews huggingface dataset:
Design it how it works, not how it looks.

That is the biggest problem with the current "designer" bubble.
I have several hardware tokens for banks; the one of the Rabobank is as big and heavy as some phones :/ It has a camera and color screen built in. Secure but jikes I don't want to drag it around. The rest all do SMS only; I have never heard of 2fa via email; that sounds like the worst idea ever.
>>It doesn't cost them $100M a month to provide the service.

This isn't that much of a factor. FB paid $19bn for Whatsapp. A small profit on a $100m or $500m revenue base is never going to justify even a fraction of that acqisition price.

FB sort of set this standard themselves. They didn't pay attention to revenue early, as the movie said: A million dollars isn't cool. A billion users is cool. At IPO-time, those billion users still didn't ad up to revenue. This is much later than google, who had a mature business model much earlier.

Then, FB actually did find a formula to turn their 2 bn free users into a revneue stream. They proved it can be done.

Putting on the ruthless analyst hat... There are two reasons for the whatsapp bidding war: (1) keep it from the competition (2) potentially turn 2bn users into >$2bn revenue. FB already achieved no. 1. The ruthless business thing to do would be to force whatsapp to bet the house on achieving no. 2.
Flywheels are alive and well in the DC industry. They are used for those crucial seconds while the generator starts up. And as a backup for the UPS-es. (After all, those batteries might not be in top shape all the time.)

Though I imagine eventually battery tech will take over.
Virtual Movie Director: Studio Stories
I'd love to see this on the Frontpage in a few hours, since it's an incredibly engaging writeup. Apparently, for LTE/4G networks, we're not really into too much trouble on high end phones. Problem is, that's not what most people are dealing with, it's a "perfect situation" that does not present itself in real life. Nice article.
Trust must be earned. In crypto it is mostly by time, since it takes quite a few research papers to arrive at scientific consensus.

Codebase size is good argument, but consider how many optional components are in Strongswan, tens of RFCs supported. You can build it smaller omitting it in make.

And what is the size of OpenBSD iked?
And most companies not knowing how to measure experience, so they pass over experienced devs and can't understand their value...
The grid isn't a fixed frequency. While on average the grid doesn't change phase, the reality is that the grid may be out of phase by several seconds most of the time.

When the grid comes back from a blackout, chances are that it browned out beforehand so your sync is to a low frequency and coming back it'll be high frequency because the grid wants to compensate for loads jumping back on.

Additionally the components to generate your own waveform are cheap, yes, but not that cheap, adding them to the microinverter would increase cost quite a bit.

And you'd still need a transfer switch because if you happen to be 180 degrees out of phase, which CAN HAPPEN then your panel will behave like a dead short at double grid voltage. The current flow will definitely exceed the maximum tolerances and the magic smoke goes out.

You will absolutely need a transfer switch just so you don't fry all your devices the moment the grid comes back. Even then, syncing to the grid is a rather delicate maneuver since the grid will be constantly changing phase and it'll be simpler to shut down all inverters, connect back and have it all run back up on the grid itself.
Cool for learning to program games.

Development environments in the 80's and 90's were so simple that you had to program down to every pixel shown on the screen (well, maybe calling some line and sprite primitives for speed), so you only needed to learn a small mental model for programming, and everything above it was designed by you. Also, the primitive hardware and no expectations of portability meant that you only had to care about one or two combinations of platforms (maybe supporting a small range of graphics and sound cards).

This can help teach younger developers to understand the basic principles, and get a glimpse of how things are done below the surface of those modern do-it-all gaming engines.
Most JS Devs think debugging is just console.log(), that's nice and all, but it's not connecting a debugger, adding breakpoints, and watching the data go around.
The amount of times I've caught issues with just a simple game of follow the calls and objects around with the debugger.

As soon as I got to the part where they just upgraded a bunch of libraries.. I rolled my eyes, I was expecting a serious look at something, perhaps even a bug in Firebase or something in-depth. But nope, what we got was "Ooops I didn't think about the number of API/DB calls we were making because we don't think that way, we just assume everything is the fault of the libraries we use."

That kind of attitude is why I cannot wait to abandon JS all together..
It would be nice if it could tell me my region (India) is not supported before taking my phone number.

Nice website though.
I think those results just show that if you persuade the autovectoriser to work you'll get the same result as for manual SIMD code, as you'd expect.
> And the number of reported issues per customer are going down.

This doesn't mean anything, maybe the customers are simply tired of reporting issues. For example last year we didn't do any updates for 6 months because we were afraid it'd break something and we were too busy to be willing to spend the time reporting problems.

We also don't report issues that are already open on gitlab.com, reporting the issue means your customer is willing to spend time reporting, following up and testing your bug. This is your job, not the customer's. At the moment we are only reporting issues that are either blocking us from work or slowing down our development. The majority of issues we are facing are performance problems.

I just wrote a script to plot the number of issues on gitlab-ce over time and percentage of open/close issues, and the overall period they have been open for, you are accumulating issues with: `backend`, `UX`, `technical debt`, `performance`, `CI/CD`, ... labels, a lot of them don't have a Milestone and have been open for a long time.

I am not sure how emailing you would help us, it's not like the problems are not reported or you don't already know about them. It just appears that the priority of GitLab, as a company, is not shipping a quality product anymore.

EDIT: I work in the aerospace industry and one of the stages of our pipelines is to run stress test on our product. I would suggest you to run a stress test on an instance of GitLab, this would be an amazing place to start looking for performance problems.
Can't agree more.

IMHO, if you want to make a dent in the space, figure out better debugging tools!

In particular, tools that explain how a certain (specific) value was calculated in the system, tools that let you bisect the source data in some way and let you focus on the source data that are likely to have a problem, tools that help you figure out that certain intermediate value in calculations is an outlier, tools that let you test certain assumptions about data over the whole pipeline..
In India, they recently launched payments within Whatsapp which is a major breakthrough IMO.
Against your favour and in their selfish but sometimes ill-conceived interest.

Only belonging works in your favor, everything else emotional is against.
Someone has to do the sorting between good and bad products. Amazon bet on buyer reviews to do that, but seeing the fake reviews and all (dozen of post on that subject on HN), it's not working so well. So the seller has to do the job.
"if you can't charge people even $1 for your product...."

Only folks aren't always just paying $1. He's describing folks needing to set up a freaking payment system for a small amount of money - and that some folks aren't going to be able to do that and others aren't going to be willing. That's even before you get into the actual payment of $1. And this is before even considering there are other free apps that will work. There is a limit to the inconvenience folks will go through for your product if there are simpler alternatives, and being blind to this sort of thing could kill your company.

It also doesn't mean that folks cannot profit from ads. It isn't like all ads require you to pay through the internet - On my phone, I've gotten ads from a local coffee shop chain. I liken this sort of ad a cable tv ad. It might not get folks clicking on a website, but it might get folks in your store.
Are these commercial off the shelf components as cheap as a microinverter?
Or, maybe you could drop the expectation that urban life involves riding around in 4000 pound climate-controlled personal vehicles, and use public transportation/get a goddamn bike.
functional yet modular distribution focused on getting out of the way and letting users use their computer.

It's been a while since I checked all possible distros out there (which used to be a doable thing 2 decades ago, not so much anymore) but to me this sounds just like a whole bunch of other distros out there? So yes, not the best PR.

Here's how you should have said it: We are focusing our resources on developing a fast, clean, functional distribution for devices manufactured in the last ten years.

They could have, but it also means something different because it specifically says something about older devices. Whereas it looks like they're actively shifting away from that. I'm saying 'looks like' because honestly after reading the text I'm still not sure what exactly the plan is.. On one point the core goals don't mention anythin about 10 years, and it says should still be usable on old systems which sounds like 'well, maybe, don't care' when on the other hand it also says we will no longer primarily focus on older hardware which implies there is still some focus left. Again, yes, not the best PR as this article just creates confusion because of the wroding.
- 2 days a week I do indoor bouldering during about 1.5 hours per session

- 2 other days a week I do 30 min of bodyweight workout on rings : 5 min plank (front + sides) then dips/rows/push-ups/pull-ups
If the flywheel can be integrated in to the generator design then generator startup can be almost instantaneous. Synchronisation would still take a few moments.

I don’t know if anyone is building systems like that though?
Safe Wi-Fi: Verizon’s VPN App to Block Targeted Ads
Something tells me you haven't read the article, much less anything else on the subject.
Pinning extreme weather on climate change is now routine and reliable science
Like certain popular politicians who shall not be named.

A common enemy is among the oldest tricks in the book.
The same pair of video codecs won't magically transcode orders-of-magnitude faster on newer CPUs†, because video codecs—like crypto primitives, compression algorithms, and a few other categories—are designed, in the choices of the types of maths they do, to take advantage of the existence of certain accelerated instructions (e.g. SSE) that exist at the time of their creation. You can't make them take advantage of newer accelerated instructions (e.g. AVX-512) without it being a different algorithm.

In other words: new CPU architectures don't make old algorithms faster†. Instead, new CPU architectures enable newer, faster algorithms.

† Yes, this used to happen, in the 90s, when "new CPU" meant "appreciably higher clock speed." Nobody is making computers faster by increasing clock speeds any more, because higher clock speeds = higher power-draw and higher TDP. CPUs are now advanced by making them work smarter, not harder: accomplishing the same abstract tasks faster by providing hardware that enables newer algorithms to be used for those tasks, while using the same or less energy than the previous implementation would have used.
Both, really. Having more ceels gives you reserves obviously, but since the per cell load is reduced, each cell degrades slower.
An introduction to webpack and it's need
> then parse the completely un-parsable output to know which keys can decrypt the file.

This reminds me so much about a tip in Effective Java .. 'Always provide an option for users to access every relevant part of your object. If not people will start to parse your toString output and you will have created an inofficial API that you have to support whether you want or not' (paraphrased from my faulty memory). That programmers make that mistake again and again is just sad. :(
What kinds of groups are there?

Given the lack of popularity and commercial support, combined with the complexity to connect a client with an available server (compared with downloading an app from the store), I'd expect that they are populated mostly by old tech people or passers-by from universities; and any special interest group would have small user base coming from that demographic profile. Are my assumptions correct?
I remember that I was a kid when I read the news on Slashdot that the Linux desktop experience was going to be basically a competition between Gnome and KDE.

At that moment I knew that Linux would never win on the desktop. All those wasted developer hours.

I am still heartbroken to the day. In capitalism, competition benefits the user, even if the products are virtually identical, because then they compete on price. In the free software world, competition of two indistinguishable products actively harms the user.
Is it possible to buy a Mac Pro with an AMD EPYC 7401 CPU? Surely the fairer comparison would be against the current top-of-the-range in Apple's lineup.
The blog authors should state up front that Google covered the costs with an additional startup grant, and that this was entirely due to a quadratically expensive query.
> heavily charged/discharged by such events, and therefore has a short lifespan (less than a year, probably, if you used the kind of battery that's in a UPS.)

But surely such events (i.e. grid power outages) are pretty rare. In Australia it's rare for the power to be out more than once a year.
Rationalizing is very different from actually making a rational decision, and is part of System 1 thinking.

Post hoc, ergo propter hoc.

A rational decision starts with defining the epistemic system in which it is made. Is it bayesian, frequentist, higher order fuzzy logic? How the weighting, if any, works? What is the data/proposition acquisition algorithm? Which heuristics are to be used to simplify decision and why?
I toured Castle Edinburgh a couple of days ago, and I had this exact thought when looking at a wand amongst the Scottish Crown Jewels.
As I'd commented recently on HN: a good friend died of cancer in the late 1980s. We were close enough that I ran interference on those trying to provide "helpful" advice, particularly of novel, or scam, cures. I came to know that therapeutic protocol pretty well, and have kept tabs on progress since.

The cancer itself was, and is, rare and aggressive. Five-year survival rates remain about 20%. Cause is unknown -- no identified genetic or environmental factors -- though the relevant mutation was identified in the 1980s.

Treatment is largely unchanged from the late 1950s / early 1970s. Heavy-dose, profound side-effect chemotherapy. Surgery. Radiation. Very poor quality of life, in exchange for a few extra months. Maybe.

(And mind, in the midst of all of this, you simply do not know -- cause, best treatment, outcome ... and there is a powerful desire to do all that is possible. The uncertainty and helplessness, the lack of agency, are crippling.)

Three decades on, and Francis Bacon is proved wrong: knowledge, without the capacity to act on it, is not in fact power. We've gotten better at imaging, gene sequencing, path lab. But we cannot differentially kill this particular malignancy faster than its host any more now than in 1988. Or 1970.

It's a real bastard.

I stumbled across a graph a month or three back showing auto deaths per passenger mile, in the US,from 1915 to present. It's common knowledge that there've been vast strides in auto safeety, especially in the 60s, 70s, and 80s.

Common knowledge is wrong.

The period of fastest improvement in auto safety was the decade 1915-25, where the mortality per passenger mile halved. Since then, progress has been remarkable consistent, with further halvings, though every two decades.

Progress is incremental. Goddamned frustratingly so, with declining returns, but that's the inconvenient truth.

In medicine, there's been a vast push to heroic measures, to 24/7/365 monitoring, to electronic patient recordss. There's much financial incentive there.

(Internet pioneer Paul Baran warned of this and other dangers. In the 1960s. I've been on a bit of a PB kick of late. https://www.rand.org/pubs/papers/P3523.html)

But little health benefit.

What's mattered most has been prevention, then access, then consistency. Remove contaminants. Get the lead out of Flint's water. (And elsewhere.) Immunise. Ensure mothers and children adequate nutrition. Remove lead, asbestos, particulates, tobacco. Reduce alcohol consumption. Diagnose, treat, or accomodate mental health. Get guns off the streets. Pay living wages. Stop evictions. Break the poverty cycle. Build social resilience.

Reward providers based on community outcomes, not measures taken: value provided rather than cost.

Recognise that these are the truly challenging problems, and tackle them.
Market Watch August 2 – CryptoPotato – Bitcoin Price and Cryptocurrency
Shodan 2000
Vlogging? I hear it's pretty big with the kids these days.
ICFP paper describing React Async style of effects embedding (no React)
Amazon isn't really a competitor to them at all it seems. You go to Amazon to get stuff you know you need. You read the HS catalog to find the stuff you didn't know you need. That's how I perceive it anyway, as an outsider to the US.
I could recommend Zenkit. It´s a SaaS for project management but because of its flexibility, it can be used for almost everything and with every size of a team.

Use the List or Kanban view to organize your tasks, set labels for prioritization and set up a custom field with estimated hours. The different columns in your Kanban Board can show the sum of all the hours in this column. You can also add start and end dates and view everything in the calendar.

There is so much more you can do just have a look at the features we offer or the templates. Maybe this task planner template would be a good start: https://zenkit.com/templates/18
Lack of testing and poor code quality are completely different things though.
Makes you wonder how the constants for the winning hash functions were chosen... (The 32/64 bit "ones to beat", not the best ones produced by this guy's project)
There is a possibility you found a bug and a workaround is known/suggested

There is the possibility you are told you made a mistake in thinking it’s a bug with the library
Why does my website say, “Not Secure”?
Ruby: Almost everything is an expression unlike Python, has symbols unlike Python, closures and anonymous functions are not crippled or second-class unlike Python, has full continuations unlike Python.

Lua: Simple, minimal syntax which is consistent (unlike Python), multiparadigm, designed around one core datastructure, metatables/metamethods, metaprogramming is encouraged, has environments.
Illusions [Imgur]
Because people think bad software is better than no software
MessageBird | Amsterdam, Netherlands | Data Engineer, ML Engineer | Full-time | Onsite | Visa

MessageBird is a Cloud Communications Platform as a Service (CPaaS) company for SMS, Voice and Chat communications that connects businesses to 7 billion phones worldwide. We’re one of the fastest growing software companies in the world and we’re looking to expand our best-in-class Engineering Team with an experienced Data Engineer and Machine Learning Engineer.

Data engineering at MessageBird is programming-heavy, so we're looking for people who like to code and have significant software engineering experience. On the ML front we're looking for engineers experienced in delivering products more than purely research-oriented folk, but if you've a solid research background and want to try moving to the private sector, give us a shout too.

Tech stack: Go, gRPC, Clickhouse, Bigtable, Java, Apache Beam (Google Dataflow), GCP, k8s.

Our data team is currently 8 engineers and 8 nationalities. We have a very well stocked kitchen and a roof terrace in our brand new Rivierenbuurt office.

Apply at https://www.messagebird.com/en/careers and feel free to contact me at piotr@messagebird.com in case you have any questions.
there's also "hy", which gives you lisp syntax and access to the python libraries.

https://github.com/hylang/hy
Line is clearly the most fun - making most of their money from selling virtual stickers.
Kylie Run (Mario Style)
I think the standard reference is probably Spivak's 'Calculus on Manifolds' but this never really did it for me.

If you have a background in physics then some combination of Nakahara's 'Geometry, Topology and Physics' and Baez and Muniain's 'Gauge Fields, Knots and Gravity' might be good (I haven't included relativity textbooks as I assume it you have a background in GR then you have enough differential geometry).

An unusual recommendation that I think is really nice is 'Stochastic Models, Information Theory and Lie Groups' by Chirikjian. It covers a few other topics mentioned in this thread and is really nice. It's _extremely_ concrete and spells out a lot of calculations in great detail. Plus, the connection to engineering applications is much more obvious.
QVSTA | Lead Frontend Developer | Berlin, Germany | Full-time | Onsite

QVSTA is an expanding online platform for model agencies and content creators in the creative industry. Our mission is to disrupt a slow, intransparent market full of gate keepers. It’s a great time to join QVSTA as we have traction and a proven business model but there’s still so much ahead. Join us at this very early stage to help building products that empower people to work as creatives.

YOU WILL
Lead the frontend development.
Your voice will be heard and you’ll be part of the decision making.
Partner with our designers to build a beautiful and customer friendly product.
Grow and learn. We don’t expect anyone to know everything, but we expect you to want to learn what you don’t know.

To apply or if you have questions email ludwig@qvsta.com

For more information: http://qvsta.com/work/
This is what I love about Python. Every method is public, but methods that start with an underscore mean "use at your own risk". It suggests that the programmer use a preferred way, without strictly requiring it. Private methods treat programmers like infants.
You can't beat free. That would result in a huge migration to FB Messenger (does it have groups?) and Telegram (which has much better groups anyway) and others.
Changing the currency will re-trigger all those conversion calls ...
Tesla is finally making money on the Model 3
Sure maybe that's where we differ. For me hate speech is not extremism at all. Still odious. But its the difference between "GroupX is smelly and dumb and not welcome" and "All GroupX living in AreaY must die, and here's how we're going to do it"
> You have no choice?

Turn your mouse around. Where is it made?
This is true since it was a joke in the 90s.

> I get it. It's not unethical when you engage in commerce with a regime you find unethical, or when you buy from all the other companies that manufacture their goods in China ... but it's unethical if Google doesn't want to ignore 1.4 billion people?

I never said it's not unethical. You say that I say that. Which is quite weak. I hope this is the result of you realizing what you did and now trying to dig yourself out by shifting blame to others.
On balance I wish the author had, but it's a well written statement of why they didn't. And doesn't shy from critique of the underlying western democracies.