skysight-inc/HackerNews huggingface dataset:
Fads are tempered by a community of people anchored in a deep understanding of the technology. As talented as many FE engineers are, I can count on one hand the number that I've met that have a deep understanding of things like await/async + Futures, closures, DOM trees, etc. These things are (perhaps unfortunately) required to do FE work, yet the engineers using them don't fully understand them, so they don't know how to discern if helper libraries are actually helpful.

Additionally, I'd argue FE draws more junior people in general, because of the theoretical rapid feedback loop, and the fact that you can "make something that looks cool" with relatively little effort (relative to a BE engineer). These junior people add confusion to the chaos of the community because they don't know what they don't know, so they're cocksure about their opinions. And as long as they've "made something that looks cool", even if the architecture behind it is hot garbage, it buys them cred in the community.

Somewhat related, I've been using Flutter for a recent FE project and I'm in love with it. It's more for webs/mobile applications than websites, but the ergonomics of it feel like a coherent vision. The people maintaining it (Googlers) are excellent, and the Dart library community seems to know what they're doing. Furthermore, the FE design choices are based on Material Design[0], which is backed by (some informal) research by UI and UX professionals, so you don't have to sweat usability quite as much as you would starting from scratch.

0. https://material.io/components?platform=flutter
One of the main uses in PHP/Laravel (probably borrowed from Ruby on Rails) is caching views for Russian doll caching and caching SQL query results:

https://laracasts.com/series/russian-doll-caching-in-laravel (subscription only)

Unfortunately, it looks like they retired their database caching lesson, which was a mistake on their part since it was so good:

https://laracasts.com/discuss/channels/laravel/cache-tutoria... (links to defunct https://laracasts.com/lessons/caching-essentials)

Laracasts are the best tutorials I've ever seen, regardless of language, outside of how php.net/<keyword> search and commenting was structured 20 years ago. They would be the best if they got outside funding to provide all lessons for free.

Anyway, one HTTP request can easily generate 100+ SQL queries under an ORM. Which sounds bad, but is trivially fixable globally without side effects via global "select" query listeners and memoization. I've applied it and seen 7 second responses drop to 100 ms or less simply by associating query strings and responses with Redis via the Cache::remember() function.

I also feel that there's a deeper problem in how web development began as hacking but devolved into application-heavy bike shedding. We have a generation of programmers taught to apply decorators by hand repeatedly, rather than take an aspect-oriented (glorified monkey patching) approach that fixes recurring problems at the framework or language level. I feel that this is mainly due to the loss of macros without runtimes providing alternative ways of overriding methods or even doing basic reflection.

So code today often isn't future-proof (requires indefinite custodianship of conventions) and has side-effect-inducing or conceptually-incorrect changes made in the name of secondary concerns like performance. The antidote to this is to never save state in classes, but instead pipe data through side-effect-free class methods, then profile the code and apply momoization to the 20-% of methods that cost 80+% of execution time.

Also microservices are definitely NOT the way to go for rapid application development or determinism. Or I should say, it's unwise to adopt microservices until there are industry-standard approaches for reverting back to monoliths.
Same on iOS safari, pretty aggravating.
I'm all for the right to die for people suffering painful terminal illnesses, for the simple moral reason that it relieves suffering itself, and the the cause of much of their suffering is directly the result of surviving long enough, that deep into an illness, because they are supported mainly by technology and medical practices that keep us alive in such a terrible state to where we couldn't end it ourselves if we tried.

However, normalizing death as a treatment option for what is essentially mental illness seems like a modern version of the UK's Blair era "Nudge" policies, where now the ultimate result is the state euthenizing people for compassionate reasons, or at least that will be the pretext, and once it's legal and normalized, it's just a matter of how the papers are filed and the numbers are tallied.

Sure, if you are truly suffering, there is absolutely no shortage of death inducing opioids that will give you a very pleasant end. This government has tacitly already prescribed it by freely addicting small towns to the stuff, and doing nothing about the trafficking from our major trading partner causing opioid deaths.

The part that makes me spitting mad is when you look at the kinds of policies made during the pandemic using truly horrific misrepresentations (e.g. "deaths with vs. of", vaers data fudging, counting deaths less than 14-days of a shot as being from covid and not from vax, "nobody made you do it,"-mandates, "pandemic-of-unvaccinated" propaganda, travel bans for people with antibodies, emergencies act used and repealed before the senate could quash it, orders of magnitude inflated childhood covid death rates, tolerance for allied partisan riots, nursing home packing, internal passport systems, geolocation tracking, unrepealed "emergency" stop and search powers - to name just a few), it's fairly clear they are dangerous and utterly mendacious nihilists, and - what can only be described as "WEF-influenced governments" - absolutely cannot be trusted to manage a "compassionate" euthenasia system.

The housing shortage is related to how this government wants to destroy the savings and standard of living in the country as a means to install permanent technocratic rule, and they are doing it by wiping out wealth and opportunity so as to subordinate the milennial and Z generations to this system. Their messaging reduces to, don't worry, you'll like it, and if you don't, you will just have to find a way to, citizen.

This MAID issue is it's own real end of life issue for an aging boomer generation, but conflating it with prescribing death to the poor and mentally ill (for now) is symptomatic of how bad these people are. It's normalizing the power of the state to do this outside the parameters of humane relief of suffering due to terminal illness, and if you will pardon the pun, that should raise a red flag for anyone.
Yes. Captum is a great library and a few of my colleagues have used it with good results in the past. Like you mention, most of the few examples that demonstrate gradient based explanation methods for Huggingface models typically focus on Pytorch models. The example here looks at things from the Tensorflow 2.0/Keras perspective.
One thing to note is that model agnostic SHAP can be resource intensive to compute , especially compared to gradient methods that require a single pass through the model for a datapoint.
It also has to do with the low entry level. The same happened to PHP. Inexperienced programmers can easily create nice things that look great on the outside.

Libs like React and Vue are stable enough but when you throw in a lot of other dependencies it is always the question how experienced the creators were. And when unstable libs become popular bugs and security issues are exposed, pull requests are created and before you know it a next version is launched that is not backwards compatible.
There is a noninvasive embryo screening method which involves sequencing of culture medium: https://www.pnas.org/doi/10.1073/pnas.1613294113

Thus the risk is avoidable.
Hinkley Point B owner says it will not extend life of nuclear plant
While I think it's a natural evolution to the MPC line and MPCs now are probably the best standalone midi workstations to exist on the market right now (probably ever?), I still think that they lack the visceral feel of the prior generations. Maybe it's just that I'm so used to using a computer for making music that the MPC doesn't feel like stepping away from it to something standalone. Maybe the large touch screen that you have to occasionally use on the MPCs and can't ignore makes it seem that way. Then again, I suppose if you're someone that's been using MPCs since the 90s and you just gradually progressed through the newer and better iterations it feels a bit less jarring than to someone who didn't.

I don't really know what to tell you about the SP line, though. You are just listing features and how they don't perfectly map to the powerful previous generations MPC. I get that it's not the same or that it has or will ever have any sort of feature parity to even the old MPCs. I still think it's closer right now than the current MPCs, which have endless options and features and power that make them basically just an underpowered laptop with feature updates that come out on the whim of Akai rather than you buying a new VST or DAW for your computer. Admittedly Akai's firmware updates have been amazing and transformative for the MPCs in how you work with them, but I digress. It's definitely too much, while the SP is maybe not enough, but for creative work and as an instrument, the SP is much more inspiring.
Cynical me thinks the simplest explanation is it was all just a big show they put on. Similar to when my aunt went to a fortune teller who guessed she had six kids. The fortune teller was probably just well informed about the local environment.

If you're running an Oracle business, your customers are already locked in. It's a long pilgrimage to get there, so you've probably got something important to ask about. The sales people will know roughly what kind of relational data is precious to you, and your branding makes Oracle a natural choice, despite what the techies of the time might say (it's expensive! There's a free and open source that we can get high at!). Once they're there, you keep the magic going by offering associated services. Maybe a bit if consulting on what the old lady said. Of course the consulting will always include coming back for more prophesies.

Most of the business is knowing what kinds of things people want to hear, and feeding back a few things you found. After all it's only once a month there's a seance, the rest of the time can be spent hanging around finding out what the customers want.
Yes! We just need to get our users to visit the website in order of their user_id, at their assigned time, and then we wouldn't have these random access patterns. /s

Unfortunately, reality.
You mean governments worldwide have had a change of heart since "Social Media" has become a thing, and have changed for the better?

Now pull the other one.
My pet hypothesis for years has been that developers always vastly underestimate the difficulty of doing a UI framework or environment. They think it'll just be a matter of painting widgets and presenting data. As a result they under-build the foundation. The insufficient structure is then released out to the world for everyone else to build upon.

Once people realize the soul devouring chthonic difficulty of doing good modern UI, they've already built on a shit foundation and been forced to realize the full system with a heap of ugly hacks and workarounds.

Then someone thinks "wow, this is way too complex! All I need is a simple UI." Then history repeats.

You can see this with immediate mode clean simple GUI library of the week. They all stagnate after getting all the basics working, and there's a reason for this.

A good mature modern UI is at least on par with a high-end game engine like Unity in terms of feature surface area and difficulty. In some ways it's worse because while the breadth and size of the problem domain is similar the problems you encounter in a game engine are probably a lot more fun. UI is a hell of incredibly hairy state management and a really long tail of edge cases.
The American who honors the memory of 200k fallen war heroes
Outbreak Investigation of Hepatitis a Virus: Strawberries (May 2022) – FDA
Ask HN: How often are you operating at 100% productivity/motivation?
Sometimes I just don't feel like working. Other times I am in flow at 100% and feel like if I didn't have to sleep or have meetings I could get everything on my plate finished.

How do others feel? Are you mostly working at your optimal productivity / motivation level? Has it changed as you got older?

Maybe it's just me but there are days I get nothing done, and when you have daily stand-ups you simply cannot say that so you just make shit up or say you were swamped in busy work.

I'm wondering if there is a better philosophy to managing people with this in mind, although I am finding that humans need deadlines and external pressure in some form or nothing gets done.
Or more probably you have to understand '80s pump&dumps, ponzis and securities frauds.
Legality indeed varies, but even if it's illegal hardware vendors easily away with it, and will still bill you the repairs if they want to repair it at all.
That’s exactly the kind of meaningless and inflated number I was talking about. Notice how they exclude hydroelectric dams.

Existing hydroelectric dams currently store vastly more energy than the average pumped hydro facility and they can easily be adapted to add additional turbines for relatively minimal costs. Collectively North American dams are storing at a minimum several days of total grid output and theoretically much more depending on how you do the calculation.

Adding turbines doesn’t increase annual production, but it does increase flexibility as it makes minimal difference to discharge 1x water for 24 hours or 5x water for 4 hours and the rest over the other 20. Several dams have already been retrofitted like that as peaking power plants are simply vastly more valuable per kWh. It’s even better for the environment as rivers naturally have significant variability which is normally smoothed out by dams.

PS: Rarely mentioned in those kind of analysis is how sensitive the required storage number is to the exact mix and oversupply of wind/solar. A grid with 1.001x average annual demand looks very different than one with say 1.1 or even 2x.
While it's good that the CHIPS act is being passed, it's far too modest of a bill considering how important semiconductors are to the US. Just compare it to the South Korean $450Bn bill[1]. In the 80's enormous foreign subsidization of commercial ship building by South Korea, Japan, and others, saw the near total loss of that key industry in America. Semiconductors must not be allowed to suffer a similar fate.

[1]: https://www.bloomberg.com/news/articles/2021-05-13/korea-unv...
[1 Non paywalled]: https://archive.ph/9Gs8q
Obviously measuring is the only way to optimize. Goodbye.
I thought VDom is old school since Svelte and such?

https://news.ycombinator.com/item?id=19950253
>It’s irresponsible, if not immoral, to design a language without a borrow checker in 2022.

The rustacean cries out in pain as it pinches you.
I don't think he's saying that the repair will teach you the first principles of phone design. It's that by taking the step of actually opening the device, you significantly lower the hurdle to any next steps.
If you started with Vue two years ago, you had to learn Vue 3 shortly after that. With a new Vuex. Which has been dropped since in favor of Pinia. Oh, Vite has been developed since, so you may want to add this to your stack, because it makes compiling during development so much faster. Also, be aware of all the breaking changes that Webpack 5 has introduced.

I hope front end development will be more stable in future, but the last two years where full of pretty major changes.
A lot of it is that UI programming is just difficult and inherently complex.

Expectations of users are very high and always shifting. Browsers/consumer OSes are constantly moving targets. Mistakes and bugs, even small ones, stand out in a glaring way, so there’s low forgiveness. There are more code paths and they’re harder to test.

All that means that unless you want to miss your deadline by a year or leave a bad impression on users, you will need a lot of libraries!

Backend/systems specialists always underestimate how hard UI programming is. Then they try their hand at frontend and quickly run into a wall. They find they either need to build something clunky that users aren’t impressed by or else spend a lot of time learning new tools and paradigms (and yes, installing lots of dependencies /shiver). This is a blow to the ego, so it’s better to criticize the language, the culture, the “churn”... anything to avoid admitting the pixel pushers are solving seriously tough problems too :)
This is why my near two year old is unaware that there is an uncountable number of hours of video made specifically to appeal to his age group. I know he'll find out sooner or later, and that it can even be called up on demand if your mommy is nice enough, but I want to keep those little brain cells engaged primarily with the quiet, physical world as long as possible.
How you would suggest to demonstrate visually that there are no trade-offs?

The tradeoff the way I see it - one needs to implement 200 Redis commands from scratch. Besides, I think DF has a marginally higher 50th percentile latency. Say, if Redis has 0.3ms for 50th percentile, DF can have 0.4ms because it uses message passing for inter-thread communication. 99th percentiles are better in DF for the same throughput because DF uses more cpu power which reduces variance under load.

Re-durability - what durability is offerred by Redis? AOF ? We will provide similar durability guarantees with better performance than AOF. We already provide snapshotting that can be 30-50 faster than of Redis.
In this case the spelling nazis had rightfully pointed to the correct spelling, because the wrong spelling is not a problem of style or preferences, but it causes a confusion between two different chemical substances, with very different properties and applications.

"silicon" is the chemical element number 14, and this name, which is used in the English-speaking countries, was coined by someone who believed that it is a good idea for it to rhyme with "carbon" (actually a bad idea in my opinion)

"silicone" is the generic name for a class of plastics, i.e. the polymers with a poly-siloxane structure. This name was coined by someone who believed that it is a good idea for it to rhyme with "acetone", because he erroneously believed that these polymers have a structure similar to ketones.
Google search on SSDB - "Saskatchewan Sheep Development Board" ;) Well to its credit it did find and put proper one to the front page as well.
The latest tube maps include the time it takes to walk along a line between stations in the central zones. It's not a to-scale map, but it gives some useful hints.

https://tfl.gov.uk/maps/track/tube

The problem with making the London map topographic and to scale is that the northwest extension of the Metropolitan line stretches far out into the countryside. A to-scale map would have to shrink the central area - the most useful part of the map - which would make it cluttered and hard to read.

The zone system on the map provides useful hints about absolute distance without being perfectly to-scale.

That aside, most people using a metro system need to know how long it will take to get somewhere on the system more than they need to know exactly where they are.

TFL's app includes journey time estimates.
Ah, that reminds me of my good old Westinghouse Radiohub [1]. When the internet goes away, you probably won't be able to freeze stuff no more.

1: https://news.ycombinator.com/item?id=22083759
This looks like three squashed commits based on the formatting of the commit message. I guess from a PR.

The “src/lread.c (readevalloop)” commit could in turn be based on many smaller commits.
So, I haven't worked in semiconductors since the mid-noughties, so keep that in mind. However, essentially every company in semiconductors in the 60's and 70's ended up with a Superfund site in Silicon Valley (back when the "Silicon" referred to actual chip manufacturing, not software). Fabs built in the 80's and 90's were much different in regards to how toxic chemicals were handled, and I believe have continued to improve.

Some of this improvement came naturally, as the requirement for cleaner and cleaner manufacturing environment for the wafers themselves (to keep particulate contamination from lowering yield) meant that the chemicals were kept in enclosed systems, thus easier to keep from leaking out.

Some of this came about because, from what I was told by "old timers", in the 60's and 70's part of the problem was that fabs were not thought of as being very dangerous. This sounds incredible now, but the risks people thought of from manufacturing then were those present in steel mills, coal mines, auto factories, etc. Big heavy things and molten steel and roofs that can collapse on you; physically obvious risks. It took some time to realize that semiconductor fabs were just as dangerous; no doubt longer than it should have, but the realization did arrive in time.

I left the semiconductor industry because it was outsourcing, not because of concerns for my safety; in new fabs, there was a great emphasis on safety and the environmental impact (which no doubt raised costs relative to some of the other places that manufacturing shifted to).
Twelve quick tips for software design
I too have found programming languages on the internet that I don't like.

I have survived through my awesome power of not having to use them.
This is a terrible argument. The costs associated with building wide, rather than building tall are hidden in future taxes and not disclosed to the homebuyer. Pretending there's some 'all costs' calculator over the useful life of the asset which is presented to homebuyers is incorrect.

Not only that, but tax funds are typically funneled from denser, more sensibly planned areas of cities to the more well-off sprawled suburbs. So people who aren't even involved in the process of participating in the market for sprawl built houses will pay for the resultant externalities created by the need for maintenance.
Yes, I think about that every day. Maybe homelessness is a standing protest against late stage capitalism, questioning the very idea that we should allocate nice places to live based on productivity and that wealth is a good proxy for productivity.

And maybe homeless encampments are the absolute worst place for someone struggling with mental health or drug issues, heightening the risk of every injury and surrounding them with enablers.
I know that magic is poo-pooed and all, but, have you considered that answer as well? Or perhaps they weren't hallucinations, and instead divinations. Calling what the Oracle of Delphi had "hallucinations" puts a bad spin on it from the onset.

Or lets not get hung up with the word "magic". Lets call it a 5th type of energy. Mechanical detection don't work, but a number of humans can feel it. Hard to measure for sure. Some people are more connected to that energy than others. But again, being human-centric at this time makes verification hard/impossible.

What I would adore is a theorem to connect that energy to the 4 other types of energy (EM, strong, weak, gravity). And then, we can start scientifically describing all of those "weird" human issues of stuff we just shouldn't know (I'm thinking of: past life recollections, feeling someone staring at you, parental intuitions that something's wrong with a child, etc).