skysight-inc/HackerNews huggingface dataset:
Sctp over UDP is a thing and still hasn't gained much general public use over the net... Sadly!
The point of Redux (or any state library) is to share state between components. Unless you're doing something like putting the state for a child in the data- attributes of a parent somewhere further up the tree I don't think element.dataset does the same job at all. element.dataset is much closer to something like using useState.
There's an interesting question of statecraft here: when does misinformation like this actually become a casus belli? If you discourage people from getting a vaccine during a pandemic, you're effectively killing civilians at one remove.
Yeh, sure - but two things come out of this "dominance". One: the enormous quantity of support online. Have a problem with littleknownbutcoolcms? You're stuffed. Have a problem with WP? 10 gazillion people have written about it. Then two: clients want it because it's familiar, they've used it before, they've got another site using it, etc etc.

So yeh, I take your point, but it's the peripheral stuff that makes this important IMO.
It's probably because invoking DOM APIs is terribly slow and if you're accessing those fields with any frequency you're better off using a JS object.
The Theory of Steinitz
Preschool’s ‘Sleeper’ Effect on Later Life
In the Introduction:

> IE6 had an interesting HTML parser. It did not necessarily produce a tree; rather it would produce a graph, to more faithfully preserve author intent. Ill-formed markup, e.g., <em><p></em></p>, would result in an ill-formed DOM. This could cause scripts to go into infinite loops by just trying to iterate over the DOM.

Huh, didn’t know that. It’s the sort of thing that makes me wonder, “hmm, was that what was happening that time all those years ago?”

> The problem is I now have to determine which of these four options to make the other three browsers implement (that is, which do I put in the spec). What do you think is the most likely to be accepted by the others? As a reminder, the options are incestual elements that can be their own uncles, elements who have secret lives in the rendering engine, elements that change their mind about who their parents are half-way through their childhood, and quantum elements whose parents change depending on whether you observe their birth or not.

That whole section is great reading, showing just a little bit of the madness that preceded the specification of HTML parsing, and how monumental a job it was.
More front-end JavaScript equals more expensive, less backward compatible and less cross-browser compatible.
I'm thinking let's just use something like netty or zmq over a simple ip+icmp interface, socket or not. Instead of having everyone learn some ossified quic kernel api... And since everything will soon move to io_uring let's wrap that thing in high-level APIs.
Unforunately sometimes you just don't have any choice.

Any also unfortunately it can end in less than ideal circumstances: during our move from UK to Croatia 2 boxes went "missing", one I couldn't have cared less about (except for the cost of replacing it), the other box however had irreplaceable items contained within.
> If your React app is too slow/unoptimized, the client will pay the cost, not you

For the client the experience is worse and the cost is higher, so it's definitely a worse solution. SPAs really only make sense when you have a mostly offline application, which is just a very tiny bit of websites out there.
When metrics are you using?
My Two-Day Crash Course in PGFPlots and TikZ
It doesn't allow any user to publish it under another licence but the copyright owner is eligible to do so.
Windows is crap because of, not in spite of, it being used by 95% of people and therefore has to be compatible and backwards compatible with everything.
It's against the law to register a company name containing binary characters
I too am not convinced that Haskell tools have to be replaced by Rust ones. In my eyes Rust's main applicability in this situation would be to replace C/C++ tools.

As for other kinds of bugs, yeah, that's inevitable, but I still prefer to have the memory safety bugs eliminated from the get go so I'd still say it's a worthy sacrifice to walk the road to safe tools one more time just for the memory safety.

So yeah, no need to rewrite tools in already memory safe languages but when it comes to C/C++ tools then yes, we need to rewrite them.
>And where, pray tell, would you find battle tested libraries for flying a drone on Mars?

this isn't magic. Image processing isn't a wholly unknown field when under the influence of Martian gravity.

It's a staggering achievement, and a testament to humankind's ability to wrangle technology, but -- to be frank here -- visual odometry is technology from 1960s era spy planes, not beyond-human voodoo.

Sometimes errors are stupid ones, even if the stupidity is causing problems a zillion miles away on distant unknown frontiers being first-explored by human kind.

tl;dr : This visual odometry problem isn't a space problem, it's a computer science problem -- one that has been encountered by numerous people even here on earth.

The repercussions of such a simple non-space-problem might very well turn into space problems when the craft crashes, however -- and that's a damn shame given that this particular set of problems has been encountered-and-fixed by numerous earthlings over and over again.

super tl;dr : as an only half-informed-participant in this discussion I bet this problem is NIH-syndrome-related, a problem NASA has encountered a lot in the past, a problem that's entirely managerial and very hard to eradicate.
Say we would assume this is a complete real-time system. How would a result be late? It seems like a failure mode that doesn't exist in that domain (given that all guarantees are verified).

Now, I get that this is probably not a real-time system.
This reminds me of Jacques Tati's wonderful film, Mon Oncle (1958). There's a residential house with many similarities to the Nakagin Capsule Tower, and it has so much personality that it's almost a character in itself. Tati gets as much comedy out of its silly, "forward-looking" design as he can, and he contrasts it excellently with an equally ridiculous old house in the centre of the village.
I have to agree. I'm a OG Rails dev looking and constantly compare the productivity of old school SSR sites compared to current complex SPA frameworks. People how tie themselves in knots, the UI interactions are tricky to get right, more places to code, then second guess the frameworks, then try it again. SSR Rails apps just had 3, maybe 4 places to write code - controllers, models, view folders - you can flip back and forth in blinding pace, and get your app up and running really, really quickly. Yes agree there's some places SPA's are really applicable. But watching an app get built that you see no distinct advantage for either end user or dev team makes you wonder.
> https://www.mdpi.com/2073-4441/13/6/849/htm

Wow, I don't know this journal at all, but something terribly odd is going on. Did anyone else read the referee reports [1]? I'd call that scathing. If I ever had those reports come back to me for one of my papers, I wouldn't even try to push the paper through. And I've never used that harsh language myself in my referee reports, even for absolute garbage papers. Look at this:

The article by D. Koutsoyiannis "Rethinking climate, climate change, and their relationship with water" is, quite simply, an opinion or editorial piece and most certainly not original experimental research. At that, it remains grossly incomplete given the current state of knowledge in hydrology, water resources, and their relationships with climate.

First, the author uses this article for an absurd quantity of self-citations.

At any rate: I smell a giant rat!

Edit: I started reading now. This isn't a scientific article. I totally agree with referee 2 above! This is an opinion piece! The author explicitly goes into things like google search results for the words "climate change". What the hell is that supposed to have to do with water's effect on climate change? What absolute garbage! I don't trust anything in this paper.

[1] https://www.mdpi.com/2073-4441/13/6/849/review_report
I like to have two books I'm actively reading at most times, typically one technical-ish book and one nontechnical-ish book. If I need more than two then probably I'm not actually interested enough in one of them and will just stop reading it altogether. I have a lot of books I've read 1% - 50% of and never finished, though coming back to one later isn't totally out of the question, it just goes back from my "reading right now" place to my shelf.
For anyone who's interested I'm currently building a few social features for Spotify at https://volt.fm.

You can already create a profile and share and compare your stats with your friends. You also get a nice page for your playlists (see https://volt.fm/playlist/x48gzqnr2xoctxu1).

I'm now looking for beta testers for the next big feature that lets you share music (and play what's shared with you) right within the Spotify apps. Let me know if you want to join the list.
From the Wikipedia page:

"It is the first graphical query language, using visual tables where the user would enter commands, example elements and conditions. Many graphical front-ends for databases use the ideas from QBE today."

GraphQL seems to borrow the name. Graph [ical] Q [uery] L [anguage]

It could be a pure coincidence, but then, further down:

"GraphQL a QBE for JSON front-ends."

As evidenced by the reply, the parent seems to have predicted correctly that there are people who have no idea the two are related, i.e., one is descended from the other.
It sounds like the alignment error persisted for the remainder of the flight. Depending on the direction of the slip, the visual system would either record motion that wasn’t yet sensed by the IMU or it would record no motion when there was some recorded by the IMU. In both cases the control loops would likely try to correct for the discrepancy. The large control inputs sound a bit like ’integral windup’ in a PID loop where persistent error between desired and observed states are essentially summed over time resulting in larger control input (in the case of a drone this would be helpful for overcoming wind).

Unless they box that in with limits you could easily get to a point where it starts flying like there’s a chimp on the yoke and either crash or saturate the navigation system and have it fall back/fail entirely.
> it seems that they use an inertial measurement unit

They should have just used GPS!

/s
Main problem i have with the article after reading a few graphs is that the author makes it seem like reporters have the most say in what gets reported and how.

That's probably a common belief amongst most people but it's not true.

Owners/publishers/editors decide.

Reporters play a 5% role, if they're extremely influential.
> "You can buy this Jekyll theme..."

Quite why I would spend money on a theme consisting of a white background and unimaginative black text beats me...
visual odometry is a fairly common feature for earth-creations (even toy drones) operating in GPS-denied environments.

We have plenty of faux-mars environments to practice these techniques on. NASA even has their own.

many of the toy indoor-use drones use such techniques for attitude/altitude-hold features when under a roof.
> forced

?? why shouldn't quick be able to use a udp socket?
OpenSSL was deemed as standing the test of time as well. Then Heartbleed happened.

Rewriting in a memory-safe language is worth it. But it shouldn't be a religion, I completely agree on that.
Doctor Alan Green[1] would disagree

[1] https://rapamycintherapy.com/
OpenMPTCPRouter uses shadowsocks [1] and its ss-redir as a kind of a transparent TCP proxy. The advantage of shadowsocks is that it creates separate outgoing TCP connection for each one it proxies, resulting in substantially better performance than SOCKS. And, of course, shadowsocks has MPTCP[2] support.

The problem OpenMPTCPRouter solves is this: you do

curl -O https://somewhere.example.com/largefile.tar.gz

(just a single TCP flow) with 3x50Mbps LTE links, or, better, 80Gbps+40Gbps+30Gbps links and you get a bit less than 150Mbps download speed.

LACP doesn't solve it at all for several reasons.

1) LACP assigns each flow to a single network interface so as to avoid packet reordering

2) Even if you use other bonding mode that can spread the flows over several network interfaces, you'll get low throughput due to the aforementioned reordering and also due to the congestion control, more on that below.

Bonding works well when you have several "equal" links, which is not the case with LTE, where the speed may be quite different across the links and also vary with time.

Last but far from least, there is congestion control mechanism which is present both in QUIC and (MP)TCP, which makes sure the transfer is as fast as possible without harming other connections on the same link(s). This mechanism as it is used in QUIC and plain TCP is not very good at handling multiple aggregated unequal links, so no matter which way you do the aggregation on L2 (bonding) or L3 (things like glorytun), the performance is going to be suboptimal.

What MPTCP does is establishing a separate subflow (think TCP subconnection) for each of the available paths, with its own separate congestion control, and spreading the main flow over multiple subflows byte-by-byte in an optimal way. This gives maximum possible utilization of all of the available links, and prevents the congestion in an optimal way, too.

[1] https://shadowsocks.org/

[2] https://www.multipath-tcp.org/
I think if the goal is to be distinguishable, then only Beam (and maybe Bauhaus) meet that. To me at least, the different marbles are forgettable - if the goal of an avatar is to appear next to a name and help me realise it's the same person who also wrote that other post, or a different comment, or the OP, then they need to be individually distinct enough.

Beam definitely meets that criteria (there's nothing like faces to trigger your brain's distinguishing algorithm), and Bauhaus could do (although I'd add a few more colours into the mix, and maybe not use all of them in every avatar).

The rest really don't.
Posted a detailed explanation slightly above... Glorytun will not work to well with TCP b/c it doesn't provide separate congestion control for each path like MPTCP does.
> Fortunately, JPL knows exactly what went wrong.

> and while the flight uncovered a timing vulnerability that will now have to be addressed, it also confirmed the robustness of the system in multiple ways.

This is so important. Imagine if it would have crashed and damaged communications, that would have been the end of it. This extra step in engineering effort really payed off and gave Ingenuity a second life, and NASA a really good opportunity to learn important lessons and do further debugging.

Also, the article at mars.nasa.gov is a delight to read, with all the information one would like to know being in there. Not to mention that there is even a video for us to see.
According to Wikipedia: The helicopter uses a Qualcomm Snapdragon 801 processor with a Linux operating system.

Considering Qualcomm never releases their kernel sources, I am really worried that NASA might have been forced to use a modified Android system.
It's not crap, it's good enough. Like wordpress is good enough. That's really how life works, subject matter experts look for perfection while the average person is happy with good enough.

Do you buy the best dishwasher or do you buy the good enough one?
In Europe we call that a trial period. In NL I'd expect it to be 2-3 months during which you get normal pay but your employer can let you go any time and you can also cancel any time. In Germany it's apparently more commonly 3-6 months and my contract said the cancelation term was 2 weeks which kind of defeats the purpose. As a Dutchman 6 months seems crazy to me, surely you can see if someone can walk the walk after some weeks, even if you're still onboarding them? And in the unlikely event they managed to hide their lacking skills, you tell them on their performance review, then they either improve or not, and if they don't you can let them go.

Anyway, a trial period like you said seems like a better way to learn whether someone is a good fit for the team (and whether the employer is a good fit for you) as well as technically skilled than trying to do these coding interviews that seem to be overemphasised in the USA (we do them here too, but most of the time they sound very reasonable). It's a bit odd because from what I know of USA law, you're permanently on trial and can be fired with 2 weeks' notice regardless of having an indefinite-term contract. Might as well do two-week trials with anyone that seems promising if it's that easy to let someone go.
OTA updates of the software are a hard requirement if your equipment is at 30 light minutes.

Actually, I remember reading somewhere that more and more they use FPGA chips, allowing to even "change out the CPU" if needed.

http://www.esa.int/Enabling_Support/Space_Engineering_Techno...
I like robohash
The Social Media Stoner
> how the sheer volume of water on the earth is more significant than C02 in terms of greenhouse effects

Where do you see this? I see a long rant about the definition of climate, sprinkled in with some cultural reference and some meaningless discussions about continuous vs discrete sampling (meaningless beyond any first year university course on any scientific topic).
Elitism alert!
According to the article, they're promoting the Russian COVID vaccine.

Also worth noting source.
Their docs intro page is really nice and has a cool gif explanation of row vs column databases. I have never used a column db before and while I kind of knew some of that theory this made it really click for me.

https://clickhouse.tech/docs/en/
Not right in using 'just'. It is not a gotcha as she admits it herself.
Craftcms is excellent.
Dataflow is another alternative that was discussed here: https://news.ycombinator.com/item?id=27145515
Postnick Globally Simplify the Postal Addressing System
You know how some people think that fizzbuzz is useless, and how no one ever uses fizzbuzz in real life? if you google it, you'll read things like "I have never needed to write fizzbuzz in production in my entire career!" or words to that effect.

Of course, fizzbuzz is just checking if you grok some super basic programming concepts like logic, branching, and iteration.

So what if you want to know if someone knows a little bit _more_ than just the basics?
It's the exact same story.

The ability to be able to work with algorithms and puzzle your way out of a problem is kind of important when you're doing some sorts of programming, especially when you need code that scales well (up OR down).

If you're really bad at it, you might write pessimal code that even overheats your regular laptop; but fortunately most people aren't quite that bad. ;-)
Unpopular opinion: I like XML, and I liked self-closing tags as well. It made more sense.

The problem with being lax in what you accept is that it builds immense complexity because you have to deal with a potentially infinite number of special cases.

But this books appears excellent. I read the encoding chapter just now, and it was very engaging and informative, explaining the historical reasons why things are the way they are.

For example, it says that meta tag about character encoding were initially meant to be read by the server so that it could set the proper encoding header... Which they never did... I did not know that!
Your average business owner also wants his site not to be defaced, and security for Wordpress is pretty bad.
> Huh, didn’t know that. It’s the sort of thing that makes me wonder, “hmm, was that what was happening that time all those years ago?”

I think it was always a graph. I remember reading DOM implementation years ago, where a node will have siblings references as well making it graph DS.
I hate WordPress because it has bad DX. But why would I hate CL, it's a simple, useful site with minimal JS.
The other issue is that they fail to categorise their "opponents" arguments into strong and weak claims.

So you often end up with articles arguing against strawmen, where the strawmen is considered to be the only view held by the other side. This isn't really useful.
Show HN: No-Code Platform to start BG/Canary Deployments within 15 mins
Effectiveness is not the only criteria that experts need to evaluate for treatments. Ivermectin is fairly easy to overdose on, and people started self-treating prophylactically because it was easy to find from veterinary supply chains.

The majority of available Ivermectin also contained inactive ingredients that had no been safety tested on humans, again because of its primary veterinary uses.

WHO looked at these facts and data from 16 trials that yielded “very low certainty" of efficacy before recommending against its use, but leaving the door open for further research suggesting additional trials were needed.
Indeed, that's my opinion as well.

Regular languages are closed under a host of more interesting operations than those that have 'grown with the capabilities of our pattern matching engines'.
> Let's not talk about working with dates and times.

Took me years of part-time use to really understand these.

Still waiting for an opportunity to code any non-trivial data structure I meticulously learned about in the past.
I think I would rather just let the logic-writer user use JS directly, and then verify the AST only uses certain language features.

This way you can ensure the code is a subset of JS (the same subset of JSON-Logic), whilst using all the tools and runtimes of JS.
I think this needs to go even further than just disclosing the algorithm and code. The companies and prosecutors should be required to fund independent audits and bug bounty programs. Otherwise, it would be very difficult for resource strapped defendants to do anything with it.
For quick comparison, Wwat's your opinion on fizzbuzz?
Here's my opinion.

There are problems that are shared between monolith and microservice architectures, and there are problems that are different.

For the problems that are different, the ones faced in microservice architectures are considered "harder," and there are fewer battle-tested tools/ecosystems to help deal with those problems (though this second part is rapidly changing).

For the problems that are the same, adopting a microservice architecture will likely force you to solve those problems much earlier. This is dangerous because it takes effort which could be directed to improving your product instead, and you may find yourself solving them in a way which doesn't end up scaling for your organization.

I think they're great, but they require a level of consistent investment in tooling which is not in many organization's DNA.
Almost certainly isn't a single human unless their governance model is atrocious
Oh dear. You're deep in the hole, aren't you?

So established science is corrupt because of grant money. Yet this Demetris Koutsoyiannis who wrote the first article, who is a professor at an established university in Greece and seemingly climbed the completely normal academic ladder, is somehow untainted by the grant money he presumably got along the way?

Which is it? You can't have it both ways.
This is indeed the correct reason. The app is much more usable.

That’s why I switched to teddit.net. It’s much faster, resembles the old Reddit layout and supports dark mode.
Sendmail never stood the test of time and is pretty much abandoned now, replaced with Postfix. Guess in what language Postfix was written...

The idea is that language will not solve poorly designed software, but a developer that knows what he is doing like Wietse did with Postix. And Postfix stood the test of time pretty well, considering how complex it is.