skysight-inc/HackerNews huggingface dataset:
Yes, there's an active albeit small community there.

I don't think I'd recommend it over TS for a new project by default, unless the person has some specific pain points with TS that Flow would fix. But Flow does still have some neat features - exact types, nominal types, explicit strict variance rules etc. - and performance benefits in large projects that could make one choose it over TS. And they have been streadily improving stuff like editor support, even though admittedly it's still a long long way behind TS.
Would you work for a cigarette company?
As a warning, this would not be good for colorblind people (such as myself).

The "Hello, Hacker News!" Hash's middle ring has half it's ring that looks identical to me, and unless I looked carefully, that entire ring looked the same to me.
They will have to find an equilibrium between the optimal number of old movies to cancel, or retain to shove ads in.
Oh, that device I mentioned was like seven years ago. I'm sure that at least the most glaring issues have been fixed since.

As for Apple, fanboy or not, I didn't buy an Apple Watch until the fourth one came out. Not waterproof? No GPS? Get outta here with your fashion watch.
Nova 1200 would be easier. Just glass panel painted mostly black and regular off-the-shelf switches. Bigger problem is the menacing glow of blinkenlichts. Leds will never do.
In particular, fake computer-generated bokeh turned out to be good enough for a lot of users. You get much better composed pictures without any additional hardware. A photographer won't be fooled, but Instragram and your scrapbook probably will be.
I really really really wish RPi would come out with a real HQ camera with at least an APS-C if not 36x24mm sensor. This dinky little IMX477 sensor is MQ, not HQ.

The uses would be endless, ranging from astrophotography to real professional-quality shots with homemade, scriptable cameras; shots synced with high-speed motion; a whole new era of homemade SLRs and mirrorless cameras that are actually competent; lots of things I can think of.
The prions are not involved in the formation of new proteins, so it's very^100 difficult that they can evolve to create more efficient versions. [I try to not use "impossible" because life finds a way ...]

Virus instead use their own material as the original to make copies, so any new good or bad variation will be copied in the offspring, and they can evolve.
As to what works in practice, most cryptocurrency exchange accounts, which are prime hacking targets as you can steal large amounts of money irreversibly work as follows:

Enter email@address.com and easypassword1

You are then asked for Google Authenticator code, which is a six digit code based on a secret key and the time of day.

It generally works quite well though it's a pain if you lose your Authenticator key (stored the in a phone app usually)
The lynch pin FDM patent was 5,121,329 which expired in 2009; there were similar later patents in the space around SLA printing that expired in the five years following that. There's been plenty of analysis both from industry and academia that it was indeed holding back the proliferation of 3D printing technology.

Being in a adjacent field of other robotic control that utilized 3d printing for our own prototyping before and after the proliferation I can also confirm the patent licensing being a major impediment to proliferation of the technology. We had high enough margins that we could spend $100k on a 3d printer before 2009. But the field has been revolutionized since then from the democratization and even our own processes changed heavily once we could have a bank of printers rather than just one. Sort of like the change of a a company sharing a mainframe with a guy dedicated to keeping it going versus ubiquitous microcomputers.
Yeah I'm not a huge fan of the way the article is written. The concerns are undoubtedly real, but the pearl-clutchy tone and the endless barrage of asides and pop culture references make me doubt the author's conclusions.
National defense so we can defend ourselves from opponents that the US created, or act as an imperial arm for American interests?

Seem to recall some very agitated US commentators bashing Canada when we chose not to enter the second war in Iraq. How's that working out for you, BTW?
llhttp different from the original http-parser. It has lesser bugs because it's written in Typescript which transpiled to C and it's faster than the original http-parser
I've been going through Roald Dahl with my 5-year-old and it's been delightful. It has kind of made me want to do my own audiobook recording of Charlie and the Chocolate Factory. James and the Giant Peach was a hit, of course, as was Matilda. We're doing The Witches right now, which I had never read as a kid. It's kind of at the edge of what my son finds too scary, though.

My son has started to notice that all of Dahl's heroes have terrible family lives in some way, and he's questioned why it's necessary. I think he starts to worry that it might happen to him. I've tried to explain to him that, because the stories aren't real (which is a concept he's comfortable with already), it's a useful shortcut for a writer to make us sympathetic to them. I think he gets it.
Here goes me opening PDFs in Firefox.
The development velocity you could get with Rails was never constrained by the interpreter speed. That was part of the point, you could get a perfectly respectable project stood up on ruby 1.8.
British coronavirus variant may have come from dogs, researchers say
Great Job.
What does 'developer experience' entail to you, and how does your company express this for prospective and new hires?
eh, that's not really the case in a lot of developer jobs these days. A lot of agile/scrum adoption/bastardization has meant that all work done has to be decided by the team and pretty much every piece of work has to be approved by a product manager. This can often lead to some demoralising meetings where you can either lie about the effort/risk/goal or you can give a true value estimate that gets shot down. If you lie, you can end up spending your own free time working on that refactor or documentation etc. For most devs working on a codebase, its not theirs, and they don't determine what has priority.

In reality, for a lot of people, if you start refactoring the codebase while waiting for a new task you are likely to break something and its just not worth the hassle for the developer or the company.

Learning new tools is always great ofc but it can be very hard to find the motivation in such a role, where unless you are a senior developer, you probably won't have much say on adoption, and you will likley just develop a half baked understanding of a new library that you will never get to use in production. Its much better to have some real free time where you can focus on your own projects and learn that way.

So in short, maybe it should never be the case that devs are in that position, but it often is. Especially for devs with less experience
Nuclear Reactor Wall Charts – 1956-1998
>As a Java developer, you may be wondering if we're trying to turn numbers into objects (we are not).

Funny that he answered that so early on, my line of thought coming from C# was "Are they trying to turn a value type into a reference type? I thought Rust doesn't have quite the same distinction so is this some weird way of working with the heap instead of the stack?"
I think it's a cost-benefit balance. Anecdotal, but when you see things bleached by the sun, they're pretty white -- not ultra #FFFFFF white, but pretty white. My roof is done with a modern membrane, which is very light gray in appearance, with tiny white stones embedded in it.

I imagine you can take a roof like that (say 80% albedo) vs a high-tech ultra-white (99.9% albedo), and the 80% roof won't degrade in reflectiveness because the sun naturally bleaches things to that level -- but the wear and tear of high-tech roof will bring it down to about the same.

Just musing here, no solid evidence to support this.
Plentiful of rain need not equal plentiful of water around.

There are states in India for example that get 2000+ mm of rain every year and still have severe water shortages.
Yes. If you design the ISA carefully, you can create a microarchitecture for it that is much more performant and simultaneously more energy efficient. This is one of the reasons that Intel struggles to compete with the Apple M1. The latter does not have baggage of backward-compatibility that Intel is forced to support. For specific use cases, you can get even more performance by tailoring the ISA to the application. E.g. many neural processors fall into this category, their SIMD instruction sets are carefully chosen to be most effective for the sort of calculations you will need to do when you build a neural network.
I think you underestimate people inventiveness when it comes to circumventing these types of systems.

People will either keep trying new strategies to embed counters in their passwords (maybe increment a letter, or multiple a number by 10), or they’ll just write the password on a post-it they keep on their laptop.

Either way you’ve now got a whole load of complicated code that makes it harder to people to create genuinely strong and memorable passwords, and no additional security.
> Because password hashing makes it impossible to retrieve the original password, there is no way to guard against people just using a basepassword and appending some type of counter to it.

Almost all the implementations require the old password when you change it to the new password, so it's trivial to check if they are too similar.

def changePassword(login, cleartextOld, cleartextNew):
if too_similar(cleartextOld, cleartextNew):
return new Error("too similar")
hashOld = hash(cleartextOld)
hashNew = hash(cleartextNew)
if authorized(login, hashOld):
setPassword(login, hashNew)
return new Ok();

If you're afraid of sending cleartext passwords - do the too_similar check on the client side. The users that can write their own client to bypass client-side checks are exactly the users you don't need to worry about.
Suggestion: shave off two bits, and switch between the variants in the "A bit of fun" section: https://francoisbest.com/posts/2021/hashvatars#a-bit-of-fun
I don't mind the aesthetic of street art (I'm not a particularly pretentious person when it comes to art of any kind), but I do mind vandalism i.e. changing the aesthetic of property you don't own without permission (whether the property is public or private). I'm sure someone will chime in with some treatise against private property and that's narrowly all well and good if you manage to democratically change the law of the land to abolish the right to private property to achieve your graffiti ends, but I don't see anything good or honorable or noble about circumventing the democratic process (although in fairness it's hardly more honorable to apply the democratic process to the restriction of others' rights).
"but the real cost of an upfront hire is my time, not money"

The most arduous hiring processes are often little more than an illusion of selection, yielding a process that is more the rolling of dice. Most hiring processes hire based upon interview skills that have extraordinarily little correlation with job performance.

Google has such a famous interview process that everyone tries to clone it. For that they get employees with an average tenure of 3.2 years, made worse that internal project-to-project migration is endemic. They have a tiny core of institutional knowledge, and then a passing army of travelers.

This industry would be far more robust if it hired quickly and fired fast, because the only way you know how someone will do in the role/team/org is by actually having them in the role/team/org. Everything else is just loose proxies that do little. Iterate through people and just punt out the ones that don't work. That shouldn't be a big deal.
I think the solution needs to live on both fronts.

IMO the boring bits are boring because there's no time spent to make them not boring.

On all layers of society there are tasks that are under-tooled and under-organized and if you make them worth doing, people will enjoy doing them 24/7.
I was thinking about this yesterday while looking for resources on building a board to read data from a modern sensor from something like an a7 (turns out its way over my head). The issue you’d run into with the pi hq camera module assuming you can get the focal plane right and everything to fit is that the sensor is way smaller than 35 film so you’ll have a rather large crop factor.
Didn’t realize that - awesome to know. Looking forward to seeing their future announcements.
> About the only thing Twitter censored was threats of violence or rape, election misinformation, or extremely blatant racism.

Twitter blocked the NYPost because they didn't approve of their entirely factual journalism.
I didn't think of that. My musical experience is on piano and voice (neither of which has a preference for sharp or flat keys) and I've played around with guitar a bit (which prefers sharp keys in standard tuning) so I tend to forget that some people like flat keys.
“If you don’t take money from companies you have a conflict of interest with, it’s dangerous! Think of the children!”
I’m sorry but I may have exaggerated for humorous effect, but your line of reasoning I reject outright.

There are ways to do this effectually. This is not that way.
> usually those integer multiples will be present as well

"usually", under what probability model? A random 3d or 2d shape will have zero harmonic partials with probability 1. What is hard to achieve is having even a few harmonic partials. A rectangular wooden piece is painstakingly carved to have a couple of harmonic partials, in order to become a xylophone or marimba bar.
DeepMind 'Podracer' TPU-Based Reinforcement Learning Frameworks
I've been using this the last few weeks on a synthesizer side project and it's been absolutely fantastic. A well designed API and easy to customise, excellent docs and sane defaults. Bravo!

https://dl.dropbox.com/s/kxlzlqypn0nz8bw/Screenshot%202021-0...
Clubhouse is by design inaccessible to be fair
PDFs are definitely not Turing complete. [0]

[0] https://www.cs.odu.edu/~zeil/cs390/latest/Public/turing-comp...
I am very much a self-sufficient, independent, think-for-yourself kind of person that scowls at stories like this Peloton one (and the stove, and the boiler) where I tend to think "don't touch the stove".

Your comment here is making me re-evaluate that, specifically the Whitehead quote. I think we can strive for both, but I never realized I was biased one way or the other until it was pointed out this way. Thanks!
Try it in a video player. They generally play video a lot better than a browser. mpv + youtube-dl can handle Twitch.
What the FLoC?
And it's time we all stopped being that dependent on the US, considering how unreliable and untrustworthy they are.
There is a kit for an Altair replica which uses simpler switches. https://adwaterandstir.com/altair/
Ok so turn the safe generators on then

Until then I feel my point stands
The first question I have about this is the evidence. If the police are the only ones giving evidence/testimony, then their findings are suspect, as they have the best incentive in the world to lie and fabricate evidence. And it's not just a theory, as there is actually body cam footage showing police planting evidence and lying.

The second question I have is, why are these incidents happening? What is causing these attacks, and why were they armed or felt the need to use their arms? Especially if they keep happening predominantly to black people? There's quite a bit of evidence that when a white person is armed and attacks the police, the police give the guy a break. Whereas when it's a black person, they're more likely to antagonize the suspect and then shoot first.
Okay. I suggest you to try Clang's Cling. It's the JIT version of C++ and everything is instant.

https://root.cern/cling/
As others have suggested, build some small projects. Pick anything in your life or work that you commonly return to Google to find answer for or collect information. Automate it or make it better.

You may want to pick a platform/language that has a low-level intro course that walks you through a small project.

Let the challenges you encounter lead you to finding solutions and building your skills.
Thanks Zach! I'm Ishan, the guy who made this thing lol
https://github.com/quackduck
I can confirm the sentiments from Humio's blogpost. I am leading a frontend team at GWI creating the platform: https://www.globalwebindex.com/platform

Complex UIs are a breeze in Elm. We have 140k lines of code of Elm so far on that one product (there are also internal admin interfaces that I don't count here) and I can't imagine writing and maintaining something like that in React+TypeScript or some other JS UI library. (Mentioning React because I have experience with it. Dunno about Vue/Svelte/others.)

Wrt. hiring, we are experiencing the Python paradox: the last time I posted a job in the #jobs channel in the Elm Slack, I had about 8 solid applicants reply in the matter of hours/days. From my perspective, people are absolutely eager to work with Elm full-time and we don't have the problem of having to sift through totally junior/beginner candidates.

Re the Elm development model: I tolerate the fact that PRs don't get picked up immediately and that work gets done in batches. It is sometimes a bit frustrating and contrary to default expectations from other open-source projects, but it's not the end of the world. In the ~3 years of working on our app I haven't found a situation where we'd be blocked without some kind of escape hatch (typically ports and WebComponents).

Re community: I can again only sing praise about it. Yeah it might be protective of the best practices and idioms, but the folks are incredibly helpful. If you are willing to listen, there will be enough advice to save you from digging yourself into a hole (native JS modules etc.) and writing a heated "Elm sucks" article later.

Overall, Elm is both what I write small experiments and spikes in, and large production-ready applications. Not to mention side-projects. 10/10 would start an Elm project again :)
How is that a counter argument to anything? The need to support multiple APIs is not free. It's a tax on everything else.
pdf documents are usually not created by web developers but by other people and then uploaded to the website. all it takes is a way to have someones computer infect a pdf with malicious js code, which, (if such an infection is possible) is way more likely to slip through than an attacker embedding malicious js into the website itself.
I think it is just due to C# being a play on C++ (the # could be seen as ++ just rearranged to overlap). No doubt the positive connotations of "sharp" also played a role. Cb or C-flat neither looks or sound cool! That said, MS did have en experimental language called C-flat, but it was not intended for general purpose use (if I remember correctly), so the name might have been chosen as a joke.

F# is in turn named after C#, as it is the functional equivalent to C# in the framework.
This is a reasonable question. I hope you are able to find an answer but I don’t have one for you. I’d start by reading the “you’re wrong about...” pair of posts covering the First Amendment [1] and Section 230 [2] as they are good primers, even if you aren’t “wrong”. I’d also read the text of Section 230 itself [3] and then read up on safe harbor in general [4]. That should get you going in the right direction.

[1]: https://www.popehat.com/2016/06/11/hello-youve-been-referred...

[2]: https://www.techdirt.com/articles/20200531/23325444617/hello...

[3]: https://www.law.cornell.edu/uscode/text/47/230

[4]: https://en.m.wikipedia.org/wiki/Safe_harbor_(law)
I totally agree with all of this! Especially "be your first code reviewer" which is something I find very helpful. Seeing my own code in the same interface that my reviewer will use helps me get a different perspective and spot some things early.

If anyone here is looking to improve their code review workflow on GitHub I've been working on a new tool that I think is much, much better than the standard GitHub UI for small teams doing reviews.

Email me at sam [at] habosa [dot] com if you're interested.
If you want to go further down the rabbit hole of symmetrical scales, checkout Olivier Messiaen's modes of limited transposition https://en.wikipedia.org/wiki/Mode_of_limited_transposition. For a given set of pitches within an octave there are a limited number of times those pitches can be transposed before you wind up with the same set of pitches. And the modes in that scale must also be fewer in number than the number of pitches in the scale, meaning at least two modes of the scale must have the same interval spelling. The simplest example is the whole tone scale. Up a half step I get the same set of pitches, another half step and I get the same pitches I started with, so it is 'limited' to one transposition. And there is only one mode of the whole tone scale, since no matter where I start I always have the same set of intervals.
If we're really pushing this analogy however, then you would expect the teacher to have a much higher accident rate than the average driver because you're claiming the teacher only does the hard stuff, or, in the very least, misses out on the majority of the easy stuff (assuming, for comparability, that the teacher is an average competence driver).

Specifically, if you're claiming only 99/100 miles are easy and have no chance of crashes, then if a human only drives for the 1/100 miles that are hard, they should have a 100x higher crash rate than the human that drives all 100. They should probably have an even worse crash rate because of the switching cost of suddenly taking control, unless you want to make the weird argument that suddenly taking control of an autopilot car is safer.

The tesla report says autopilot experiences a crash every 4 million miles. With autopilot disengaged, it's every 2 million miles. The baseline national average is every 0.5 million miles.

I can't find the perfect statistics, but one study suggest uneducated people are 4x more likely to die in a car crash, so let's give some generous rounding and say, normalized to wealth, tesla drivers not actively using autopilot are at comparable levels to the average driver (1 per 2 million miles).

Unless telsa drivers are phenomenal emergency handlers, its difficult to explain how the non-autopilot crash rate could be so low, while also claiming tesla is hiding the true crash rate of its autopilot features by pushing difficult miles to human drivers, because the human drivers are receiving normal crash rates on what you claim is a much more difficult set of miles.

Its possible (probable) that the autopilot would experience a higher crash rate if it were not allowed to call in a human. But to ask generally if autopilot is reducing the total number of accidents that the drivers would experience otherwise, I'd say 'probably'.
Coincidentally Judges vehemently dont care about police conduct.
This wouldn't work either. It would just make users bounce between 2 passwords: foo100 -> bar200 -> foo101 -> bar201 -> foo102, etc.
So much this, I find it frustrating that we do this at my workplace.