skysight-inc/HackerNews huggingface dataset:
Crypto people: “programmers really need to get better at using crypto!”

Also crypto people: “how DARE ye mere mortal even touch crypto!!!”

This doesn’t help. The only people who will listen to “don’t roll your own crypto” are the very people who ought to be learning how to do it. The arrogant types who should never touch crypto will ignore this advice and still write bad crypto.

The most effective thing would be to just tell programmers why crypto is hard in ways other code is not.

Crypto is hard because you can’t simply unit test for vulnerabilities. “Anyone can write a crypto system they themselves can’t break.”

For the majority of code it’s good code if it works and is fast and lacks things like memory safety bugs.

For crypto it can work perfectly and still be grossly insecure. The only way to tell is to deeply understand cryptanalysis and do academic mathy stuff.

As a result if you use crypto it’s best to write boring conservative crypto and use it the way pro cryptographers suggest. Try to use a peer reviewed library or if you can’t and must implement then try to ape a peer reviewed library exactly.

Don’t even try to invent new stuff in crypto unless your understanding is very thorough and don’t use anything new without peer review.

Edit: another example of abnormally hard code is distributed databases. They can be unit tested but adequately doing so is extremely difficult. It’s easy to write one that seems to work but loses data at scale or under edge case failure scenarios. Crypto is even worse.
PWM is awful, in displays, flashlights, headlights, taillights, and dash lights. I challenge the notion that PWM is more efficient than analogue dimming. PWM adversely affects enough of a percentage of a population that it should be eliminated and banned. In those that PWM does not affect, it causes two issues, one revealing callousness and the second a fallacy: 1) "PWM doesn't bother me, so I like PWM and I don't care about anyone that PWM bothers or hurts; and 2) "I can't detect PWM, therefore it does not hurt me."

To drive home the fallacy in 2), "I can not detect CO, therefore it does not hurt me."

PWM is pure evil.
I’ve been thinking about that for the rewrite! Maybe some chance to incorporate snippets of opcodes from the consumed.
New Webex Suite and Branding
And furthermore, the content was from a guy (Tim Morgan) who answered a question on Quora (linked at the bottom of the article). So Gizmodo just copies it and puts lots of ads around it. I don't understand the modern internet.

https://www.quora.com/How-does-a-fighter-jet-lock-onto-and-k...
Lots of cope here. Market cap isn't everything, being in business is stressful and it made me sad, there's more to life than money, etc. All true, just as long as you're ok with being gobbled up by Amazon. Amazon if you're lucky, otherwise some random inscrutable Chinese holding company. Then again, maybe not so much daylight between those in any case.

On the bright side, you'll have even more time to reflect on how there's more to life than money!
Life of Brian had something similar to say:

https://www.youtube.com/watch?v=QDcturOGF_4
USGS Water Data for the USA
So no nation not colonized by the British has a legal system that gives them rights ?

A cursory look at colonial India is enough to show this to be complete nonsense. The Rowlatt act wasn’t exactly the beacon of human rights.
Round it to a given precision and maybe fuzz it?
But also those US companies brought this tech they bought to the masses. To say they were built by others anyway reduced the role big tech played here same way a naive developer thinks a company’s success is just because of code he wrote.
market prices of securities don't really reflect the value of 'real things'. market prices reflect capital flows. sometimes the two align - but this also depends on the definition of value you use. (you frequently hear that somethings trades at X multiple of ABC and Y multiple of DEF... and those multiples are wildly different across the whole market, yet prices are stable - because capital flows balance out.)
Today, today it's culturally acceptable to ridicule, scorn, and otherwise attack men and manhood; to portray men as arrogant, abusive, and controlling. The word 'masculine' is now a derogatory term that means the same thing as 'toxic'. "Men are trash".

The message is that to be a man is to be lesser, or irrelevant, or harmful to society. That there's something shameful about being a man.

"There's nothing wrong with taking men down a peg or two; after all, they rule pretty much everything". Yeah, now what about the overwhelmingly vast percentage of men who will never have a management position or hold office? Whose life is just mediocre? Is it also okay to tell him he's toxic trash?

And sure, the proper response is "don't listen to the garbage". Doesn't mean it's okay to spew garbage.

As for entertainment media, it's a shit-show on both sides -- women and men are both horribly stereotyped.
Why don’t you want me to be required for transfers?

You already depend on me for redeeming your coins for USD, so depending on me for transfers doesn’t present any additional risk.
Mechanic is quite simplistic comparing to life science to me. Every single component of the car was built by a spec made by human. We dont borrow components of nature that oporate at a scale we're not fully able to inspect, to produce code we dont fully understand, then claim that the code does exactly what we want and nothing else.

Aside from that, cars were also tested for more than 1 year you know?
I think you're missing something important here by applying the worker pool simplification to the idea. Order is important i that case as well. It forces both fair scheduling of the work and the metrics from the queue can easily describe the overall latency of the work being done and the capacity and utilisation. The latter can be used to scale the consumers of the queue and/or alert on when things aren't working properly.

If you throw a proper messaging broker on the table like RabbitMQ then you're getting message acknowledgement as well which is important if you must do the work. A failed consumer will result in the work being rescheduled on another consumer transparently. Of course there are metrics you can see and get heads up when your consumers are not working.

Ergo, don't simplify something too soon. Even reliable delivery of newsletters is rather important otherwise why would all the tracking pixels exist? (they are a form of message acknowledgement)
> The point of queues is sequencing, storage and decoupling of events for the sake of scalability and durability.

The point of queues in any particular application is some subset of that; the calculus of implementation approaches that make sense depends not on the abstract point of queues in general but on the concrete point of queues in your use case.
You could also use the formula, "rich, mostly smart".
Pretty much my biggest fear, right here! Always uneasy around big things in the watery abyss.
I thought I was imagining things in my head.
This is true, but there is a consistent identifier cross account (likely to make it possible to build multi-account architectures without having to measure network latency between zones manually) - this is the AZ ID instead of the AZ Name [1].

[1]: https://docs.aws.amazon.com/ram/latest/userguide/working-wit...
I use Queues for retries, buffering, and parallelization. It's pretty easy to write most programs to support at least once and to run multiple queue workers that you auto scale.
Yes. Pay Amazon to do it and add use all that saved time to add business value instead.

They'll also manage the consumers of the queue and scale them too! Serverless is bliss.
https://www.google.com/search?sxsrf=ALeKk02SkvKxY0RsgH6wex0w...
This is really helpful, thank you for the thorough explanation
vi has persistence support
IMHO assuming that 'true value' even exists is very bold. you'd have to integrate all possible timelines into your valuation, modeled with very fine precision, and then you're lucky if your model converges to anything other than 0 or infinity...
It's better to adopt filtering instead of reducing your sample rate, only if the opportunity cost of sampling and processing is sufficiently cheap (given scenario). If it's relatively expensive to sample and process (which I think apply to many business type scenarios),, just decreasing your sampling rate to more appropriately match your ability to manipulate outcomes make sense.
This is why it’s great to focus on Siam if you play with that one person who always focuses on AU.
Is it possible, without Javascript, to have:

- drag drop reorder and move?

- accessibility?

- draw on top of webpage?

- popup menus?

- show/hide sidebar?

Any links for examples?
I love HN.

"I read your Forth code from 20 years ago, please help me understand your comment string" - to the original author.

I am praying this gets resolved. This needs to be on the front page by itself.
It fails when $script is something that needs to read data from standard input.

I find that happens rather often with remote commands, so much that other quoting approaches are useful to have available
I got vaccinated few weeks ago. So far no green skin, no strong brain preferences, no magnetism or better phone reception. If you are reasonably young and healthy you should not be afraid from both the virus or the vaccine, but by vaccinating, you are doing a social service to protect everybody else.
> The word 'masculine' is now a derogatory term that means the same thing as 'toxic'.

This whole comment was BS, but I’ll focus on one example. This is the exact opposite of the truth, “toxic masculinity” is a common phrase because “toxic” is an adjective that is seen as *adding significant information to the description which is not already present in ‘masculinity’”.

If masculinity were viewed as inherently toxic, “toxic masculinity” wouldn’t be a needed phrase.
I really hope nickel takes off.

As a nix-lang fan, I've been using dhall as a nix-like build system configuration language when I need to work outside of the nix ecosystem. I love its use of static typing, but it's not without its rough edges. Defining recursive types is not simple and writing configs which need to mix rigidly-typed domain knowledge with arbitrary loose json data can be very tricky.

It looks nickel's authors have these use cases in mind. I'm excited to keep an eye on this project.
I agree, but it won't be possible to expand construction enough to cover all of the jobs that agriculture lost. Back in 1950 that was almost 5% of the work population. Construction might absorb 2% or 3% under ideal conditions. But some creativity will be needed to reabsorb all of what was lost.
It wasn't a problem for Sybase on a commodity host circa 2000 because clearly that host wasn't doing a whole lot of other stuff. It's a big problem for our 48 core nodes with 2TiB of RAM and a metric shit ton of DAS NVMe. Ergo anecdotes don't scale either.

To clarify we just moved this entire problem to SQS.
The Termination Event – Spaceweather.com
for good reason. it is impossible to define strictly in general.
I agree with you, this shouldn’t even be an issue in 2021.
How is this "misleading"?

We want the poorer countries to get richer faster in order to close the gap. Accomplishing precisely this is a large part of EU policy. And it is working.
That's assuming there is a viable alternative for the same price point - and no, I don't consider abstinence as a valid alternative.
The script isn't being passed over ssh's stdin.
Yes - see the popularity of uBlock Origin, NoScript, uMatrix etc.
I used lynx on a computer of mine a while ago when an upgrade broke the login. I could switch to a different terminal to do that, find the issue, then run the commands to fix it.

I've also used the Raspberry Pi as a computer in the past and used Dillo (or similar browser) as it was lightweight.
Ah cool, no company involvement makes it much more interesting to me. Because sooner or later they'll always want to monetise and that has privacy impacts generally.

I missed the internet part, sorry! It doesn't say so explicitly, just that the info is not collected. But how do the peers find each other then?
I do agree that there are a lot of internet and media headlines that portray men in a negative light. Yes, writers generate Internet/media content with provocative headlines declaring "The End of Men". But in real life I see plenty of men getting good jobs, having families, winning awards, changing the world. Everywhere I look there are positive examples of men killing it: in business, sports, politics. So I feel like you would have to ignore all of the male political leaders, sports super stars, highly regarded thinkers and scientists, business leaders, entrepreneurs, religious clergy, and just focus only on stupid things people on the internet said to feel like the world is bleak for men. Yes, women are getting higher grades in school and graduating in higher numbers than men. I don't think that one metric by itself spells a doom and gloom future for men. Men don't have to be better than women in every metric to have a bright future.
>"(His class on mushroom identification at the New School for Social Research was immensely popular.) How Cage accidentally poisoned himself and some friends"

I just read it and find this delightful, independently of John Cage. This formulation begs the question about how many of the students of this "immensely popular" class were later accident prone.

Maybe is voluntary humour from the part of the author, but I'd not bet on that.
I don't think the cities were in such a bad place before the Revolution, this is a more recent thing. They "prune" the trees by cutting pretty much every branch, then a couple of years down the road they cut them off because they've died. I've seen this happen many times.

You're right, of course, those in forests and those in the cities bring different benefits, but most people don't seem to care enough about either.
This sounds dangerous. Without some good way to prevent workers stepping on each other, that will result in lots of useless queries and failed updates if a lot of jobs get scheduled at the same time.

In the Drupal case, the database returns a single row which is pretty much guaranteed to be the same for all workers in between updates. You really don't want that in the same database your page views hit. At least selecting N rows at a time and then claiming a random item from them would be slightly better.
>>When quantifying things, people naturally focus on things that can easily be measured. Measuring the final result doesn’t provide enough quantitative data, so it’s tempting to include the data from intermediate steps. This is an attempt to shorten the feedback loop, and trying to shorten feedback loops is very dangerous in complex systems.

This is a really important point that the author sort of glosses over -- adding measurements, or tighter measurements must be done extremely carefully for two reasons: 1) the risk is 'looking for the key under the streetlamp because it'd better light', and 2) unintended side effects.

The first will cause data to just be basically irrelevant or even inverse to the desired signal, but people will chase it anyway because it is easy to measure. The second taps into the management phenomena of "you get the results that you measure", and create perverse incentives to do the wrong thing, either self-managing, learning, or managing an org.

Good article, much more worthwhile than I expected!
Living on Cape Cod these days, I read “Burt Dow Deep-water Man” to my son fairly regularly when it’s time for bed. I think this guy just picked up a new nickname for himself.
My main concern would be monitoring. Most queue systems connect to alerting systems and can page you if you suddenly stop processing thongs or retrying the same query many many times. For a DB, since the scope of access is much larger, you don't get these sort of guarantees for access patterns and you essentially need to reinvent the wheel for monitoring.

All to save 2 to 3 hr of Googling for the best queue for your use case and finding s library for your language.

It makes sense if you don't care about reliability and just need something easy for many many people to deploy (ex: Drupal).
Meatless Monday: two recipes to join the movement
What do you think "ionize" means in this context?

Or, for that matter, hull? These aircraft have many layers of material between the traditional tensioned skin of the aircraft and the outside air.
Why yes, they could've done without all that.

But whatever, if it wasn't the British, it would've been someone else, such is human nature and such were the times.
Popup menus, sidebars, drawing on top of a pages can all be done to a certain extent with some CSS

Accessibility is possible with standard semantic HTML and aria tags (again to a certain extent)

D&D is probably not workable though
I never prefer free OS. Mac i best for me.
https://deals.ogili.com/
Stealth is not perfect and not about never being detected, it's about shooting first. You are going after a military aircraft that is trying to kill you. By the time you lock a B2 it has released its bombs. By the time you lock an F35 you're dead.

These aircraft don't just fly around and let you take your sweet time killing them.

If you manage to lock one you have to deal with this as well:

https://en.wikipedia.org/wiki/Radar_jamming_and_deception

Some of these are quite sophisticated, example:

>Digital radio frequency memory, or DRFM jamming, or Repeater jamming is a repeater technique that manipulates received radar energy and retransmits it to change the return the radar sees. This technique can change the range the radar detects by changing the delay in transmission of pulses, the velocity the radar detects by changing the Doppler shift of the transmitted signal, or the angle to the plane by using AM techniques to transmit into the sidelobes of the radar. Electronics, radio equipment, and antenna can cause DRFM jamming causing false targets, the signal must be timed after the received radar signal. By analysing received signal strength from side and backlobes and thus getting radar antennae radiation pattern, false targets can be created to directions other than one where the jammer is coming from. If each radar pulse is uniquely coded it is not possible to create targets in directions other than the direction of the jammer
The History of Code is Free Speech (2020)
Yeah this title is clickbait. No strategy wins every time, especially if everyone's cognizant of your one style.
Sort of. Etymologically, you're correct that 火曜日 originates as the term 火曜-日, the day (日) of the fire light (火曜).

But I don't think even most Japanese people are aware of this today; the only common use of 曜 is its use in the name of every weekday, so people think of 火曜日 as being segmented 火-曜日, the weekday ("曜日", etymologically spurious) of fire (火).

I don't know the modern Japanese word for Mars, but in Chinese it's 火星, not 火曜.
> being ruled by a fascist supporter and/or supported by fascist sympathizers has an enormous impact on the quality of life

Of course. It's the "about to be ruled by" part that's the cheap-ish rhetoric, as it implies an unsubstantiated imminent threat, not just "some of these guys are really going in the wrong direction".

> having 10 times the chances of dying shot by a stranger makes it 10 times more probable that in US I would be dead instead of alive.

No, it absolutely certainly does not, unless that's the only way you could die. That's really, really basic statistics.

I don't even need to check the statistics to assert that you're much, much more likely to die of causes other than violence, both in (at least the majority of) Europe and in (at least the majority of) the U.S.

If you have a full watermelon, and then take a small slice of the watermelon and somehow multiply the slice by ten, you don't have ten watermelons as a result.

> Would you trade it for a better salary or a larger household, knowing that it's 10 times more probable that it could happen?

Depends on what it's 10 times probable than, and what my other circumstances were. I might not want to live in the most dangerous city, and certainly not in its most dangerous areas, but that doesn't mean I wouldn't want to live in the entire country. In any of those cases, I'd probably be much more likely to die of other causes than because of being shot; it's certainly that way outside of the most dangerous places. But what I want to do is not really the point.

> 366 of the deaths in the past seven years

I'm apparently past my paywall-free articles at nytimes.com, so I'll have to make some assumptions here. 366 deaths in seven years means ~50 deaths per year. That's, of course, an astoundingly large number for a modern western country, which typically see very few of these kinds of incidents. But if that's for the entire U.S. which has ~330 million people, that means an approximately one in a million chance of getting killed in a mass shooting per year.

[edit: and of course I botched the maths -- it's more like one in ten million per year -- but the point still stands]

The numbers would make me question what's going on. The risk of violence might also make me not want to live in the most dangerous areas. But a one in a million chance of dying would not stop me from wanting to live in a country if I otherwise so desired.

You can't really just argue with numbers without putting them in some kind of a context.
I'm surprised they don't have a bot that check circular references inside Wikipedia.
If being a British Colony was so great, the colonies would still be colonies.
You could still do it with 6 weeks vacation though, with the sort of balance Europeans have come to expect.
1. Probably not in general? Maybe with a vertical <input type="range"> for each item and a lot of server-generated CSS hackery, for small lists?

2. Use ARIA

3. Use position: absolute?

4. Create it with position: absolute/relative and use CSS :hover selector to show it (or see #5 for explicit open/close)

5. Use <details> or a checkbox along with the appropriate CSS
Your argument is a rhetorical diversion away from my comment regarding the crime's of the British empire.

When someone commits a murder do you say. Well what about all the other murderers?

What hypothetical American indigenous tribes may or may not have done is not the subject of this thread.
>accessibility?

HTML is pretty accessible by itself, simply follow the standard and WAI-ARIA.

>popup menus?

https://www.w3schools.com/howto/howto_css_dropdown.asp

>show/hide sidebar?

You can use the checkbox way to handle that: https://codepen.io/Sfate/pen/nLBGr

The rest isn't really possible without JS as far as I know.
I don't think where I work
R&I expenditure numbers are extremely slanted if you count private expenditure as that's mostly tax categories. E.g. hiring a developer doesn't mean that you are doing R&I, its often just the cost of business. But in the statistics especially the big companies will mark anything that isn't sales, support or logistics as R&I as that brings tax benefits.

I would argue the big molochs are bad for economy and society. Apple and Google are proportionally not more innovative than a random small German or French software house, they just have more scale to market/sell/push their products.
The art of Front end Engineering